bsod driver power state failure 3 mins after pc starts.

LoneBear · 02 Nov 2015

hey there
i have been have this problem for a while now and i think its time to get it sorted out. i do believe my drivers are all up to date, i have also updated my bios to the newest version. i have done abit of research on this and more then likely a driver issue.

so please point me in the right direction

Problem signature
Problem Event Name: BlueScreen
Code: 9f
Parameter 1: 3
Parameter 2: ffffe00131c8ae20
Parameter 3: ffffd0013af30960
Parameter 4: ffffe0013497e620
OS version: 6_3_9600
Service Pack: 0_0
Product: 256_1
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 2057

mini dump attached

thanks

koolkat77 · 03 Nov 2015

Code:

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


Loading Dump File [C:\Users\Yusra\Downloads\IRON-CLAD-02_11_2015_183423_07\110215-9406-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
Built by: 9600.18066.amd64fre.winblue_ltsb.150928-1002
Machine Name:
Kernel base = 0xfffff803`89202000 PsLoadedModuleList = 0xfffff803`894d7630
Debug session time: Tue Nov  3 00:24:35.967 2015 (UTC + 6:00)
System Uptime: 0 days 6:54:14.663
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, ffffe00131c8ae20, ffffd0013af30960, ffffe0013497e620}

*** WARNING: Unable to verify timestamp for ViaHub3.sys
*** ERROR: Module load completed but symbols could not be loaded for ViaHub3.sys
Probably caused by : ViaHub3.sys

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

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

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ViaHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f18eff1

MODULE_NAME: ViaHub3

FAULTING_MODULE: fffff801c4353000 ViaHub3

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:  FFFFD0013AF37FB0

STACK_TEXT:  
ffffd001`3af30928 fffff803`89406dfa : 00000000`0000009f 00000000`00000003 ffffe001`31c8ae20 ffffd001`3af30960 : nt!KeBugCheckEx
ffffd001`3af30930 fffff803`89406d1a : ffffe001`35488130 00000000`00000000 00000000`00000000 fffff803`89287a59 : nt!PopIrpWatchdogBugcheck+0xde
ffffd001`3af30990 fffff803`89288ed8 : 00000000`00000000 ffffd001`3af30ae0 00000000`00000001 00000000`00000002 : nt!PopIrpWatchdog+0x32
ffffd001`3af309e0 fffff803`893553ea : ffffd001`3af07180 ffffd001`3af07180 ffffd001`3af132c0 ffffe001`34a37580 : nt!KiRetireDpcList+0x4f8
ffffd001`3af30c60 00000000`00000000 : ffffd001`3af31000 ffffd001`3af2b000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_xusb22_IMAGE_ViaHub3.sys

BUCKET_ID:  0x9F_3_POWER_DOWN_xusb22_IMAGE_ViaHub3.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_xusb22_image_viahub3.sys

FAILURE_ID_HASH:  {47df79db-78b6-c769-8dad-66eb9ddbd7d2}

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

1: kd> lmvm ViaHub3
start             end                 module name
fffff801`c4353000 fffff801`c438a000   ViaHub3  T (no symbols)           
    Loaded symbol image file: ViaHub3.sys
    Image path: \SystemRoot\System32\drivers\ViaHub3.sys
    Image name: ViaHub3.sys
    Timestamp:        Fri Jan 20 10:39:13 2012 (4F18EFF1)
    CheckSum:         0003F14B
    ImageSize:        00037000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Check for an update on this driver. Driver Reference Table

Sometimes drivers remain and do not get completely uninstalled.

Driver Removal Process:

Download Driver Sweeper to the desired location.
Extract the files from the zip.
Uninstall the driver Program & Features - Control Panel.
Run Driver Sweeper, check the drivers you want to uninstall or clean registry leftovers of.

Link to full tutorial: Drivers - Clean Left over Files after Uninstalling