HELP ME DUDERS! No, really. Help. Please.

[weemadando]

OK, so I've had 4 BSODs since upgrading my PC and am trying to pin down the cause. I suspect it's a video card driver issue given what I've seen in this .dmp file, but can people have a look at this and tell me if there's another issue I'm missing?

Code: Select all

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at end of path element
Symbol search path is: srv*e:\symbols\*http://msdl.microsoft.com/download/symbols;srv*e:\symbols\*http://msdl.microsoft.com/download/symbols. 
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0320b000 PsLoadedModuleList = 0xfffff800`03448e50
Debug session time: Thu Nov 17 18:29:48.729 2011 (UTC + 11:00)
System Uptime: 0 days 22:54:57.245
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff800032c2349, fffff880009a9998, fffff880009a9200}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800032c2349, The address that the exception occurred at
Arg3: fffff880009a9998, Exception Record Address
Arg4: fffff880009a9200, Context Record Address

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!MmZeroPageThread+3d4
fffff800`032c2349 f0410fba6d1000  lock bts dword ptr [r13+10h],0

EXCEPTION_RECORD:  fffff880009a9998 -- (.exr 0xfffff880009a9998)
ExceptionAddress: fffff800032c2349 (nt!MmZeroPageThread+0x00000000000003d4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a9200 -- (.cxr 0xfffff880009a9200)
rax=0000000000000032 rbx=85ffffffffffffff rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa80069011d0 rdi=0000000000000032
rip=fffff800032c2349 rsp=fffff880009a9bd0 rbp=000000000000003f
 r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
r11=fffff880009a9bc8 r12=000000000000000a r13=1ffffa7fffffffd0
r14=0000000000000040 r15=fffff800033f5e80
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!MmZeroPageThread+0x3d4:
fffff800`032c2349 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:002b:1ffffa7f`ffffffe0=????????
Resetting default scope

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff 

FOLLOWUP_IP: 
nt!MmZeroPageThread+3d4
fffff800`032c2349 f0410fba6d1000  lock bts dword ptr [r13+10h],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8000351fc06 to fffff800032c2349

STACK_TEXT:  
fffff880`009a9bd0 fffff800`0351fc06 : fffffa80`06a215b0 00000000`00000080 fffffa80`06a21b30 fffff800`03259c19 : nt!MmZeroPageThread+0x3d4
fffff880`009a9d00 fffff800`03259c26 : fffff800`033f5e80 fffffa80`06a215b0 fffff800`03403c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmZeroPageThread+3d4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff880009a9200 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4

BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800032c2349, The address that the exception occurred at
Arg3: fffff880009a9998, Exception Record Address
Arg4: fffff880009a9200, Context Record Address

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!MmZeroPageThread+3d4
fffff800`032c2349 f0410fba6d1000  lock bts dword ptr [r13+10h],0

EXCEPTION_RECORD:  fffff880009a9998 -- (.exr 0xfffff880009a9998)
ExceptionAddress: fffff800032c2349 (nt!MmZeroPageThread+0x00000000000003d4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a9200 -- (.cxr 0xfffff880009a9200)
rax=0000000000000032 rbx=85ffffffffffffff rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa80069011d0 rdi=0000000000000032
rip=fffff800032c2349 rsp=fffff880009a9bd0 rbp=000000000000003f
 r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
r11=fffff880009a9bc8 r12=000000000000000a r13=1ffffa7fffffffd0
r14=0000000000000040 r15=fffff800033f5e80
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!MmZeroPageThread+0x3d4:
fffff800`032c2349 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:002b:1ffffa7f`ffffffe0=????????
Resetting default scope

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff 

FOLLOWUP_IP: 
nt!MmZeroPageThread+3d4
fffff800`032c2349 f0410fba6d1000  lock bts dword ptr [r13+10h],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8000351fc06 to fffff800032c2349

STACK_TEXT:  
fffff880`009a9bd0 fffff800`0351fc06 : fffffa80`06a215b0 00000000`00000080 fffffa80`06a21b30 fffff800`03259c19 : nt!MmZeroPageThread+0x3d4
fffff880`009a9d00 fffff800`03259c26 : fffff800`033f5e80 fffffa80`06a215b0 fffff800`03403c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmZeroPageThread+3d4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff880009a9200 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4

BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4

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

[Dominus Atheos]

Here's the Microsoft kb article on the issue. it has a hotfix that it says will fix the problem.

The issue was most likely caused by a USB video device, like a webcam.

[weemadando]

I've got no USB video stuff, but I'll give it a shot as the new vidja card might be triggering something.

[weemadando]

Aaaand it just went down again. Here's the most recent minidump and two other earlier examples after it. I'm beginning to think it's my GPU drivers or a dud Video RAM given some of the errors that are cropping up. But, I only ever get a BSOD, I haven't had artefacting or any of the other telltales that people describe.

Ideas? Exorcisms?

Code: Select all

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8000331c349, fffff880009a9998, fffff880009a9200}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8000331c349, The address that the exception occurred at
Arg3: fffff880009a9998, Exception Record Address
Arg4: fffff880009a9200, Context Record Address

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!MmZeroPageThread+3d4
fffff800`0331c349 f0410fba6d1000  lock bts dword ptr [r13+10h],0

EXCEPTION_RECORD:  fffff880009a9998 -- (.exr 0xfffff880009a9998)
ExceptionAddress: fffff8000331c349 (nt!MmZeroPageThread+0x00000000000003d4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a9200 -- (.cxr 0xfffff880009a9200)
rax=0000000000000012 rbx=00ffffffffffffff rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8006900cd0 rdi=0000000000000012
rip=fffff8000331c349 rsp=fffff880009a9bd0 rbp=000000000000003f
 r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
r11=000000000000000a r12=0000000000000000 r13=2ffffa7fffffffd0
r14=0000000000000040 r15=fffff80003265000
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!MmZeroPageThread+0x3d4:
fffff800`0331c349 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:002b:2ffffa7f`ffffffe0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350d0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!MmZeroPageThread+3d4
fffff800`0331c349 f0410fba6d1000  lock bts dword ptr [r13+10h],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80003579c06 to fffff8000331c349

STACK_TEXT:  
fffff880`009a9bd0 fffff800`03579c06 : fffffa80`06a075b0 00000000`00000080 fffffa80`06a07b30 fffff800`032b3c19 : nt!MmZeroPageThread+0x3d4
fffff880`009a9d00 fffff800`032b3c26 : fffff800`0344fe80 fffffa80`06a075b0 fffff800`0345dc40 db6c0212`549bc769 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmZeroPageThread+3d4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff880009a9200 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4

BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4

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

Here are some older ones:

Code: Select all

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa7fffffffe0, 2, 1, fffff800032e4f9e}

Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+13e )

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: fffffa7fffffffe0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff800032e4f9e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034f70e0
 fffffa7fffffffe0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiRemoveAnyPage+13e
fffff800`032e4f9e f0410fba6c241000 lock bts dword ptr [r12+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002fcc620 -- (.trap 0xfffff88002fcc620)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032e4f9e rsp=fffff88002fcc7b0 rbp=fffff88002fcc800
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiRemoveAnyPage+0x13e:
fffff800`032e4f9e f0410fba6c241000 lock bts dword ptr [r12+10h],0 ds:2df8:00000000`00000010=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032beca9 to fffff800032bf740

STACK_TEXT:  
fffff880`02fcc4d8 fffff800`032beca9 : 00000000`0000000a fffffa7f`ffffffe0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02fcc4e0 fffff800`032bd920 : fffffa80`0a873bd0 00000000`00000012 00000000`14290000 fffff6fc`c0235c78 : nt!KiBugCheckDispatch+0x69
fffff880`02fcc620 fffff800`032e4f9e : fffff800`034f9840 00000000`000a8573 fffffa80`01f90590 fffffa80`09eba900 : nt!KiPageFault+0x260
fffff880`02fcc7b0 fffff800`0328374d : fa800b7a`bdc004c0 00000000`00000000 00000000`000002b0 00000000`00000000 : nt!MiRemoveAnyPage+0x13e
fffff880`02fcc8d0 fffff800`0355fa22 : fffffa80`0b64abe0 fffffa80`00000001 fffffa80`0b64abe0 00000000`00000005 : nt!MiPfPutPagesInTransition+0x764
fffff880`02fcca40 fffff800`03271a67 : fffffa80`0b64abe0 00000000`0a840000 00000000`0a840000 fffff800`034645a0 : nt!MmPrefetchForCacheManager+0x96
fffff880`02fcca90 fffff800`032b3576 : fffffa80`0bde4580 fffffa80`06a1db00 fffff880`00000000 fffff880`03d3f734 : nt!CcPerformReadAhead+0x2f3
fffff880`02fccbc0 fffff800`032cc961 : fffffa80`06a1a800 fffff880`016ab010 fffff800`034c6150 00000000`00000002 : nt!CcWorkerThread+0x21e
fffff880`02fccc70 fffff800`03563c06 : 00000000`00000000 fffffa80`06a1db60 00000000`00000080 fffffa80`06a07b30 : nt!ExpWorkerThread+0x111
fffff880`02fccd00 fffff800`0329dc26 : fffff880`009e7180 fffffa80`06a1db60 fffff880`009f1f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fccd40 00000000`00000000 : fffff880`02fcd000 fffff880`02fc7000 fffff880`02fcc9b0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRemoveAnyPage+13e
fffff800`032e4f9e f0410fba6c241000 lock bts dword ptr [r12+10h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiRemoveAnyPage+13e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiRemoveAnyPage+13e

BUCKET_ID:  X64_0xA_nt!MiRemoveAnyPage+13e

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

Code: Select all

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80003314349, The address that the exception occurred at
Arg3: fffff880009a9998, Exception Record Address
Arg4: fffff880009a9200, Context Record Address

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!MmZeroPageThread+3d4
fffff800`03314349 f0410fba6d1000  lock bts dword ptr [r13+10h],0

EXCEPTION_RECORD:  fffff880009a9998 -- (.exr 0xfffff880009a9998)
ExceptionAddress: fffff80003314349 (nt!MmZeroPageThread+0x00000000000003d4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a9200 -- (.cxr 0xfffff880009a9200)
rax=000000000000002e rbx=0bffffffffffffff rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8006901130 rdi=000000000000002e
rip=fffff80003314349 rsp=fffff880009a9bd0 rbp=000000000000003f
 r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
r11=fffff880009a9bc8 r12=0000000000000005 r13=3ffffa7fffffffd0
r14=0000000000000040 r15=fffff880009e7180
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!MmZeroPageThread+0x3d4:
fffff800`03314349 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:002b:3ffffa7f`ffffffe0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800035050e0
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!MmZeroPageThread+3d4
fffff800`03314349 f0410fba6d1000  lock bts dword ptr [r13+10h],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80003571c06 to fffff80003314349

STACK_TEXT:  
fffff880`009a9bd0 fffff800`03571c06 : fffffa80`06a075b0 00000000`00000080 fffffa80`06a07b30 fffff800`032abc19 : nt!MmZeroPageThread+0x3d4
fffff880`009a9d00 fffff800`032abc26 : fffff800`03447e80 fffffa80`06a075b0 fffff800`03455c40 fbc33715`ff20498b : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmZeroPageThread+3d4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff880009a9200 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4

BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80003314349, The address that the exception occurred at
Arg3: fffff880009a9998, Exception Record Address
Arg4: fffff880009a9200, Context Record Address

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!MmZeroPageThread+3d4
fffff800`03314349 f0410fba6d1000  lock bts dword ptr [r13+10h],0

EXCEPTION_RECORD:  fffff880009a9998 -- (.exr 0xfffff880009a9998)
ExceptionAddress: fffff80003314349 (nt!MmZeroPageThread+0x00000000000003d4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a9200 -- (.cxr 0xfffff880009a9200)
rax=000000000000002e rbx=0bffffffffffffff rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8006901130 rdi=000000000000002e
rip=fffff80003314349 rsp=fffff880009a9bd0 rbp=000000000000003f
 r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
r11=fffff880009a9bc8 r12=0000000000000005 r13=3ffffa7fffffffd0
r14=0000000000000040 r15=fffff880009e7180
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!MmZeroPageThread+0x3d4:
fffff800`03314349 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:002b:3ffffa7f`ffffffe0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff 

FOLLOWUP_IP: 
nt!MmZeroPageThread+3d4
fffff800`03314349 f0410fba6d1000  lock bts dword ptr [r13+10h],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80003571c06 to fffff80003314349

STACK_TEXT:  
fffff880`009a9bd0 fffff800`03571c06 : fffffa80`06a075b0 00000000`00000080 fffffa80`06a07b30 fffff800`032abc19 : nt!MmZeroPageThread+0x3d4
fffff880`009a9d00 fffff800`032abc26 : fffff800`03447e80 fffffa80`06a075b0 fffff800`03455c40 fbc33715`ff20498b : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmZeroPageThread+3d4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff880009a9200 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4

BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4

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

[Tolya]

What exactly have you upgraded? If you can, try removing some of the new components and/or replacing them with old ones.

To me it looks like you RAM (either main or on your video card) might be corrupted, but that's just an educated guess.

[weemadando]

Upgraded RAM and GPU.

Have stripped out all my drivers, windows updated and then rolled everything back in with latest versions. Has been okay since then, but that's only 12 hours.

Temperatures and voltages are stable and normal. BSODs have happened while idling and under load. No odd behaviour happens when the system is under load, no artefacts or crashes.

Hopefully it was a legacy driver conflict or something. Some lost DLL or whatever.

I really hope I've seen the last one.

Next step is isolation testing.