Solved Desperately need assistance fixing BSoDs (7100 64bit)

[nuvas]

Hello sirs. I typically find myself to be relatively computer savvy, though I have not had much experience troubleshooting errors like this. I have several recent dump files that have been analyzed via the windbg tool I saw referenced in a different thread. I get bluescreens usually about once a day, sometimes twice a day. It doesn't really matter what I'm doing. I can be surfing the net talking on ventrilo. I can be poking around checking out Win7 features. I can be playing an online game. I can even be asleep and when I wake up, it's there. I assume it's some kind of driver related issue but when looking over the dump files, I'm really not sure what I should be looking for. Hopefully there is someone out there that can share their wealth of knowledge.

I run a Core2Duo E6600, 4 gigs of Patriot DDR2, an Asus P5N32-E SLI Motherboard, an EVGA 8800GTS 640mb video card, and 3 Seagate drives.

I initially thought the problem could be sound related. So I installed the latest Vista drivers for my onboard sound device courtesy of the Asus website. A friend had suggested that the Win7 Nvidia display drivers could be the culprit. So I am currently running 64bit Vista Nvidia drivers. However my system has crashed after each attempt at fixing it. I ran a memory diagnostic through Windows. I walked away while it was doing it and when I came back it had booted into Windows and nothing was stated one way or the other. For the record it seemed fine during the first pass so I walked away thinking it would report something when it was done. For the most part I've just rebooted and kinda chalked it up to it being RC and maybe I needed to wait for Win7 specific drivers in order to address whatever issue I was having. But as time went on, I've come to the conclusion that I should try to address this issue as it may not be something that simply goes away come final release. So without further ado, I present several dumps and really appreciate anyone that takes the time to look through these and offer advice. The dumps are newest to oldest.

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


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

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c8ee90
Debug session time: Fri May 29 20:52:21.599 2009 (GMT-4)
System Uptime: 0 days 4:11:14.472
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002ae8eb8, fffff88006be1150, 0}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c8 )

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

1: 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: fffff80002ae8eb8, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88006be1150, 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!MiReplenishPageSlist+c8
fffff800`02ae8eb8 f00fba6b1000 lock bts dword ptr [rbx+10h],0

CONTEXT: fffff88006be1150 -- (.cxr 0xfffff88006be1150)
rax=0000f80000041a8f rbx=002e7a8000c4fad0 rcx=0000000000000000
rdx=000000000000004f rsi=000000000000000e rdi=0000000000000001
rip=fffff80002ae8eb8 rsp=fffff88006be1b30 rbp=fffffa800237ced0
r8=fffff80002cfb400 r9=fffffa8003900000 r10=fffffa8003900278
r11=0000000000000000 r12=2aaaaaaaaaaaaaab r13=fffffa8003900258
r14=fdffffffffffffff r15=0000058000000000
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!MiReplenishPageSlist+0xc8:
fffff800`02ae8eb8 f00fba6b1000 lock bts dword ptr [rbx+10h],0 ds:002b:002e7a80`00c4fae0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002ae8c32 to fffff80002ae8eb8

STACK_TEXT:
fffff880`06be1b30 fffff800`02ae8c32 : fffff800`02cfb400 00000000`0000000f 00000000`00000000 00000000`0000000f : nt!MiReplenishPageSlist+0xc8
fffff880`06be1ba0 fffff800`02aed8e3 : 00000000`00000002 fffff880`00000002 fffff880`02f83c00 00000000`00000000 : nt!MiRemoveAnyPage+0x252
fffff880`06be1cc0 fffff800`02ae52f9 : 00000000`00000001 fffff900`c44a3000 fffff880`06be2020 fffff6fc`80622518 : nt!MiResolveDemandZeroFault+0x543
fffff880`06be1db0 fffff800`02ae230c : 00000000`00099996 fffff900`c439d000 00000000`00000000 00000000`00000034 : nt!MiDispatchFault+0x8b9
fffff880`06be1ec0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0xa2c


FOLLOWUP_IP:
nt!MiReplenishPageSlist+c8
fffff800`02ae8eb8 f00fba6b1000 lock bts dword ptr [rbx+10h],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiReplenishPageSlist+c8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 49ee9439

STACK_COMMAND: .cxr 0xfffff88006be1150 ; kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x3B_nt!MiReplenishPageSlist+c8

BUCKET_ID: X64_0x3B_nt!MiReplenishPageSlist+c8

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

..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a0ffb5c400, 1, fffff80002d65126, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!CmpAllocateKeyControlBlock+72 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a0ffb5c400, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002d65126, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc30e0
fffff8a0ffb5c400

FAULTING_IP:
nt!CmpAllocateKeyControlBlock+72
fffff800`02d65126 48895808 mov qword ptr [rax+8],rbx

MM_INTERNAL_CODE: 5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88002c6f2c0 -- (.trap 0xfffff88002c6f2c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0ffb5c3f8 rbx=0000000000000000 rcx=fffff8a00f3d6e60
rdx=fffff88002c6f4b8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d65126 rsp=fffff88002c6f450 rbp=0000000000ac6d28
r8=fffff8a00347dd2c r9=fffff8a0082b9de8 r10=fffff8a003004160
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!CmpAllocateKeyControlBlock+0x72:
fffff800`02d65126 48895808 mov qword ptr [rax+8],rbx ds:0001:fffff8a0`ffb5c400=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002b05fc9 to fffff80002a9df80

STACK_TEXT:
fffff880`02c6f158 fffff800`02b05fc9 : 00000000`00000050 fffff8a0`ffb5c400 00000000`00000001 fffff880`02c6f2c0 : nt!KeBugCheckEx
fffff880`02c6f160 fffff800`02a9c06e : 00000000`00000001 fffff800`02c91080 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3de2b
fffff880`02c6f2c0 fffff800`02d65126 : 00000000`00000000 fffff880`02c6f750 00000000`00000001 fffff8a0`0ff32500 : nt!KiPageFault+0x16e
fffff880`02c6f450 fffff800`02d648e7 : 00000000`00000000 00000000`9a79204b 00000000`00000000 fffff8a0`03c31e90 : nt!CmpAllocateKeyControlBlock+0x72
fffff880`02c6f480 fffff800`02d33d07 : fffff8a0`00024010 00000000`00ac6d28 fffff8a0`0347dd2c fffff8a0`082b9de8 : nt!CmpCreateKeyControlBlock+0xe8
fffff880`02c6f520 fffff800`02d2eea4 : fffff8a0`00000000 fffff8a0`00ac6d28 fffff8a0`00024010 fffffa80`04493b10 : nt!CmpDoOpen+0x387
fffff880`02c6f5e0 fffff800`02d7fcd4 : fffff800`02d2e9c0 fffffa80`00000001 fffffa80`04493b10 00000000`00000001 : nt!CmpParseKey+0x4e4
fffff880`02c6f8c0 fffff800`02d8c8e6 : 00000000`000003c4 fffffa80`04493b10 00000000`00000000 fffffa80`03a0fa50 : nt!ObpLookupObjectName+0x504
fffff880`02c6f9c0 fffff800`02d3391c : 00000000`10d74c00 00000000`00000000 fffff8a0`10d74c01 fffff880`02c6faa8 : nt!ObOpenObjectByName+0x316
fffff880`02c6fa90 fffff800`02d3659f : 00000000`01acd8a0 00000000`000f003f 00000000`01acd928 00000000`00000008 : nt!CmOpenKey+0x28a
fffff880`02c6fbe0 fffff800`02a9d1d3 : fffffa80`07ba6b60 fffff880`02c6fca0 00000000`01ace3b8 00010000`00000000 : nt!NtOpenKeyEx+0xf
fffff880`02c6fc20 00000000`77bdf42a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01acd838 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bdf42a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CmpAllocateKeyControlBlock+72
fffff800`02d65126 48895808 mov qword ptr [rax+8],rbx

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!CmpAllocateKeyControlBlock+72

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 49ee9439

FAILURE_BUCKET_ID: X64_0x50_nt!CmpAllocateKeyControlBlock+72

BUCKET_ID: X64_0x50_nt!CmpAllocateKeyControlBlock+72

Followup: MachineOwner

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


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

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02867000 PsLoadedModuleList = 0xfffff800`02aa0e90
Debug session time: Wed May 27 15:30:38.640 2009 (GMT-4)
System Uptime: 0 days 12:02:30.513
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa000715c090, 2, 0, fffff8000298683f}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa000715c090, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000298683f, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b0b0e0
fffffa000715c090

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiIdentifyPfn+23f
fffff800`0298683f 4c8b7500 mov r14,qword ptr [rbp]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff88005b0e4e0 -- (.trap 0xfffff88005b0e4e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0200000000000020
rdx=00000000000bb2f6 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000298683f rsp=fffff88005b0e670 rbp=fffffa000715c090
r8=00000000000bb2f7 r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!MiIdentifyPfn+0x23f:
fffff800`0298683f 4c8b7500 mov r14,qword ptr [rbp] ss:0018:fffffa00`0715c090=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800028e54e9 to fffff800028e5f80

STACK_TEXT:
fffff880`05b0e398 fffff800`028e54e9 : 00000000`0000000a fffffa00`0715c090 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`05b0e3a0 fffff800`028e4160 : 00000000`42506650 02000000`000a3497 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`05b0e4e0 fffff800`0298683f : 00000000`00000000 02000000`000bac37 00000000`00000000 fffff800`02b6e4df : nt!KiPageFault+0x260
fffff880`05b0e670 fffff800`0298751b : 00000000`00000000 00000000`00000004 fffffa80`076fce98 fffffa80`076fc000 : nt!MiIdentifyPfn+0x23f
fffff880`05b0e710 fffff800`02ce7de5 : fffffa80`076fc000 fffff880`05b0eca0 fffff880`05b0e7e8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`05b0e750 fffff800`02c2c314 : 00000000`00000006 00000000`00000000 fffffa80`076fc000 00000000`00000001 : nt!PfpPfnPrioRequest+0x115
fffff880`05b0e7a0 fffff800`02bcb5b6 : 00000000`00000000 00000000`00000004 00000000`64496d4d fffffa80`64496d01 : nt! ?? ::NNGAKEGL::`string'+0x47fdd
fffff880`05b0e830 fffff800`02bcbe5d : 00000000`01debb68 00000000`02c8d280 00000000`01debbc0 00000000`00000001 : nt!ExpQuerySystemInformation+0x2362
fffff880`05b0ebe0 fffff800`028e51d3 : 00000000`05ce4f70 fffff880`05b0eca0 00000000`00000000 00000000`02c8d280 : nt!NtQuerySystemInformation+0x4d
fffff880`05b0ec20 00000000`772de83a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01deba88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772de83a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiIdentifyPfn+23f
fffff800`0298683f 4c8b7500 mov r14,qword ptr [rbp]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiIdentifyPfn+23f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 49ee9439

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f

BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f

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

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


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

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02861000 PsLoadedModuleList = 0xfffff800`02a9ae90
Debug session time: Fri May 22 23:57:54.587 2009 (GMT-4)
System Uptime: 0 days 2:11:24.460
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa80204176d0, 2, 0, fffff8000298083f}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa80204176d0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000298083f, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b050e0
fffffa80204176d0

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiIdentifyPfn+23f
fffff800`0298083f 4c8b7500 mov r14,qword ptr [rbp]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff88005f1b4e0 -- (.trap 0xfffff88005f1b4e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0a00000000000020
rdx=00000000000c3703 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000298083f rsp=fffff88005f1b670 rbp=fffffa80204176d0
r8=00000000000c3743 r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MiIdentifyPfn+0x23f:
fffff800`0298083f 4c8b7500 mov r14,qword ptr [rbp] ss:0018:fffffa80`204176d0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800028df4e9 to fffff800028dff80

STACK_TEXT:
fffff880`05f1b398 fffff800`028df4e9 : 00000000`0000000a fffffa80`204176d0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`05f1b3a0 fffff800`028de160 : 00000000`42506650 02000000`000bdcc5 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`05f1b4e0 fffff800`0298083f : 00000000`000135a3 fffffa80`060e5fb8 0000000f`ffffffff fffff800`02b684df : nt!KiPageFault+0x260
fffff880`05f1b670 fffff800`0298151b : 00000000`00000000 00000000`00000004 fffffa80`060e5fd0 fffffa80`060e5000 : nt!MiIdentifyPfn+0x23f
fffff880`05f1b710 fffff800`02ce1de5 : fffffa80`060e5000 fffff880`05f1bca0 fffff880`05f1b7e8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`05f1b750 fffff800`02c26314 : 00000000`00000006 00000000`00000000 fffffa80`060e5000 00000000`00000001 : nt!PfpPfnPrioRequest+0x115
fffff880`05f1b7a0 fffff800`02bc55b6 : 00000000`00000000 00000000`00000004 00000000`64496d4d fffffa80`64496d01 : nt! ?? ::NNGAKEGL::`string'+0x47fdd
fffff880`05f1b830 fffff800`02bc5e5d : 00000000`01e6b848 00000000`000c3161 00000000`01e6b8a0 00000000`01e6b868 : nt!ExpQuerySystemInformation+0x2362
fffff880`05f1bbe0 fffff800`028df1d3 : fffffa80`059a2060 00000000`03026630 00000000`00004000 00000000`05ed07c0 : nt!NtQuerySystemInformation+0x4d
fffff880`05f1bc20 00000000`77b3e83a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01e6b778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b3e83a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiIdentifyPfn+23f
fffff800`0298083f 4c8b7500 mov r14,qword ptr [rbp]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiIdentifyPfn+23f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 49ee9439

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f

BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f

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

I hope I've provided all the necessary information needed in order to identify the problem. If there is anything else, please let me know. Again, I appreciate the help.

Also, nice site by the way!

 

[aln688]

Without giving you a 20 paragraph e-mail, first of all I have to ask, are you overclocking your system? That's the first point.

For blue screens like this, I would think the likely causes are, in no particular order:

1) A RAM module is defective
2) Overclocking with voltages too low
3) Hardware drivers

If I were you, try this:

1) Remove the sound card
2) Remove any other card plugged into the motherboard, except the graphics card of course.
3) Download this, Memtest86+, which makes sure your RAM is not defective:

http://www.memtest.org/download/2.11/memtest86+-2.11.iso.zip

Unzip it, burn it to a CD-ROM, then boot from the CD.

If that produces no errors, keep all your other cards unplugged, then go into your BIOS and find the option to "Load Setup Defaults". If you have to, enable AHCI for your drives, depends on whether you had this set when you installed Windows 7.

After Load Setup Defaults, boot into Windows 7 in Safe Mode. Play around in Windows 7 for a while, see if it crashes or not. If not, reboot in normal mode. Then download this, the NVidia Windows 7 64-bit driver:

GeForce/ION Driver Release 185

Install it and see if that helps. Basically with problems like this, you know it's not Windows 7 as everyone would have this problem if it were, it must be a knock-on effect from hardware. So you eliminate the hardware angle by removing hardware, and keep it removed until the problem goes away and add the hardware back one by one.

Let me know the situation after performing these steps.

 

[nuvas]

So far I've run the memtest on extended testing and it found nothing. I don't have any cards plugged into the board except the video card. The sound is onboard. I'm not overclocking. I've run the 185.85 nvidia drivers before but I'll try them again. I've not yet bluescreened but I will post as soon as it happens again. Thanks for the advice.

 

[aln688]

Good about the Memtest86+ results.

In that case, disable the sound, firewire and network ports on your motherboard through the BIOS. Doing this will eliminate the potential of faulty drivers being installed in Windows.

Once those integrated devices are disabled, boot your Windows 7 in safe mode, try it out, then boot in normal mode, and install that NVidia driver I gave you. Make sure before you install, fully remove any previous driver.

 

[nuvas]

Just randomly bluescreened like usual when I went to open Thunderbird.

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


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

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02a08000 PsLoadedModuleList = 0xfffff800`02c41e90
Debug session time: Thu Jun 4 02:18:40.665 2009 (GMT-4)
System Uptime: 0 days 7:10:26.538
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa808ae49718, 2, 0, fffff80002a655ba}

Probably caused by : memory_corruption ( nt!MiResolveProtoPteFault+13a )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa808ae49718, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a655ba, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cac0e0
fffffa808ae49718

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiResolveProtoPteFault+13a
fffff800`02a655ba 488b00 mov rax,qword ptr [rax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: thunderbird.ex

TRAP_FRAME: fffff880061f9790 -- (.trap 0xfffff880061f9790)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa808ae49718 rbx=0000000000000000 rcx=0000000000000004
rdx=00000000000a8dca rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a655ba rsp=fffff880061f9920 rbp=fffff8a001818610
r8=0000000000000000 r9=0000000fffffffff r10=0000058000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!MiResolveProtoPteFault+0x13a:
fffff800`02a655ba 488b00 mov rax,qword ptr [rax] ds:8520:fffffa80`8ae49718=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a864e9 to fffff80002a86f80

STACK_TEXT:
fffff880`061f9648 fffff800`02a864e9 : 00000000`0000000a fffffa80`8ae49718 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`061f9650 fffff800`02a85160 : 00000000`00000000 00000000`a8dca121 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`061f9790 fffff800`02a655ba : fffff880`061f9a80 fffffa80`04483300 00000000`00000000 fffff800`02e29bf6 : nt!KiPageFault+0x260
fffff880`061f9920 fffff800`02a97c1e : 00000000`76149778 00000000`76149778 fffff680`003b0a48 fffffa80`04483718 : nt!MiResolveProtoPteFault+0x13a
fffff880`061f99b0 fffff800`02a94c23 : 00000000`00000000 00000000`76149778 00000000`00000000 fffff800`00000000 : nt!MiDispatchFault+0x1de
fffff880`061f9ac0 fffff800`02a8506e : 00000000`00000008 00000000`003cbfc8 00000000`7efdb001 fffffa80`00000004 : nt!MmAccessFault+0x343
fffff880`061f9c20 00000000`76149778 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0018f314 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76149778


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiResolveProtoPteFault+13a
fffff800`02a655ba 488b00 mov rax,qword ptr [rax]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiResolveProtoPteFault+13a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 49ee9439

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiResolveProtoPteFault+13a

BUCKET_ID: X64_0xA_nt!MiResolveProtoPteFault+13a

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

Have not yet tried disabling the network/firewire/sound in BIOS and messing around in safe mode yet. The bluescreens typically don't happen for several hours of doing things, so not sure booting into safe mode for a little while would be effective for troubleshooting purposes.

I had hoped through examining the dump files someone could figure out the rogue driver causing the issue. Is this not the case? Event Viewer has really not been any help either. I'm not really familiar with windows debugging but there is some way to identify exactly what caused the problem isn't there?

 

[Chappy]

I do NOT hold allot of faith in Memtest, and neither should you.
A few years ago I had an exasperating issue of random service errors causing hard stops, never really the same service caused the issue, and that usually points to a faulty RAM stick depemding on which service is loaded into a faulty ram address.

5 times I did 20 passes with Memtest, those of you who have run it know how frikkin LONG that takes each pass...anyway, it always reported everything was OK.
Yet when I took out my second stick, all errors stopped, if I put it back it all started again. Replaced that stick and never had the problem again, obviously a faulty stick yet Memtest said it was fine.

Try removing sticks and see if that fixes this or not. I haven't had time to read all your bug reports to see what modules are faulting but the randomness you state has me thinking of RAM.

 

[nuvas]

I do NOT hold allot of faith in Memtest, and neither should you.
A few years ago I had an exasperating issue of random service errors causing hard stops, never really the same service caused the issue, and that usually points to a faulty RAM stick depemding on which service is loaded into a faulty ram address.

5 times I did 20 passes with Memtest, those of you who have run it know how frikkin LONG that takes each pass...anyway, it always reported everything was OK.
Yet when I took out my second stick, all errors stopped, if I put it back it all started again. Replaced that stick and never had the problem again, obviously a faulty stick yet Memtest said it was fine.

Try removing sticks and see if that fixes this or not. I haven't had time to read all your bug reports to see what modules are faulting but the randomness you state has me thinking of RAM.

I did actually purchase some new memory when I picked up a new hard drive to test out Win7. It's entirely possible that there is something wrong with it. I replaced the old 2gigs with a new 4gigs so I think in addition to your suggestion I may just replace the sticks with my old memory and see if the stability issues go away. Once again, I really appreciate the help guys.

 

[aln688]

I saw two things in the logs that were interesting:

"Probably caused by : memory_corruption ( nt!MiResolveProtoPteFault+13a )"

...and...

"An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses."

It could be memory of course, and it could likely be drivers. Try what the other user said, remove memory sticks to try and eliminate a bad stick. What make is your memory modules?

If that doesn't help, then as much as you might not like to hear this, re-install Windows 7 from fresh, no upgrade. Once it's installed try it out with NO drivers installed from you, let it run with the drivers it comes with. As said, disable all of the integrated devices in your BIOS before you do this, if it is a driver, the less hardware Windows finds, the less drivers it'll install to support it.

This one is difficult to check easily, but make sure the power supply you're using has sufficient power to run your system, and it's a good quality power supply as well.

 

[ooze]

built by AMD?

Is it strange that the beginning of his dump has the following:

Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700

I'm having identical issues on my machine and have the same Built by attribute value. Furthermore, all the drivers in my DriverStore\FileRepository\ folder follow a naming convention like *.inf_amd64_neutral_*

Maybe it's nothing, but it did strike me as abnormal...

edit:
I should probably point out that we're both have Intel E6600's.

My system specs:
Intel Core2Duo E6600
MSI platinum 975x powerup
4GB CORSAIR XMS2 DDR2 800
nvidia 9800 gt

 

[nuvas]

Sorry to bump this but wanted to report the problem. It was improper memory voltage. I appreciate all the help guys.