Windows 7: Daily BSOD

ZooMan · 01 Jan 2010

Having BSOD almos daily. I have included the last five.

I have Windows 7 X64 Ultimate with all current updates.
Running on a Home Brew MSI x48 with the latest bios and drivers installed. Quad 9400 four gigs of memory.
I have run Memtest86 v4 and Prime95 with no problems.

Thanks in advance for all the help

zigzag3143 · 01 Jan 2010

Quote: Originally Posted by ZooMan

Having BSOD almos daily. I have included the last five.

I have Windows 7 X64 Ultimate with all current updates.
Running on a Home Brew MSI x48 with the latest bios and drivers installed. Quad 9400 four gigs of memory.
I have run Memtest86 v4 and Prime95 with no problems.

Thanks in advance for all the help

Zooman Hi and welcome

As you can see all these dmps say PFN_LIST_CORRUPT. this is a very strong indicator of a memory problem. How long did you run memtest for? MINIMUM is overnight, 5 passes at least. The only other thing it can be is a bad driver passing bad information into memory.

Since win 7 files were referenced you should run a system file check to verify and repair your system files. type cmd in search>right click and run as admin
SFC /SCANNOW

LET US KNOW THE RESULTS AS YOU WILL PROBALY HAVE TO RUN IT MORE THAN ONCE>

Hope this helps

Kenn J+

Code:

122809-18859-01.dmp    12/28/2009 4:01:38 PM    NTFS_FILE_SYSTEM    0x00000024    00000000`001904fb    fffff880`0cbef378    fffff880`0cbeebd0    fffff880`0129c884    Ntfs.sys    Ntfs.sys+7a884                    
121909-20750-01.dmp    12/19/2009 4:11:18 PM    PFN_LIST_CORRUPT    0x0000004e    00000000`00000099    00000000`0008931c    00000000`00000002    00000000`000892ef    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122809-17453-01.dmp    12/28/2009 6:42:22 PM    PFN_LIST_CORRUPT    0x0000004e    00000000`00000099    00000000`0000c523    00000000`00000002    00000000`0000c521    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122909-21796-01.dmp    12/29/2009 2:39:32 PM    PFN_LIST_CORRUPT    0x0000004e    00000000`00000099    00000000`00035171    00000000`00000002    00000000`000350bc    ntoskrnl.exe    ntoskrnl.exe+71f00                    
123109-30890-01.dmp    12/31/2009 7:23:24 PM    PFN_LIST_CORRUPT    0x0000004e    00000000`00000099    00000000`00041476    00000000`00000002    00000000`00030375    ntoskrnl.exe    ntoskrnl.exe+71f00

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\122909-21796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Tue Dec 29 14:37:57.766 2009 (GMT-5)
System Uptime: 0 days 1:58:13.250
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 35171, 2, 350bc}

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: 0000000000035171, page frame number
Arg3: 0000000000000002, current page state
Arg4: 00000000000350bc, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d4b32c to fffff80002cbcf00

STACK_TEXT:  
fffff880`0a7be868 fffff800`02d4b32c : 00000000`0000004e 00000000`00000099 00000000`00035171 00000000`00000002 : nt!KeBugCheckEx
fffff880`0a7be870 fffff800`02d1bb82 : 00000000`00000002 00000000`00000000 fffffa80`0042c840 00000000`00000080 : nt!MiBadShareCount+0x4c
fffff880`0a7be8b0 fffff800`02d7c23d : fffffa80`0042c840 fffff880`0a7bea00 00000000`00000080 00000000`000a76a6 : nt! ?? ::FNODOBFM::`string'+0x11ae2
fffff880`0a7be910 fffff800`02d2c68e : 00000000`00000002 fffff880`0a7bea00 fffffa80`08a92ec8 00000000`00000002 : nt!MiRemoveLowestPriorityStandbyPage+0x2ad
fffff880`0a7be990 fffff800`02cd71a6 : 00000000`00000000 00000000`0b9effd0 fffff880`0a7bebe0 fffff680`0005cf78 : nt! ?? ::FNODOBFM::`string'+0x29c37
fffff880`0a7bea80 fffff800`02cbafee : 00000000`00000000 00000000`01dcf260 00000000`00000001 00000000`00000000 : nt!MmAccessFault+0x5c6
fffff880`0a7bebe0 000007fe`fa453abf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`01dce5d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fa453abf


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

ZooMan · 09 Jan 2010

New MB ....

Thanks

Windows 7: Daily BSOD

Daily BSOD problems?