Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\021711-25942-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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 Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e52e50
Debug session time: Thu Feb 17 19:29:06.199 2011 (UTC - 5:00)
System Uptime: 3 days 1:56:31.228
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
...................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff9004d72981c, 1, fffff96000241986, 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+221986 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff9004d72981c, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff96000241986, 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 fffff80002ebd0e0
fffff9004d72981c
FAULTING_IP:
win32k+221986
fffff960`00241986 4883ec20 sub rsp,20h
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88006fb35b0 -- (.trap 0xfffff88006fb35b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000008ac rbx=0000000000000000 rcx=fffff900c22a7730
rdx=fffffa80045f0b60 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000241986 rsp=fffff88006fb3740 rbp=fffff88006fb3d90
r8=0000000000000000 r9=0000000000000000 r10=00000000008ed800
r11=fffff88006fb3750 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
win32k+0x221986:
fffff960`00241986 4883ec20 sub rsp,20h
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002d048c1 to fffff80002c85740
STACK_TEXT:
fffff880`06fb3448 fffff800`02d048c1 : 00000000`00000050 fffff900`4d72981c 00000000`00000001 fffff880`06fb35b0 : nt!KeBugCheckEx
fffff880`06fb3450 fffff800`02c8382e : 00000000`00000001 fffff900`c22a7730 fffff880`06fb3600 fffff960`0009504c : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`06fb35b0 fffff960`00241986 : fffff900`c22a7730 fffff960`000a63ab 00000000`0000001c fffff900`c0081070 : nt!KiPageFault+0x16e
fffff880`06fb3740 fffff900`c22a7730 : fffff960`000a63ab 00000000`0000001c fffff900`c0081070 00000000`00000094 : win32k+0x221986
fffff880`06fb3748 fffff960`000a63ab : 00000000`0000001c fffff900`c0081070 00000000`00000094 fffff900`c0867290 : 0xfffff900`c22a7730
fffff880`06fb3750 00000000`0000001c : fffff900`c0081070 00000000`00000094 fffff900`c0867290 00000000`00000000 : win32k+0x863ab
fffff880`06fb3758 fffff900`c0081070 : 00000000`00000094 fffff900`c0867290 00000000`00000000 fffff960`00054fad : 0x1c
fffff880`06fb3760 00000000`00000094 : fffff900`c0867290 00000000`00000000 fffff960`00054fad 00000000`00000000 : 0xfffff900`c0081070
fffff880`06fb3768 fffff900`c0867290 : 00000000`00000000 fffff960`00054fad 00000000`00000000 fffff900`c22a7750 : 0x94
fffff880`06fb3770 00000000`00000000 : fffff960`00054fad 00000000`00000000 fffff900`c22a7750 fffff900`00000006 : 0xfffff900`c0867290
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k+221986
fffff960`00241986 4883ec20 sub rsp,20h
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k+221986
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x50_win32k+221986
BUCKET_ID: X64_0x50_win32k+221986
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\021711-39359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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 Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Thu Feb 17 22:17:14.884 2011 (UTC - 5:00)
System Uptime: 0 days 2:47:39.897
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 : ndis.sys ( ndis!ndisInterruptDpc+6a )
Followup: MachineOwner
---------
1: 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:
+3536303635636134
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: fffff8800371b9c8 -- (.exr 0xfffff8800371b9c8)
ExceptionAddress: fffff88001eb8cba (ndis!ndisInterruptDpc+0x000000000000006a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff8800371ba70 -- (.trap 0xfffff8800371ba70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800371bc88 rbx=0000000000000000 rcx=fffff8800371bc38
rdx=fffffa80057868e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001eb8cba rsp=fffff8800371bc00 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000da7a64
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
ndis!ndisInterruptDpc+0x6a:
fffff880`01eb8cba ff1588350500 call qword ptr [ndis!_imp_KeQueryDpcWatchdogInformation (fffff880`01f0c248)] ds:7123:fffff880`01f0c248=00000000000dc6b2
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002cb346e to fffff80002cbb710
STACK_TEXT:
fffff880`0371aab8 fffff800`02cb346e : fffff880`0371abe8 00000000`00000000 fffff880`0371b230 fffff800`02ce8668 : nt!KeBugCheck
fffff880`0371aac0 fffff800`02ce140d : fffff800`02ec9b7c fffff800`02e03ea4 fffff800`02c4b000 fffff880`0371b9c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0371aaf0 fffff800`02ce8a90 : fffff800`02e0ab34 fffff880`0371ab68 fffff880`0371b9c8 fffff800`02c4b000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0371ab20 fffff800`02cf59ef : fffff880`0371b9c8 fffff880`0371b230 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x410
fffff880`0371b200 fffff800`02cbad82 : fffff880`0371b9c8 fffffa80`057868e0 fffff880`0371ba70 fffffa80`052fe1a0 : nt!KiDispatchException+0x16f
fffff880`0371b890 fffff800`02cb968a : fffffa80`00000001 fffffa80`05592030 00000000`00000000 fffffa80`047901b0 : nt!KiExceptionDispatch+0xc2
fffff880`0371ba70 fffff880`01eb8cba : 00000000`00000000 00000000`00da7a64 00000000`00000000 fffffa80`047633f0 : nt!KiGeneralProtectionFault+0x10a
fffff880`0371bc00 fffff800`02cc6bfc : fffffa80`05786908 00000004`00000000 00000000`00000000 fffff880`009e8180 : ndis!ndisInterruptDpc+0x6a
fffff880`0371bc90 fffff800`02cc3eea : fffff880`009e8180 fffff880`009f2f40 00000000`00000000 fffff880`01eb8c50 : nt!KiRetireDpcList+0x1bc
fffff880`0371bd40 00000000`00000000 : fffff880`0371c000 fffff880`03716000 fffff880`0371bd00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
ndis!ndisInterruptDpc+6a
fffff880`01eb8cba ff1588350500 call qword ptr [ndis!_imp_KeQueryDpcWatchdogInformation (fffff880`01f0c248)]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: ndis!ndisInterruptDpc+6a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ndis
IMAGE_NAME: ndis.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc184
FAILURE_BUCKET_ID: X64_0x1E_0_ndis!ndisInterruptDpc+6a
BUCKET_ID: X64_0x1E_0_ndis!ndisInterruptDpc+6a
Followup: MachineOwner
---------