BSOD every startup on desktop after 2-5 minutes - Memory Management

[oldcity]

Hello folks!

Recently I've had a BSOD problem where every time I'm able to login into my desktop, I will be prompted shortly by a BSOD with the error message: MEMORY_MANAGEMENT.

I was able to run the Windows Memory Diagnostics Tool on safe mode, but there were no errors at all from the Diagnostics. Also, I will also get the BSOD even on safe mode as well which means that it has a chance of it being a hardware related issue.

I took out my video card that was very dusty and cleaned it very well with a compressed air can. I cleaned everything else within my pc such that there's no dust clogging anywhere or as much. But the problem of BSOD still persists. I'm not sure if it's a ram issue because I intially had 4 gb of ram from the very beginning and just about half a year ago I upgraded and installed 8 more gigs of ram which came up to a total of 12 gigs of ram. It ran perfectly fine, allowing me to play Fall Out 4 perfectly.

So I'm not sure why it's having memory related problems now after about 4-5 months after installing the 8 gigs of ram that it's suddenly having a BSOD that reports an error saying MEMORY_MANAGEMENT.

I might have an idea that because I recently let my dad to use my computer but however from time to time there will be an automatic windows update after shutting off the computer. Since my dad is impatient or doesn't know so he will shut it down during the process, so would this might be the cause then? If so, how would I go about to fixing it as I have not made any recovery backup at all?

 

[Mark RM]

Similar thread here, the Windows 10 and Windows 8.1 troubleshooting is the same for this

http://www.tomshardware.com/answers/id-1915864/memory-management-error-windows.html

 

[johnbl]

a bugchek in memory management does not have to always be a RAM problem. It means that window detected the wrong data stored in RAM. It could be bad bios memory timings, bad ram, or problems in your virtual memory system related to your pagefile.sys. things like a old SATA driver, bugs in firmware of solid state drives, errors returned from a hard drive. Just to make it more fun, it could be any 3rd party (non microsoft device driver) driver overwriting memory it does not own. I say non microsoft driver simply because microsoft windows update will update their drivers but not OEM drivers. You have to update those. Then there is the class of memory management errors caused by rootkits, viruses and malware attempting to worm into your system.

generally, for this problem you would update your BIOS to get the newest memory timings and clear any memory overclocks, then you would run memtest86 to confirm your memory subsystem is ok.

if it is ok, then you would boot into windows, and update your motherboard drivers and remove any overclocking drivers reboot and see if you still get a bugcheck. if you do, then you would post your memory dump from c:\windows\minidump directory to a cloud server like microsoft one drive, share the files as public and post a link. if I see it i will take a look at it with a windows debugger and see why windows shut down.