Windows 10: Windows 10 Home - MEMORY_MANAGEMENT BSOD While shutting down

Good evening, everybody

I'm sorry to bother by asking for some help, but i got a weird BSOD just hours ago and i can't figure out what caused it. I tried BlueScreenView from Nirsoft but it gave me a not-so-helpful "ntoskrnl.exe caused it", which after some research i learned it doesn't help that much.
While getting the blue screen and after the "Collecting info" status showed 100% it didn't reboot as it normally does, it simply froze, forcing me to force-shutdown the system by holding the power button.

I searched on the other threads about MEMORY_MANAGEMENT BSOD but similar cases require specific debugging to find the culprit, and as i have no idea and couldn't find any tool that helped yours truly to get from rookie to pro, i decided to ask for help.

I've attached the .zip file and followed the intructions on the "BSOD Post Guide". I'm sorry to bother and if i'm breaking any rule please let me know. I really hope someone can help me.

Thank you in advance!
======
(The same file, two times just in case)
Attachment 81476
Attachment 81476

:)

 

Stopping the 1709 update

is there any way to delay in windows 10 Home? It is a nightmare trying to upgrade to 1709 again and again. Can Microsoft solve this upgrade problems? MEMORY_MANAGEMENT is the only sign in BSOD .

 

Hard drive clicking followed by BSOD error memory_management

My hard drive started to click all of a sudden while I was playing a game, Windows crashed and the BSOD appeared with a memory_management error. I will try to upload a video of the noise.

 

Warning Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Booster 3, please remove them as it may cause trouble.
An easy way would be by using a restore point prior the use.

Please remove all pirated programs and such from your system before we can start troubleshooting.
The Forum rules is meant for everything regarding piracy

• Discussing it,
• Asking for guidance,
• Asking for a crack,
• The use of it,
• Etc.

Code: 127.0.0.1 activation.cloud.techsmith.com127.0.0.1 oscount.techsmith.com 127.0.0.1 65.52.240.48 127.0.0.1 69.167.144.18 127.0.0.1 updater.techsmith.com 127.0.0.1 camtasiatudi.techsmith.com 127.0.0.1 tsccloud.cloudapp.net 127.0.0.1 assets.cloud.techsmith.com[/quote]

 

Please configure Ccleaner at least to not remove dump files:




Let me know how it goes without the DB3 drivers *Smile

 

So far so good, there's the list of the ones removed and manually installed:

• 1x1 11b/g/n Wireless LAN PCI Express Half Mini Card Adapter
• AMD SATA Controller
• Lenovo 720P Cam
• Realtek High Definition Audio
• Realtek PCIE Card Reader
• Realtek PCIe GBE Family Controller
• AMD High Definition Audio Device

I haven't been able to relate those to he BSOD. Could one of them have been the culprit?
I mean, i totally believe you and i'm gonna unistall DB3 and never use it or recommend it ever again, but those drivers have been installed for months, and just 'till now i got the BSOD. None of them has been updated in the past days, not even Windows has updated anything in the past days.

Maybe some weird long-term failure from the drivers or something?
Anyway, i've unchecked Ccleaner so it doesn't screw me ever again.
Thanks for being attentive!

 

The dump didn't blame any particular driver, but it is often being caused by drivers passing data to the wrong memory address.

This situation is often present, but there is always something that changed causing the problem though in most cases the user isn't aware of it or doesn't think about it. You can think of modifications like changing settings in Windows or programs or removing something or anything else.

 

Oh i see...Can't really think of anything right now, but i do appreciate your attention, responses and for explaining that.
Everything seems to be fine right now. Should i mark this as solved or wait a few days first?

 

Preferable wait a few days to see if stability stays this way, after that you can mark this thread as solved *Smile

 

I hope mine is solved by Friday been a week of screwed display

 

Problem seems to be solved
Thank you very much for your assistance!
I'll mark it as solved now