Code:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a67000 PsLoadedModuleList = 0xfffff800`02ca4e50
Debug session time: Fri Feb 4 01:09:36.297 2011 (GMT-5)
System Uptime: 0 days 1:17:45.372
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffc9853375, 0, fffff960001a6295, 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 : win32k.sys ( win32k+156295 )
Followup: MachineOwner
---------
5: 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: ffffffffc9853375, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960001a6295, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0f0e0
ffffffffc9853375
FAULTING_IP:
win32k+156295
fffff960`001a6295 85c0 test eax,eax
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800a4c5840 -- (.trap 0xfffff8800a4c5840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000008 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960001a6295 rsp=fffff8800a4c59d0 rbp=0000000001040058
r8=00000000000001fe r9=0000000000000001 r10=0000000056000000
r11=0000000000000800 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
win32k+0x156295:
fffff960`001a6295 85c0 test eax,eax
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b56bc2 to fffff80002ad8f00
STACK_TEXT:
fffff880`0a4c56d8 fffff800`02b56bc2 : 00000000`00000050 ffffffff`c9853375 00000000`00000000 fffff880`0a4c5840 : nt!KeBugCheckEx
fffff880`0a4c56e0 fffff800`02ad6fee : 00000000`00000000 00000000`00000800 006dec00`00000300 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f90
fffff880`0a4c5840 fffff960`001a6295 : fffff900`c00b9f20 00000000`01040058 00000000`00000001 fffff960`001140d1 : nt!KiPageFault+0x16e
fffff880`0a4c59d0 fffff900`c00b9f20 : 00000000`01040058 00000000`00000001 fffff960`001140d1 fffff900`c08275a0 : win32k+0x156295
fffff880`0a4c59d8 00000000`01040058 : 00000000`00000001 fffff960`001140d1 fffff900`c08275a0 fffff960`00095fd9 : 0xfffff900`c00b9f20
fffff880`0a4c59e0 00000000`00000001 : fffff960`001140d1 fffff900`c08275a0 fffff960`00095fd9 fffff880`0a4c5a80 : 0x1040058
fffff880`0a4c59e8 fffff960`001140d1 : fffff900`c08275a0 fffff960`00095fd9 fffff880`0a4c5a80 00000000`00001001 : 0x1
fffff880`0a4c59f0 fffff900`c08275a0 : fffff960`00095fd9 fffff880`0a4c5a80 00000000`00001001 00000000`00000001 : win32k+0xc40d1
fffff880`0a4c59f8 fffff960`00095fd9 : fffff880`0a4c5a80 00000000`00001001 00000000`00000001 fffff900`c0200840 : 0xfffff900`c08275a0
fffff880`0a4c5a00 fffff880`0a4c5a80 : 00000000`00001001 00000000`00000001 fffff900`c0200840 fffff900`c08275a0 : win32k+0x45fd9
fffff880`0a4c5a08 00000000`00001001 : 00000000`00000001 fffff900`c0200840 fffff900`c08275a0 00000000`01040058 : 0xfffff880`0a4c5a80
fffff880`0a4c5a10 00000000`00000001 : fffff900`c0200840 fffff900`c08275a0 00000000`01040058 00000000`01040058 : 0x1001
fffff880`0a4c5a18 fffff900`c0200840 : fffff900`c08275a0 00000000`01040058 00000000`01040058 00000000`00000000 : 0x1
fffff880`0a4c5a20 fffff900`c08275a0 : 00000000`01040058 00000000`01040058 00000000`00000000 00000000`00001001 : 0xfffff900`c0200840
fffff880`0a4c5a28 00000000`01040058 : 00000000`01040058 00000000`00000000 00000000`00001001 fffff960`00095e33 : 0xfffff900`c08275a0
fffff880`0a4c5a30 00000000`01040058 : 00000000`00000000 00000000`00001001 fffff960`00095e33 fffff900`c08275a0 : 0x1040058
fffff880`0a4c5a38 00000000`00000000 : 00000000`00001001 fffff960`00095e33 fffff900`c08275a0 00000000`00000000 : 0x1040058
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k+156295
fffff960`001a6295 85c0 test eax,eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k+156295
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e1
FAILURE_BUCKET_ID: X64_0x50_win32k+156295
BUCKET_ID: X64_0x50_win32k+156295
Followup: MachineOwner
---------
Debug session time: Sat Feb 5 00:57:02.253 2011 (GMT-5)
System Uptime: 0 days 0:48:16.689
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:
+5de9952f00c6d918
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002ffc9f8 -- (.exr 0xfffff88002ffc9f8)
ExceptionAddress: fffff80002a8ddb2 (nt!KiTimerExpiration+0x00000000000000f2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002ffcaa0 -- (.trap 0xfffff88002ffcaa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffbff88002fd6fe8 rbx=0000000000000000 rcx=fffff88002fd6fe8
rdx=0000000000000053 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a8ddb2 rsp=fffff88002ffcc30 rbp=000000000002d553
r8=fffffa8006020bb0 r9=00000000000000c1 r10=0000000000000053
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!KiTimerExpiration+0xf2:
fffff800`02a8ddb2 48894808 mov qword ptr [rax+8],rcx ds:ffbff880`02fd6ff0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a79c2e to fffff80002a81ed0
STACK_TEXT:
fffff880`02ffbad8 fffff800`02a79c2e : 00000000`002cdaa8 00000006`be8169db fffff880`02ffc250 fffff800`02aaee28 : nt!KeBugCheck
fffff880`02ffbae0 fffff800`02aa7bed : fffff800`02c8ec24 fffff800`02bc7a3c fffff800`02a10000 fffff880`02ffc9f8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffbb10 fffff800`02aaf250 : fffff800`02bcfb5c fffff880`02ffbb88 fffff880`02ffc9f8 fffff800`02a10000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffbb40 fffff800`02abc1b5 : fffff880`02ffc9f8 fffff880`02ffc250 fffff880`00000000 fffff880`02fd4180 : nt!RtlDispatchException+0x410
fffff880`02ffc220 fffff800`02a81542 : fffff880`02ffc9f8 00000006`be8fb21c fffff880`02ffcaa0 fffff880`02fd6fe8 : nt!KiDispatchException+0x135
fffff880`02ffc8c0 fffff800`02a7fe4a : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`05358819 : nt!KiExceptionDispatch+0xc2
fffff880`02ffcaa0 fffff800`02a8ddb2 : 00000000`000207cc 00000000`00000948 00000000`00000000 00000000`0000b33b : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffcc30 fffff800`02a8d697 : 00000001`fb9bdcc1 00000001`0002d554 00000001`fb9bdc33 00000000`00000053 : nt!KiTimerExpiration+0xf2
fffff880`02ffccd0 fffff800`02a8a6fa : fffff880`02fd4180 fffff880`02fdf040 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff880`02ffcd80 00000000`00000000 : fffff880`02ffd000 fffff880`02ff7000 fffff880`02ffcd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02a79c2e 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: 4a5bc600
FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------
Debug session time: Sat Feb 5 00:07:54.928 2011 (GMT-5)
System Uptime: 0 days 18:31:56.364
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002dbfaae, fffff88002792ab0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+173 )
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: fffff80002dbfaae, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88002792ab0, 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!ObpWaitForMultipleObjects+173
fffff800`02dbfaae 0fb64718 movzx eax,byte ptr [rdi+18h]
CONTEXT: fffff88002792ab0 -- (.cxr 0xfffff88002792ab0)
rax=00000000ffe0fffc rbx=fffff8a0073e96e0 rcx=ffbffa80067cfcf0
rdx=fffffa8003a1e001 rsi=0000000000000031 rdi=ffbffa80067cfcf0
rip=fffff80002dbfaae rsp=fffff88002793490 rbp=fffff88002793ca0
r8=0000000000000008 r9=fffff8a00759d000 r10=fffffa8003ff3b60
r11=fffffffffffffd80 r12=fffff88002793b20 r13=fffff8a002955d80
r14=0000000000000030 r15=0000000000000039
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!ObpWaitForMultipleObjects+0x173:
fffff800`02dbfaae 0fb64718 movzx eax,byte ptr [rdi+18h] ds:002b:ffbffa80`067cfd08=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002dbfaae
STACK_TEXT:
fffff880`02793490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x173
FOLLOWUP_IP:
nt!ObpWaitForMultipleObjects+173
fffff800`02dbfaae 0fb64718 movzx eax,byte ptr [rdi+18h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObpWaitForMultipleObjects+173
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff88002792ab0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!ObpWaitForMultipleObjects+173
BUCKET_ID: X64_0x3B_nt!ObpWaitForMultipleObjects+173
Followup: MachineOwner
---------