Memory_Management BSODs

Associate
Joined
31 Mar 2010
Posts
790
So starting today my PC has started BSODing fairly consistently after running for a few minutes with a Memory_Management error. I ran the windows memory diagnostic and memtest86, both of which found no problems. I reduced the OC on my CPU but that seems to have had no effect. Are there any other tests you can recommend I try?
 
Intel Core i5-2500K
Corsair Hydro H60 (temps are fine)
Asrock Z68 Extreme4 Intel Z68
Corsair XMS3 8GB (2x4GB) DDR3 PC3-12800C9 1600MHz Dual Channel Kit (CMX8GX3M2A1600C9)
Corsair HX 850W Power Supply


Windows 10 currently installed on a Samsung 256GB SSD 840 PRO. I've had the PC since 2011 and have been on win 10 since launch. All I can think of that changed on the PC before the problems is that I installed stata the night before, but I don't see how that would be the problem. It's BSODing when just browsing the internet.

Motherboard BIOS is fully updated and has been for a long time.
Ram is just using the XMP profile and also hasn't been changed in a very long time.
 
Last edited:
Was it an 0X0000001A error code? A lack of voltage to your ram can cause this, if you have overclocked your ram it may not be getting enough voltage.

Where would I see this exactly? I'm not getting any code beyond Memory_Management in the BSOD.
 
IIRC I never had a code of any kind beyond Memory_Management.

In typical Sampsy fashion the undiagnosed problem has now disappeared entirely on its own. I guess my PC just had a bad day.
 
Unfortunately it's time for me to revive this thread as the issue is back. I haven't changed anything on the PC since yesterday when it was working fine and now it's BSODing every few minutes again. I snapped a photo of the BSOD screen this time

As you can see I'm getting no information beyond Memory_Management.

 
Last edited:
I have a whole pile of errors in the event viewer. That's filtered to just errors, critical and warnings from the last hour.



all the criticals and warnings are the same





I have a whole bunch of Distributed COM errors (among other things) in the history, but at times when it wasn't BSODing

 
Last edited:
Back
Top Bottom