psymn Posted January 5, 2014 Posted January 5, 2014 (edited) I need help with this BSOD minidump from my windows 8.1 desktop. When teh system crashed, I think there was a message on the screen about a USB failure, but I don't remember the specifics. Can anyone advise me how to fix this issue? If it is caused by USB, is the crash due to a USB device or a USB controller/driver/software?The minidump information is below and my system is as follows:Homemade DesktopWindows 8.1ASUS X79-deluxe MBIntel core i7 4790K16GB ram (Team Extreem Quad channel DDR3 2400mhz)Nvidia GTX 770ThanksMicrosoft ® Windows Debugger Version 6.3.9600.16384 AMD64Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\010514-15234-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available ************* Symbol Path validation summary **************Response Time (ms) LocationDeferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsSymbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 8 Kernel Version 9600 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.16452.amd64fre.winblue_gdr.131030-1505Machine Name:Kernel base = 0xfffff802`03c8c000 PsLoadedModuleList = 0xfffff802`03f50990Debug session time: Sun Jan 5 14:48:13.199 2014 (UTC - 5:00)System Uptime: 0 days 17:25:59.872Loading 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 SymbolsLoading unloaded module list....................******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, ffffe0001001c640, fffff80205913840, ffffe0000a22f010} Probably caused by : USBSTOR.SYS Followup: MachineOwner--------- 0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** DRIVER_POWER_STATE_FAILURE (9f)A driver has failed to complete a power IRP within a specific time.Arguments:Arg1: 0000000000000003, A device object has been blocking an Irp for too long a timeArg2: ffffe0001001c640, Physical Device Object of the stackArg3: fffff80205913840, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stackArg4: ffffe0000a22f010, The blocked IRP Debugging Details:------------------ DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: USBSTOR.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 5215f827 MODULE_NAME: USBSTOR FAULTING_MODULE: fffff80005634000 USBSTOR CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre DPC_STACK_BASE: FFFFF8020591AFB0 STACK_TEXT: fffff802`05913808 fffff802`03e831a6 : 00000000`0000009f 00000000`00000003 ffffe000`1001c640 fffff802`05913840 : nt!KeBugCheckExfffff802`05913810 fffff802`03e830c6 : ffffe000`10783bd0 00000000`00000008 fffff802`059138f8 fffff802`03ce8a04 : nt!PopIrpWatchdogBugcheck+0xdefffff802`05913870 fffff802`03d39f64 : ffffe000`10783c08 fffff802`05913939 ffffe000`10783c48 00000000`00000000 : nt!PopIrpWatchdog+0x32fffff802`059138c0 fffff802`03d3a478 : 00000000`00000001 ffffe000`07abe328 fffff802`03f7a180 fffff802`03f7d2e0 : nt!KiProcessExpiredTimerList+0x1d8fffff802`059139a0 fffff802`03d96478 : fffff802`03f7a180 00000000`00da7a64 fffff802`002487f3 00000000`0024880b : nt!KiExpireTimerTable+0x218fffff802`05913a40 fffff802`03ce6abc : ffffe000`00000000 00001f80`00000001 00000092`1fceca41 00000000`00000002 : nt!KiTimerExpiration+0x148fffff802`05913af0 fffff802`03ddd7ea : fffff802`03f7a180 fffff802`03f7a180 00000000`001a3fe0 fffff802`03fd2a80 : nt!KiRetireDpcList+0x19cfffff802`05913c60 00000000`00000000 : fffff802`05914000 fffff802`0590e000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner IMAGE_VERSION: 6.3.9600.16384 FAILURE_BUCKET_ID: 0x9F_3_disk_IMAGE_USBSTOR.SYS BUCKET_ID: 0x9F_3_disk_IMAGE_USBSTOR.SYS ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x9f_3_disk_image_usbstor.sys FAILURE_ID_HASH: {2a1b1805-fa25-100a-378d-17c96d91e5f2} Followup: MachineOwner--------- 0: kd> lmvm USBSTORstart end module namefffff800`05634000 fffff800`0565a000 USBSTOR (pdb symbols) c:\symbols\usbstor.pdb\D52634D8FE8E497190EA3C76D99A0FC42\usbstor.pdb Loaded symbol image file: USBSTOR.SYS Mapped memory image file: c:\symbols\USBSTOR.SYS\5215F82726000\USBSTOR.SYS Image path: USBSTOR.SYS Image name: USBSTOR.SYS Timestamp: Thu Aug 22 07:38:15 2013 (5215F827) CheckSum: 00030D00 ImageSize: 00026000 File version: 6.3.9600.16384 Product version: 6.3.9600.16384 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 2.0 Dll File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: usbstor.sys OriginalFilename: usbstor.sys ProductVersion: 6.3.9600.16384 FileVersion: 6.3.9600.16384 (winblue_rtm.130821-1623) FileDescription: USB Mass Storage Class Driver LegalCopyright: © Microsoft Corporation. All rights reserved. Edited January 6, 2014 by Yzöwl pasted data moved into quote box
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now