Sign in with
Sign up | Sign in
Your question
Solved

Memory Management BSOD, No Memtest Errors

Last response: in Memory
Share
September 22, 2013 7:16:31 AM

Hello everyone,

I'm experiencing a once a day Memory Management BSOD (typically 0x0000001A).

I have run 7 passes on Memtest 86+ and gotten 0 errors, and at this point I'm not sure what I should do next.

Below is a summary of installed hardware:

CPU: AMD Phenom II X4 955
Motherboard: Micro-STAR 790FX-GD70
Memory: 8GB Kingston DDR3
GPU: Radeon HD 5750

We're running on Windows 7 64 Bit as well.

I'm by no means an expert so please let me know if I have left out any information that would be needed to diagnose the issue. Any help would be much appreciated.
a c 1941 } Memory
September 22, 2013 2:45:52 PM

What set of DRAM, the model #, sort of guessing it may be 1600 (possibly 1333) DRAM,if so may want to raise DRAM voltage + 0.05 and the CPU/NB voltage the same
m
0
l
September 22, 2013 5:00:11 PM

PC3-10700, which when googling seems to be 1333Mhz.

How do I change the voltage? In the BIOS?
m
0
l
Related resources
a c 1941 } Memory
September 22, 2013 5:02:23 PM

Yes and it's 1333, should be able to find the model number in CPU-Z on the SPD page under part number
m
0
l
September 22, 2013 5:35:35 PM

Great! I'll try the bump and get report back

If this isn't the answer it shouldn't damage my cpu/ram?
m
0
l
a c 1941 } Memory
September 22, 2013 6:04:31 PM

No, a sligh bump of voltage to DRAM is fine, maybe add + 0.05 so if 1.5 sticks go to 1.55
m
0
l
September 24, 2013 3:12:41 PM

So I have a few quick questions

All my voltages are set to Auto so I don't know what to bump them up to

In CPU-Z the RAM seems to be at 1.5 so that isn't so confusing

But the CPU voltage is fluctuating anywhere between .96 and 1.3

What do I use for the CPU-NB voltage?
m
0
l
a c 1941 } Memory
September 24, 2013 5:24:31 PM

Just try the DRAM bump first to 1.55
m
0
l
September 29, 2013 6:16:02 AM

Tradesman1 said:
Just try the DRAM bump first to 1.55


Ok, I tried this, and it does seem to have helped a little? We went three days without the Memory Management error. However I got it again this morning.

Given that the CPU voltage seems to change, I'm not sure what my next step should be
m
0
l

Best solution

a c 1941 } Memory
September 29, 2013 8:16:26 AM

OK, now let's take the CPU/NB (which is the MC (memory controller) voltage up about + 0.06
Share
September 29, 2013 12:55:37 PM

Tradesman1 said:
OK, now let's take the CPU/NB (which is the MC (memory controller) voltage up about + 0.06


The problem is that the CPU NB is set to AUTO so I don't actually know what to up it to.

Also I accidentally selected your previous post as the best answer and don't know how to undo it. Great day for me.
m
0
l
a c 1941 } Memory
September 29, 2013 1:15:17 PM

Just try setting it to 1.2 for the moment and see how it goes, think that will prob suffice, but have seen people up as high as 1.4, I prefer to keep as low as possible for stabbility to help keep heat down, which is why I suggested low increments
m
0
l
September 30, 2013 3:12:26 PM

Thanks, off to do that now. Quick addendum, today for the first time I got a different error other than memory management: Bad Pool Header

NO idea what that one means
m
0
l
a c 1941 } Memory
September 30, 2013 3:22:56 PM

Might try running CHKDSK /R from the command prompt as Administrator,
m
0
l
October 3, 2013 11:52:50 AM

Ok, I have run chkdsk and the Bad Pool Header hasn't shown up again. We went a full day this time without the Memory management error and just got it again today. Do I up the voltage again?
m
0
l
a c 1941 } Memory
October 3, 2013 12:10:42 PM

Sounds like we may have it, but have that in the back of your mind so can just try a voltage increase and then post back
m
0
l
October 15, 2013 6:15:01 PM

how much should I up it this time? .05 again?
m
0
l
a c 1941 } Memory
October 15, 2013 6:19:13 PM

Yep, to the CPU/NB
m
0
l
January 25, 2014 1:00:07 PM

So I've been Quite busy but I have a report if you're around, Tradesman

I upped the voltage of the CPU/NB by .05 again and I'm still getting intermittent blue screens.

Would it be acceptable to try this again? Is it still the likely solution? and at what point have I raised the voltage too high?
m
0
l
a c 1941 } Memory
January 25, 2014 3:53:40 PM

Yes, some have had to go to 1.4 and slightly higher
m
0
l
a b } Memory
January 27, 2014 11:13:58 AM

The memory corruption error reported by the OS is often caused by a device driver that over writes into shared device driver memory.
When a windows driver detects the modified data it calls a bugcheck an does a memory dump so the problem can be isolated and fixed.
you will generally get slightly different memory dumps in this case due to the fact that windows attempts to load device drivers in different orders on each boot.

if you post the memory dump on a cloud server with public access I can take a quick look at it and see if the cause is clear or if I have a good guess.
also, sometimes when memtest86 passes you still want to swap your memory modules around and run it again. There is always a chance that there could be a bad memory spot that is not in memory that the tool can test. (memory that the tool itself is loaded into for example)


m
0
l
February 17, 2014 6:24:13 AM

So I have bumped CPU/NB to 1.4

I'm still getting the error every other day or so, and I'm at a loss as to what to do next.

Could the power supply itself be going bad? How would I know?

And can memory still be bad even if memtest gives the all clear?
m
0
l
February 20, 2014 5:23:17 PM

chinchymcchilla said:
So I have bumped CPU/NB to 1.4

I'm still getting the error every other day or so, and I'm at a loss as to what to do next.

Could the power supply itself be going bad? How would I know?

And can memory still be bad even if memtest gives the all clear?


I'm encountering the same issues as you, including the occasional bad pool header. I've tried everything I've been told, although increasing the voltage was new to me. I did not try this but I've tried everything else without success....

I'm wondering if this could be the SATA Controller or just a bad MC in general... so in otherwords motherboard replacement... but i'm not sure. Could anyone provide some insight?

I'm running a completely different setup than Chinch, though.

i7 4770k on an MSI Z87-G41, 16gb corsair vengeance RAM, GTX 650. Win7 x64....

I'm a bit more familiar, working in IT and PC gaming now for 13 years, so ANY suggestions or input would greatly help...
m
0
l
March 2, 2014 2:56:07 PM

Is there any way to un-mark an answer as a solution on the thread? I am still stuck and can't figure out what to do next.
m
0
l
March 2, 2014 3:03:53 PM

Sorry for bumping a thread so old but I am at the end of my rope, I'm about to buy a whole new PC to fix this problem and I KNOW that there must be a simpler way but I just absolutely can't figure out what needs to be replaced. Any help would be incredibly welcome.
m
0
l
March 2, 2014 3:12:41 PM

One additional piece of information: Before it throws the Memory Management error, it hard locks and repeats the last second of audio and gives visual distorion before going to the blue screen.
m
0
l
March 5, 2014 4:07:17 PM

One last attempt at bumping this, still have no idea what's going on.
m
0
l
!