Windows 7: Random BSOD ntoskrnl.exe+7c1e9

Mesmo · 18 Jan 2012

This Blue Screen happens randomly. Could be gaming, watching video, or just idle. Windows Ultimate 7 64Bit Full Retail Less than 1 Year on all hardware except HD's. Hd's are less than 2 Years. Mobo: Gigabyte GA-880GA-UD3H Cpu: AMD Phenom II X6 1075T 3.0Ghz Vcard: Geforce GTX 460 If you look at the dump and notice a video card driver fail. Ive already fixed that 1 (nvldd) Any advice would be every helpful been trying to figure this out on my own for at least 3 months

Was looking around at other nto bsod topics and some mentioned driver verifier.
Ive tested that recently and i cant even boot up without blue screening.

Ive also ran memtest and all the ram sticks came back pass

Was looking over perfmon and it says i have no anti virus which i do its Kaspersky KIS 2012.
The Printer device drivers are intentionally disabled

writhziden · 18 Jan 2012

Code:


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mesmo\Windows_NT6_BSOD_jcgriff2\011212-21247-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a5b000 PsLoadedModuleList = 0xfffff800`03ca0670
Debug session time: Thu Jan 12 00:58:49.714 2012 (UTC - 7:00)
System Uptime: 0 days 11:25:47.932
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80003b0ac81, fffff880039920e8, fffff88003991940}

Probably caused by : memory_corruption ( nt!MiGetNextNode+15 )

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

0: 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: fffff80003b0ac81, The address that the exception occurred at
Arg3: fffff880039920e8, Exception Record Address
Arg4: fffff88003991940, 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!MiGetNextNode+15
fffff800`03b0ac81 48394808        cmp     qword ptr [rax+8],rcx

EXCEPTION_RECORD:  fffff880039920e8 -- (.exr 0xfffff880039920e8)
ExceptionAddress: fffff80003b0ac81 (nt!MiGetNextNode+0x0000000000000015)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003991940 -- (.cxr 0xfffff88003991940)
rax=f7fffa800769e750 rbx=fffffa8006a59b60 rcx=fffffa800a3cacb0
rdx=fffffa8007acb918 rsi=fffffa800a144d48 rdi=fffffa800a3cacb0
rip=fffff80003b0ac81 rsp=fffff88003992328 rbp=fffffa8009c10e30
 r8=0000000000000009  r9=00000000000007ff r10=0000000000000801
r11=0000000000000000 r12=fffff8a011109000 r13=0000000000000000
r14=fffff8a011109078 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!MiGetNextNode+0x15:
fffff800`03b0ac81 48394808        cmp     qword ptr [rax+8],rcx ds:002b:f7fffa80`0769e758=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  avp.exe

CURRENT_IRQL:  0

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 fffff80003d0a100
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!MiGetNextNode+15
fffff800`03b0ac81 48394808        cmp     qword ptr [rax+8],rcx

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80003e6f000 to fffff80003b0ac81

STACK_TEXT:  
fffff880`03992328 fffff800`03e6f000 : 00001104`00000bc0 fffffa80`06a59b60 fffff880`09160000 00000000`03450000 : nt!MiGetNextNode+0x15
fffff880`03992330 fffff800`03eb37c1 : fffffa80`0a144b30 00000000`00001403 fffffa80`0b79f000 fffff800`03e6a98f : nt!MmEnumerateAndReferenceImages+0x160
fffff880`039923b0 fffff800`03eb39fe : fffffa80`0a144b30 fffff800`03eb3801 fffff800`03eb3801 fffff880`039924d0 : nt!EtwpEnumerateImages+0x51
fffff880`03992400 fffff800`03e6a906 : fffffa80`0a03eb30 fffffa80`0a144b30 fffff800`03eb3860 fffff880`039924d0 : nt!EtwpProcessEnumCallback+0x19e
fffff880`03992480 fffff800`03eb3b81 : fffff880`039925d8 fffffa80`07c0ef01 00000000`00000001 00000000`00000001 : nt!PsEnumProcesses+0x26
fffff880`039924b0 fffff800`03eb3bd7 : 00000000`00000000 00000000`00000000 00000000`00000020 00000000`00000000 : nt!EtwpProcessThreadImageRundown+0x51
fffff880`03992500 fffff800`03f1f8a8 : 00000000`00401802 fffffa80`07c0ef28 00000000`00000000 fffff800`03c79860 : nt!EtwpKernelTraceRundown+0x47
fffff880`03992530 fffff800`03e35b8d : 00000000`00000000 fffff8a0`0baab9d0 00000000`00000000 00000000`00000000 : nt!EtwpUpdateLoggerGroupMasks+0x268
fffff880`03992630 fffff800`03f43bf6 : fffff8a0`0baab9d0 fffff8a0`0baab9d0 00000000`00000000 fffff800`03c808e6 : nt! ?? ::NNGAKEGL::`string'+0x54ef4
fffff880`03992730 fffff800`03f43fa3 : 00000000`00000010 ffffffff`80003768 00000000`00000001 00000000`00000001 : nt!EtwpStartAutoLogger+0x8e6
fffff880`03992c40 fffff800`03f46d9f : ffffffff`ffffffff 00000000`00000000 ffffffff`fff85ee0 00000000`00000001 : nt!PerfDiagpRestartCKCL+0x63
fffff880`03992c70 fffff800`03ae2001 : fffff800`000000b0 fffff800`03f46b70 fffff800`03c782b8 fffffa80`06a59b60 : nt!PerfDiagpProxyWorker+0x22f
fffff880`03992cb0 fffff800`03d72fee : 00000000`00000000 fffffa80`06a59b60 00000000`00000080 fffffa80`069acb30 : nt!ExpWorkerThread+0x111
fffff880`03992d40 fffff800`03ac95e6 : fffff880`03888180 fffffa80`06a59b60 fffff880`03893040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03992d80 00000000`00000000 : fffff880`03993000 fffff880`0398d000 fffff880`03992180 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiGetNextNode+15

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff88003991940 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MiGetNextNode+15

BUCKET_ID:  X64_0x7E_nt!MiGetNextNode+15

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mesmo\Windows_NT6_BSOD_jcgriff2\011312-20654-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a1d000 PsLoadedModuleList = 0xfffff800`03c62670
Debug session time: Fri Jan 13 15:35:02.507 2012 (UTC - 7:00)
System Uptime: 0 days 0:23:08.741
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3835363736396166
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9c3a8 -- (.exr 0xfffff80000b9c3a8)
ExceptionAddress: fffff80003aa54f9 (nt!KiProcessExpiredTimerList+0x0000000000000129)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9c450 -- (.trap 0xfffff80000b9c450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8006e11088 rbx=0000000000000000 rcx=f7fffa8006e11088
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003aa54f9 rsp=fffff80000b9c5e0 rbp=fffffa8006c20c68
 r8=fffff80003c12001  r9=0000000000000003 r10=00000000000000bd
r11=fffffa80089415f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiProcessExpiredTimerList+0x129:
fffff800`03aa54f9 48894108        mov     qword ptr [rcx+8],rax ds:f7fffa80`06e11090=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003a915fe to fffff80003a99c10

STACK_TEXT:  
fffff800`00b9b488 fffff800`03a915fe : fffff800`00b9ab30 00000000`00000003 fffff800`00b9bc00 fffff800`03ac5830 : nt!KeBugCheck
fffff800`00b9b490 fffff800`03ac54fd : fffff800`03ca371c fffff800`03be0c30 fffff800`03a1d000 fffff800`00b9c3a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b4c0 fffff800`03ac42d5 : fffff800`03be40fc fffff800`00b9b538 fffff800`00b9c3a8 fffff800`03a1d000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b4f0 fffff800`03ad5361 : fffff800`00b9c3a8 fffff800`00b9bc00 fffff800`00000000 fffffa80`06e11080 : nt!RtlDispatchException+0x415
fffff800`00b9bbd0 fffff800`03a992c2 : fffff800`00b9c3a8 fffffa80`06c20c68 fffff800`00b9c450 00000000`00000000 : nt!KiDispatchException+0x135
fffff800`00b9c270 fffff800`03a97bca : fffffa80`071794a0 fffffa80`000e0082 ffff001b`00000060 00000000`40dfff21 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c450 fffff800`03aa54f9 : fffffa80`06c20c20 fffffa80`06c26768 00000000`00000000 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c5e0 fffff800`03aa537e : 00000003`3bc1138a fffff800`00b9cc58 00000000`00015bbd fffff800`03c13a28 : nt!KiProcessExpiredTimerList+0x129
fffff800`00b9cc30 fffff800`03aa5167 : 00000000`f3a9f4c2 00000000`00015bbd 00000000`f3a9f498 00000000`000000bd : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03a9196a : fffff800`03c0fe80 fffff800`03c1dcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`03a915fe 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mesmo\Windows_NT6_BSOD_jcgriff2\011412-19203-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a15000 PsLoadedModuleList = 0xfffff800`03c5a670
Debug session time: Sat Jan 14 17:54:12.608 2012 (UTC - 7:00)
System Uptime: 0 days 5:17:42.826
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003a85204, fffff8800863a050, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+d4 )

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

2: 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: fffff80003a85204, Address of the instruction which caused the bugcheck
Arg3: fffff8800863a050, 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!KiDeliverApc+d4
fffff800`03a85204 498b4a30        mov     rcx,qword ptr [r10+30h]

CONTEXT:  fffff8800863a050 -- (.cxr 0xfffff8800863a050)
rax=0000000000000002 rbx=fffffa8006fbc660 rcx=0000000000000001
rdx=0000000000000000 rsi=fffffa8006fbc6b0 rdi=fffffa8006fbc660
rip=fffff80003a85204 rsp=fffff8800863aa30 rbp=0000000000000000
 r8=f7fffa8006fbc6b0  r9=0000000000000000 r10=f7fffa8006fbc6a0
r11=0000000000100003 r12=0000000000000001 r13=0000000000000600
r14=fffffa800a3ef730 r15=fffff8800863ac20
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!KiDeliverApc+0xd4:
fffff800`03a85204 498b4a30        mov     rcx,qword ptr [r10+30h] ds:002b:f7fffa80`06fbc6d0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003a3ef35 to fffff80003a85204

STACK_TEXT:  
fffff880`0863aa30 fffff800`03a3ef35 : 00000000`00000000 00000000`00000000 fffffa80`06fbc720 00000000`00000000 : nt!KiDeliverApc+0xd4
fffff880`0863aab0 fffff800`03d8835e : fffff780`00000008 fffff800`03a96f32 fffffa80`06fbc660 fffffa80`06fbc660 : nt!KiCheckForKernelApcDelivery+0x25
fffff880`0863aae0 fffff800`03d88405 : 00000000`74ee2400 00000000`00100000 00000000`00000000 00000000`7eedf001 : nt!ObReferenceObjectByHandleWithTag+0x3ce
fffff880`0863abb0 fffff800`03a90ed3 : fffffa80`06fbc660 00000000`3029ea04 00000000`00000000 fffffa80`0a73ed30 : nt!NtWaitForSingleObject+0x95
fffff880`0863ac20 00000000`74ee2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0d16f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74ee2e09


FOLLOWUP_IP: 
nt!KiDeliverApc+d4
fffff800`03a85204 498b4a30        mov     rcx,qword ptr [r10+30h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiDeliverApc+d4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff8800863a050 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiDeliverApc+d4

BUCKET_ID:  X64_0x3B_nt!KiDeliverApc+d4

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mesmo\Windows_NT6_BSOD_jcgriff2\011512-17924-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a17000 PsLoadedModuleList = 0xfffff800`03c5c670
Debug session time: Sun Jan 15 12:33:56.473 2012 (UTC - 7:00)
System Uptime: 0 days 0:19:21.707
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff95ff8114bb0, 8, fffff95ff8114bb0, 5}

Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Could not read faulting driver name
Probably caused by : win32k.sys ( win32k+87488 )

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

0: 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: fffff95ff8114bb0, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff95ff8114bb0, 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 fffff80003cc6100
 fffff95ff8114bb0 

FAULTING_IP: 
+3835363736396166
fffff95f`f8114bb0 ??              ???

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  League of Lege

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800bc46a20 -- (.trap 0xfffff8800bc46a20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c2dc8c20 rbx=0000000000000000 rcx=00000000001a030b
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff95ff8114bb0 rsp=fffff8800bc46bb8 rbp=00000000001a030b
 r8=0000000076c8420b  r9=0000000076c7743b r10=fffff9600016d108
r11=000000007efdb000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff95f`f8114bb0 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003a3e3bf to fffff80003a93c40

STACK_TEXT:  
fffff880`0bc468b8 fffff800`03a3e3bf : 00000000`00000050 fffff95f`f8114bb0 00000000`00000008 fffff880`0bc46a20 : nt!KeBugCheckEx
fffff880`0bc468c0 fffff800`03a91d6e : 00000000`00000008 fffff95f`f8114bb0 00000002`b4b92900 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`0bc46a20 fffff95f`f8114bb0 : fffff960`00117488 00000000`0008fd20 fffffa80`07ac9b60 fffff880`0bc46ca0 : nt!KiPageFault+0x16e
fffff880`0bc46bb8 fffff960`00117488 : 00000000`0008fd20 fffffa80`07ac9b60 fffff880`0bc46ca0 fffff880`0bc46c38 : 0xfffff95f`f8114bb0
fffff880`0bc46bc0 00000000`0008fd20 : fffffa80`07ac9b60 fffff880`0bc46ca0 fffff880`0bc46c38 00000000`001a030b : win32k+0x87488
fffff880`0bc46bc8 fffffa80`07ac9b60 : fffff880`0bc46ca0 fffff880`0bc46c38 00000000`001a030b fffff960`0016d141 : 0x8fd20
fffff880`0bc46bd0 fffff880`0bc46ca0 : fffff880`0bc46c38 00000000`001a030b fffff960`0016d141 00000000`00000000 : 0xfffffa80`07ac9b60
fffff880`0bc46bd8 fffff880`0bc46c38 : 00000000`001a030b fffff960`0016d141 00000000`00000000 fffff880`0bc46ca0 : 0xfffff880`0bc46ca0
fffff880`0bc46be0 00000000`001a030b : fffff960`0016d141 00000000`00000000 fffff880`0bc46ca0 00000000`00000000 : 0xfffff880`0bc46c38
fffff880`0bc46be8 fffff960`0016d141 : 00000000`00000000 fffff880`0bc46ca0 00000000`00000000 00000000`7efdb000 : 0x1a030b
fffff880`0bc46bf0 00000000`00000000 : fffff880`0bc46ca0 00000000`00000000 00000000`7efdb000 00000000`00000020 : win32k+0xdd141


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k+87488
fffff960`00117488 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32k+87488

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ecdcd5b

FAILURE_BUCKET_ID:  X64_0x50_win32k+87488

BUCKET_ID:  X64_0x50_win32k+87488

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mesmo\Windows_NT6_BSOD_jcgriff2\011512-18891-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a4b000 PsLoadedModuleList = 0xfffff800`03c90670
Debug session time: Sun Jan 15 16:32:19.748 2012 (UTC - 7:00)
System Uptime: 0 days 3:57:40.605
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3064356231386535
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  League of Lege

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880009b05d8 -- (.exr 0xfffff880009b05d8)
ExceptionAddress: fffff80003ad34f9 (nt!KiProcessExpiredTimerList+0x0000000000000129)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880009b0680 -- (.trap 0xfffff880009b0680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80071da8b8 rbx=0000000000000000 rcx=f7fffa80071da8b8
rdx=fffff88003768700 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003ad34f9 rsp=fffff880009b0810 rbp=fffffa800c11aaf8
 r8=fffffa8009056c00  r9=0000000000000008 r10=fffff80003a4b000
r11=fffff880009b07e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiProcessExpiredTimerList+0x129:
fffff800`03ad34f9 48894108        mov     qword ptr [rcx+8],rax ds:f7fffa80`071da8c0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003abf5fe to fffff80003ac7c10

STACK_TEXT:  
fffff880`009af6b8 fffff800`03abf5fe : fffff880`0184c9a0 fffffa80`086b1100 fffff880`009afe30 fffff800`03af3830 : nt!KeBugCheck
fffff880`009af6c0 fffff800`03af34fd : fffff800`03cd171c fffff800`03c0ec30 fffff800`03a4b000 fffff880`009b05d8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009af6f0 fffff800`03af22d5 : fffff800`03c12028 fffff880`009af768 fffff880`009b05d8 fffff800`03a4b000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009af720 fffff800`03b03361 : fffff880`009b05d8 fffff880`009afe30 fffff880`00000000 fffffa80`071da8b0 : nt!RtlDispatchException+0x415
fffff880`009afe00 fffff800`03ac72c2 : fffff880`009b05d8 fffffa80`0c11aaf8 fffff880`009b0680 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`009b04a0 fffff800`03ac5bca : fffffa80`080a81a0 fffff880`0154710c fffff880`009b0830 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`009b0680 fffff800`03ad34f9 : fffffa80`0aacdc20 fffffa80`09056c68 fffffa80`09056c68 fffffa80`0c11aa90 : nt!KiGeneralProtectionFault+0x10a
fffff880`009b0810 fffff800`03ad337e : 00000021`33fbc09a fffff880`009b0e88 00000000`000df2d7 fffff880`037d9068 : nt!KiProcessExpiredTimerList+0x129
fffff880`009b0e60 fffff800`03ad3167 : fffff880`037d51c5 fffffa80`000df2d7 00000000`00000000 00000000`000000d7 : nt!KiTimerExpiration+0x1be
fffff880`009b0f00 fffff800`03aca765 : 00000000`00000000 fffffa80`0a9ceb60 00000000`00000000 fffff800`03be2b40 : nt!KiRetireDpcList+0x277
fffff880`009b0fb0 fffff800`03aca57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`08932be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`03abf5fe 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mesmo\Windows_NT6_BSOD_jcgriff2\011612-18064-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03814000 PsLoadedModuleList = 0xfffff800`03a59670
Debug session time: Mon Jan 16 17:18:13.512 2012 (UTC - 7:00)
System Uptime: 0 days 5:18:06.369
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003884204, fffff88009f45a00, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+d4 )

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

4: 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: fffff80003884204, Address of the instruction which caused the bugcheck
Arg3: fffff88009f45a00, 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!KiDeliverApc+d4
fffff800`03884204 498b4a30        mov     rcx,qword ptr [r10+30h]

CONTEXT:  fffff88009f45a00 -- (.cxr 0xfffff88009f45a00)
rax=0000000000000002 rbx=fffffa8009cbe060 rcx=0000000000000001
rdx=0000000000000000 rsi=fffffa8009cbe0b0 rdi=0000000000000000
rip=fffff80003884204 rsp=fffff88009f463e0 rbp=0000000000000000
 r8=f7fffa8009cbe0b0  r9=0000000000000000 r10=f7fffa8009cbe0a0
r11=fffffffffffffd80 r12=0000000000000001 r13=fffff8a002f4b000
r14=fffffa8009b6eb30 r15=fffff88009f46c20
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!KiDeliverApc+0xd4:
fffff800`03884204 498b4a30        mov     rcx,qword ptr [r10+30h] ds:002b:f7fffa80`09cbe0d0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003884204

STACK_TEXT:  
fffff880`09f463e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0xd4


FOLLOWUP_IP: 
nt!KiDeliverApc+d4
fffff800`03884204 498b4a30        mov     rcx,qword ptr [r10+30h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiDeliverApc+d4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff88009f45a00 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiDeliverApc+d4

BUCKET_ID:  X64_0x3B_nt!KiDeliverApc+d4

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mesmo\Windows_NT6_BSOD_jcgriff2\011612-20748-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a56000 PsLoadedModuleList = 0xfffff800`03c9b670
Debug session time: Tue Jan 17 00:05:11.929 2012 (UTC - 7:00)
System Uptime: 0 days 6:46:05.146
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003dc909c, fffff8800b44a000, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+10c )

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: fffff80003dc909c, Address of the instruction which caused the bugcheck
Arg3: fffff8800b44a000, 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!ObReferenceObjectByHandleWithTag+10c
fffff800`03dc909c 0fb64518        movzx   eax,byte ptr [rbp+18h]

CONTEXT:  fffff8800b44a000 -- (.cxr 0xfffff8800b44a000)
rax=f7fffa80099f1431 rbx=fffff8a004356400 rcx=f7fffa80099f1430
rdx=0000000000000002 rsi=fffff8a0037c4680 rdi=fffffa8009af8060
rip=fffff80003dc909c rsp=fffff8800b44a9e0 rbp=f7fffa80099f1430
 r8=fffff8a003b0a000  r9=0000000000000010 r10=0000000000000200
r11=000000000600ac01 r12=0000000000000000 r13=0000000000000901
r14=0000000000000001 r15=fffffa8006f09060
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ObReferenceObjectByHandleWithTag+0x10c:
fffff800`03dc909c 0fb64518        movzx   eax,byte ptr [rbp+18h] ss:0018:f7fffa80`099f1448=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  SearchIndexer.

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003de5cd3 to fffff80003dc909c

STACK_TEXT:  
fffff880`0b44a9e0 fffff800`03de5cd3 : fffff880`0b44ab00 ffffdf3a`00000002 fffffa80`06b3e9c0 fffffa80`00000001 : nt!ObReferenceObjectByHandleWithTag+0x10c
fffff880`0b44aab0 fffff800`03ad1ed3 : 00000000`00000001 00000000`00000901 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x832
fffff880`0b44abb0 00000000`77a3139a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0787ec88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a3139a


FOLLOWUP_IP: 
nt!ObReferenceObjectByHandleWithTag+10c
fffff800`03dc909c 0fb64518        movzx   eax,byte ptr [rbp+18h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObReferenceObjectByHandleWithTag+10c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff8800b44a000 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectByHandleWithTag+10c

BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectByHandleWithTag+10c

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mesmo\Windows_NT6_BSOD_jcgriff2\011712-17128-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a0b000 PsLoadedModuleList = 0xfffff800`03c50670
Debug session time: Tue Jan 17 15:25:50.244 2012 (UTC - 7:00)
System Uptime: 0 days 2:11:32.478
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8800c506188, 8, fffff8800c506188, 2}

Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Could not read faulting driver name
Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkEscape+c4c )

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

3: 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: fffff8800c506188, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff8800c506188, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003cba100
 fffff8800c506188 

FAULTING_IP: 
+3064356231386535
fffff880`0c506188 ??              ???

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800847a6d0 -- (.trap 0xfffff8800847a6d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a00faf8010 rbx=0000000000000000 rcx=fffff8800847a910
rdx=fffff880037e2000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800c506188 rsp=fffff8800847a868 rbp=fffff8800847aca0
 r8=0000000000013038  r9=0000000000000250 r10=fffff80003a0b000
r11=000000000000079b r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff880`0c506188 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003a323f0 to fffff80003a87c40

STACK_TEXT:  
fffff880`0847a568 fffff800`03a323f0 : 00000000`00000050 fffff880`0c506188 00000000`00000008 fffff880`0847a6d0 : nt!KeBugCheckEx
fffff880`0847a570 fffff800`03a85d6e : 00000000`00000008 fffff880`0c506188 4e564458`00000200 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x447c6
fffff880`0847a6d0 fffff880`0c506188 : fffff880`1452c530 fffff8a0`0fa3b010 00000000`00000000 fffff880`4b677844 : nt!KiPageFault+0x16e
fffff880`0847a868 fffff880`1452c530 : fffff8a0`0fa3b010 00000000`00000000 fffff880`4b677844 00000000`00000799 : 0xfffff880`0c506188
fffff880`0847a870 fffff960`001ffc02 : fffffa80`09bf9b60 fffffa80`09bf9b60 00000000`00000000 00000000`00000020 : dxgkrnl!DxgkEscape+0xc4c
fffff880`0847abf0 fffffa80`09bf9b60 : fffffa80`09bf9b60 00000000`00000000 00000000`00000020 00000000`00000020 : win32k+0x18fc02
fffff880`0847abf8 fffffa80`09bf9b60 : 00000000`00000000 00000000`00000020 00000000`00000020 fffff800`03a86ed3 : 0xfffffa80`09bf9b60
fffff880`0847ac00 00000000`00000000 : 00000000`00000020 00000000`00000020 fffff800`03a86ed3 fffffa80`09bf9b60 : 0xfffffa80`09bf9b60


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DxgkEscape+c4c
fffff880`1452c530 488d8c24c8000000 lea     rcx,[rsp+0C8h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  dxgkrnl!DxgkEscape+c4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa

FAILURE_BUCKET_ID:  X64_0x50_dxgkrnl!DxgkEscape+c4c

BUCKET_ID:  X64_0x50_dxgkrnl!DxgkEscape+c4c

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mesmo\Windows_NT6_BSOD_jcgriff2\011712-23353-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a1d000 PsLoadedModuleList = 0xfffff800`03c62670
Debug session time: Tue Jan 17 23:01:40.300 2012 (UTC - 7:00)
System Uptime: 0 days 7:35:06.518
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003a9f00d, fffff8800bb2c0a0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+2ad )

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

4: 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: fffff80003a9f00d, Address of the instruction which caused the bugcheck
Arg3: fffff8800bb2c0a0, 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!KiCommitThreadWait+2ad
fffff800`03a9f00d 48894808        mov     qword ptr [rax+8],rcx

CONTEXT:  fffff8800bb2c0a0 -- (.cxr 0xfffff8800bb2c0a0)
rax=f7fff880009b5e48 rbx=fffff880009b5e40 rcx=fffffa80071b8c40
rdx=0000000000000000 rsi=fffffa800716c120 rdi=0000000000000000
rip=fffff80003a9f00d rsp=fffff8800bb2ca80 rbp=0000000000000000
 r8=fffff80003a1d000  r9=0000000000000000 r10=ffffffffffffffef
r11=fffff880009b2100 r12=0000000000000000 r13=0000000000000000
r14=fffff880009b4380 r15=00000000000000c6
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!KiCommitThreadWait+0x2ad:
fffff800`03a9f00d 48894808        mov     qword ptr [rax+8],rcx ds:002b:f7fff880`009b5e50=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  LolClient.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003aa174f to fffff80003a9f00d

STACK_TEXT:  
fffff880`0bb2ca80 fffff800`03aa174f : 00000000`000001a8 fffff960`00132325 fffff900`000000c6 00000000`00000401 : nt!KiCommitThreadWait+0x2ad
fffff880`0bb2cb10 fffff800`03d9044e : 00000000`00000000 fffff880`00000006 00000000`00000001 00000000`00010500 : nt!KeWaitForSingleObject+0x19f
fffff880`0bb2cbb0 fffff800`03a98ed3 : fffffa80`0716c060 00000000`000001a8 fffff880`0bb2cbf8 fffffa80`06d22950 : nt!NtWaitForSingleObject+0xde
fffff880`0bb2cc20 00000000`748b2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03a6f0a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x748b2e09


FOLLOWUP_IP: 
nt!KiCommitThreadWait+2ad
fffff800`03a9f00d 48894808        mov     qword ptr [rax+8],rcx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiCommitThreadWait+2ad

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff8800bb2c0a0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiCommitThreadWait+2ad

BUCKET_ID:  X64_0x3B_nt!KiCommitThreadWait+2ad

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


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mesmo\Windows_NT6_BSOD_jcgriff2\011812-21060-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a1f000 PsLoadedModuleList = 0xfffff800`03c64670
Debug session time: Wed Jan 18 16:41:45.491 2012 (UTC - 7:00)
System Uptime: 0 days 3:16:01.709
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003cee2af, fffff8800ba665b0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+1e263 )

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

5: 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: fffff80003cee2af, Address of the instruction which caused the bugcheck
Arg3: fffff8800ba665b0, 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! ?? ::NNGAKEGL::`string'+1e263
fffff800`03cee2af ff5330          call    qword ptr [rbx+30h]

CONTEXT:  fffff8800ba665b0 -- (.cxr 0xfffff8800ba665b0)
rax=0000000000000000 rbx=fffff880010d5540 rcx=0000000000000000
rdx=00000000000000a8 rsi=00000000000000a8 rdi=0000000000000042
rip=fffff80003cee2af rsp=fffff8800ba66f90 rbp=0000000000000000
 r8=0000000063664d46  r9=0000000000000000 r10=fffff880010d5540
r11=0000000000000060 r12=fffff880010cb890 r13=0000000000100001
r14=fffffa8006aee220 r15=0000000000000000
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! ?? ::NNGAKEGL::`string'+0x1e263:
fffff800`03cee2af ff5330          call    qword ptr [rbx+30h] ds:002b:fffff880`010d5570=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880010dbe0a to fffff80003cee2af

STACK_TEXT:  
fffff880`0ba66f90 fffff880`010dbe0a : fffffa80`0950e5d0 00000000`00000008 fffff880`0ba670e8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1e263
fffff880`0ba66fd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!TargetedIOCtrlGenerateECP+0x7a


FOLLOWUP_IP: 
nt! ?? ::NNGAKEGL::`string'+1e263
fffff800`03cee2af ff5330          call    qword ptr [rbx+30h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt! ?? ::NNGAKEGL::`string'+1e263

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff8800ba665b0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!_??_::NNGAKEGL::_string_+1e263

BUCKET_ID:  X64_0x3B_nt!_??_::NNGAKEGL::_string_+1e263

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

1. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...
2. 5. Possible causes are Memory problems... Viruses... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...
Thanks to JMH for helping with my understanding of this crash.
3. 6. 7. 9. 10. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Graphics Driver...
4. 8. Possible causes are Memory problems... Graphics card memory problems... CMOS... Corrupted hard disk system files... Corrupted System Files... Missing Windows Updates... Drivers...
Thanks to Dave76 for help understanding possible causes.

Start with the following steps.

If you are overclocking anything, please stop.

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).

Download and install HWiNFO64 Download to check hardware temperatures.

Use the FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net and |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card and its memory (from STOP 0x116: VIDEO_TDR_ERROR troubleshooting).

Mesmo · 19 Jan 2012

While Gaming HWinFO64

Cpu Temp: 68 Max 79 Faren
Hd 1 Temp: 82.4 Max 82.4 Faren
Hd 2 Temp: 73.4 Max 73.4 Faren
Gpu Temp 105.8 Max 111.2 Faren ( Stock OC Vcard )

Temps WIth Speedfan
Cpu 66 Faren
GPU 106 Faren
Hd1 82 Faren
Hd2 73 Faren

Will be running memtest tonight and will post results 2morrow

Ran Furmark for 10min
GPU got to 156.2 Faren and stabelized at that temp. No BSOD or errors

Also adding that ever since post, there hasnt been any BSOD.

writhziden · 19 Jan 2012

Quote: Originally Posted by Mesmo

While Gaming HWinFO64

Cpu Temp: 68 Max 79 Faren
Hd 1 Temp: 82.4 Max 82.4 Faren
Hd 2 Temp: 73.4 Max 73.4 Faren
Gpu Temp 105.8 Max 111.2 Faren ( Stock OC Vcard )

Temps WIth Speedfan
Cpu 66 Faren
GPU 106 Faren
Hd1 82 Faren
Hd2 73 Faren

Will be running memtest tonight and will post results 2morrow

Ran Furmark for 10min
GPU got to 156.2 Faren and stabelized at that temp. No BSOD or errors

Also adding that ever since post, there hasnt been any BSOD.

Temperatures are within acceptable ranges, so we can rule that out as a problem.

Mesmo · 19 Jan 2012

Ran memtest last night and 20% into the first pass it had 16 errors. Since there quad channel ram, there's no need to check which one is faulty as all of them have to be returned in the RMA. Filed an RMA this morn so should come soon.

Any other possible things it can be other than the ram?

writhziden · 19 Jan 2012

Is the memory kit you bought definitely compatible with the motherboard?

Another possible problem could be the motherboard itself. The sockets for the RAM could be faulty and causing those errors just as easily as the RAM could. You probably won't know until you get the new RAM (assuming the RAM is compatible with the board).

Mesmo · 19 Jan 2012

The mobo i bought supports 1333 memory
Newegg.com - Open Box: GIGABYTE GA-880GA-UD3H AM3 AMD 880G HDMI SATA 6Gb/s USB 3.0 ATX AMD Motherboard ( MOBO)
The link provided above is jsut for reference, both mobo and ram were bought new.

The ram is also 1333
Newegg.com - Kingston HyperX 8GB (4 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 Desktop Memory Model KHX1333C7D3K4/8GX (RAM)

writhziden · 19 Jan 2012

Quote: Originally Posted by Mesmo

The mobo i bought supports 1333 memory
Newegg.com - Open Box: GIGABYTE GA-880GA-UD3H AM3 AMD 880G HDMI SATA 6Gb/s USB 3.0 ATX AMD Motherboard ( MOBO)
The link provided above is jsut for reference, both mobo and ram were bought new.

The ram is also 1333
Newegg.com - Kingston HyperX 8GB (4 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 Desktop Memory Model KHX1333C7D3K4/8GX (RAM)

The only 1333 Kingston I see as widely supported by that motherboard is KVR1333D3N9/1G

http://download.gigabyte.us/FileList...880ga-ud3h.pdf

Mesmo · 19 Jan 2012

Quote: Originally Posted by writhziden

Quote: Originally Posted by Mesmo

The mobo i bought supports 1333 memory
Newegg.com - Open Box: GIGABYTE GA-880GA-UD3H AM3 AMD 880G HDMI SATA 6Gb/s USB 3.0 ATX AMD Motherboard ( MOBO)
The link provided above is jsut for reference, both mobo and ram were bought new.

The ram is also 1333
Newegg.com - Kingston HyperX 8GB (4 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 Desktop Memory Model KHX1333C7D3K4/8GX (RAM)

The only 1333 Kingston I see as widely supported by that motherboard is KVR1333D3N9/1G

http://download.gigabyte.us/FileList...880ga-ud3h.pdf

so even though its 1333 it could still be a compatibility problem?
And does that mean that replacing it with the new RAM from the RMA wont fix the problem?

writhziden · 19 Jan 2012

Quote: Originally Posted by Mesmo

Quote: Originally Posted by writhziden

Quote: Originally Posted by Mesmo

The mobo i bought supports 1333 memory
Newegg.com - Open Box: GIGABYTE GA-880GA-UD3H AM3 AMD 880G HDMI SATA 6Gb/s USB 3.0 ATX AMD Motherboard ( MOBO)
The link provided above is jsut for reference, both mobo and ram were bought new.

The ram is also 1333
Newegg.com - Kingston HyperX 8GB (4 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 Desktop Memory Model KHX1333C7D3K4/8GX (RAM)

The only 1333 Kingston I see as widely supported by that motherboard is KVR1333D3N9/1G

http://download.gigabyte.us/FileList...880ga-ud3h.pdf

so even though its 1333 it could still be a compatibility problem?

It can. My general rule is to find memory that is actually listed by the motherboard manufacturer as being tested as compatible. You can speak with a representative at Kingston and see what they say about your motherboard and CPU and if they are willing to provide a kit better suited for your board and CPU through an RMA.

Windows 7: Random BSOD ntoskrnl.exe+7c1e9

Random BSOD ntoskrnl.exe+7c1e9 problems?