Question Getting constant DRIVER_POWER_STATE_FAILURE BSOD on MSI GP66 laptop

[Jclau77]

Lately, I have gotten constant DRIVER_POWER_STATE_FAILURES on my MSI GP66 laptop. Before having this issue, I was originally on Windows 10 but I decided to upgrade both my laptop and desktop to Win11. My laptop has no issues after jumping to Win11 but my laptop on the other hand has an issue where I get the BSOD.

I've pretty much exhausted every possible solution that might solve the BSOD issue but unfortunately, none have worked. Here is what I have tried doing to remedy this issue:

1. Updating Windows
2. SFC scan
3. Using DDU
4. Updating GPU drivers
5. Updating all of my drivers via DriverEasy
6. Updating the BIOS
7. Virus scan

I pretty much tried everything that I can possibly think of except a hard factory reset/clean installation of Windows. I'm only considering this as a last resort as since this is my work laptop, I have a lot of personal files stored on this device which I cannot afford on losing. I have proceeded to upload both my Perfmon and dmp files on my Google Drive. I'll be providing the links down below. But if anyone has a possible solution that does not involve a fresh clean installation of Windows or a hard reset nor that I haven't tried as of yet, please let me know.

Thanks.

Dmp zip file: https://drive.google.com/file/d/1wYrJI-Bg87oXClSvtU8imBnAVq_zML9Q/view?usp=sharing
Perfmon zip file: https://drive.google.com/file/d/1AvwaR_CWBOWgG78TT6FcJo4U7TtXBjqm/view?usp=sharing

Here are my computer specs if need be:

Laptop: MSI GP66
OS: Windows 11
x64 computer
CPU model: 11800h (Intel i7 11th gen laptop CPU)
GPU: Laptop RTX 3080
32 GB of RAM
1 TB SSD

 

[Colif]

Updating all of my drivers via DriverEasy

that could just complicate matters as 3rd party driver updaters aren't always accurate

report

looks like cause possibly a USB device of some type?

if you getting constant BSOD, how come dump is almost 20 days old? Do you have more?

Jul 21 2017 - SteamStreamingSpeakers.sys - Steam Streaming Speakers driver (Valve Corporation)
Jul 29 2017 - SteamStreamingMicrophone.sys - Steam Streaming Microphone driver (Valve Corporation)
can cause errors
May 06 2013 - ScpVBus.sys - Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus driver http://forums.pcsx2.net/
is the driver used for PS3 controllers, can cause errors. No new versions
Oct 26 2016 - rzendpt.sys - Razer RzEndPt driver https://www.razer.com/
Oct 26 2016 - rzudd.sys - Razer Rzudd Engine Driver https://www.razer.com/
tried to update Synapse?

not sure what USB devices you have?

new chipset drivers could help, don't need stormi or raid - https://www.google.com/search?channel=crow5&client=firefox-b-d&q=B550+chipset+drivers

 

[Jclau77]

@Colif
Google Drive says the wrong date as it actually is the most recent file from yesterday/ The 25th. I am not entirely sure if it's my USB device. The only USB devices I use are my G502, my Razer Huntsman Mini and a portable charger I use to charge my phone. But other than that, I've gone ahead and installed the most recent chipset drivers. I'll get back to you if I get another BSOD of the same error.

 

[Jclau77]

@Colif

Just to update you, I got the same BSOD just now. Despite the new Chipset driver that I installed, the problem still persists. Here is the most recent dmp file: https://drive.google.com/file/d/1BdJ62rt799QuRauaXXguvfg0jOuygzl0/view?usp=sharing

 

[Colif]

File: 102622-25109-01.dmp (Oct 27 2022 - 03:06:57)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
*** WARNING: Unable to verify timestamp for StreamingFSD.sys
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 22 Hour(s), 57 Min(s), and 47 Sec(s)

report

Mar 31 2022

StreamingFSD.sys

Application Jukebox Player (Endeavors Technologies, Inc.)

I haven't seen that one before.
Update or remove it.

 

[Jclau77]

@Colif

Same, I don't even know where to go with this. My best bet right now is to back up all of my work files and just preform a factory reset to how it was when I received the laptop. I'm not to concerned about my steam games as that's all stored on the cloud but I'll just have to redownload all of the software I use for my work. But other than that, I'll see if I can find that driver and somehow remove it.

Edit: Just found out that was the software I used for college in order to run applications like Photoshop as I was not able to pay for the full version at the time. I proceeded to remove it. I'll follow up with this later on whether or not I get another BSOD.

 

[Colif]

I am confused.
the first dump file here - https://drive.google.com/file/d/1wYrJI-Bg87oXClSvtU8imBnAVq_zML9Q/view
links to a Mag B550 Tomahawk
5600X
16gb of ram

But the second dump here - https://drive.google.com/file/d/1BdJ62rt799QuRauaXXguvfg0jOuygzl0/view
links to the PC in your original description... GP66 Leopard 11UH

How you do that?
I thought I was wrong so I just re ran the 1st dump again and its still same
this shows 5600 - https://jsfiddle.net/5q0smod9/show
This shows i7-11800H - https://jsfiddle.net/8jo9sa64/show

I guess 1st sentence does mention laptop and desktop but well, I assumed dumps were from same machine.
Its very confusing.

It doesn't help. You could have said which was which as I thought I was somehow looking at someone elses PC

My laptop has no issues after jumping to Win11 but my laptop on the other hand has an issue where I get the BSOD.

I assume one of the laptops here was the desktop?

Please stick to one PC at a time
No throwing a 3rd one at me

 

[Jclau77]

@Colif I don't know why the dmp file said it was a different PC 😅. Maybe I might've accidentally provided the wrong dmp file the first time was due to me downloading a dmp file on Reddit that had a similar BSOD than mine. If that was the case then my apologies!

But yes, the 2nd dmp file is mine. The one that says Intel I7 of course.

My apologies for providing the wrong one! 😅

 

[Colif]

i guess that explains also why its dated the 2nd, I did ask about that at time.

I would have noticed the first day but the website I used to put the report on wasn't working right the 1st day and that threw enough of a distraction at me that I didn't notice the PC in dump was a completely different one. Good thing all I suggested at time was update chipset drivers which can never hurt.
It was only when I was trying to figure out why one driver was on your PC that I saw they were different pc on both reports.