Question DRIVER_POWER_STATE_FAILURE occurs randomly ?

Parroty69

Great
Oct 27, 2021
233
7
95
1
I have an error with my Windows system where it just randomly blue screens with the error. It could happen in right after boot or maybe a few hours after that, or it won’t happen at all.
It occurred on one of my programming sessions once and I almost lost a bunch of code, thankfully it was autosaved so I didn’t lose much data.
Can anyone help me with this issue?
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
56,557
4,476
160,690
10,208
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
what are specs of the PC?
 

Parroty69

Great
Oct 27, 2021
233
7
95
1
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
what are specs of the PC?
Hello, I have done the steps you have told me, however, I cannot upload the file to cloud right now. Can I send it by email instead?

The specs of the pc are:
CPU: Intel 6700HQ
RAM: 16GB DDR4 SODIMM
GPU: GTX 1060
Drive: 1TB HDD and 256GB SSD
 

Parroty69

Great
Oct 27, 2021
233
7
95
1
what is problem uploading file?

email is difficult as I don't have a Tom's email and would have to give you my own.

is this a laptop? what make/model?
The problem was that I could not connect to the servers of the data sharing website, I have since fixed it and now able to send you the link to the file here
This is a laptop, the brand is MSI and the model is GE72VR 6RF Apache Pro.
 

gardenman

Distinguished
Moderator
Hi, I ran the dump file through the debugger and got the following information: https://jsfiddle.net/kjwqm3zf/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:060622-5828-01.dmp (Jun 6 2022 - 00:22:28)
Bugcheck:DRIVER_POWER_STATE_FAILURE (9F)
Probably caused by:pci.sys (Process running at time of crash: System)
Uptime:0 Day(s), 0 Hour(s), 09 Min(s), and 47 Sec(s)

Comment: The overclocking driver "NTIOLib_X64.sys" was found on your system. (MSI Afterburner or other MSI software)

System: https://www.msi.com/Laptop/GE72vr-6rF-Apache-Pro/Specification
There is a BIOS update available for your system. You are using version 105 and the latest is 10E. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
56,557
4,476
160,690
10,208
Sep 20 2018e2xw10x64.sysKiller PCI-E Gigabit Ethernet Controller driver http://www.killernetworking.com/
Dec 12 2019KfeCo10X64.sysKiller Networking Suite driver

finding newer versions of these are fun, as the company who made them got taken over by Intel and they don't support the chipset on your laptop anymore, and drivers you have installed are newer than what are on MSI website

I think actual cause is an intel driver, so the driver updater I offered before might help.
 

Parroty69

Great
Oct 27, 2021
233
7
95
1
Sep 20 2018e2xw10x64.sysKiller PCI-E Gigabit Ethernet Controller driver http://www.killernetworking.com/
Dec 12 2019KfeCo10X64.sysKiller Networking Suite driver

finding newer versions of these are fun, as the company who made them got taken over by Intel and they don't support the chipset on your laptop anymore, and drivers you have installed are newer than what are on MSI website

I think actual cause is an intel driver, so the driver updater I offered before might help.
The driver updater you linked found one driver and that was the integrated graphics driver. I updated the driver with the tool and then uninstalled it because I don’t want bloatware on my computer, I think it might have fixed it since it didn’t crash yet today. We will have to wait to see if it fixed it, I will reply to you if I continue to get BSODs.
 

Parroty69

Great
Oct 27, 2021
233
7
95
1
Sep 20 2018e2xw10x64.sysKiller PCI-E Gigabit Ethernet Controller driver http://www.killernetworking.com/
Dec 12 2019KfeCo10X64.sysKiller Networking Suite driver

finding newer versions of these are fun, as the company who made them got taken over by Intel and they don't support the chipset on your laptop anymore, and drivers you have installed are newer than what are on MSI website

I think actual cause is an intel driver, so the driver updater I offered before might help.
The blue screen has came back again. I noticed the blue screen didn't happen until a few months prior, and I didn't manually update the drivers and don't have any driver updaters other than included software for hardware devices so it could've been Windows Update.
Because of that, I have rounded up a few suspects that might have caused the blue screens here:
View: https://imgur.com/XmZ3EPv
 
you should link your current minidump. the old minidump
was the PCI bus having issues due to your graphics card.

: kd> !devnode ffffa988eff444a0
DevNode 0xffffa988eff444a0 for PDO 0xffffa988eff29120
Parent 0xffffa988eff30ca0 Sibling 0000000000 Child 0000000000
InterfaceType 0 Bus Number 0
InstancePath is "PCI\VEN_10DE&DEV_1C20&SUBSYS_11D71462&REV_A1\4&343593a9&0&0008"
ServiceName is "nvlddmkm"
State = Unknown State (0x0)
Previous State = Unknown State (0x0)
Flags (0000000000)

pci vendor =10de device= 1c20
GP106M [GeForce GTX 1060 Mobile]

PCI\VEN_10DE&DEV_1C20 - GP106M [GeForce GTX 1060 Mobile] | Device Hunt

first fix attempt would be to remove the overclock driver NTIOLib_X64.sys

update this driver also:
RTKVHD64.sys Tue Dec 19 02:58:42 2017
this sound driver can crash GPU drivers

download microsoft autoruns64 and remove this driver:
winio64.sys Thu Jun 3 21:08:03 2010
Autoruns for Windows - Windows Sysinternals | Microsoft Docs

KfeCo10x64.sys, Description: Killer Traffic Control Callout Driver
Timestamp: Thu Dec 12 10:23:54 2019
e2xw10x64.sys Wed Sep 19 22:10:32 2018
I would suspect the traffic control driver as causing problems.

if you have more problems, you should provide the minidump or change the dump type to kernel and provide the kernel dump. It can provide more conclusive info.

7: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.0, DMIVersion 0, Size=4090]
BiosMajorRelease = 1
BiosMinorRelease = 5
BiosVendor = American Megatrends Inc.
BiosVersion = E179BIMS.105
BiosReleaseDate = 09/02/2016
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = GE72VR 6RF
SystemFamily = G
SystemVersion = REV:1.0
SystemSKU = 179B.1
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MS-179B
BaseBoardVersion = REV:1.0

old machine: confirm fans on gpu are still spinning, blow out dust.
 
Last edited:

Parroty69

Great
Oct 27, 2021
233
7
95
1
you should link your current minidump. the old minidump
was the PCI bus having issues due to your graphics card.

: kd> !devnode ffffa988eff444a0
DevNode 0xffffa988eff444a0 for PDO 0xffffa988eff29120
Parent 0xffffa988eff30ca0 Sibling 0000000000 Child 0000000000
InterfaceType 0 Bus Number 0
InstancePath is "PCI\VEN_10DE&DEV_1C20&SUBSYS_11D71462&REV_A1\4&343593a9&0&0008"
ServiceName is "nvlddmkm"
State = Unknown State (0x0)
Previous State = Unknown State (0x0)
Flags (0000000000)

pci vendor =10de device= 1c20
GP106M [GeForce GTX 1060 Mobile]

PCI\VEN_10DE&DEV_1C20 - GP106M [GeForce GTX 1060 Mobile] | Device Hunt

first fix attempt would be to remove the overclock driver NTIOLib_X64.sys

update this driver also:
RTKVHD64.sys Tue Dec 19 02:58:42 2017
this sound driver can crash GPU drivers

download microsoft autoruns64 and remove this driver:
winio64.sys Thu Jun 3 21:08:03 2010
Autoruns for Windows - Windows Sysinternals | Microsoft Docs

KfeCo10x64.sys, Description: Killer Traffic Control Callout Driver
Timestamp: Thu Dec 12 10:23:54 2019
e2xw10x64.sys Wed Sep 19 22:10:32 2018
I would suspect the traffic control driver as causing problems.

if you have more problems, you should provide the minidump or change the dump type to kernel and provide the kernel dump. It can provide more conclusive info.

7: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.0, DMIVersion 0, Size=4090]
BiosMajorRelease = 1
BiosMinorRelease = 5
BiosVendor = American Megatrends Inc.
BiosVersion = E179BIMS.105
BiosReleaseDate = 09/02/2016
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = GE72VR 6RF
SystemFamily = G
SystemVersion = REV:1.0
SystemSKU = 179B.1
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MS-179B
BaseBoardVersion = REV:1.0

old machine: confirm fans on gpu are still spinning, blow out dust.
After the first minidump, I had turned the settings back to Automatic Memory Dump but I still get new minidumps in the minidump folder so I can you you the new minidumps here:
https://we.tl/t-FaVPNcvSSA
 
looks like some miracast device is not getting installed .
-----
looks like directx via \nvlddmkm not responding to power request

you should update the bios and motherboard drivers from the motherboard vendor
-----------

go to control panel device manager and look for devices with a failed install.
(yellow icon) WiFiDirect\C6:65:16:4D:50:CD
pooltag 202b

------------

see if you have a kernel dump c:\windows\memory.dmp file
it will have full debug info.
-------------
7: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.0, DMIVersion 0, Size=4090]
BiosMajorRelease = 1
BiosMinorRelease = 5
BiosVendor = American Megatrends Inc.
BiosVersion = E179BIMS.105
BiosReleaseDate = 09/02/2016
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = GE72VR 6RF
SystemFamily = G
SystemVersion = REV:1.0
SystemSKU = 179B.1
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MS-179B
CPU Information]
~MHz = REG_DWORD 2592
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 94 Stepping 3
ProcessorNameString = REG_SZ Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Update Status = REG_DWORD 0
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD cc00000000
 
Last edited:

Parroty69

Great
Oct 27, 2021
233
7
95
1
looks like some miracast device is not getting installed .
-----
looks like directx via \nvlddmkm not responding to power request

you should update the bios and motherboard drivers from the motherboard vendor
-----------

go to control panel device manager and look for devices with a failed install.
(yellow icon) WiFiDirect\C6:65:16:4D:50:CD
pooltag 202b

------------

see if you have a kernel dump c:\windows\memory.dmp file
it will have full debug info.
-------------
7: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.0, DMIVersion 0, Size=4090]
BiosMajorRelease = 1
BiosMinorRelease = 5
BiosVendor = American Megatrends Inc.
BiosVersion = E179BIMS.105
BiosReleaseDate = 09/02/2016
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = GE72VR 6RF
SystemFamily = G
SystemVersion = REV:1.0
SystemSKU = 179B.1
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MS-179B
CPU Information]
~MHz = REG_DWORD 2592
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 94 Stepping 3
ProcessorNameString = REG_SZ Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Update Status = REG_DWORD 0
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD cc00000000
I cannot find any device with a yellow failed install in Device Manager. There doesn’t seem to be a memory.dmp file in the windows folder.
I will try to update the bios as a last resort later as I am going through a series of power outages.
 
I cannot find any device with a yellow failed install in Device Manager. There doesn’t seem to be a memory.dmp file in the windows folder.
I will try to update the bios as a last resort later as I am going through a series of power outages.
maybe we can find the name of the driver that had tag 202b
start cmd.exe as an admin then run
cd c:\windows\system32
findstr.exe /s /m /l 202b *.sys

and see what driver name is returned.
it could be your touchpad driver. (you might update the touchpad driver from the motherboard vendor)

you should be able to avoid the bugcheck by running your system in high performance mode. There was some indications that the device was a usb hid device but minidumps do not include usb information so I could not check.

do you have a miracast device attatched to your machine. something like a usb device that wirelessly connects to a tv monitor or xbox display?

you should also go into windows control panel and find the option to display hidden devices and display them. Look for software drivers that were hidden/greyed out and remove them. these are devices that were at one time plugged into your system then removed. There driver still runs but is hidden in case you plug the device back int. bugs in these drivers can cause system problems that people don't expect since the device is removed.

also, what was the apple usb device you installed?

it is hard to tell what device caused the problem since the pci bus stopped responding and all hardware connected to the bus started complaining.
 
Last edited:

Parroty69

Great
Oct 27, 2021
233
7
95
1
maybe we can find the name of the driver that had tag 202b
start cmd.exe as an admin then run
cd c:\windows\system32
findstr.exe /s /m /l 202b *.sys

and see what driver name is returned.
it could be your touchpad driver. (you might update the touchpad driver from the motherboard vendor)

you should be able to avoid the bugcheck by running your system in high performance mode. There was some indications that the device was a usb hid device but minidumps do not include usb information so I could not check.

do you have a miracast device attatched to your machine. something like a usb device that wirelessly connects to a tv monitor or xbox display?

you should also go into windows control panel and find the option to display hidden devices and display them. Look for software drivers that were hidden/greyed out and remove them. these are devices that were at one time plugged into your system then removed. There driver still runs but is hidden in case you plug the device back int. bugs in these drivers can cause system problems that people don't expect since the device is removed.

also, what was the apple usb device you installed?

it is hard to tell what device caused the problem since the pci bus stopped responding and all hardware connected to the bus started complaining.
I ran the command you told me but it doesn't show anything up. I don't have any miracast devices connected to my laptop right now. The apple usb device is probably just my iPhone or iPad connected to iTunes on my computer.
Also, if you need a kernel dump or another type of dump, I can generate one when it crashes if you like.
 
I ran the command you told me but it doesn't show anything up. I don't have any miracast devices connected to my laptop right now. The apple usb device is probably just my iPhone or iPad connected to iTunes on my computer.
Also, if you need a kernel dump or another type of dump, I can generate one when it crashes if you like.
kernel dump lets me look at the hardware info and logs
try doing this:
start cmd.exe as an admin then run
cd c:\windows\system32
findstr.exe /s /m /l 202b *.sys


it scans the device drivers on your machine to find one that has a pool tag of 202b
each driver put a name code on memory allocations in kernel. something put this code but it is not a known code. most likely going to be a driver that is only on your machine.
 

ASK THE COMMUNITY

TRENDING THREADS