BSOD - pfn list corrupt & memory management

[Cpuk]

I had rebuilt my computer around 2 weeks ago and ever since then I have been having random BSOD daily. They usually happen after the computer has been running from anywhere between 30 mins - 8 hours (usually while playing games but have also happened while just browsing internet)

As far as I can remember, every BSOD has been either 'pfn list corrupt' or ' memory management'

I have not overclocked anything at all. I have ran both the windows memory diagnostics and memtest and neither have shown any errors.

So far I have tried (to no avail)
- increasing Ram voltage
- switching ram from Dimm slots 1&3 to 2&4
- updated all of my drivers (that I can find/am aware of)

System:
Windows 7 Ultimate 64bit
Intel Core i5-2500k @ 3.30GHz
Corsair CMZ8GX3M2A1600C9 8GB 1600MHz CL9 DDR3 Vengeance (2x4GB)
Asus GTX560 TI 2GB Graphics card
Gigabyte GA-Z68AP-D3 Z68 Motherboard
850W PSU

I use microsoft security essentials.

The only thing that seems to work (though I haven't tested for longer than about 8-9 hours) is just running with 1 Ram stick.

I have attached the dump files. Any help would be greatly appreciated.

 

[ePeen]

TONS of memory_corruption and hardware_ram culprits. Could either be an evil third party driver causing all of this, or your RAM is taking a vacation (more likely than a 3rd party driver at this point it looks like).

Two things I'd like you to do:

Memtest:

Read the following to test your memory for errors.

Driver Verifier:

Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\032112-17955-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03019000 PsLoadedModuleList = 0xfffff800`03255e70
Debug session time: Wed Mar 21 13:15:18.252 2012 (UTC - 4:00)
System Uptime: 0 days 0:14:59.204
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 8aeac, 2, 1}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000008aeac, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000000001, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  plugin-contain

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000311887c to fffff80003089540

STACK_TEXT:  
fffff880`0888b198 fffff800`0311887c : 00000000`0000004e 00000000`00000099 00000000`0008aeac 00000000`00000002 : nt!KeBugCheckEx
fffff880`0888b1a0 fffff800`030fb37b : 00000000`00000000 fffffa80`01977810 0000000f`ffffffff fffff8a0`0a1b1a08 : nt!MiBadShareCount+0x4c
fffff880`0888b1e0 fffff800`030cf441 : 93200000`00000000 fffff680`00071f00 00000000`00000200 000fffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x320a7
fffff880`0888b260 fffff800`030ca7ae : 00000000`00000001 00000000`00000000 fffffa80`0a493b30 fffffa80`0a493ec8 : nt!MiDecommitPages+0x1a1
fffff880`0888baf0 fffff800`03088793 : ffffffff`ffffffff 00000000`0025e0d0 00000000`0025e0c8 00000000`00000001 : nt!NtFreeVirtualMemory+0x2de
fffff880`0888bbe0 00000000`76f8f89a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0025e098 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f8f89a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`0311887c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec7a284

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------




Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\031112-35802-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0301d000 PsLoadedModuleList = 0xfffff800`0325ae70
Debug session time: Sun Mar 11 08:36:05.777 2012 (UTC - 4:00)
System Uptime: 0 days 0:40:04.729
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8887, fffffa800182c010, fffffa800002be90, 205}

Probably caused by : hardware_ram ( ZEROED_PAGE_CORRUPTED )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008887, The subtype of the bugcheck.
Arg2: fffffa800182c010
Arg3: fffffa800002be90
Arg4: 0000000000000205

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_8887

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  2

STACK_TEXT:  
fffff880`068228d8 fffff800`030ae764 : 00000000`0000001a 00000000`00008887 fffffa80`0182c010 fffffa80`0002be90 : nt!KeBugCheckEx
fffff880`068228e0 fffff800`030a99dc : fffffa80`01578270 fffffa80`00000000 00000000`01578270 fffffa80`0182c010 : nt!MiUnlinkPageFromLockedList+0x2e4
fffff880`06822970 fffff800`030a7593 : ffffffff`ffffff00 00000000`0251fff8 00000000`00000000 ffffffff`00000000 : nt!MiDispatchFault+0x7ac
fffff880`06822a80 fffff800`0308b6ae : 00000000`00000000 00000000`75112828 00000000`00000001 00000000`00001000 : nt!MmAccessFault+0x343
fffff880`06822be0 000007fe`ff6a117a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`021ad808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff6a117a


STACK_COMMAND:  kb

SYMBOL_NAME:  ZEROED_PAGE_CORRUPTED

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware_ram

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x1a_8887_ZEROED_PAGE_CORRUPTED

BUCKET_ID:  X64_0x1a_8887_ZEROED_PAGE_CORRUPTED

Followup: MachineOwner
---------

 

[Cpuk]

I have already used memtest to test the sticks both together and individually and no errors are showing. As mentioned in my original post, both sticks also seem to work when use on their own just not jointly.

 

[ePeen]

Then please enable Driver Verifier.

 

[Cpuk]

I have enabled verifier while only have 1 Ram stick installed and am not having any problems (as was the case before enabling verifier)

Even though I have never had problems when using just 1 Ram stick, surely this should prove that it is not a driver issue?

With both Ram sticks installed then I would get BSOD's regardless of the verifier running. Are drivers likely to work differently if I were to have verifier enabled while both are installed?

 

[ePeen]

If you're not BSOD'ing with one stick, but you BSOD when you insert the second stick, I believe you've found the answer to your own problem, yes?

Replace your other stick of RAM.

 

[Cpuk]

Both sticks work fine on their own, it is only when they are both installed at the same time when the BSOD's appear, that's what is confusing me.

 

[ePeen]

Could possibly be an issue with timings and voltages. Are you running the advised timings and DRAM voltage when running in dual channel?

 

[Cpuk]

I have been tried both the default motherboard settings as well as the advised timings + voltage etc as described by Corsair and have contiuned to have BSOD's in both instances.

I have no idea where to go from here really.

 

[writhziden]

Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

Also, go into your BIOS and post all Voltages (CPU, RAM, NB, IMC, etc.) and all RAM settings (timings, frequency, etc.)

Thanks to Dave76 for help learning RAM Stability

 

[Cpuk]

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)

 

[writhziden]

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.

 

[Cpuk]

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

 

[writhziden]

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.

 

[badwhippet]

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.

 

[writhziden]

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.

 

[badwhippet]

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: http://www.sevenforums.com/crashes-debugging/154679-memory-management-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!

 

[Cpuk]

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.

 

[writhziden]

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

 

[Cpuk]

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