Question (BSOD) DRIVER_POWER_STATE_FAILURE ntoskrnl.exe ?

Toggle sidebar Toggle sidebar
Unleashed72397

Unleashed72397

Mar 21, 2025
20
0
10
Hi everyone ive bulit my first pc about a month ago but since then ive been getting random black screens during gaming where i have to hard reset the pc to unfreeze it
im not quite sure what to do
people told me it might be problem with graphic card,ram,psu but i did memtest86 with no errors also both cpu and gpu furmark,cinebench
i only have 1 minidump from around when the pc was made
https://drive.google.com/file/d/1fu1sFtxo47Xd8Ly2o-r8sl6PZonmTfoI/view?usp=sharing
 
download and run microsoft autoruns64.exe as an admin
you have two copies of
CorsairLLAccess64.sys Thu Jul 25 00:15:07 2024
CorsairLLAccess64.sys Mon Feb 5 01:17:49 2024

use autoruns64 and delete the older version of CorsairLLAccess64.sys
(stupid setup issue where they expect you to uninstall manually before doing a update)

the actual bugcheck was in your media tek bluetooth driver you can look for a update but it is just likely that it was a victim caused by the two copies of CorsairLLAccess64.sys.

you also had some unusual memory address being used but it might be coming out of some firmware of a audio device. just check for firmware updates for mice and headphones if they have updatable firmware. otherwise, if the address is not from firmware I would be looking for a virus.

note: the actual bugcheck was called because usbccgp.sys
took too long to respond to a power request.
3 power request were pending.
bluetooth was trying to cancel a power request
the media tek bluetooth driver was waiting to respond
and the usb generic parent driver bugcheck because it took too long.
I think some new devices have a new feature that they get to handle their own sleep/wakeup and it causes problems if their firmware is not updated or the drivers are not updated to the correct specification level. you can also go into device manager, find the usb hub, right mouse click to bring up properties, check to see if there is a power management tab and tell windows not to turn it off to save power. it will keep the port powered but avoids problems with headphones that handle their own sleep functions.
real fix attempt is update bios, update cpu chipset drivers, update any motherboard firmware for usb or bluetooth, update media tek bluetooth driver and update any firmware for any add on hardware device (mostly new mouse or headphone that sleep to save power) (telling windows not to power down the hub is just a work around)

problem is generally cause by these device trying to wake up the hub that they are attached to. Often the signal never makes it up the chain of devices (because the drivers conform to older versions of specification.
 
Last edited:
johnbl said:
download and run microsoft autoruns64.exe as an admin
you have two copies of
CorsairLLAccess64.sys Thu Jul 25 00:15:07 2024
CorsairLLAccess64.sys Mon Feb 5 01:17:49 2024

use autoruns64 and delete the older version of CorsairLLAccess64.sys
(stupid setup issue where they expect you to uninstall manually before doing a update)

the actual bugcheck was in your media tek bluetooth driver you can look for a update but it is just likely that it was a victim caused by the two copies of CorsairLLAccess64.sys.

you also had some unusual memory address being used but it might be coming out of some firmware of a audio device. just check for firmware updates for mice and headphones if they have updatable firmware. otherwise, if the address is not from firmware I would be looking for a virus.

note: the actual bugcheck was called because usbccgp.sys
took too long to respond to a power request.
3 power request were pending.
bluetooth was trying to cancel a power request
the media tek bluetooth driver was waiting to respond
and the usb generic parent driver bugcheck because it took too long.
I think some new devices have a new feature that they get to handle their own sleep/wakeup and it causes problems if their firmware is not updated or the drivers are not updated to the correct specification level. you can also go into device manager, find the usb hub, right mouse click to bring up properties, check to see if there is a power management tab and tell windows not to turn it off to save power. it will keep the port powered but avoids problems with headphones that handle their own sleep functions.
real fix attempt is update bios, update cpu chipset drivers, update any motherboard firmware for usb or bluetooth, update media tek bluetooth driver and update any firmware for any add on hardware device (mostly new mouse or headphone that sleep to save power) (telling windows not to power down the hub is just a work around)

problem is generally cause by these device trying to wake up the hub that they are attached to. Often the signal never makes it up the chain of devices (because the drivers conform to older versions of specification.
Click to expand...
im not quite sure how to use autoruns64 to remove the older versions so could you help me out there?
also ive updated all drivers, turned off windows power savings
the only driver i have is for my mouse but its quite old
my headphones nor mic has drivers so i had to download different firmware for it
also no viruses as i found
 
Unleashed72397 said:
im not quite sure how to use autoruns64 to remove the older versions so could you help me out there?
also ive updated all drivers, turned off windows power savings
the only driver i have is for my mouse but its quite old
my headphones nor mic has drivers so i had to download different firmware for it
also no viruses as i found
Click to expand...
download autoruns from here:
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

run it as an administrator, look at the list of drivers loaded
find this entry and delete it:
CorsairLLAccess64.sys Mon Feb 5 01:17:49 2024
then reboot your system
 
johnbl said:
download autoruns from here:
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

run it as an administrator, look at the list of drivers loaded
find this entry and delete it:
CorsairLLAccess64.sys Mon Feb 5 01:17:49 2024
then reboot your system
Click to expand...
the issue is i only found 2 newest copies in the autorun which are from :
C:\Program Files\Corsair\Corsair iCUE5 Software\CorsairLLAccess64.sys Thu Apr 3 00:51:03 2025
C:\Program Files\Corsair\Corsair Device Control Service\bin\CorsairLLAccess64.sys Mon Feb 3 23:25:54 2025
 
Unleashed72397 said:
the issue is i only found 2 newest copies in the autorun which are from :
C:\Program Files\Corsair\Corsair iCUE5 Software\CorsairLLAccess64.sys Thu Apr 3 00:51:03 2025
C:\Program Files\Corsair\Corsair Device Control Service\bin\CorsairLLAccess64.sys Mon Feb 3 23:25:54 2025
Click to expand...
generally, you should never see two copies of the same driver being loaded. you should delete the oldest install.
when windows sees two copies of the same driver name installed it will attempt to load them but the second copy will collide with the first loaded copy. Windows will attempt to resolve the problem by loading the second copy at some second memory offset.
both driver get their turn responding to a service and you end up getting both drivers making event log entries and tweaking the device they control twice. Really bad for some overclock drivers that tweak voltages by offset values but it still can cause problems. I have seen corsair drivers that were doing millions of usb requests in a very short time. now most systems run the usb request thru the PCI/e bus and on one system it caused the GPU to get watchdog timeout bugchecks. (2 second timeout for a GPU) (30 second timeout for a drive, and i think usb has 500 second timeout) normally with a ssd you would not see the drive timeout and the ssd can handle the event log filling with usb transactions from icue. (or you can turn it off)
 
johnbl said:
generally, you should never see two copies of the same driver being loaded. you should delete the oldest install.
when windows sees two copies of the same driver name installed it will attempt to load them but the second copy will collide with the first loaded copy. Windows will attempt to resolve the problem by loading the second copy at some second memory offset.
both driver get their turn responding to a service and you end up getting both drivers making event log entries and tweaking the device they control twice. Really bad for some overclock drivers that tweak voltages by offset values but it still can cause problems. I have seen corsair drivers that were doing millions of usb requests in a very short time. now most systems run the usb request thru the PCI/e bus and on one system it caused the GPU to get watchdog timeout bugchecks. (2 second timeout for a GPU) (30 second timeout for a drive, and i think usb has 500 second timeout) normally with a ssd you would not see the drive timeout and the ssd can handle the event log filling with usb transactions from icue. (or you can turn it off)
Click to expand...
sorry i havent responded i was really busy those past few days, i deleted the older copy and we will see if anything changed if not ill be updating as soon as possible
 
Unleashed72397 said:
well nope since i deleted it its now even worse
it crashed 3 times past 2 hours
Click to expand...
you should provide the updated minidump file. I think you might also want to change the memory dump type to be a kernel dump. It will be much bigger and will include the internal log files, and show what was running on all of the cpu cores.

you might also want to start cmd.exe as an admin and run
powercfg.exe /energy
and look at the report.

most bugchecks related to driver power state failure
are caused by old drivers that are not coded correctly for the new lower power states (sleep functions) that windows has implemented. (assuming the bios is updated)

you can also just work around the problem and tell windows not to use the lower power states. IE set windows to use performance mode until you get all of the drivers updated.
most common failure I have been seeing with the new low power states was caused Bluetooth/wireless drivers (mostly media tek versions) kernel dumps will contain the proper debug info.
 
Last edited:
note: your media tek driver is dated:
mtkbtfilterx.sys Sat Jun 29 08:21:15 2024

BiosVersion = 2613
BiosReleaseDate = 04/12/2024
BaseBoardProduct = ROG STRIX B650-A GAMING WIFI

current versions is
Version 3222 2025/03/07

here is the current version of the mediatek driver:
MTK_7921_7922_7902 WiFi driver v3.4.0.1063 for windows10, windows11 64-bit.
rog.asus.com

ROG STRIX B650-A GAMING WIFI | ROG Strix | Gaming motherboards｜ROG - Republic of Gamers｜ROG Global

The ROG Strix B650-A Gaming WiFi is a future-forward platform with 12 + 2 power stages, hyperspeed DDR5 memory, and next-gen PCIe® 5.0 storage capabilities. It is equipped with three M.2 slots with heatsinks, a USB 3.2 Gen 2x2 port, WiFi 6E, AI Networking, Two-Way AI Noise Cancelation, and Aura...
rog.asus.com rog.asus.com

Version 3.4.0.1063
9.16 MB 2024/12/26

you should update the bios, the audio firmware and the media tek drivers.
(or turn off the sleep functions until you can do the update)

i would not install the armory crate utility and would turn it off in bios. (best not to leave it installed)
 
johnbl said:
you should provide the updated minidump file. I think you might also want to change the memory dump type to be a kernel dump. It will be much bigger and will include the internal log files, and show what was running on all of the cpu cores.

you might also want to start cmd.exe as an admin and run
powercfg.exe /energy
and look at the report.

most bugchecks related to driver power state failure
are caused by old drivers that are not coded correctly for the new lower power states (sleep functions) that windows has implemented. (assuming the bios is updated)

you can also just work around the problem and tell windows not to use the lower power states. IE set windows to use performance mode until you get all of the drivers updated.
most common failure I have been seeing with the new low power states was caused Bluetooth/wireless drivers (mostly media tek versions) kernel dumps will contain the proper debug info.
Click to expand...
and thats where real stairs begin because since i made the pc the minidump that i provided was the only one pc ever created. and i cant quite find the reason behind it but ill try to do the kernel dump
also ive done the command so i can provide you with powercfg report
file:///C:/Windows/System32/energy-report.html
ive turned off the lower power state a while back as a try to fix it
 
johnbl said:
note: your media tek driver is dated:
mtkbtfilterx.sys Sat Jun 29 08:21:15 2024

BiosVersion = 2613
BiosReleaseDate = 04/12/2024
BaseBoardProduct = ROG STRIX B650-A GAMING WIFI

current versions is
Version 3222 2025/03/07

here is the current version of the mediatek driver:
MTK_7921_7922_7902 WiFi driver v3.4.0.1063 for windows10, windows11 64-bit.
rog.asus.com

ROG STRIX B650-A GAMING WIFI | ROG Strix | Gaming motherboards｜ROG - Republic of Gamers｜ROG Global

The ROG Strix B650-A Gaming WiFi is a future-forward platform with 12 + 2 power stages, hyperspeed DDR5 memory, and next-gen PCIe® 5.0 storage capabilities. It is equipped with three M.2 slots with heatsinks, a USB 3.2 Gen 2x2 port, WiFi 6E, AI Networking, Two-Way AI Noise Cancelation, and Aura...
rog.asus.com rog.asus.com

Version 3.4.0.1063
9.16 MB 2024/12/26

you should update the bios, the audio firmware and the media tek drivers.
(or turn off the sleep functions until you can do the update)

i would not install the armory crate utility and would turn it off in bios. (best not to leave it installed)
Click to expand...
the bios was updated to i believe current version a while back its not noted on the old minidump
 
you have to put the powercfg report on a server to be viewed.
if your system is not making a mindump, you should google
"how to force a windows memory dump using a keyboard"
then make the registry settings and force a kernel memory dump while the system is working before it crashes.

I can take a look at the working kernel dump and see if I can tell if something is wrong from the internal log files.

generally, if your system is not making a memory dump at crash you would be looking for a problem in the storage subsystem.
IE update the chipset drivers from the motherboard vendors website. (also make sure your ssd has updated firmware)
There are just too many causes for this type of failure, even something like a fan stopping on a cpu can cause overheating that will cause the bugcheck. but it should not cause a power state failure bugcheck. failure of a cpu fan will look like a overclock bugcheck and should be bugcheck 0x124 with parameter 1 value of 0.
 
johnbl said:
you have to put the powercfg report on a server to be viewed.
if your system is not making a mindump, you should google
"how to force a windows memory dump using a keyboard"
then make the registry settings and force a kernel memory dump while the system is working before it crashes.

I can take a look at the working kernel dump and see if I can tell if something is wrong from the internal log files.

generally, if your system is not making a memory dump at crash you would be looking for a problem in the storage subsystem.
IE update the chipset drivers from the motherboard vendors website. (also make sure your ssd has updated firmware)
There are just too many causes for this type of failure, even something like a fan stopping on a cpu can cause overheating that will cause the bugcheck. but it should not cause a power state failure bugcheck. failure of a cpu fan will look like a overclock bugcheck and should be bugcheck 0x124 with parameter 1 value of 0.
Click to expand...
im not sure if theres something wrong with me or my keyboard but im 100% sure i did it right but it doesnt seem to work? the crash itself
i made a minidump with notmyfault.exe but i cant really upload it to google drive or microsoft onedrive or zip it so im looking for a way
 
Unleashed72397 said:
im not sure if theres something wrong with me or my keyboard but im 100% sure i did it right but it doesnt seem to work? the crash itself
i made a minidump with notmyfault.exe but i cant really upload it to google drive or microsoft onedrive or zip it so im looking for a way
Click to expand...
you have to copy it from its current location to a new location. You can not move the file since you are not the default owner of the file.
ie you have copy rights but "system" has ownership rights.
 
note: no logs in minidump. kernel dump has a name of memory.dmp and is much larger.

I was expecting a kernel dump but I took notes on the minidump file.
main issue is the winring0x64.sys and why it is running on your system. you also have asus ai driver running
you might be using these to delay packets on network games
or malware can use them to steal info from your machine and inject ads. I would remove them unless you know about them and really want their functions. winring8x64 is unprotected and is a common target of malware


notes: from running minidump
system running 18 seconds
suspect drivers:
WinRing0x64.sys Sat Jul 26 06:29:37 2008
Symantec Extended File Attributes driver from
C:\WINDOWS\system32\Drivers\SYMEVENT64x86.SYS Tue Oct 26 13:53:12 2021
(looks like you have these drivers dated in 2021, 2022, 2024)

RvNetMP60.sys Thu Aug 11 05:40:11 2022 (vpn software)
mtkbtfilterx.sys Sat Jun 29 08:21:15 2024
IOMap64.sys Mon Dec 2 00:42:15 2024(asus game network driver i think it is part of asus ai suite)
C:\WINDOWS\temp\cpuz158\cpuz158_x64.sys Tue Feb 20 00:21:31 2024
C:\WINDOWS\temp\cpuz159\cpuz159_x64.sys Wed Sep 4 00:00:25 2024
(suspect: bad form to have a driver running out of a temp directory, strange that you have two running)

\SystemRoot\System32\drivers\AVoluteSS3Vad.sys Tue Aug 6 01:38:40 2019 this driver tends to cause some problems with some game anticheat software. i would look for a update for the driver. microsoft update catalog has a older version than the one you have. you might check your motherboard vendor to see if they have updated it

AMDRyzenMasterDriver.sys Mon Sep 2 23:16:28 2024
is running so it overrides various voltages in bios.
 
Last edited:
johnbl said:
note: no logs in minidump. kernel dump has a name of memory.dmp and is much larger.

I was expecting a kernel dump but I took notes on the minidump file.
main issue is the winring0x64.sys and why it is running on your system. you also have asus ai driver running
you might be using these to delay packets on network games
or malware can use them to steal info from your machine and inject ads. I would remove them unless you know about them and really want their functions. winring8x64 is unprotected and is a common target of malware


notes: from running minidump
system running 18 seconds
suspect drivers:
WinRing0x64.sys Sat Jul 26 06:29:37 2008
Symantec Extended File Attributes driver from
C:\WINDOWS\system32\Drivers\SYMEVENT64x86.SYS Tue Oct 26 13:53:12 2021
(looks like you have these drivers dated in 2021, 2022, 2024)

RvNetMP60.sys Thu Aug 11 05:40:11 2022 (vpn software)
mtkbtfilterx.sys Sat Jun 29 08:21:15 2024
IOMap64.sys Mon Dec 2 00:42:15 2024(asus game network driver i think it is part of asus ai suite)
C:\WINDOWS\temp\cpuz158\cpuz158_x64.sys Tue Feb 20 00:21:31 2024
C:\WINDOWS\temp\cpuz159\cpuz159_x64.sys Wed Sep 4 00:00:25 2024
(suspect: bad form to have a driver running out of a temp directory, strange that you have two running)

\SystemRoot\System32\drivers\AVoluteSS3Vad.sys Tue Aug 6 01:38:40 2019 this driver tends to cause some problems with some game anticheat software. i would look for a update for the driver. microsoft update catalog has a older version than the one you have. you might check your motherboard vendor to see if they have updated it

AMDRyzenMasterDriver.sys Mon Sep 2 23:16:28 2024
is running so it overrides various voltages in bios.
Click to expand...
i honestly thought that it was a kernel dump cause registry settings were set to that

WinRing0x64.sys Sat Jul 26 06:29:37 2008 comes from a MasterPlus software for my fans
some of them autoruns couldnt find like
RvNetMP60.sys Thu Aug 11 05:40:11 2022
mtkbtfilterx.sys Sat Jun 29 08:21:15 2024
and the rest of them are up to date i would say?
could it come from the armoury crate software from asus?

AMDRyzenMasterDriver.sys how can i turn it off?
 
strange that you don't see
RvNetMP60.sys in the driver list. it looks like a vpn file. I have never seen anyone who was running it.
looks like famatech vpn https://www.radmin-vpn.com/
connect remotely to a computer behind a firewall.
I assume you do this on purpose and it is not just being used by malware. I do not know why it would be hiding from autoruns64 driver list.

i do not think it comes from armoury crate, I have people disable armory crate in bios just because it reinstalls itself from so many different locations and causes so many problems. in windows you uninstall it, then the next day it comes back since they put a installer in the scheduler and the installer runs every day.

-------------
I normally have people install the ryzen master driver to work around cpu related bugs that have not been fixed in updated bios versions yet. (windows update will then install a microsoft cpu update dll later) uninstall it if you have updated the bios.

you should be able to uninstall AMDRyzenMasterDriver.sys
  1. Uninstall the AMD Ryzen Master utility via Settings → Apps and Features1.
 
johnbl said:
strange that you don't see
RvNetMP60.sys in the driver list. it looks like a vpn file. I have never seen anyone who was running it.
looks like famatech vpn https://www.radmin-vpn.com/
connect remotely to a computer behind a firewall.
I assume you do this on purpose and it is not just being used by malware. I do not know why it would be hiding from autoruns64 driver list.

i do not think it comes from armoury crate, I have people disable armory crate in bios just because it reinstalls itself from so many different locations and causes so many problems. in windows you uninstall it, then the next day it comes back since they put a installer in the scheduler and the installer runs every day.

-------------
I normally have people install the ryzen master driver to work around cpu related bugs that have not been fixed in updated bios versions yet. (windows update will then install a microsoft cpu update dll later) uninstall it if you have updated the bios.

you should be able to uninstall AMDRyzenMasterDriver.sys
  1. Uninstall the AMD Ryzen Master utility via Settings → Apps and Features1.
Click to expand...
it was downloaded a while back to play with friends on some game

i removed AMDRyzenMasterDriver.sys

is there any more options as to why pc keeps crashing?
 
Unleashed72397 said:
it was downloaded a while back to play with friends on some game

i removed AMDRyzenMasterDriver.sys

is there any more options as to why pc keeps crashing?
Click to expand...
normally the ryzen master driver would not cause a power state failure bugcheck. If i was betting money, i would assume it would be caused by the sound effects driver from AVoluteSS3Vad.sys
I think it is installed as asus sonic studio mixer driver.
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom