Windows 10: Multiple Instances of DRIVER_POWER_STATE_FAILURE 9f

I've gotten a blue screen of death due to a Driver State Power Error on multiple occasions over the past three weeks while playing Modern Warfare. This error only occurs when I'm playing this game, though not every time and not in a predictable pattern ex: duration of play.


I have taken the following troubleshooting steps:


1. Power settings set to maximum in both Windows and 3D settings for Nvidia graphics card. Sleep and hibernation settings set to off.
2. Checked device manager to see if anything flagged nothing is
3. Updated graphics card drivers. Events not correlated with driver updates happened pre and post driver update

4. There has been no recently added hardware or software.


Below I've included some text from both the event viewer and the DMP file. Can anybody help me understand what is causing this issue and the steps I need to take in order to prevent it in the future?


Thank you!


////////////////////////////


Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 6/16/2020 12:46:15 AM
Event ID: 41
Task Category: 63
Level: Critical
Keywords: 70368744177664,2
User: SYSTEM
Computer: DESKTOP-REMOVED
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>41</EventID>
<Version>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2020-06-16T04:46:15.597282400Z" />
<EventRecordID>7024</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>DESKTOP- Removed
<Security UserID= Removed
</System>
<EventData>
<Data Name="BugcheckCode">159</Data>
<Data Name="BugcheckParameter1">0x3</Data>
<Data Name="BugcheckParameter2">0xffffd187b64b90b0</Data>
<Data Name="BugcheckParameter3">0xffffea80eb067c00</Data>
<Data Name="BugcheckParameter4">0xffffd187b64b19a0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">41</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">2</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>
Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64
Copyright c Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\minidump\061620-11343-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 18362 MP 8 procs Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff806`77c00000 PsLoadedModuleList = 0xfffff806`78048190
Debug session time: Tue Jun 16 00:45:30.309 2020 UTC - 4:00
System Uptime: 2 days 12:22:00.961
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.......................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`77dc23a0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffea80`eb067bd0=000000000000009f
4: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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: ffffd187b64b90b0, Physical Device Object of the stack
Arg3: ffffea80eb067c00, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd187b64b19a0, The blocked IRP


Debugging Details:------------------*** WARNING: Unable to verify timestamp for iaStorAC.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 3 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-2CF5R6I Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 25 Key : Analysis.Memory.CommitPeak.Mb Value: 72 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 9fBUGCHECK_P1: 3BUGCHECK_P2: ffffd187b64b90b0BUGCHECK_P3: ffffea80eb067c00BUGCHECK_P4: ffffd187b64b19a0DRVPOWERSTATE_SUBCODE: 3IMAGE_NAME: iaStorAC.sysMODULE_NAME: iaStorACFAULTING_MODULE: fffff8067a9a0000 iaStorACBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: ModernWarfare.exeDPC_STACK_BASE: FFFFEA80EB067FB0STACK_TEXT: ffffea80`eb067bc8 fffff806`77eee817 : 00000000`0000009f 00000000`00000003 ffffd187`b64b90b0 ffffea80`eb067c00 : nt!KeBugCheckExffffea80`eb067bd0 fffff806`77eee721 : ffffd187`c1111200 ffffd187`f3bcd080 ffffc000`5f440100 ffffc000`5f440180 : nt!PopIrpWatchdogBugcheck+0xefffffea80`eb067c40 fffff806`77c512d9 : ffffd187`c1111238 ffffd187`f3bcd1f0 00000000`00000080 000001f9`fd62c1b9 : nt!PopIrpWatchdog+0x31ffffea80`eb067c90 fffff806`77c50039 : 00000000`00000004 00000000`00989680 00000000`007e7f58 00000000`00000070 : nt!KiProcessExpiredTimerList+0x169ffffea80`eb067d80 fffff806`77dc93a5 : d421fb05`69ffaea4 ffffc000`5f440180 ffffd187`b34d3600 00000000`00000000 : nt!KiRetireDpcList+0x4e9ffffea80`eb067fb0 fffff806`77dc9190 : ffffea80`00000000 fffff806`786ba37b ffffea80`ecf7fa18 00000000`00000000 : nt!KxRetireDpcList+0x5ffffea80`ecf7f9c0 fffff806`77dc8a45 : 00000000`00000000 fffff806`77dc4411 00000200`a1384740 ffffea80`ecf7fa80 : nt!KiDispatchInterruptContinueffffea80`ecf7f9f0 fffff806`77dc4411 : 00000200`a1384740 ffffea80`ecf7fa80 ffffd187`b34d3600 ffffd187`f41e79e0 : nt!KiDpcInterruptBypass+0x25ffffea80`ecf7fa00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1STACK_COMMAND: .thread ; .cxr ; kbFAILURE_BUCKET_ID: 0x9F_3_disk_IMAGE_iaStorAC.sysOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {ae90980e-48b4-28fd-d132-5d53dd366e2b}Followup: MachineOwner---------

:)

 

BSOD DRIVER_POWER_STATE_FAILURE (9f) HELP

A. Analysis Results

File Name: 012419-10859-01.dmp

DRIVER_POWER_STATE_FAILURE (9f)

IMAGE_NAME: nwifi.sys

*** WARNING: Unable to verify timestamp for VBoxNetLwf.sys

B. Third Party Drivers

VBoxNetLwf.sys - Virtual Box

Driver Date - 8-Nov-2018

C. Recommendations

1. Create a system restore point so that if something wrong happens you can revert.

Type restore point in Cortana Search > Create a Restore point > Check whether against your drive, Protection is ON or not. If not ON, click Configure button below to Make it ON > Now press Create to create a restore point

2. Update your Virtual box to latest. Your driver date is 8-Nov-18 and see if you get a driver later than this. If Virtual box is not required, get it uninstalled.

 

Multiple instances of Windows Explorer

So in the Processes tab, under Apps, however many Windows Explorers I actually have open is however many it will list, and expanding will list the specific folder that is open, there is no problem there. The problem is when you scroll down to Windows processes, that's where all the multiple instances are. Right now it's only showing 7 but that is because I restarted my computer a couple hours ago, I've counted as many as 40+ before.

 

Blue Screen of Death - DRIVER_POWER_STATE_FAILURE (9f)

My computer started crashing with DRIVER_POWER_STATE_FAILURE (9f).

I analyzed the dump files but cannot resolve which driver is resulting in this error. I also used google but not many errors of this type seem to occur and I was not able to find any with this specific driver.

I hoped someone could clear this up for me.

Here is the dump file: