Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\My Documents\Desktop\011813-28548-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*D:\symbols\*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0465e000 PsLoadedModuleList = 0xfffff800`048a2670
Debug session time: Fri Jan 18 17:23:59.661 2013 (UTC + 8:00)
System Uptime: 5 days 0:39:29.933
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
..................................................
3: 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: fffff800046d4dd0, The address that the exception occurred at
Arg3: fffff88004fdfbe8, Exception Record Address
Arg4: fffff88004fdf440, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0x80000003 (2147483651) - {

FAULTING_IP: 
nt!DbgBreakPoint+0
fffff800`046d4dd0 cc              int     3

EXCEPTION_RECORD:  fffff88004fdfbe8 -- (.exr 0xfffff88004fdfbe8)
ExceptionAddress: fffff800046d4dd0 (nt!DbgBreakPoint)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000000

CONTEXT:  fffff88004fdf440 -- (.cxr 0xfffff88004fdf440)
rax=0000000000000000 rbx=fffffa800718c8b0 rcx=1f22ee23a0cc0000
rdx=0000000000000008 rsi=0000057ff2dc4f78 rdi=fffffa800d23b3c0
rip=fffff800046d4dd0 rsp=fffff88004fdfe28 rbp=fffff88000e7de50
 r8=0000000000000001  r9=fffff8000471a420 r10=0000000000000080
r11=fffff88004fdfe28 r12=0000000000000001 r13=0000000000000000
r14=fffffa800d23b3c0 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`046d4dd0 cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0x80000003 - {

EXCEPTION_PARAMETER1:  0000000000000000

LAST_CONTROL_TRANSFER:  from fffff88000e96028 to fffff800046d4dd0

STACK_TEXT:  
fffff880`04fdfe28 fffff880`00e96028 : fffff880`00e7db70 fffffa80`06a1eb50 fffff880`00e7de50 0000057f`f2dc4f78 : nt!DbgBreakPoint
fffff880`04fdfe30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70


FOLLOWUP_IP: 
Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
fffff880`00e96028 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 0xfffff88004fdf440 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70

BUCKET_ID:  X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70

Followup: MachineOwner
---------

3: kd> .ecxr
Unable to get exception context, HRESULT 0x8000FFFF
3: kd> kb
RetAddr           : Args to Child                                                           : Call Site
fffff880`00e96028 : fffff880`00e7db70 fffffa80`06a1eb50 fffff880`00e7de50 0000057f`f2dc4f78 : nt!DbgBreakPoint
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70
3: kd> dv
Unable to enumerate locals, HRESULT 0x80004005
Private symbols (symbols.pri) are required for locals.
Type ".hh dbgerr005" for details.
3: kd> lmvm Wdf01000
start             end                 module name
fffff880`00e7a000 fffff880`00f3c000   Wdf01000   (pdb symbols)          d:\symbols\Wdf01000.pdb\FABEC58794454D0D9B539B58E2D0A0922\Wdf01000.pdb
    Loaded symbol image file: Wdf01000.sys
    Mapped memory image file: d:\symbols\Wdf01000.sys\5010AA89c2000\Wdf01000.sys
    Image path: \SystemRoot\system32\drivers\Wdf01000.sys
    Image name: Wdf01000.sys
    Timestamp:        Thu Jul 26 10: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.
3: kd> .exr 0xfffff88004fdfbe8
ExceptionAddress: fffff800046d4dd0 (nt!DbgBreakPoint)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000000
3: kd> .cxr 0xfffff88004fdf440
rax=0000000000000000 rbx=fffffa800718c8b0 rcx=1f22ee23a0cc0000
rdx=0000000000000008 rsi=0000057ff2dc4f78 rdi=fffffa800d23b3c0
rip=fffff800046d4dd0 rsp=fffff88004fdfe28 rbp=fffff88000e7de50
 r8=0000000000000001  r9=fffff8000471a420 r10=0000000000000080
r11=fffff88004fdfe28 r12=0000000000000001 r13=0000000000000000
r14=fffffa800d23b3c0 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`046d4dd0 cc              int     3