BSOD - Random intervals with PFN_LIST_CORRUPT and MEMEORY_MANAGEMENT

YTN3rd · 21 Jan 2013

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.

Code:

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*http://msdl.microsoft.com/download/symbols
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 · 22 Jan 2013

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

Code:

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 · 22 Jan 2013

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 · 22 Jan 2013

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 · 22 Jan 2013

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?...ducts_id=16510), I think I might order some of them, fit them in my machine then send my others away for RMA.

Dave76 · 22 Jan 2013

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 · 22 Jan 2013

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 · 22 Jan 2013

Good plan.

Let us know your status.

YTN3rd · 23 Jan 2013

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 · 23 Jan 2013

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?