Please help me read my .dmp file in windows 8.1.

Dear everyone!!!

Not something shocking I believe, but I hope there are people here which had similar problems or perhaps even EXACTLY the same ones as me :-)

I managed to open the .dmp file with the help of WinDbg. And I put the "Symbols" directory on the OS drive.

This is what it said after analyzing it:

7: 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: ffffe001cb5eb060, Physical Device Object of the stack
Arg3: ffffd0016a1db960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe001cb52e010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4

MODULE_NAME: pci

FAULTING_MODULE: fffff8019f81e000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_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: FFFFD0016A1E2FB0

STACK_TEXT:
ffffd001`6a1db928 fffff803`16210782 : 00000000`0000009f 00000000`00000003 ffffe001`cb5eb060 ffffd001`6a1db960 : nt!KeBugCheckEx
ffffd001`6a1db930 fffff803`162106a2 : ffffe001`cb5e0618 00000000`00000001 ffffe001`cb5e0650 fffff803`160ac391 : nt!PopIrpWatchdogBugcheck+0xde
ffffd001`6a1db990 fffff803`160ae2d8 : 00000000`00000000 ffffd001`6a1dbae0 00000000`00000001 00000000`00000002 : nt!PopIrpWatchdog+0x32
ffffd001`6a1db9e0 fffff803`1615c7ea : ffffd001`6a1ac180 ffffd001`6a1ac180 ffffd001`6a1b83c0 ffffe001`cb28f040 : nt!KiRetireDpcList+0x4f8
ffffd001`6a1dbc60 00000000`00000000 : ffffd001`6a1dc000 ffffd001`6a1d6000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 6.3.9600.17238

FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_3_acpi_image_pci.sys

FAILURE_ID_HASH: {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}

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


I never had this one before but I remember I turned on my Asus laptop from sleep mode with no AC power connected. So it's running from the battery. Then I opened some torrents to download something through wifi. After a few minutes when I came back my laptop was rebooted and I checked the Minidump dir (because I remember) and indeed, there was one .dmp file and it's the one above.

Can someone help me determine what really caused it and how I could change it? Thanks a lot!
3 answers Last reply
More about read dmp file windows
  1. Looks like some component was ignoring or stalling I/O requests from a driver. Unfortunately, from your dump I cannot determine what component it is nor can I tell if the issue is actually software related. Open the crash dump with WhoCrashed to see if it can diagnose the issue for you, or at least provide a source. If you have a history of mindless torrenting, then I would not rule out malware wiping some system drivers. You can run:

    sfc /scannow

    to check. Malware or not, I nevertheless discourage torrenting, though the message falls on deaf ears. That's okay, row your boat however you like. Report back if you want to provide more info / need more help
  2. Thanks for your reply. I personally do not believe it has anything to do with possible malware attacks. Of course, I can never be too sure, that is correct. However, I do have a bought version of malware bytes anti malware and norton 360. Add I get some warnings sometimes through anti malware but nothing that couldn't be blocked.

    I will try WhoCrashed but for now I can't get that link of yours.

    EDIT: Link worked now and got it installed and runned it. Could't also give us more specific information to my despite.
  3. That's unfortunate, but WhoCrashed isn't perfect. I you will, open the dump file back up with something like BlueScreenView. From there, you can actually start web searches regarding the culprit driver and the crash parameter, if you please. You should also be able to export the report to txt, which is what I would like to see. I hope you can find some resolution!
Ask a new question

Read More

Windows 8