Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\New folder (3)\032410-20014-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0304c000 PsLoadedModuleList = 0xfffff800`03289e50
Debug session time: Wed Mar 24 19:39:05.515 2010 (GMT-4)
System Uptime: 0 days 0:00:11.107
Loading Kernel Symbols
...............................................................
.................................
Loading User Symbols
Unable to load image \SystemRoot\system32\DRIVERS\Thpevm.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Thpevm.SYS
*** ERROR: Module load completed but symbols could not be loaded for Thpevm.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, 0, fffff880035ba8d8, fffff880035ba130}
Probably caused by : Thpevm.SYS ( Thpevm+9aa )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: fffff880035ba8d8, Exception Record Address
Arg4: fffff880035ba130, 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:
+9aa
00000000`00000000 ?? ???
EXCEPTION_RECORD: fffff880035ba8d8 -- (.exr 0xfffff880035ba8d8)
ExceptionAddress: 0000000000000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000008
Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000
CONTEXT: fffff880035ba130 -- (.cxr 0xfffff880035ba130)
rax=0000000000000000 rbx=fffffa800499e500 rcx=0000000000000000
rdx=0000000000000081 rsi=0000000000000081 rdi=0000000000000081
rip=0000000000000000 rsp=fffff880035bab18 rbp=fffffa8004a60000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=fffff88000efef44
r14=0000000000008004 r15=fffff880009eaf40
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
00000000`00000000 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
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: 0000000000000008
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f40e0
0000000000000000
FOLLOWUP_IP:
Thpevm+9aa
fffff880`01bfe9aa ?? ???
FAILED_INSTRUCTION_ADDRESS:
+6004952f036adcb0
00000000`00000000 ?? ???
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88001bfe9aa to 0000000000000000
STACK_TEXT:
fffff880`035bab18 fffff880`01bfe9aa : 00000000`00000081 00000000`54414448 00000000`00000081 fffffa80`0499e560 : 0x0
fffff880`035bab20 00000000`00000081 : 00000000`54414448 00000000`00000081 fffffa80`0499e560 00000000`00000000 : Thpevm+0x9aa
fffff880`035bab28 00000000`54414448 : 00000000`00000081 fffffa80`0499e560 00000000`00000000 00000000`00000000 : 0x81
fffff880`035bab30 00000000`00000081 : fffffa80`0499e560 00000000`00000000 00000000`00000000 00000000`00000000 : 0x54414448
fffff880`035bab38 fffffa80`0499e560 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x81
fffff880`035bab40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff0000`02e45e88 : 0xfffffa80`0499e560
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Thpevm+9aa
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Thpevm
IMAGE_NAME: Thpevm.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a487829
STACK_COMMAND: .cxr 0xfffff880035ba130 ; kb
FAILURE_BUCKET_ID: X64_0x7E_NULL_IP_Thpevm+9aa
BUCKET_ID: X64_0x7E_NULL_IP_Thpevm+9aa
Followup: MachineOwner
---------
