Help With Debugging a Crash

[mc962]

I noticed that my computer crashed today while I was out and it was sleeping. I downloaded WinDbg and I believe I set it up correctly, but am not quite sure how to read it properly.

These are the specs of my computer: http://pcpartpicker.com/user/mc962/saved/25iX
And I'm using Windows 8.1
Unless any new drivers came out in the last 2 weeks all my drivers as well as my BIOS are up to date

For those that don't wish to read what's below, I'll try to sum it up from what I was able to understand of it:

Driver state power failure (9f) was one of the things that popped up there
There was also this bit, which I believe I've seen in another crash a few months ago:
MODULE_NAME: pci
FAULTING_MODULE: fffff800004ae000 pci
FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_acpi_image_pci.sys
This also looked like an important bit under the Followup: section
FileDescription: NT Plug and Play PCI Enumerator
It did mention that there was insufficient dump file size

Again the ^above is just a really short summary of what I thought looked important, the full text is below. Can anyone help me decode this, and if possible suggest solutions? The crashes are very infrequent and I believe have only happened at times when the computer has been sleeping, but I would like to figure out what is happening if possible




Below is the text that I got from the dump that was analyzed, no need to read further if you don't want to see it:----------------------------------------------------------------------------------------------------


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


Loading Dump File [C:\Windows\Minidump\013114-4937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff801`5ba1a000 PsLoadedModuleList = 0xfffff801`5bcde990
Debug session time: Fri Jan 31 00:02:02.641 2014 (UTC - 5:00)
System Uptime: 16 days 9:07:27.824
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 9F, {3, ffffe00000fa3880, fffff8015d89d840, ffffe00036c34bd0}

Unable to load image AiCharger.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AiCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AiCharger.sys
Probably caused by : pci.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: ffffe00000fa3880, Physical Device Object of the stack
Arg3: fffff8015d89d840, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe00036c34bd0, The blocked IRP

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


DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5215f837

MODULE_NAME: pci

FAULTING_MODULE: fffff800004ae000 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.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE: FFFFF8015D8A4FB0

STACK_TEXT:
fffff801`5d89d808 fffff801`5bc111a6 : 00000000`0000009f 00000000`00000003 ffffe000`00fa3880 fffff801`5d89d840 : nt!KeBugCheckEx
fffff801`5d89d810 fffff801`5bc110c6 : ffffe000`35ca5e50 00000000`00000008 00000000`00000002 fffff801`5ba76a04 : nt!PopIrpWatchdogBugcheck+0xde
fffff801`5d89d870 fffff801`5bac7f64 : ffffe000`35ca5e88 fffff801`5d89d939 ffffe000`35ca5ec8 00000000`00000002 : nt!PopIrpWatchdog+0x32
fffff801`5d89d8c0 fffff801`5bac8478 : 00000000`00000000 ffffe000`067b5460 fffff801`5bd08180 fffff801`5bd0c000 : nt!KiProcessExpiredTimerList+0x1d8
fffff801`5d89d9a0 fffff801`5bb24478 : fffff801`5bd08180 00000000`00da7a64 fffff801`0337c85c 00000000`0337c874 : nt!KiExpireTimerTable+0x218
fffff801`5d89da40 fffff801`5ba74abc : ffffe000`00000000 00001f80`00000001 00000cdf`217281bf 00000000`00000002 : nt!KiTimerExpiration+0x148
fffff801`5d89daf0 fffff801`5bb6b7ea : fffff801`5bd08180 fffff801`5bd08180 00000000`001a3fe0 fffff801`5bd60a80 : nt!KiRetireDpcList+0x19c
fffff801`5d89dc60 00000000`00000000 : fffff801`5d89e000 fffff801`5d898000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 6.3.9600.16384

FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_ACPI_IMAGE_pci.sys

BUCKET_ID: 0x9F_3_POWER_DOWN_ACPI_IMAGE_pci.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_acpi_image_pci.sys

FAILURE_ID_HASH: {91e270e6-abe3-8adb-6919-2785fb7b1574}

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

0: kd> lmvm pci
start end module name
fffff800`004ae000 fffff800`004f7000 pci (pdb symbols) c:\symbols\pci.pdb\719D117970C846899E06177D8E992F962\pci.pdb
Loaded symbol image file: pci.sys
Mapped memory image file: c:\symbols\pci.sys\5215F83749000\pci.sys
Image path: pci.sys
Image name: pci.sys
Timestamp: Thu Aug 22 07:38:31 2013 (5215F837)
CheckSum: 0004DF95
ImageSize: 00049000
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: pci.sys
OriginalFilename: pci.sys
ProductVersion: 6.3.9600.16384
FileVersion: 6.3.9600.16384 (winblue_rtm.130821-1623)
FileDescription: NT Plug and Play PCI Enumerator
LegalCopyright: © Microsoft Corporation. All rights reserved.

 

[johnbl]

(you might want to just update your ethernet driver to start with, just my guess as to the cause of the failure)

-it looks like windows told the system to go to sleep or shutdown and the hardware got confused, did not respond and the OS called a bugcheck for failing hardware.

first you will want to update your BIOS, this configures the hardware and tells windows what and how to talk to the hardware. After you update, check to your BIOS power management settings or set everything to the defaults. I would also update any device drivers for you motherboard, look for chipset drivers to install.

note this will not be caused by PCI.sys, it will be caused by a driver that failed to respond.
you will want to update your 3rd party drivers for you machine from motherboard vendor or the hardware vendor.
(very common for ethernet drivers to not handle power management correctly)

look here for ethernet driver from intel

https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Ethernet+Components&ProductLine=Ethernet+Controllers&ProductProduct=Intel%C2%AE+Ethernet+Connection+I217-V&ProdId=3682&LineId=976&FamilyId=2280

 

[mc962]

My drivers and BIOS are all updated. However, I did notice that the Intel Management Engine Interface driver wasnt working properly according to the device manager. I attempted to reinstall it but the installation failed at the end, some error about being unable to install one or more of the services. However, after attempting the update I see no more errors in Device manager. Could Intel MEI have caused this or would it be something else?

*I did, however, update the network driver as I saw that it is a bit newer than what ASUS has at the moment

 

[johnbl]

it could be the hard drive not responding correctly to sleep functions (low power link states) These were off by default on windows 7,and were turnned on in windows 8. very common that they don't work in a lot of hardware without a firmware update, or patch. You can go to the control panel, power management setting and tweak the one for your hard drive or ssd and tell it not to power down. (or make it power down faster so you can find out if it was the cause of the error)