Sign in with
Sign up | Sign in
Your question
Solved

Trying to Figure Out what caused the OS crash

Tags:
Last response: in Windows 8
Share
a b * Windows 8
September 15, 2013 8:34:55 PM

Windows 8 crashed just recently and I wanted to figure out why (wasnt at the computer at the time so didnt see it happen). I just installed a graphics card 2 days ago and wanted to make sure the issue I have now is not being caused by it. I have noticed that the boot device led stays lit while in bios, but goes off when I exit to windows, or when I go to the EZ Flash Utility and back out of it into the bios. More info on that issue can be found here: http://www.tomshardware.com/answers/id-1800634/cpu-fan-...

Im unfamiliar with how exactly to debug Windows 8 crashes, but apparently Windows has tools to download for that (I believe the name was Windbg). After grabbing that and running it here is what seems to be showing up:


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

Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff803`b5274000 PsLoadedModuleList = 0xfffff803`b5540a20
Debug session time: Sun Sep 15 22:56:33.622 2013 (UTC - 4:00)
System Uptime: 0 days 7:57:11.194
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006be9060, fffff803b51657f0, fffffa800d142010}

Unable to load image \SystemRoot\SysWow64\drivers\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 (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006be9060, Physical Device Object of the stack
Arg3: fffff803b51657f0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800d142010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5010ab1f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000c7f000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

TAG_NOT_DEFINED_c000000f: FFFFF803B516BFB0

STACK_TEXT:
fffff803`b51657b8 fffff803`b540a722 : 00000000`0000009f 00000000`00000003 fffffa80`06be9060 fffff803`b51657f0 : nt!KeBugCheckEx
fffff803`b51657c0 fffff803`b540a755 : fffffa80`07d69400 fffff803`b5224e61 00000000`00000001 fffff803`b53980a0 : nt!PopIrpWatchdogBugcheck+0xe2
fffff803`b5165820 fffff803`b52f71ea : fffffa80`07d69438 fffff803`b5165939 00000000`00000001 fffffa80`0670a940 : nt!PopIrpWatchdog+0x32
fffff803`b5165870 fffff803`b52f5655 : 00000000`00000000 fffff803`b52349f9 00000000`00140001 fffff803`b55700a0 : nt!KiProcessExpiredTimerList+0x22a
fffff803`b51659a0 fffff803`b52f7668 : fffff803`b556c180 fffff803`b556ef80 ffffffff`00000009 00000000`0010aa61 : nt!KiExpireTimerTable+0xa9
fffff803`b5165a40 fffff803`b52f6a06 : fffffa80`00000000 00001f80`00560080 00000000`00000000 00000000`00000002 : nt!KiTimerExpiration+0xc8
fffff803`b5165af0 fffff803`b52f79ba : fffff803`b556c180 fffff803`b556c180 00000000`00183de0 fffff803`b55c6880 : nt!KiRetireDpcList+0x1f6
fffff803`b5165c60 00000000`00000000 : fffff803`b5166000 fffff803`b5160000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

Followup: MachineOwner



^^ I don't understand all of this, but it looks like driver issues? Could someone shed more light on it?

More about : figure caused crash

a b * Windows 8
September 15, 2013 8:41:36 PM

AiCharger.sys check for the driver of the aicharger on the board maker site .
m
0
l
a b * Windows 8
September 15, 2013 8:58:53 PM

Ai charger is a utility to quick charge things like phones/tablets etc. through the usb port, and I thought it was just a program? In which case I'm not really sure where the driver for it would be if it isnt part of the drivers for the usb. I do know that it's the latest version, and it's been working fine for about a month now (I didn't have anything plugged in at the time either).
m
0
l

Best solution

a b * Windows 8
September 15, 2013 9:09:03 PM

pci.sys this is the file you need to check try a windows 8 repair with your os cd disk .
Share
!