Share via

Driver Power State Failure

Anonymous
2015-03-04T08:29:14+00:00

After trying to restart my PC I get the BSoD stating the below information.  Can anyone tell me what it means.  I have a copy of the dump file if needed.

Thanks,

Joseph

Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_8db07a48e649168f3c2560cdc29fa85ed852bf15_00000000_cab_1285c500\030415-52921-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 (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 9600.17630.amd64fre.winblue_r7.150109-2022

Machine Name:

Kernel base = 0xfffff8038d48d000 PsLoadedModuleList = 0xfffff8038d766250

Debug session time: Wed Mar  4 03:06:45.738 2015 (UTC - 5:00)

System Uptime: 0 days 2:48:59.621

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, {4, 12c, ffffe001daad5040, fffff8038ef08ac0}

Implicit thread is now ffffe001`daad5040

Probably caused by : ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+6a )

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: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp

 subsystem.

Arg2: 000000000000012c, Timeout in seconds.

Arg3: ffffe001daad5040, The thread currently holding on to the Pnp lock.

Arg4: fffff8038ef08ac0, nt!TRIAGE_9F_PNP on Win7 and higher

Debugging Details:

Implicit thread is now ffffe001`daad5040

DUMP_FILE_ATTRIBUTES: 0x8

  Kernel Generated Triage Dump

DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  ffffe001daad5040

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

LAST_CONTROL_TRANSFER:  from fffff8038d66b356 to fffff8038d5dd9a0

STACK_TEXT: 

fffff8038ef08a88 fffff8038d66b356 : 000000000000009f 0000000000000004 000000000000012c ffffe001daad5040 : nt!KeBugCheckEx

fffff8038ef08a90 fffff8038d8192b6 : ffffe00100000000 fffff80300000000 000000000005e600 fffff80300000000 : nt!PnpBugcheckPowerTimeout+0x6a

fffff8038ef08af0 fffff8038d541428 : 000000000000000a 0000000000da7a64 fffff8038ef08c20 0000000000000002 : nt!PopBuildDeviceNotifyListWatchdog+0x16

fffff8038ef08b20 fffff8038d5e14ea : fffff8038d790180 fffff8038d790180 fffff8038d7e9a00 ffffe001d8c29080 : nt!KiRetireDpcList+0x4f8

fffff8038ef08da0 0000000000000000 : fffff8038ef09000 fffff8038ef03000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  .thread 0xffffe001daad5040 ; kb

FOLLOWUP_IP:

nt!PnpBugcheckPowerTimeout+6a

fffff803`8d66b356 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PnpBugcheckPowerTimeout+6a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  54b0c2f7

IMAGE_VERSION:  6.3.9600.17630

BUCKET_ID_FUNC_OFFSET:  6a

FAILURE_BUCKET_ID:  0x9F_4_nt!PnpBugcheckPowerTimeout

BUCKET_ID:  0x9F_4_nt!PnpBugcheckPowerTimeout

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_4_nt!pnpbugcheckpowertimeout

FAILURE_ID_HASH:  {626456dc-f029-5ddb-d8eb-a53e0f3ffebc}

Followup: MachineOwner

0: kd> lmvm nt

start             end                 module name

fffff8038d48d000 fffff8038dc21000   nt         (pdb symbols)          c:\symbols\ntkrnlmp.pdb\2BCBB42C1BC741DF9E1D4E2D28DAC9631\ntkrnlmp.pdb

    Loaded symbol image file: ntkrnlmp.exe

    Mapped memory image file: c:\symbols\ntoskrnl.exe\54B0C2F7794000\ntoskrnl.exe

    Image path: ntkrnlmp.exe

    Image name: ntkrnlmp.exe

    Timestamp:        Sat Jan 10 01:13:11 2015 (54B0C2F7)

    CheckSum:         0072D721

    ImageSize:        00794000

    File version:     6.3.9600.17630

    Product version:  6.3.9600.17630

    File flags:       0 (Mask 3F)

    File OS:          40004 NT Win32

    File type:        1.0 App

    File date:        00000000.00000000

    Translations:     0409.04b0

    CompanyName:      Microsoft Corporation

    ProductName:      Microsoft® Windows® Operating System

    InternalName:     ntkrnlmp.exe

    OriginalFilename: ntkrnlmp.exe

    ProductVersion:   6.3.9600.17630

    FileVersion:      6.3.9600.17630 (winblue_r7.150109-2022)

    FileDescription:  NT Kernel & System

    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous
2015-03-04T17:45:17+00:00

First, uninstall TuneUpUtilities and all of it's components immediately.

Why you should not use Registry Cleaners and Optimization Tools.

http://www.bleepingcomputer.com/forums/t/407147/answers-to-common-security-questions-best-practices/?p=2853053

When you are done with that, download "autoruns" and use it to locate and delete ksapi64.sys, a Kingsoft Antivirus driver, probably leftover when you uninstalled it after making certain that all Microsoft entries have been hidden, to eliminate the possibility of a mistake.(instructions in the youtube video link below.)

ksapi64.sys, is probably conflicting with AVG, and causing performance and corruption issues. If you still crash, after removing kingsoft, upload and share a link to the new dump files.

Autoruns for Windows

v13.01

This utility, which has the most comprehensive knowledge of auto-starting locations of any startup monitor, shows you what programs are configured to run during system bootup or login, and shows you the entries in the order Windows processes them. These programs include ones in your startup folder, Run, RunOnce, and other Registry keys. You can configure Autoruns to show other locations, including Explorer shell extensions, toolbars, browser helper objects, Winlogon notifications, auto-start services, and much more. Autoruns goes way beyond the MSConfig utility bundled with Windows Me and XP.Autoruns' Hide Signed Microsoft Entries option helps you to zoom in on third-party auto-starting images that have been added to your system and it has support for looking at the auto-starting images configured for other accounts configured on a system

https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

How to use Autoruns.

https://www.youtube.com/watch?v=HhtSDsQYi28

Was this answer helpful?

0 comments

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-03-04T16:54:30+00:00

    I have uploaded them to my OneDrive.  Below is the link to access them.

    https://onedrive.live.com/redir?resid=7F59D844A755FBB9!16569&authkey=!ALJ2S2yh8GTTjqc&ithint=folder%2cdmp

    Thanks,

    Joseph

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-03-04T13:03:23+00:00

    The files that I have will follow.  Are these the ones you need?

    030415-52921-01.dmp

    Report.wer

    WER-102953-0.sysdata

    WERC406.tmp.WERInternalMetadata

    Yes.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-03-04T11:20:25+00:00

    The files that I have will follow.  Are these the ones you need?

    030415-52921-01.dmp

    Report.wer

    WER-102953-0.sysdata

    WERC406.tmp.WERInternalMetadata

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-03-04T10:31:30+00:00

    To be able to troubleshoot what might be causing your system to crash, we need the dump files.

    Please refer to the link below for steps to retrieve, zip and upload them to the file sharing site like onedrive, google's "dropbox, etc.

    Blue Screen of Death Co-Authored by ZigZag3143& JMH3143

    **http://answers.microsoft.com/en-us/windows/wiki/windows\_other-system/blue-screen-of-death-bsod/1939df35-283f-4830-a4dd-e95ee5d8669d**

    Was this answer helpful?

    0 comments