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\031611-40076-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x8301a000 PsLoadedModuleList = 0x83164850
Debug session time: Tue Mar 15 15:32:50.241 2011 (UTC - 4:00)
System Uptime: 0 days 0:10:12.364
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\System32\Drivers\US4Vista.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for US4Vista.sys
*** ERROR: Module load completed but symbols could not be loaded for US4Vista.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8dc015ee, a2d87ad0, 0}
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : US4Vista.sys ( US4Vista+15ee )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 8dc015ee, The address that the exception occurred at
Arg3: a2d87ad0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
US4Vista+15ee
8dc015ee 8b490c mov ecx,dword ptr [ecx+0Ch]
TRAP_FRAME: a2d87ad0 -- (.trap 0xffffffffa2d87ad0)
ErrCode = 00000000
eax=88a4ffb8 ebx=88a4ff00 ecx=00000010 edx=88a4ff00 esi=882bfb98 edi=00000000
eip=8dc015ee esp=a2d87b44 ebp=a2d87b68 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
US4Vista+0x15ee:
8dc015ee 8b490c mov ecx,dword ptr [ecx+0Ch] ds:0023:0000001c=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: PDEngine.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8dc0394c to 8dc015ee
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a2d87b68 8dc0394c 882bfb98 00000000 a2d87b90 US4Vista+0x15ee
a2d87b78 83051593 882bfae0 88a4ff00 88a4ff00 US4Vista+0x394c
a2d87b90 8324599f 8674c518 88a4ff00 88a4ffb8 nt!IofCallDriver+0x63
a2d87bb0 83248b71 882bfae0 8674c518 00000000 nt!IopSynchronousServiceTail+0x1f8
a2d87c4c 8328f3f4 882bfae0 88a4ff00 00000000 nt!IopXxxControlFile+0x6aa
a2d87c80 9283c1d0 00000210 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
a2d87d04 830581ea 00000210 00000000 00000000 klif+0x2e1d0
a2d87d04 774070b4 00000210 00000000 00000000 nt!KiFastCallEntry+0x12a
00ceeb00 00000000 00000000 00000000 00000000 0x774070b4
STACK_COMMAND: kb
FOLLOWUP_IP:
US4Vista+15ee
8dc015ee 8b490c mov ecx,dword ptr [ecx+0Ch]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: US4Vista+15ee
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: US4Vista
IMAGE_NAME: US4Vista.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4abbde87
FAILURE_BUCKET_ID: 0x8E_US4Vista+15ee
BUCKET_ID: 0x8E_US4Vista+15ee
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\031611-40154-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x83002000 PsLoadedModuleList = 0x8314c850
Debug session time: Tue Mar 15 15:44:16.106 2011 (UTC - 4:00)
System Uptime: 0 days 0:10:14.104
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\System32\Drivers\US4Vista.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for US4Vista.sys
*** ERROR: Module load completed but symbols could not be loaded for US4Vista.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8ddc35ee, a382bad0, 0}
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : US4Vista.sys ( US4Vista+15ee )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 8ddc35ee, The address that the exception occurred at
Arg3: a382bad0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
US4Vista+15ee
8ddc35ee 8b490c mov ecx,dword ptr [ecx+0Ch]
TRAP_FRAME: a382bad0 -- (.trap 0xffffffffa382bad0)
ErrCode = 00000000
eax=883cdaf8 ebx=883cda40 ecx=00000010 edx=883cda40 esi=8848cb58 edi=00000000
eip=8ddc35ee esp=a382bb44 ebp=a382bb68 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
US4Vista+0x15ee:
8ddc35ee 8b490c mov ecx,dword ptr [ecx+0Ch] ds:0023:0000001c=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: PDEngine.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8ddc594c to 8ddc35ee
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a382bb68 8ddc594c 8848cb58 00000000 a382bb90 US4Vista+0x15ee
a382bb78 83039593 8848caa0 883cda40 883cda40 US4Vista+0x394c
a382bb90 8322d99f 86c67610 883cda40 883cdaf8 nt!IofCallDriver+0x63
a382bbb0 83230b71 8848caa0 86c67610 00000000 nt!IopSynchronousServiceTail+0x1f8
a382bc4c 832773f4 8848caa0 883cda40 00000000 nt!IopXxxControlFile+0x6aa
a382bc80 8d79e1d0 00000220 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
a382bd04 830401ea 00000220 00000000 00000000 klif+0x2e1d0
a382bd04 777270b4 00000220 00000000 00000000 nt!KiFastCallEntry+0x12a
0083eb00 00000000 00000000 00000000 00000000 0x777270b4
STACK_COMMAND: kb
FOLLOWUP_IP:
US4Vista+15ee
8ddc35ee 8b490c mov ecx,dword ptr [ecx+0Ch]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: US4Vista+15ee
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: US4Vista
IMAGE_NAME: US4Vista.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4abbde87
FAILURE_BUCKET_ID: 0x8E_US4Vista+15ee
BUCKET_ID: 0x8E_US4Vista+15ee
Followup: MachineOwner
---------