New
#1
BSOD while waking from sleep mode
After running the log collector program, here is the zip file it produced. Please help me find what caused this.
Last edited by Dishman316; 21 Oct 2014 at 20:58. Reason: It did not upload the file
After running the log collector program, here is the zip file it produced. Please help me find what caused this.
Last edited by Dishman316; 21 Oct 2014 at 20:58. Reason: It did not upload the file
Upload your MSINFO32.nfo file. Ii is highly needed to suggest you anything depending on this situation.
- Click on the start button
- Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
- File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
- Give the time for processing, it will save a .nfo file on your desktop.
- Zip it, and upload it following the instruction.
____________________________________________________
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa80044e96f0, fffff80003c073d8, fffffa800650fc10} Unable to load image \SystemRoot\system32\DRIVERS\amd_xata.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for amd_xata.sys *** ERROR: Module load completed but symbols could not be loaded for amd_xata.sys *** WARNING: Unable to verify timestamp for amd_sata.sys *** ERROR: Module load completed but symbols could not be loaded for amd_sata.sys Probably caused by : amd_sata.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 time Arg2: fffffa80044e96f0, Physical Device Object of the stack Arg3: fffff80003c073d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: fffffa800650fc10, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: amd_sata.sys DEBUG_FLR_IMAGE_TIMESTAMP: 51cd1607 MODULE_NAME: amd_sata FAULTING_MODULE: fffff88000de0000 amd_sata CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre DPC_STACK_BASE: FFFFF80003C0DFB0 STACK_TEXT: fffff800`03c07388 fffff800`035468d2 : 00000000`0000009f 00000000`00000003 fffffa80`044e96f0 fffff800`03c073d8 : nt!KeBugCheckEx fffff800`03c07390 fffff800`034e185c : fffff800`03c074c0 fffff800`03c074c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0 fffff800`03c07430 fffff800`034e16f6 : fffff800`03687140 00000000`00064633 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c fffff800`03c074a0 fffff800`034e15de : 0000000e`ef60767e fffff800`03c07b18 00000000`00064633 fffff800`036548e8 : nt!KiProcessExpiredTimerList+0xc6 fffff800`03c07af0 fffff800`034e13c7 : 00000002`e9640ac1 00000002`00064633 00000002`e9640a6b 00000000`00000033 : nt!KiTimerExpiration+0x1be fffff800`03c07b90 fffff800`034ce8ca : fffff800`03651e80 fffff800`0365fcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277 fffff800`03c07c40 00000000`00000000 : fffff800`03c08000 fffff800`03c02000 fffff800`03c07c00 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_disk_IMAGE_amd_sata.sys BUCKET_ID: X64_0x9F_3_POWER_DOWN_disk_IMAGE_amd_sata.sys ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_disk_image_amd_sata.sys FAILURE_ID_HASH: {bd3723e5-7ce7-7570-8bcd-85961145548a} Followup: MachineOwner --------- 0: kd> !irp fffffa800650fc10 Irp is active with 5 stacks 3 is current (= 0xfffffa800650fd70) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned cmd flg cl Device File Completion-Context [ 16, 0] 0 0 fffffa80044e96f0 00000000 fffff880010ef648-00000000 \Driver\amd_sata amd_xata Args: 00000000 00000000 00000000 00000002 [ 16, 0] 0 0 fffffa80036c5ac0 00000000 fffff88001b6fd30-fffffa80047295a0 \Driver\amd_xata CLASSPNP!ClasspPowerUpCompletion Args: 00000000 00000000 00000000 00000002 >[ 16, 2] 0 e1 fffffa8004729060 00000000 fffff88000e05f50-00000000 Success Error Cancel pending \Driver\Disk partmgr!PmPowerCompletion Args: 00051100 00000001 00000001 00000002 [ 16, 2] 0 e1 fffffa80045ff890 00000000 00000000-00000000 pending \Driver\partmgr Args: 00051100 00000001 00000001 00000002 [ 0, 0] 0 0 00000000 00000000 00000000-fffffa80072be930 Args: 00000000 00000000 00000000 00000000 0: kd> lmvm amd_sata start end module name fffff880`00de0000 fffff880`00df8000 amd_sata T (no symbols) Loaded symbol image file: amd_sata.sys Image path: \SystemRoot\system32\DRIVERS\amd_sata.sys Image name: amd_sata.sys Timestamp: Fri Jun 28 10:20:15 2013 (51CD1607) CheckSum: 00014AE1 ImageSize: 00018000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4