Memory_Management BSODs

Sampsy

Sampsy

Sampsy

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?
 
Did you updated your motherboard to latest BIOS?

I had BSODs memory management errors all the times years ago with old Phenom II X4 940 BE, ASUS A8N-E with OCZ 8GB DDR2 RAM. Already been updated BIOS but it didn't fixed issue so I had an idea that would solved issue. I went into BIOS noticed RAM timings was set to AUTO, I switched it to manual and entered exactly OCZ timings from labels found on OCZ sticks then next day surprise surprise PC no longer had BSODs memory management errors anymore. :)

I would suggest you to do same to turned off AUTO RAM timings in BIOS and manually entered correct memory timings found on your RAM sticks.
 
Sampsy said:
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?
Click to expand...

Need more information, still likely going to be memory corruption from instability or faulty memory.


List system specs
 
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.
 
Uaon said:
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.
Click to expand...

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:
As of Windows 8 and above, it doesn't display the error code on the screen, you have to look it up yourself in the event viewer.

If you look that up in the event viewer (between BSODs) you should find that this is a 0X0000001A error code.
 
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:
Yeah, the BSODs are definitely 0x1As. As for the other errors, Kernel 41 is just the fact it has unexpectedly lost power/rebooted - you always get this when you press the reset button or get a BSOD.

The fact you're getting a BSOD straight after the Task Scheduler warning suggests to me that something isn't right with that program.

See if you can get WhoCrashed and/or BlueScreenView installed. They should give you an idea of what driver/program caused the BSOD.
 
You must log in or register to reply here.
Back
Top Bottom