Windows 10: DRIVER_POWER_STATE_FAILURE Blue Screen

Hi,

I have been having BSOD's with the error DRIVER_POWER_STATE_FAILURE it usually happens during gaming or alt+tabbing. I get it quite often. My PC freezes for some time or just gives me BSOD. I don't know much about this subject so I can you guys help out? Thanks in advance!

You can acess my minidump file here.

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

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

Implicit thread is now ffffad86`3b8f0040
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys

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: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER: MONSTER

SYSTEM_PRODUCT_NAME: ABRA A5 V9.2

SYSTEM_SKU: Not Applicable

SYSTEM_VERSION: Not Applicable

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1.05.22

BIOS_DATE: 03/27/2018

BASEBOARD_MANUFACTURER: MONSTER

BASEBOARD_PRODUCT: ABRA A5 V9.2

BASEBOARD_VERSION: Not Applicable

DUMP_TYPE: 2

BUGCHECK_P1: 3

BUGCHECK_P2: ffffad863e99d570

BUGCHECK_P3: ffff8588e743f7b0

BUGCHECK_P4: ffffad8644680490

DRVPOWERSTATE_SUBCODE: 3

FAULTING_THREAD: ffffad863b8f0040

CPU_COUNT: 8

CPU_MHZ: af8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 8E'00000000 (cache) 8E'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-TDBVB2U

ANALYSIS_SESSION_TIME: 07-21-2019 18:23:44.0739

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER: from fffff80231c3b7e2 to fffff80231dc35a6

STACK_TEXT:
ffff8588`e74167c0 fffff802`31c3b7e2 : ffff9981`fffffffe fffff802`0000000d ffff9981`294b9180 ffffad86`3b8f0040 : nt!KiSwapContext+0x76
ffff8588`e7416900 fffff802`31c3ae74 : 00000000`000000ff 00000000`00000010 ffff8588`00051d8a 00000000`00000000 : nt!KiSwapThread+0x3f2
ffff8588`e74169a0 fffff802`31c3a615 : 00000000`00000000 ffffad86`00000000 00000016`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x144
ffff8588`e7416a40 fffff802`501c0148 : ffffad86`458f9590 fffff802`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x255
ffff8588`e7416b20 ffffad86`458f9590 : fffff802`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x1d0148
ffff8588`e7416b28 fffff802`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`ffffffff : 0xffffad86`458f9590
ffff8588`e7416b30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`ffffffff 00000000`00000001 : 0xfffff802`00000000


STACK_COMMAND: .thread 0xffffad863b8f0040 ; kb

THREAD_SHA1_HASH_MOD_FUNC: 91c09f95649eaff6bfa06c2196d3e0ff4295c271

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 993c4b673e51423529957351a7447ab99448c851

THREAD_SHA1_HASH_MOD: 4e96c4bcc4ec8f85ee49d7124864474789fdce87

FOLLOWUP_IP:
nvlddmkm+1d0148
fffff802`501c0148 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nvlddmkm+1d0148

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5d1c6acd

BUCKET_ID_FUNC_OFFSET: 1d0148

FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm!unknown_function

BUCKET_ID: 0x9F_3_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS: 0x9F_3_nvlddmkm!unknown_function

TARGET_TIME: 2019-07-21T09:01:12.000Z

OSBUILD: 18362

OSSERVICEPACK: 239

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: 1972-02-02 11:33:06

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: d1d6

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_3_nvlddmkm!unknown_function

FAILURE_ID_HASH: {8b257f08-e34e-7c26-3880-084b82f90c48}

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

:)

 

Blue Screen

Hi,





Blue screens could be caused by problems with your computer’s hardware or with its driver. Still, we
would like to know more about the issue. Please clarify the following:

• Did you get a STOP code?
• Did you install any hardware or driver recently?

For basic troubleshooting steps to resolve blue screen errors, we suggest checking out this
article and simply follow the steps.



Feel free to contact us if you need further help.

 

getting blue screen error/Stop Code

Hi Abhijit,

Stop code: DRIVER_POWER_STATE_FAILURE is probably due to a compatibility issue with the driver, as most blue screen errors are. Since you encountered this error after updating Windows, most probably, you would need to update the drivers
as well.

We suggest that you go through the steps in this article on how to troubleshoot blue screen errors.
On step 1, select After an update was installed.

Kindly update us on the results.

 

Windows 10 Keeps freezing after a certain period of time, then blue screens

Hi,

The Blue screen error DRIVER_POWER_STATE_FAILURE usually occurs if the drivers on a PC is damaged. For us to provide an accurate solution, we would need you to answer the following questions:

• Which build, version and edition of Windows 10 is installed on your computer?
• What changes have you made to your device before this issue happened?

In the meantime, we suggest booting your device into safe mode and then follow the steps provided on this
link. The link serves as a guide on how to troubleshoot blue screen errors.

We are looking forward to your response.