Unpredictable BSOD's, PFN_LIST_CORRUPT & SYSTEM_SERVICE_EXCEPTION

dom1610 · 03 Mar 2012

Having frequent BSOD's on my system. It is a brand new self-built system.

The system specs are:

Windows 7 Professional x64 with Service pack 1 (from MSDNAA)
Intel i5 2500K (Using stock cooler)
Gigabyte Z68X-UD5-B3
Corsair Vengeance 8GB (2x 4GB) DDR3 1600MHz CL9 (CMZ8GX3M2A1600C9)
Asus GeForce GTX 560 Ti (DirectCU II TOP)
Corsair CX600 V2 (600W)
Seagate Barracuda 1TB 7200.12 (Bought new for this system)
Seagate Barracuda 250GB 7200.10 (From my old system)

No overclocking at all.

I have run memtest86+ v4.20 overnight on both sticks of RAM with zero errors and have run on each stick separately for 6 passes with zero errors.

I have run memtest HCI for one hour with no problems (four instances running).

I have run Seatools on both drives with zero errors.

I also have Ubuntu 11.10 installed which has run with no problems at all. BSOD's started before Ubuntu installation.

Attached are the results of perfmon /report and the BSOD dump & system file collection app.
I really appreciate any help with this, as it's driving me crazy!

Thanks.

writhziden · 03 Mar 2012

I'm afraid you attached the executable for gathering the crash reports and not the actual crash reports. Please follow the https://www.sevenforums.com/crashes-d...tructions.html more carefully to provide us with the reports. Thank you. :)

dom1610 · 03 Mar 2012

Sorry about that. I've re-zipped and uploaded the correct files.

writhziden · 03 Mar 2012

Problem Devices:

Code:

Android Phone	USB\VID_0BB4&PID_0C87&MI_01\7&16C24EFA&0&0001	The drivers for this device are not installed.

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\dom1610\Windows_NT6_BSOD_jcgriff2\030312-29312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`0304a670
Debug session time: Sat Mar  3 05:34:45.631 2012 (UTC - 7:00)
System Uptime: 0 days 1:18:01.880
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 96a6c, 4, 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: 0000000000096a6c, page frame number
Arg3: 0000000000000004, current page state
Arg4: 0000000000000001, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  msiexec.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f0ad7c to fffff80002e81c40

STACK_TEXT:  
fffff880`0a1d34f8 fffff800`02f0ad7c : 00000000`0000004e 00000000`00000099 00000000`00096a6c 00000000`00000004 : nt!KeBugCheckEx
fffff880`0a1d3500 fffff800`02e293d7 : 00000000`0000fce4 fffff680`001245a0 d3900000`93b6b025 00000000`00000002 : nt!MiBadShareCount+0x4c
fffff880`0a1d3540 fffff800`02eb3bb7 : 00000000`00000000 fffff680`00124ff8 fffffa80`077a7060 e8400000`952b6025 : nt! ?? ::FNODOBFM::`string'+0x3309d
fffff880`0a1d36f0 fffff800`02eb5569 : 00000000`00000000 00000000`29b48fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`0a1d38b0 fffff800`03199221 : fffffa80`081f32c0 00000000`00000000 fffffa80`07390d60 fffffa80`07390d60 : nt!MiRemoveMappedView+0xd9
fffff880`0a1d39d0 fffff800`03199623 : 0000007f`00000000 00000000`18ad0000 fffffa80`00000001 00000000`047a6801 : nt!MiUnmapViewOfSection+0x1b1
fffff880`0a1d3a90 fffff800`02e80ed3 : 00000000`00000001 00000000`17aedcd8 fffffa80`077a7060 00000000`17aedcd0 : nt!NtUnmapViewOfSection+0x5f
fffff880`0a1d3ae0 00000000`77c015ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`014edbb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c015ba


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

Possible causes are Memory problems... Drivers...

Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

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

Shut down and turn off your computer.
Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
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.

dom1610 · 03 Mar 2012

First of all...Thank you for your help.

I've now installed a driver for my phone.
I ran memtest86+ (v4.20) last night. It completed 10 passes with 0 errors.
I will run the Windows memory diagnostic tool tonight.

How would be best to upload additional dump files. Should I just compress and upload or re-run the BSOD dump & system file collection app?

Thanks again.

writhziden · 03 Mar 2012

Re-running the app is the preferred method if changes have been made to the system since the previous crash, i.e. adding drivers, software, hardware, Windows updates, etc.

dom1610 · 05 Mar 2012

Okay, I've run Windows memory diagnostic with extended settings for 10 passes and it too detected no problems.

Any thoughts? Next steps?

Thank you.

writhziden · 05 Mar 2012

An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

dom1610 · 29 Mar 2012

Sorry this took so long, life got in the way.

I've attached the new reports and I've left verifier running.

Thanks,
Dom

writhziden · 29 Mar 2012

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\dom1610\Windows_NT6_BSOD_jcgriff2\031912-32339-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e66000 PsLoadedModuleList = 0xfffff800`030aa650
Debug session time: Mon Mar 19 11:38:53.011 2012 (UTC - 6:00)
System Uptime: 0 days 0:01:55.245
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002f6afe5, fffff88009765b40, 0}

Probably caused by : memory_corruption ( nt!MiGetTopLevelPfn+65 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002f6afe5, Address of the instruction which caused the bugcheck
Arg3: fffff88009765b40, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiGetTopLevelPfn+65
fffff800`02f6afe5 4c8b4928        mov     r9,qword ptr [rcx+28h]

CONTEXT:  fffff88009765b40 -- (.cxr 0xfffff88009765b40)
rax=000ffffffffdfffd rbx=000fffffffffffff rcx=02fffa7fff9fff70
rdx=fffffff55587ccc8 rsi=fffffa80065ec000 rdi=0000058000000000
rip=fffff80002f6afe5 rsp=fffff88009766528 rbp=0000000000000000
 r8=fffffe0009766560  r9=000ffffffffdfffd r10=fffff880097665d8
r11=0000000000000001 r12=000000003ffffff8 r13=0000000000000000
r14=fffff6fb40000000 r15=0000000fffffffff
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!MiGetTopLevelPfn+0x65:
fffff800`02f6afe5 4c8b4928        mov     r9,qword ptr [rcx+28h] ds:002b:02fffa7f`ff9fff98=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002f6afe5

STACK_TEXT:  
fffff880`09766528 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiGetTopLevelPfn+0x65


FOLLOWUP_IP: 
nt!MiGetTopLevelPfn+65
fffff800`02f6afe5 4c8b4928        mov     r9,qword ptr [rcx+28h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiGetTopLevelPfn+65

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

STACK_COMMAND:  .cxr 0xfffff88009765b40 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_VRF_nt!MiGetTopLevelPfn+65

BUCKET_ID:  X64_0x3B_VRF_nt!MiGetTopLevelPfn+65

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

Your Verifier enabled crashes are still pointing to memory.

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.

You may want to disable Verifier before doing the above if you have not already disabled it.