Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\040114-20968-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*%systemroot%\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*%systemroot%\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16659.x86fre.win8_gdr.130708-1504
Machine Name:
Kernel base = 0xe166f000 PsLoadedModuleList = 0xe185ce48
Debug session time: Tue Apr  1 23:50:05.042 2014 (UTC + 4:00)
System Uptime: 0 days 0:01:48.737
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, ca7e8280, 0, 0}

Unable to load image cmdguard.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmdguard.sys
*** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
Probably caused by : USBSTOR.SYS ( USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+fe )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: ca7e8280
Arg3: 00000000
Arg4: 00000000

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


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  ekrn.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from d5b623ef to e183719a

STACK_TEXT:  
f5289060 d5b623ef 00000200 00000088 70627375 nt!ExAllocatePoolWithTag+0x185
f52890ec d5b5e350 c4c66028 c79e4298 c5f63bf0 USBPORT!USBPORT_Core_AllocTransferEx+0x23b
f5289194 d5b5edaf c7396280 c79e4298 c79a6508 USBPORT!USBPORT_ProcessURB+0x47c
f52891c4 e1694032 c4c600e0 02396280 c7396280 USBPORT!USBPORT_Dispatch+0x190
f52891e0 cacaf4a0 c57e9740 c7396434 f5289210 nt!IofCallDriver+0x3f
f52891f0 cacb9a5d c57e9740 c7396280 c3587768 ACPI!ACPIDispatchForwardIrp+0x2e
f5289210 cacaf17d c57e9740 c7396280 00000000 ACPI!ACPIIrpDispatchDeviceControl+0x62
f5289254 e1694032 c57e9740 c7396280 c7396280 ACPI!ACPIDispatchIrp+0x165
f5289270 d4e1212e 00000000 c7396434 c739620f nt!IofCallDriver+0x3f
f52892a0 d4e11034 c59f6650 02396280 c59f6650 usbhub!UsbhPdoInternalDeviceControl+0x1c4
f52892b4 e1694032 c59f6650 c7396280 c7396280 usbhub!UsbhGenDispatch+0x2f
f52892d0 cacaf4a0 c69d5718 c7396434 f5289300 nt!IofCallDriver+0x3f
f52892e0 cacb9a5d c69d5718 c7396280 c3587318 ACPI!ACPIDispatchForwardIrp+0x2e
f5289300 cacaf17d c69d5718 c7396280 00000000 ACPI!ACPIIrpDispatchDeviceControl+0x62
f5289344 e1694032 c69d5718 c7396280 c79e40f0 ACPI!ACPIDispatchIrp+0x165
f5289360 f2d1f15b c79e431b c6986f10 c7396280 nt!IofCallDriver+0x3f
f528938c f2d1f00e c6ff2f3c 00000000 0000001f USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+0xfe
f52893d8 f2d1f57d c79e40f0 c7396280 ca7e4570 USBSTOR!USBSTOR_CbwTransfer+0x17c
f5289418 e1716580 c79e40f0 c7396280 c7ded650 USBSTOR!USBSTOR_StartIo+0x3bc
f5289438 f2d1d3d8 c79e40f0 c7396280 c6986efc nt!IoStartPacket+0xdb
f528948c e1694032 c7ded598 c7396280 c6967770 USBSTOR!USBSTOR_Scsi+0x3d3
f52894a8 cb991edd 002d4800 00074800 c6986ed0 nt!IofCallDriver+0x3f
f52894c8 cb98ca41 c69676b8 c6986ed0 c7396280 CLASSPNP!ClassSendSrbAsynchronous+0x159
f5289580 cb9726b7 c69676b8 c7cd0228 c69676b8 CLASSPNP!ClassDeviceControl+0x545
f52895c4 cb98d11b c69676b8 c7cd0228 c69676b8 disk!DiskDeviceControl+0x134
f52895d8 cb98ad1c c69676b8 c7cd0228 00000000 CLASSPNP!ClassDeviceControlDispatch+0x2e
f52895f0 e1694032 c69676b8 c7cd0228 c7cd0448 CLASSPNP!ClassGlobalDispatch+0x23
f528960c ca9dab8d c7c39758 c7cd0448 c7cd0228 nt!IofCallDriver+0x3f
f528962c ca9da32e c7c39758 c7c39848 00000000 partmgr!PmFilterDeviceControl+0xc7
f5289664 e1694032 c7c39758 c7cd0228 c7cd0228 partmgr!PmGlobalDispatch+0x329
f5289680 ca9da95c c738f648 c7cd0448 c7cd0228 nt!IofCallDriver+0x3f
f52896a4 ca9da32e c738f648 c7cd0228 00000000 partmgr!PmLegacyDeviceControl+0x11c
f52896dc e1694032 c738f648 c7cd0228 c797b528 partmgr!PmGlobalDispatch+0x329
f52896f8 caa505c0 00000000 c797b470 0000000e nt!IofCallDriver+0x3f
f528972c e1694032 c797b470 c7cd0228 00000000 volmgr!VmDeviceControl+0x27a
f5289748 e171fb2f c7cd04ac c6f86430 ca040000 nt!IofCallDriver+0x3f
f5289768 e19ad384 c797b470 c7cd0228 c7cd0228 nt!IoSynchronousCallDriver+0x41
f5289780 cb840553 c797b470 c7cd0228 00000000 nt!IoForwardIrpSynchronously+0x2a
f52897cc e1694032 c6f86378 c7cd0228 c7cd0228 fvevol!FveFilterDeviceControl+0x44d
f52897e8 cb8d9073 00000000 c345f590 0000180e nt!IofCallDriver+0x3f
f5289820 e1694032 c345f590 c7cd0228 00001800 volsnap!VolSnapDeviceControl+0x6e
f528983c f2d4800e 00000000 c7d0f3e8 c7040000 nt!IofCallDriver+0x3f
f5289868 f2d59fea 00074800 c345f590 f5289898 fastfat!FatPerformDevIoCtrl+0x60
f52898a0 f2d432b0 c7c8ef78 e7b3aacd 00000000 fastfat!FatVerifyVcb+0x4e
f5289af4 f2d42e9a e7b3ab0d 00000000 c7d0f2f0 fastfat!FatCommonCreate+0x3a6
f5289b34 e1694032 01d0f2f0 c6ea9098 c6ee0af0 fastfat!FatFsdCreate+0x4c
f5289b50 cab59a9f 00000000 c6efe160 c6ea9098 nt!IofCallDriver+0x3f
f5289b8c cab742dd f5289bd0 00000000 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24c
f5289bec e1694032 c649b498 c6ea9098 c7970004 fltmgr!FltpCreate+0x2d8
f5289c08 e19fc98d 999ab44c e19fb5e5 cb610000 nt!IofCallDriver+0x3f
f5289d28 e18da73e c797b470 c3342040 c7c2c950 nt!IopParseDevice+0x13a5
f5289dac e18da163 00000000 f5289e08 00000240 nt!ObpLookupObjectName+0x251
f5289e14 e190ad92 f528a028 c3342040 53a2eb00 nt!ObOpenObjectByName+0xfe
f5289e90 e190aa99 f528a048 80000000 f528a028 nt!IopCreateFile+0x2a5
f5289edc d20ecac4 f528a048 80000000 f528a028 nt!NtCreateFile+0x36
WARNING: Stack unwind information not available. Following frames may be wrong.
f5289f48 e17af978 f528a048 80000000 f528a028 cmdguard+0x24ac4
f5289f48 e1738fed f528a048 80000000 f528a028 nt!KiSystemServicePostCall
f5289fec d20ffe9d f528a048 80000000 f528a028 nt!ZwCreateFile+0x11
f528a04c d20fff1f f528a068 f528a070 c4e5cba8 cmdguard+0x37e9d
f528a08c d20fe6f9 0000004a c6373270 00000250 cmdguard+0x37f1f
f528a0bc d20f3b13 c4e5cbac c741a8e4 80000ce8 cmdguard+0x366f9
f528a0d8 d20fb0a5 80000ce8 d213be42 c741a8e4 cmdguard+0x2bb13
f528a0fc d20f7f44 80000ce8 c741a678 00000000 cmdguard+0x330a5
f528a13c d20e744b 749e0b4b c66a2b98 c64232d0 cmdguard+0x2ff44
f528a220 cab7bac0 f528a240 00000005 00000003 cmdguard+0x1f44b
f528a258 cab7aa17 46273560 00000000 c84fa538 fltmgr!FltpDoInstanceSetupNotification+0x7b
f528a2a4 cab7ad0f c4c15bf8 c64232d0 00000005 fltmgr!FltpInitInstance+0x273
f528a314 cab7bc51 c4c15bf8 c64232d0 00000005 fltmgr!FltpCreateInstanceFromName+0x17d
f528a38c cab7b7bb c4c15bf8 c64232d0 00000005 fltmgr!FltpEnumerateRegistryInstances+0x116
f528a3dc cab74398 c64232d0 00000000 c7c3fed8 fltmgr!FltpDoFilterNotificationForNewVolume+0x121
f528a434 e1694032 c7c3fed8 c7c430c0 c4de0004 fltmgr!FltpCreate+0x393
f528a450 e19fc98d 999a8c14 e19fb5e5 cb610000 nt!IofCallDriver+0x3f
f528a570 e18da73e c4de0848 c3342040 c7cdda90 nt!IopParseDevice+0x13a5
f528a5f4 e18da163 00000000 f528a650 00000240 nt!ObpLookupObjectName+0x251
f528a65c e190ad92 f528a870 c3342040 53a2eb00 nt!ObOpenObjectByName+0xfe


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+fe
f2d1f15b 807dfc00        cmp     byte ptr [ebp-4],0

SYMBOL_STACK_INDEX:  10

SYMBOL_NAME:  USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+fe

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBSTOR

IMAGE_NAME:  USBSTOR.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  51b00c86

IMAGE_VERSION:  6.2.9200.16632

BUCKET_ID_FUNC_OFFSET:  fe

FAILURE_BUCKET_ID:  0x7f_8_USBSTOR!USBSTOR_IssueBulkOrInterruptRequest

BUCKET_ID:  0x7f_8_USBSTOR!USBSTOR_IssueBulkOrInterruptRequest

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7f_8_usbstor!usbstor_issuebulkorinterruptrequest

FAILURE_ID_HASH:  {718a75b4-eb19-1853-5963-9e874c276c7e}

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