*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffff80000003, fffff80002eba990, fffff880009e04f8, fffff880009dfd50}
Probably caused by : Wdf01000.sys ( Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70 )
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: ffffffff80000003, The exception code that was not handled
Arg2: fffff80002eba990, The address that the exception occurred at
Arg3: fffff880009e04f8, Exception Record Address
Arg4: fffff880009dfd50, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
FAULTING_IP:
nt!DbgBreakPoint+0
fffff800`02eba990 cc int 3
EXCEPTION_RECORD: fffff880009e04f8 -- (.exr 0xfffff880009e04f8)
ExceptionAddress: fffff80002eba990 (nt!DbgBreakPoint)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 0000000000000000
CONTEXT: fffff880009dfd50 -- (.cxr 0xfffff880009dfd50)
rax=0000000000000000 rbx=fffffa8007a4ba90 rcx=165c5934eb180000
rdx=0000000000000008 rsi=0000057ff85aef78 rdi=fffffa8007a513c0
rip=fffff80002eba990 rsp=fffff880009e0738 rbp=fffff88000ea6e50
r8=0000000000000001 r9=fffff80002f000b0 r10=fffff80002e4d000
r11=fffff880009e0738 r12=0000000000000001 r13=0000000000000000
r14=fffffa8007a513c0 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=00000202
nt!DbgBreakPoint:
fffff800`02eba990 cc int 3
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_PARAMETER1: 0000000000000000
LAST_CONTROL_TRANSFER: from fffff88000ebf028 to fffff80002eba990
STACK_TEXT:
fffff880`009e0738 fffff880`00ebf028 : fffff880`00ea6b70 fffffa80`03730590 fffff880`00ea6e50 0000057f`f85aef78 : nt!DbgBreakPoint
fffff880`009e0740 fffff880`00eb962d : ffffffff`dc3cba00 0000057f`f85aef78 fffff880`009e07b0 fffffa80`07a51090 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70
fffff880`009e0780 fffff880`00eb93f0 : fffffa80`07a51080 0000057f`f85aef00 fffffa80`07a513f0 fffffa80`07a51090 : Wdf01000!FxIoQueue::StopProcessingForPower+0x1ed
fffff880`009e07d0 fffff880`00eb91a8 : 00000000`00000000 fffff880`009e0800 fffffa80`07a503f0 fffffa80`07a5e080 : Wdf01000!FxPkgIo::StopProcessingForPower+0x22c
fffff880`009e0840 fffff880`00eb9131 : 00000000`00000004 00000000`00000000 00000000`00000000 00000000`00000001 : Wdf01000!FxPkgPnp::PowerGotoDx+0x64
fffff880`009e0880 fffff880`00eb6c3c : 00000000`0000031a fffff880`009e09b0 00000000`ffff7fff fffffa80`07a5e080 : Wdf01000!FxPkgPnp::PowerGotoDxArmedForWakeNP+0x9
fffff880`009e08b0 fffff880`00eb7106 : fffff880`00f3bf60 fffffa80`07a5e238 fffffa80`07a5e080 fffffa80`07a5e080 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
fffff880`009e0a10 fffff880`00eb6e9f : 00000000`00000000 fffff880`009e0af0 fffffa80`07a5e220 fffffa80`07a5e080 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`009e0a80 fffff880`00ec0687 : 00000000`00000000 fffffa80`07a5e080 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
fffff880`009e0b20 fffff880`00eb4fea : 00000000`00000002 0000057f`f85b2f78 fffffa80`07a5e6d0 fffffa80`038c2502 : Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x117
fffff880`009e0b70 fffff880`00eac9da : fffffa80`038c2510 fffffa80`038c2510 fffffa80`038c2510 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x2aa
fffff880`009e0bd0 fffff880`00eacaa6 : fffffa80`038c2510 00000000`00000000 fffffa80`07a5e6d0 fffffa80`07a5e6d0 : Wdf01000!FxDevice::Dispatch+0x19a
fffff880`009e0c10 fffff800`02fdeea5 : 00000000`00000001 00000000`00000000 fffffa80`07a5e6d0 fffffa80`038c25b8 : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`009e0c50 fffff800`03160bae : 00000000`00000000 fffffa80`03730590 00000000`00000080 00000000`00000000 : nt!PopIrpWorker+0x3c5
fffff880`009e0d00 fffff800`02eb38c6 : fffff880`009e8180 fffffa80`03730590 fffffa80`036de040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009e0d40 00000000`00000000 : fffff880`009e1000 fffff880`009db000 fffff880`009e0490 00000000`00000000 : nt!KxStartSystemThread+0x16
FOLLOWUP_IP:
Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
fffff880`00ebf028 488b442440 mov rax,qword ptr [rsp+40h]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Wdf01000
IMAGE_NAME: Wdf01000.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5010aa89
STACK_COMMAND: .cxr 0xfffff880009dfd50 ; kb
FAILURE_BUCKET_ID: X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
BUCKET_ID: X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
Followup: MachineOwner
---------
0: kd> lmvm Wdf01000
start end module name
fffff880`00ea3000 fffff880`00f65000 Wdf01000 (pdb symbols) c:\symbols\Wdf01000.pdb\FABEC58794454D0D9B539B58E2D0A0922\Wdf01000.pdb
Loaded symbol image file: Wdf01000.sys
Mapped memory image file: c:\symbols\Wdf01000.sys\5010AA89c2000\Wdf01000.sys
Image path: \SystemRoot\system32\drivers\Wdf01000.sys
Image name: Wdf01000.sys
Timestamp: Thu Jul 26 08:25:13 2012 (5010AA89)
CheckSum: 000CDBF1
ImageSize: 000C2000
File version: 1.11.9200.16384
Product version: 1.11.9200.16384
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: wdf01000.sys
OriginalFilename: wdf01000.sys
ProductVersion: 1.11.9200.16384
FileVersion: 1.11.9200.16384 (win8_rtm.120725-1247)
FileDescription: Kernel Mode Driver Framework Runtime
LegalCopyright: © Microsoft Corporation. All rights reserved.
rb:
I will update my pc as advised and let u know of any further issues.
