Quantcast
Channel: Windows 8.1 Performance forum
Viewing all articles
Browse latest Browse all 1658

Used WinDBG to diagnose error in windows 8

$
0
0
ive been having a problem with my laptop just turning off and then when starting back up it tells me there was a problem and needed to restart. i used windbg to try and find the problem but i dont really understand what it means so im looking for some help.
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112113-19671-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 9200 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff802`9326f000 PsLoadedModuleList = 0xfffff802`9353ba20
Debug session time: Thu Nov 21 01:01:37.024 2013 (UTC - 5:00)
System Uptime: 0 days 2:05:40.335
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8003f29060, fffff802924a7930, fffffa800410bbd0}

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

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5010ab1f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f1f000 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:  FFFFF802924ADFB0

STACK_TEXT:  
fffff802`924a78f8 fffff802`93405722 : 00000000`0000009f 00000000`00000003 fffffa80`03f29060 fffff802`924a7930 : nt!KeBugCheckEx
fffff802`924a7900 fffff802`93405755 : fffffa80`06d36f00 fffff802`9321fe3b 00000000`00000001 fffff802`933930a0 : nt!PopIrpWatchdogBugcheck+0xe2
fffff802`924a7960 fffff802`932f21ea : fffffa80`06d36f38 fffff802`924a7a79 00000000`00000001 fffffa80`031c6040 : nt!PopIrpWatchdog+0x32
fffff802`924a79b0 fffff802`932f0655 : 00000000`00000000 fffff802`932f1cff 00000000`00140001 fffff802`9356b780 : nt!KiProcessExpiredTimerList+0x22a
fffff802`924a7ae0 fffff802`932f2668 : fffff802`93567180 fffff802`93569f80 00000000`00000008 00000000`00046398 : nt!KiExpireTimerTable+0xa9
fffff802`924a7b80 fffff802`932f1a06 : fffffa80`00000000 00001f80`00560080 00000000`00000000 00000000`00000002 : nt!KiTimerExpiration+0xc8
fffff802`924a7c30 fffff802`932f29ba : fffff802`93567180 fffff802`93567180 00000000`001a3db0 fffff802`935c1880 : nt!KiRetireDpcList+0x1f6
fffff802`924a7da0 00000000`00000000 : fffff802`924a8000 fffff802`924a2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  6.2.9200.16384

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_rtwlane_IMAGE_pci.sys

BUCKET_ID:  0x9F_3_POWER_DOWN_rtwlane_IMAGE_pci.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_rtwlane_image_pci.sys

FAILURE_ID_HASH:  {3e2d1ac0-08ea-222a-afe0-52cffb7dce4d}

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

0: kd>


Viewing all articles
Browse latest Browse all 1658

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>