Solved BSOD - Random intervals with PFN_LIST_CORRUPT and MEMEORY_MANAGEMENT

[YTN3rd]

Ordering a Noctua NH-D14 CPU Cooler. Will post after running driver verification with the new cooler.

 

[Dave76]

Nice CPU cooler.

CPU overheating can cause issues like you're having, after you get the new cooler installed test the system for stability before running Driver Verifier. It might be stable.
Let us know the results.

 

[YTN3rd]

I was going to get a Antec Kuhler 620 for $74, but looking at benchmarks the NH-D14 ($85) is better. Not sure if all companies do this or if noctua is just awesome, but they have a motherboard and ram compatibility list.

 

[Dave76]

Noctua is a good company, their CPU coolers and fans are great.
Their fans are known to be excellent quality, durable and very quiet.

 

[YTN3rd]

Had the cooler in for a few days, got a BSOD. Will enable driver verification for all non-windows drivers and report back at next BSOD.

Is there a way I can clear out all those logs that sevenfourms program collects so it'll only show new logs as of today?

 

[Dave76]

Let us know what Driver Verifier comes up with.

The old dump files may be useful later, they don't take up much room, I would just leave them there.
You can take them out of the folder before you zip it.
The folder the dumps are stored in is %SystemRoot%\Minidump, ie C: \Minidump, you can delete them from there if you want.

 

[YTN3rd]

Got a BSOD with driver verification turned on, hopefully this puts more light on the subject.
Only thing I can see from windows debugger that is different is,

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

Maybe my computer has a vista driver installed?

When this crash happened I wasn't even at my computer, it was sitting there playing fullscreen YouTube videos for me and I was walking past the computer. I do know for a fact that the video I was watching was not finished, so its not like there was some form of web page interaction like going to the next video happening.

EDIT:
Looking at my drivers, my brother (printer, though not currently plugged in) drivers appear to be old.

BrFiltLo Brother USB Mass-Stora Kernel 7/08/2006 11:51:06 AM
BrFiltUp Brother USB Mass-Stora Kernel 7/08/2006 11:51:02 AM
Brserid Brother MFC Serial Por Kernel 7/08/2006 11:51:11 AM
BrSerWdm Brother WDM Serial dri Kernel 7/08/2006 11:51:05 AM
BrUsbMdm Brother MFC USB Fax On Kernel 7/08/2006 11:51:00 AM
BrUsbSer Brother MFC USB Serial Kernel 9/08/2006 10:11:02 PM

Went to go update them, says they are already installed -_- Even though the driver pack is from 2011.

 

[Dave76]

Vista Driver fault is common, it's the symbol used.

How many hours have you been running Driver Verifier in the past 3 days?

Though, the Brother drivers are old, may be causing problems. Un-install them for testing purposes, at least until you get another crash.

Last crash, same as before, is blaming memory corruption.

STOP 0x0000004E: PFN_LIST_CORRUPT
Usual causes:  Device driver, ?memory
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
PROCESS_NAME:  chrome.exe
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0x4E_99_VRF_nt!MiBadShareCount+4c

Chrome is implicated again, un-install Chrome for testing purposes. You can install it again later if the system is stable.

Are these two voltages still set in BIOS?
DRAM Voltage - 1.550v
VCCIO Voltage - 1.150v

Manually set the first four RAM timings to 9-9-9-25 and the 'Command Rate' to 2T, leave the rest on auto, Save & Exit.

Do you have any Asus utility programs installed?
If you do, un-install them, they are know to cause instability.

 

[YTN3rd]

I had been using the computer, maybe 10-14 hours a day over the last 3 days? If I shutdown my computer, the driver verification is still enabled for next boot, correct?

I had ASUS PC Diagnostics and ASUS AI Suite II installed, removing them now. Have also removed brother drivers.

BIOS is set to correct DRAM and VCCIO voltages. Changed my memory timings as requested, why change the cycle time from what the spec says they should run at?

I can uninstall chrome, but if the issue happens when chrome is doing things, or when steam is sometimes doing this, uninstalling them doesn't really solve the problem. I find it hard to believe that chrome is incompatible with my PC for some unknown reason. And saying to uninstall it is like saying the flat tyres on your car are not a problem so long as you don't try to drive it anywhere. I'll keep it on for now to see if uninstalling the some drivers, ASUS AI Suite and changing the RAM timings help.

EDIT: Should I enable driver verification for all drivers, including the Microsoft ones?

 

[Dave76]

Yes it has to be disabled manually.
You can disable Driver Verifier now.

The RAM timings I posted are from the CPUZ SPD tab, CPUZ reads it from the permanent file on the RAM cards which is put there by the manufacturer. This is their recommended, tested, settings.
It's a standard procedure when dealing with possible RAM issues, I run mine like that allways.

As mentioned above, 'for testing purposes', if the crashes stop with Chrome uninstalled, then we can try a fresh install or an older version.
With all the browser versions coming out quickly, they do have issues and are known, you can search and find them. Although Chrome has been pretty stable, this is the easiest way to confirm stability.

Keep Chrome if you want, we may need to come back to it later.

 

[YTN3rd]

Got another BSoD, again while using chrome. Uninstalled it, now using FireFox 18.0.1. I have taken the liberty to analyze the crash dump.

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


Loading Dump File [C:\Windows\Minidump\012213-6692-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*[URL]http://msdl.microsoft.com/download/symbols[/URL]
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0340e000 PsLoadedModuleList = 0xfffff800`03652670
Debug session time: Tue Jan 22 10:18:42.988 2013 (UTC + 11:00)
System Uptime: 0 days 0:33:37.689
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, fffff6800004b458, aa200000bfbcb867, fffffa8008be5170}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+136f2 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff6800004b458
Arg3: aa200000bfbcb867
Arg4: fffffa8008be5170

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


BUGCHECK_STR:  0x1a_41201

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800034e8d0e to fffff8000348cfc0

STACK_TEXT:  
fffff880`0d212878 fffff800`034e8d0e : 00000000`0000001a 00000000`00041201 fffff680`0004b458 aa200000`bfbcb867 : nt!KeBugCheckEx
fffff880`0d212880 fffff800`03457f61 : fffffa80`0a0f6200 fffffa80`09ed8550 00000000`00000000 aa200000`bfbcb867 : nt! ?? ::FNODOBFM::`string'+0x136f2
fffff880`0d2128c0 fffff800`03457bfa : fffffa80`08be5170 fffffa80`093ce580 fffffa80`093ce580 00000000`0968b000 : nt!MiQueryAddressState+0x2b1
fffff880`0d212910 fffff800`03763284 : fffff880`00000004 00000000`0968c000 fffffa80`08be5170 fffff680`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`0d212980 fffff800`0348c253 : 00000000`00000520 fffffa80`09ed8550 fffff880`0d212a88 00000000`00f5dfb8 : nt!NtQueryVirtualMemory+0x382
fffff880`0d212a70 00000000`779d154a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00f5df98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779d154a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+136f2
fffff800`034e8d0e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+136f2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+136f2

BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+136f2

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

Attached is the crash dumps and all other files. Turns out my brother drivers are still installed, I thought it removed them when I uninstalled the software.

 

[Dave76]

Use the 'Code' tags when posting a Windows Debugger report, it takes less room.
Where is the analyses?
Just see the debugger report.

STOP 0x0000001A: MEMORY_MANAGEMENT 
Usual causes:  Device driver, memory, kernel
This indicates that a severe memory management error occurred.

Let's bump DRAM and IMC voltage again.
DRAM Voltage - 1.600v
VCCIO Voltage - 1.170v

Don't see the Brother printer drivers loaded.

Here are some out of date drivers, update them or remove the software.
UltraMonUtility.sys Fri Nov 14 09:10:30 2008 - UltraMon multi-monitor - UltraMon Support
WinRing0x64.sys Sat Jul 26 21:29:37 2008 - many different programs that center around the using of the WinRing libraries (RealTemp, Corsair Link2 (known BSOD issues w/Win8), Razer GameBooster, etc)

 

[YTN3rd]

Will remember to use code tags

Updated ultramon, had version 3.2.1 rather than 3.2.2 (Dec 25, 2012).
As for WinRing0x64.sys, no idea how to update it, but I only use RealTemp to monitor my temps, which I don't need to do. Also I don't think the link you linked me to has anything to do with the only support link it lists, which takes me to download python? Can you check and clarify?

As for CPU overheating, that was pre-CPU cooler instillation.

Guess next step is to go pick up some new ram sticks, even though countless error checking failed to find anything they can still be frigidity like that.

One other thing I thought of, when my CPU did get that hot and didn't shut itself down, could it have damaged the MMU which is now causing it to sometimes misbehave?

 

[Dave76]

The CPU temps would have to be very high and for long periods, CPUs are robust. Likely not damaged, unless you had a max overclock and kept the system at max frequency for long periods of time.

Sometimes the RAM has enough of a defect to not be picked up in testing but will crash your system.
I would try to RMA the RAM or get new, the increased voltage and therefore temps aren't worth it for me.

Let us know what you decide to get and if it's stable.

 

[YTN3rd]

Yeah, I don't think I had run it too hot for too long.

If I was to get new RAM I think I would get the same sticks, so if the sticks were not to blame I'd at least then still have an extra 8gb of RAM. But then again, 16gb of RAM is < $100 (Corsair CMX16GX3M4A1600C9 16GB (4x4GB) DDR3 [CMX16GX3M4A1600C9] - $95.00 : PC Case Gear)

EDIT: Actually, same sticks are about $55 (http://www.pccasegear.com/index.php?main_page=product_info&products_id=16510), I think I might order some of them, fit them in my machine then send my others away for RMA.

 

[Dave76]

I'm like my Corsair Vengeance RAM, their return policy is very good.

I would be concerned about getting the same RAM, considering the problems. It might be ok.
Check with the store you bought them from, they may let you exchange the old RAM towards the Corsair RAM or credit for your next upgrade.
Doesn't solve the no RAM problem.

 

[YTN3rd]

Had already ordered them. When I get them I'll go back to chrome (as its what I BSoD in most of the time) and see if it happens again. If it does I would think its safe to say that its either that type of RAM with my motherboard (though a lot of people apparently have this combo) OR its something else. I have my housemates old RAM after he recently updated (XMS3) so then I'll test that. I may just leave my computer on with a youtube playlist tonight and see if I can BSoD it in FireFox.


Worst case scenario, BSoD still happens after I test the corsair RAM, which means the 16gb of ripjaws are fine. Best case scenario, new ripjaws fix it and the old RAM is replaced under warranty and I get new shiny sticks to match the sticks I just bought.

 

[Dave76]

Good plan.

Let us know your status.

 

[YTN3rd]

Got the new RAM installed. I noticed something when I was looking in BIOS. When I changed XMP profile with the old RAM it'd change the CPU max frequency (to 4.2 or 4.4 I think). People have said XMP has nothing to do with the BLCK or any of that stuff, so not sure what was going on there. But when I set the XMP profile all CPU stuff stayed.

I also took a new cpu-z screenshot and compared it next to my previous screenshot of the older RAM.
Is it odd that values are different for all the timings table?

EDIT: Just seen that it says JEDEC #1 - #3 on the left image, #4 - #6 on the right image. But still, is that normal?

 

[Dave76]

XMP should not increase the CPU frequency or base clock on your motherboard, have you updated the BIOS since the old RAM XMP setting?

CPUZ SPD tab is just a file installed on the RAM card with manufacturers recommended/tested RAM timings and voltages.
System RAM does get upgraded design and mostly memory chips, it's not uncommon to get different reading on the SPD tab, there may be compatibility issues with the old and new RAM cards, even though from the same manufacturer and P/N. They usually are compatible but, not always.

Is your system stable now?