Page 1 of 9 123 ... LastLast
  1.    15 Mar 2016 #1
    Join Date : Dec 2015
    Posts : 109
    windows 10

    All of a sudden 2 new Driver Power State Failure BSOD have happened!!


    3 month old laptop, i76700 HQ Quad Core Processor, NVidia GTX 950m, 512 SSD, 4K Touchscreen, 16 GB RAM

    Axe0 I am trying to upload the 2 dump files but I am having a lot of trouble. First I can't even find the one that just happened 30 minutes ago and second, there is one from the other day but it won't let me open it(can't find program to open it but I already zipped it) Then I followed the instructions to upload it and it said invalid file.

    What do I do??

    I want you to look at the 2 dump files but I can't find the most recent one and it says invalid file.

    Thx
      My ComputerSystem Spec
  2.    15 Mar 2016 #2
    Join Date : Jun 2015
    Posts : 12,960
    Windows 10 Pro

    I suggest that you try following below tutorial(s)
      My ComputersSystem Spec
  3.    15 Mar 2016 #3
    Join Date : Dec 2015
    Posts : 109
    windows 10
    Thread Starter

    Quote Originally Posted by axe0 View Post
    I suggest that you try following below tutorial(s)
    I read it and it still is not working

    I chose the file(031316-5296-01.dmp) and then I clicked on upload. After 1 second it listed my file and then says "invalid file"

    Now what?

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




    Loading Dump File [C:\Users\Michael B\Desktop\LAPTOP-TPCUEM10-Tue_03_15_2016__74732_50\031316-5296-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 10586 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 10586.122.amd64fre.th2_release_inmarket.160222-1549
    Machine Name:
    Kernel base = 0xfffff802`eb405000 PsLoadedModuleList = 0xfffff802`eb6e3cf0
    Debug session time: Sun Mar 13 22:51:53.698 2016 (UTC - 7:00)
    System Uptime: 8 days 5:10:41.923
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................................................
    Loading User Symbols
    Loading unloaded module list
    ....................................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************


    Use !analyze -v to get detailed debugging information.


    BugCheck 9F, {3, ffffe001fe1d9650, fffff802edad2890, ffffe00201a776b0}


    Implicit thread is now ffffe001`fbebd040
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.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: ffffe001fe1d9650, Physical Device Object of the stack
    Arg3: fffff802edad2890, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00201a776b0, The blocked IRP


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


    Implicit thread is now ffffe001`fbebd040


    DUMP_CLASS: 1


    DUMP_QUALIFIER: 400


    BUILD_VERSION_STRING: 10586.122.amd64fre.th2_release_inmarket.160222-1549


    SYSTEM_MANUFACTURER: TOSHIBA


    SYSTEM_PRODUCT_NAME: Satellite S55t-C


    SYSTEM_SKU: PSPUGU


    SYSTEM_VERSION: PSPUGU-00400D


    BIOS_VENDOR: INSYDE Corp.


    BIOS_VERSION: 1.20


    BIOS_DATE: 10/08/2015


    BASEBOARD_MANUFACTURER: FF50


    BASEBOARD_PRODUCT: 06F4


    BASEBOARD_VERSION: Type2 - Board Version


    DUMP_TYPE: 2


    DUMP_FILE_ATTRIBUTES: 0x8
    Kernel Generated Triage Dump


    BUGCHECK_P1: 3


    BUGCHECK_P2: ffffe001fe1d9650


    BUGCHECK_P3: fffff802edad2890


    BUGCHECK_P4: ffffe00201a776b0


    DRVPOWERSTATE_SUBCODE: 3


    FAULTING_THREAD: fbebd040


    IMAGE_NAME: pci.sys


    DEBUG_FLR_IMAGE_TIMESTAMP: 5632d60a


    MODULE_NAME: pci


    FAULTING_MODULE: fffff800ae800000 pci


    CPU_COUNT: 8


    CPU_MHZ: a20


    CPU_VENDOR: GenuineIntel


    CPU_FAMILY: 6


    CPU_MODEL: 5e


    CPU_STEPPING: 3


    CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 33'00000000 (cache) 33'00000000 (init)


    CUSTOMER_CRASH_COUNT: 1


    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


    BUGCHECK_STR: 0x9F


    PROCESS_NAME: System


    CURRENT_IRQL: 2


    ANALYSIS_SESSION_HOST: LAPTOP-TPCUEM10


    ANALYSIS_SESSION_TIME: 03-15-2016 08:36:13.0216


    ANALYSIS_VERSION: 10.0.10586.567 amd64fre


    STACK_TEXT:
    ffffd001`8f916570 fffff802`eb47b3ea : 00000000`00000000 00000000`00000001 ffffe002`09b203f8 ffffe002`00feb800 : nt!KiSwapContext+0x76
    ffffd001`8f9166b0 fffff802`eb47ae79 : ffffe002`09e87010 ffffe001`fe15360e 00000000`00000000 00000000`00000001 : nt!KiSwapThread+0x15a
    ffffd001`8f916760 fffff802`eb47aae5 : 00000000`00000004 00000000`00000000 ffffffff`ffffffd2 00000000`00000000 : nt!KiCommitThreadWait+0x149
    ffffd001`8f9167f0 fffff800`af131a98 : ffffd001`8f916918 ffffe001`00000000 ffffe001`fe156b00 ffffc001`fbef4300 : nt!KeWaitForSingleObject+0x375
    ffffd001`8f9168b0 fffff800`af1317fd : ffffd001`00000000 ffffc002`07da7ab0 ffffe001`fd560c10 00000000`00000004 : ACPI!SyncEvalObject+0x258
    ffffd001`8f916960 fffff800`af13c89b : 00000000`00000000 fffff802`eb445b49 00000000`00000000 ffffc001`fbef43f0 : ACPI!AMLIEvalNameSpaceObject+0xad
    ffffd001`8f9169c0 fffff800`af131427 : ffffe001`fd560c10 ffffc001`00000004 00000000`00000000 ffffc002`07da7ab0 : ACPI!ACPIIoctlEvalControlMethod+0x8b
    ffffd001`8f916a20 fffff800`af1310be : ffffe001`fbfa08d0 00000000`00000007 ffffe001`fd560d70 fffff800`00000004 : ACPI!ACPIIrpDispatchDeviceControl+0x157
    ffffd001`8f916a60 fffff800`b094cc72 : 00000000`00000007 00000000`00000000 ffffe002`012c4120 ffffe002`012c4270 : ACPI!ACPIDispatchIrp+0xbe
    ffffd001`8f916ad0 fffff800`b373c054 : ffffe001`fd560c10 ffffe001`fd560d70 ffffe001`fd560c10 ffffe002`012c4120 : dxgkrnl!DpiDispatchIoctl+0xa2
    ffffd001`8f916bf0 ffffe001`fd560c10 : ffffe001`fd560d70 ffffe001`fd560c10 ffffe002`012c4120 ffffe002`012c4120 : nvlddmkm+0x14c054
    ffffd001`8f916bf8 ffffe001`fd560d70 : ffffe001`fd560c10 ffffe002`012c4120 ffffe002`012c4120 ffffe002`012c4120 : 0xffffe001`fd560c10
    ffffd001`8f916c00 ffffe001`fd560c10 : ffffe002`012c4120 ffffe002`012c4120 ffffe002`012c4120 ffffe001`fd560c10 : 0xffffe001`fd560d70
    ffffd001`8f916c08 ffffe002`012c4120 : ffffe002`012c4120 ffffe002`012c4120 ffffe001`fd560c10 fffff800`b373bf6e : 0xffffe001`fd560c10
    ffffd001`8f916c10 ffffe002`012c4120 : ffffe002`012c4120 ffffe001`fd560c10 fffff800`b373bf6e 00000000`c0000002 : 0xffffe002`012c4120
    ffffd001`8f916c18 ffffe002`012c4120 : ffffe001`fd560c10 fffff800`b373bf6e 00000000`c0000002 ffffe002`014a7000 : 0xffffe002`012c4120
    ffffd001`8f916c20 ffffe001`fd560c10 : fffff800`b373bf6e 00000000`c0000002 ffffe002`014a7000 ffffe001`fd560d70 : 0xffffe002`012c4120
    ffffd001`8f916c28 fffff800`b373bf6e : 00000000`c0000002 ffffe002`014a7000 ffffe001`fd560d70 fffff800`b366ad66 : 0xffffe001`fd560c10
    ffffd001`8f916c30 00000000`c0000002 : ffffe002`014a7000 ffffe001`fd560d70 fffff800`b366ad66 00000000`0032c004 : nvlddmkm+0x14bf6e
    ffffd001`8f916c38 ffffe002`014a7000 : ffffe001`fd560d70 fffff800`b366ad66 00000000`0032c004 fffff800`b366ad77 : 0xc0000002
    ffffd001`8f916c40 ffffe001`fd560d70 : fffff800`b366ad66 00000000`0032c004 fffff800`b366ad77 ffffe001`fd261930 : 0xffffe002`014a7000
    ffffd001`8f916c48 fffff800`b366ad66 : 00000000`0032c004 fffff800`b366ad77 ffffe001`fd261930 ffffe002`014a7000 : 0xffffe001`fd560d70
    ffffd001`8f916c50 00000000`0032c004 : fffff800`b366ad77 ffffe001`fd261930 ffffe002`014a7000 ffffe002`012c4120 : nvlddmkm+0x7ad66
    ffffd001`8f916c58 fffff800`b366ad77 : ffffe001`fd261930 ffffe002`014a7000 ffffe002`012c4120 00000000`00000200 : 0x32c004
    ffffd001`8f916c60 ffffe001`fd261930 : ffffe002`014a7000 ffffe002`012c4120 00000000`00000200 ffffe002`10739000 : nvlddmkm+0x7ad77
    ffffd001`8f916c68 ffffe002`014a7000 : ffffe002`012c4120 00000000`00000200 ffffe002`10739000 00000000`0000101c : 0xffffe001`fd261930
    ffffd001`8f916c70 ffffe002`012c4120 : 00000000`00000200 ffffe002`10739000 00000000`0000101c 00000000`00000000 : 0xffffe002`014a7000
    ffffd001`8f916c78 00000000`00000200 : ffffe002`10739000 00000000`0000101c 00000000`00000000 ffffd001`8f916cc0 : 0xffffe002`012c4120
    ffffd001`8f916c80 ffffe002`10739000 : 00000000`0000101c 00000000`00000000 ffffd001`8f916cc0 ffffd001`8f916cb0 : 0x200
    ffffd001`8f916c88 00000000`0000101c : 00000000`00000000 ffffd001`8f916cc0 ffffd001`8f916cb0 fffff802`eb4f4643 : 0xffffe002`10739000
    ffffd001`8f916c90 00000000`00000000 : ffffd001`8f916cc0 ffffd001`8f916cb0 fffff802`eb4f4643 ffffe002`012c4120 : 0x101c




    STACK_COMMAND: .thread 0xffffe001fbebd040 ; kb


    THREAD_SHA1_HASH_MOD_FUNC: f00f7463c690d8ba5b06e07930e7dc1c4a3c96d3


    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 079f5d560f4cf01a2c73f7c0f206d036087d0938


    THREAD_SHA1_HASH_MOD: 5fac8d07f1a073ea7e8bd3180119714826c8556e


    FOLLOWUP_NAME: MachineOwner


    IMAGE_VERSION: 10.0.10586.0


    FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys


    BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys


    PRIMARY_PROBLEM_CLASS: 0x9F_3_ACPI_IMAGE_pci.sys


    TARGET_TIME: 2016-03-14T05:51:53.000Z


    OSBUILD: 10586


    OSSERVICEPACK: 0


    SERVICEPACK_NUMBER: 0


    OS_REVISION: 0


    SUITE_MASK: 784


    PRODUCT_TYPE: 1


    OSPLATFORM_TYPE: x64


    OSNAME: Windows 10


    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal


    OS_LOCALE:


    USER_LCID: 0


    OSBUILD_TIMESTAMP: 2016-02-22 23:16:30


    BUILDDATESTAMP_STR: 160222-1549


    BUILDLAB_STR: th2_release_inmarket


    BUILDOSVER_STR: 10.0.10586.122.amd64fre.th2_release_inmarket.160222-1549


    ANALYSIS_SESSION_ELAPSED_TIME: 44a


    ANALYSIS_SOURCE: KM


    FAILURE_ID_HASH_STRING: km:0x9f_3_acpi_image_pci.sys


    FAILURE_ID_HASH: {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}


    Followup: MachineOwner
    ---------
      My ComputerSystem Spec
  4.    15 Mar 2016 #4
    Join Date : Dec 2015
    Posts : 109
    windows 10
    Thread Starter

    think i got it uploaded now too. I still don't know what happened to the BSOD this morning. The one I have uploaded is from Sunday night.

    Please help Axe0
      My ComputerSystem Spec
  5.    15 Mar 2016 #5
    Join Date : Jun 2015
    Posts : 12,960
    Windows 10 Pro

    Dumps arent supported for direct upload, which is why a zip is being created when running the tool.

    I'll check the file when I have time.
      My ComputersSystem Spec
  6.    15 Mar 2016 #6
    Join Date : Jun 2015
    Posts : 12,960
    Windows 10 Pro

    Pretty clear, nvidia display drivers are a bit outdated.
    Code:
    0: kd> lmvm nvlddmkm
    Browse full module list
    start             end                 module name
    fffff800`b35f0000 fffff800`b40e1000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Browse all global symbols  functions  data
        Timestamp:        Thu Oct 15 04:58:52 2015 (561F166C)
        CheckSum:         00AB4560
        ImageSize:        00AF1000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My ComputersSystem Spec
  7.    15 Mar 2016 #7
    Join Date : Dec 2015
    Posts : 109
    windows 10
    Thread Starter

    Quote Originally Posted by axe0 View Post
    Pretty clear, nvidia display drivers are a bit outdated.
    Code:
    0: kd> lmvm nvlddmkm
    Browse full module list
    start             end                 module name
    fffff800`b35f0000 fffff800`b40e1000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Browse all global symbols  functions  data
        Timestamp:        Thu Oct 15 04:58:52 2015 (561F166C)
        CheckSum:         00AB4560
        ImageSize:        00AF1000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Okay thx but Toshiba doesn't have any new drivers on their support page. What do I do? Last update for nvidia drivers was 3 months ago which I downloaded from Toshiba page.
      My ComputerSystem Spec
  8.    15 Mar 2016 #8
    Join Date : Jun 2015
    Posts : 12,960
    Windows 10 Pro

    Uninstall everything of Nvidia using Display Driver Uninstaller and reinstall the drivers from Toshiba. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
    Attachment 69636
      My ComputersSystem Spec
  9.    15 Mar 2016 #9
    Join Date : Dec 2015
    Posts : 109
    windows 10
    Thread Starter

    Quote Originally Posted by axe0 View Post
    Uninstall everything of Nvidia using Display Driver Uninstaller and reinstall the drivers from Toshiba. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
    Attachment 69636
    Okay, will do it in a couple hours and let you know when it's done. Thx Axe0
      My ComputerSystem Spec
  10.    15 Mar 2016 #10
    Join Date : Dec 2015
    Posts : 109
    windows 10
    Thread Starter

    Quote Originally Posted by axe0 View Post
    Uninstall everything of Nvidia using Display Driver Uninstaller and reinstall the drivers from Toshiba. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
    Attachment 69636
    Hey Axe0 quick question - I just checked again and the last nvidia driver update from Toshiba for my laptop was in late December and I have it installed. It was working fine until the other day.

    Why all of a sudden wouldn't it work? I am confused. If Toshiba didn't put out a new driver update shouldn't everything still be working fine??

    Thanks
      My ComputerSystem Spec

 
Page 1 of 9 123 ... LastLast


Similar Threads
Thread Forum
BSOD - IRQ Not Less than or Equal and Driver Power State Failure
I continue to have issues with the subject BSODs. I have attempted to follow on line help (e.g., deleting devices that have issues), but continue to get them. I am not sure how to read this mini dump file and am asking for your help. Thanks. ...
BSOD Crashes and Debugging
BSOD - Driver Power State Failure
In a bit of a jam here, Currently I have windows 10 installed, although the problem was persisting even while I was using windows 7. The problems started when I ran out of space on my SSD and tried to bring files over to my other HDD for storage....
BSOD Crashes and Debugging
BSOD Driver Power State Failure
Hey guys, Ever since I updated to windows 10, my computer automatically installs some Nvidia drivers from their servers. From past experience I know that my computer can get random BSOD's with the wrong Nvidia drivers installed (WinDBG always...
BSOD Crashes and Debugging
Solved BSOD Driver Power State Failure
Hi, First of all I would like to thank you for taking the time to view my thread, over the years I have found these type of forums to be very useful and appreciate the generosity of time and experience shown members.:) I recently upgraded my PC...
BSOD Crashes and Debugging
Solved BSOD driver power state failure 0x0000009f
Whenever I boot my pc for the first time I get this error but when my pc restarts from this error it works fine. 35565
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 14:20.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums