BSOD - pfn list corrupt & memory management

Sorry for the delay, I haven't had time to do what you asked up until now.

Attached are the screenshots you requested and below is the BIOS info:


Advanced Voltage settings:

CPU Vcore -1.225v
QPI/Vtt - 1.050v (have already tried increasing to 1.100v alongside DRAM voltage at 1.6)
System Agent Voltage - 0.920v
Graphics Core - 1.030v

CPU PLL - 1.800V

DRAM Voltage - 1.500v (have tried increasing to 1.52v, 1.56v, 1.60v)
DRAM VRef - 0.750v
DRAM Termination - 0.750v
Ch-A Data VRef - 0.750v
Ch-B Data VRef - 0.750v
Ch-A address Vref - 0.750v
Ch-B address Vref - 0.750v

Advanced Memory Settings:

Frequency - 1333mhz (system memory multiplier - 13.33) (have tried increasing to 1600 both with and without the other bold changes above)
Performance Enhance - Standard ('Turbo' and 'Extreme' are the alternatives) (Turbo was even less stable, haven't tried extreme)

Channel A Timings - 9-9-9-24
Channel B Timings - 9-9-9-24

Hopefully all of the info you need is amongst the above info.

The info in bold are the changes I have previously made, none of which have solved my problem or noticeably helped it (made it stable for longer etc)

Load setup defaults in the BIOS. See how it runs.

If you have another crash, up QPI/VTT to 1.15 Volts. Keep DRAM at 1.5 Volts.

If that still does not work, try QPI/VTT at 1.20 Volts and DRAM at 1.65 Volts.

If the system is still unstable, load setup defaults in the BIOS again. Then do your normal routine on one module at a time. Test each module in each slot of the board until you find a good module and a good slot. Test the other module in the known good slot. Then test the good module in all slots. This will help determine if you have bad modules and/or slots. Avoid Static Damage to Your PC when swapping the modules.


If you swap any memory components, follow these steps for ESD safety:

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.

Once these steps have been followed, it is safe to remove and replace components within your computer.

I have had no luck with either of the voltage settings that you had recommended.

The RAM always works in single channel regardless of which slot it is in.

I am back to square 1 it seems

Alright, go into the BIOS, load setup defaults, save, and exit.

Then, go into the BIOS again, and change the command rate for your RAM to 2T. See if you can run dual channel stable with that change.

I've been having the 'memory management' BSOD on a brand new Windows 7 system. My memory was also fine in tests. Each time I rebuilt my system, it was after a joint process of Windows Update and Kaspersky installation that my PC would start locking up necessitating a forced reboot, and then BSODs would start happening. Finally I carried out updates but left out Kasp[ersky and all was stable. Having Googled, various people were blaming Kaspersky for BSODs, so I've since switched to a new solution and my system is good again. Hardly scientific, but if you have Kaspersky it might be worth uninstalling to see whether your problem is resolved.

I do not see Kaspersky installed on the OP's system. Everyone has different problems that cause crashes because everyone has a very different software/hardware/Windows configuration. I'd be shocked to find two systems that were exactly the same.

I'm not wishing to imply that any two systems are the same by any means, but I too had this same BSOD and after a similar hardware chase it transpired to be nothing to do with my hardware. Googling it, there are several (not just Kaspersky) anti-virus and security software products that also seem to cause the memory-management BSOD error. An older thread here pinpoints Avast as another perpetrator - see: https://www.sevenforums.com/crashes-d...ment-bsod.html

I know it could indeed be a hardware problem, but if it happens to be nothing more than an anti-virus program being the culprit, it's a great relief! :)

Changing the command rate to 2T has made no difference either.

I do not have Kapersky installed and the only anti virus I use is microsoft security essentials.

You said everything runs fine in single channel, correct? You do not get crashes in Windows with it in single channel mode?

That is correct, I don't experience any problems at all when just using 1 Ram stick in a single channel set up.