none
driver_power_state_failure

    Question

  • Hi, I purchased a Razor blade 2018, really impressed with the computer but I get the occasional Freeze / blue screen. 

    Windows tells me it is a driver_power_state_failure. So I ran the debugging tool. I am a little unsure as to what the problem is though.

    ******************************************************************************* * * * 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: ffffd90e53774060, Physical Device Object of the stack Arg3: ffff858b17e8f7d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffd90e586eb9e0, The blocked IRP Debugging Details: ------------------ Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvrzi.inf_amd64_f89d57020658bf08\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys Implicit thread is now ffffd90e`516902c0 KEY_VALUES_STRING: 1 PROCESSES_ANALYSIS: 1 SERVICE_ANALYSIS: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434 SYSTEM_MANUFACTURER: Razer SYSTEM_PRODUCT_NAME: Blade SYSTEM_SKU: RZ09-02386EM2 SYSTEM_VERSION: 1.05 BIOS_VENDOR: Razer BIOS_VERSION: 1.06 BIOS_DATE: 09/05/2018 BASEBOARD_MANUFACTURER: Razer BASEBOARD_PRODUCT: C1_MB DUMP_TYPE: 2 BUGCHECK_P1: 3 BUGCHECK_P2: ffffd90e53774060 BUGCHECK_P3: ffff858b17e8f7d0 BUGCHECK_P4: ffffd90e586eb9e0 DRVPOWERSTATE_SUBCODE: 3 FAULTING_THREAD: ffffd90e516902c0 CPU_COUNT: c CPU_MHZ: 8a0 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 9e CPU_STEPPING: a CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init) BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXPNP: 1 (!blackboxpnp) CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 ANALYSIS_SESSION_HOST: DESKTOP-9BA5FFF ANALYSIS_SESSION_TIME: 03-29-2019 18:46:33.0248 ANALYSIS_VERSION: 10.0.18317.1001 amd64fre LAST_CONTROL_TRANSFER: from fffff800d05dd5d0 to fffff800d05b9fb1 BAD_STACK_POINTER: fffff802768671d8 STACK_TEXT: fffff802`768671d8 fffff800`d05dd5d0 : ffffd90e`5897e000 00000000`00000000 00000000`00000000 fffff800`d05d6ca6 : nvlddmkm+0x1e9fb1 fffff802`768671e0 ffffd90e`5897e000 : 00000000`00000000 00000000`00000000 fffff800`d05d6ca6 fffff802`00000020 : nvlddmkm+0x20d5d0 fffff802`768671e8 00000000`00000000 : 00000000`00000000 fffff800`d05d6ca6 fffff802`00000020 fffff802`76867220 : 0xffffd90e`5897e000 STACK_COMMAND: .thread 0xffffd90e516902c0 ; kb THREAD_SHA1_HASH_MOD_FUNC: 937b3f6b9f108baa77f33abf3804c5271eba72b0 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 12c181ebece9ce4f2dabf9ca436dceaa25b03fd6 THREAD_SHA1_HASH_MOD: 937b3f6b9f108baa77f33abf3804c5271eba72b0 FOLLOWUP_IP: nvlddmkm+1e9fb1 fffff800`d05b9fb1 ?? ??? SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nvlddmkm+1e9fb1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5c78e109 BUCKET_ID_FUNC_OFFSET: 1e9fb1 FAILURE_BUCKET_ID: 0x9F_3_STACKPTR_ERROR_nvlddmkm!unknown_function BUCKET_ID: 0x9F_3_STACKPTR_ERROR_nvlddmkm!unknown_function PRIMARY_PROBLEM_CLASS: 0x9F_3_STACKPTR_ERROR_nvlddmkm!unknown_function TARGET_TIME: 2019-03-29T02:27:17.000Z OSBUILD: 17763 OSSERVICEPACK: 379 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: unknown_date BUILDDATESTAMP_STR: 180914-1434 BUILDLAB_STR: rs5_release BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434 ANALYSIS_SESSION_ELAPSED_TIME: 744d ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x9f_3_stackptr_error_nvlddmkm!unknown_function FAILURE_ID_HASH: {8a514180-b6e9-8eb3-31fd-edab360f2285} Followup: MachineOwner

     
    Saturday, March 30, 2019 1:53 AM

All replies

  • Hi Ash.M.Don.

    The 0x0000009F (DRIVER_POWER_STATE_FAILURE) bug check indicates that a driver is in an inconsistent or invalid power state.
    The nvlddmkm.sys file is the NVIDIA Windows Kernel Mode Driver: try updating the video card driver to a newer version.

    Bye.


    Luigi Bruno
    MCP, MOS, MTA, MCTS, MCSA, MCSE

    Saturday, March 30, 2019 11:17 AM
  • Could this possibly be a Hardware issue ? 
    Saturday, March 30, 2019 7:14 PM
  • Could this possibly be a Hardware issue ? 

    It could be, but that error does not automatically map to a hardware failure: try updating the drivers and check the system's behavior.

    Bye.


    Luigi Bruno
    MCP, MOS, MTA, MCTS, MCSA, MCSE

    Saturday, March 30, 2019 7:43 PM
  • The BSOD bugcheck was 9F.

    The displayed misbehaving driver was nvlddmkm.sys or Nvidia GPU drivers.

    For any BSOD it is best to have the dump files.

    Commands are then ran on the files for debugging.

    For some bugchecks the displayed driver was a participant in the crash and not the cause of the crash.

    Other times the displayed driver was seen after the crash and not the cause of the crash.

    For any future BSOD:

    Using administrative command prompt copy and paste this whole command.

    Make sure the default language is English so that the logs can be scanned and read.

    Choose the applicable link for the operating system:
    https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html
    https://www.eightforums.com/threads/language-add-or-remove-in-windows-8.5849/
    https://www.sevenforums.com/tutorials/87317-display-language-change.html

    The command will automatically collect the computer files and place them on the desktop.

    Then use 7zip to organize the files and one drive, drop box, or google drive to place share links into the thread for troubleshooting.

    https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

    This command will automatically collect these files:  msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.

    Open administrative command prompt and copy and paste the whole command:

    copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

    There are two files for you to find manually:

    a) C:\Windows\MEMORY.DMP

    Use file explorer > this PC > local C: drive > right upper corner search enter the above to find results.

    b) dxdiag:  

    In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread

    https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.
    .
    .
    .
    .
    .



    Saturday, March 30, 2019 10:26 PM
  • Hi,

    We also could check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.

    As Luigi Bruno suggested, please try to update the NVIDIA driver and check the issue.

    Best regards,

    Yilia 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, April 1, 2019 3:12 AM
    Moderator
  • Hi,

    Is there anything I can do for you?

    If you have any problems or concerns, please feel free to post here. 

    Best regards,

    Yilia


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, April 5, 2019 6:40 AM
    Moderator
  • Hi Thanks for all the replies. I thought it was fine until I got the blue screen and same error code yesterday. It seems to happen when im playing League of Legends and Alt-Tab'ing out and back in. I Have all updated drivers. 
    Sunday, April 7, 2019 4:36 PM
  • Windows by default automatically cleans and deletes dump files.

    Immediately after any BSOD run the administrative command prompt to collect the files.  Then zip and post a share link into the thread.  Manually search for the memory dump file.  If the file size is < 1.5 GB the zip and post a separate share link into the thread.

    Sunday, April 7, 2019 5:16 PM
  • Sorry I don't quite understand. are you asking for me to just post a report like the one at the start of the thread? Perhaps you could help me with some instructions if possible. 

    Thanks for the help everyone. 

    Sunday, April 7, 2019 8:59 PM
  • See post dated March 30, 2019:

    For any future BSOD:

    Using administrative command prompt copy and paste this whole command.

    Make sure the default language is English so that the logs can be scanned and read.

    Choose the applicable link for the operating system:
    https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html
    https://www.eightforums.com/threads/language-add-or-remove-in-windows-8.5849/
    https://www.sevenforums.com/tutorials/87317-display-language-change.html

    The command will automatically collect the computer files and place them on the desktop.

    Then use 7zip to organize the files and one drive, drop box, or google drive to place share links into the thread for troubleshooting.

    https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

    This command will automatically collect these files:  msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.

    Open administrative command prompt and copy and paste the whole command:

    copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

    There are two files for you to find manually:

    a) C:\Windows\MEMORY.DMP

    Use file explorer > this PC > local C: drive > right upper corner search enter the above to find results.

    b) dxdiag:  

    In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread

    Sunday, April 7, 2019 10:27 PM
  • Ok, So I just got another BSOD, And have the information you asked for. It seems like a lot of information about my network and system I am putting out on the table. How do I know I am save doing so ?
    Tuesday, April 16, 2019 2:37 AM
  • It's a public forum with user id and password access.

    When posting use share links (one drive, drop box, google drive).

    When the information is no longer needed you can control the access to the folder/files or delete them.

    Tuesday, April 16, 2019 5:40 AM
  • Ok, So I just got another BSOD, And have the information you asked for. It seems like a lot of information about my network and system I am putting out on the table. How do I know I am save doing so ?

    Upload only the memory dump file to your OneDrive.
    Once we've finished examining it, we'll tell you the result and you can safely remove it.

    Bye.


    Luigi Bruno
    MCP, MOS, MTA, MCTS, MCSA, MCSE

    Tuesday, April 16, 2019 12:29 PM
  • For a comprehensive analysis of the BSOD crashes please post share links for:

    a) the results of the administrative command prompt command with dxdiag

    b) a separate share link for the memory.dmp if the file size is < 1.5 GB

    Tuesday, April 16, 2019 5:02 PM