[SOLVED] Blue Screen of Death: DRIVER_POWER_STATE_FAILURE

[Ellowas]

Hi everyone,

I'm having an issue with BSODs that I started getting around... March or sometime before that, and I can't place a finger on what's causing them to happen besides what the crash .dmps have been showing me—something about ntoskrnl.exe in every single crash .dmp from a program I use. Unfortunately, I don't know how to properly read the actual .dmp files (they have a bunch of NULs and other gibberish in them) to determine if that .exe is really the cause.

Whenever I play certain games, these BSODs would happen. Here's a list of games and their activities that caused them:

• Enderal - Forgotten Stories: BSOD yesterday when I paused the game and ALT+Tabbed for a while. When I tried to tab back in, the game was frozen, and it crashed my computer seconds afterwards. I never had this problem with Enderal prior to March when I used to play it very often.
• Paladins: The game where the BSODs began during that month. After the game goes through its logos, there is a random chance I would experience a BSOD at the now frozen 'Attempting to log in...' screen. I've had the most BSODs from this game even though I never had a single BSOD from it when I played it in the past.
• RimWorld: My first time trying to play this game. It often causes a BSOD whenever it's in the middle of loading my mods before I'm able to access any settings or play the game. If I manage to get pass the loading screen, the game will eventually freeze then cause a BSOD anyway.

So far, those are the only three I've played lately—Enderal for the first time after months—that caused BSODs only during those specified moments I detailed. Every other game I play such as Heroes of the Storm, Overwatch, Warframe, Guild Wars 2, and so on are completely fine.

Here are five of my latest crash .dmps that I uploaded through Catbox (clicking them will directly download them):

• https://files.catbox.moe/b5toy1.dmp
• https://files.catbox.moe/c1dpqo.dmp
• https://files.catbox.moe/50pavj.dmp
• https://files.catbox.moe/qk5nd1.dmp
• https://files.catbox.moe/wwhcxa.dmp

Three new crash .dmps from a test I ran with Driver Verifier which warned me that I will most likely experience BSODs after restarting:

• https://files.catbox.moe/13bopi.dmp
• https://files.catbox.moe/ax80ka.dmp
• https://files.catbox.moe/qdyhnl.dmp

ntoskrnl.exe is still at the top of the list, but this time, VerifierExt.sys and winio64.sys are directly below it. Again, I don't know if they are truly the causes behind my BSODs.

If there is any way I can fix this, please enlighten me. I'd really like to get back to playing certain games without worrying about a BSOD lurking around a corner.

 

[johnbl]

i think your graphic driver requested some power mode and your gpu returned
Error code: (NTSTATUS) 0xc0000002 (3221225474) - {Not Implemented} The requested operation is not implemented.

the graphic driver just waited for a response and waited too long and caused a bugcheck.

most likely you need this video bios update:
https://www.msi.com/Laptop/GP62MVR-6RF-Leopard-Pro/support#firmware

Manufacturer Micro-Star International Co., Ltd.
Product Name GP62MVR 6RF
BIOS Version E16JBIMS.110
BIOS Starting Address Segment f000
BIOS Release Date 01/16/2018


or you can work around this problem by setting your notebook to run in high performance mode.

you will want to start cmd.exe as an admin and run
dism.exe /online /cleanup-image /restorehealth
(to fix your modified windows core files)

---------
2: kd> !devnode ffff9b0f18d4acb0
DevNode 0xffff9b0f18d4acb0 for PDO 0xffff9b0f18d4a370
Parent 0xffff9b0f18ce0ca0 Sibling 0000000000 Child 0000000000
InstancePath is "PCI\VEN_10DE&DEV_1C20&SUBSYS_11D51462&REV_A1\4&25d24fa&0&0008"
ServiceName is "nvlddmkm"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[12] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[11] = DeviceNodeEnumeratePending (0x30c)
StateHistory[10] = DeviceNodeStarted (0x308)
StateHistory[09] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[08] = DeviceNodeEnumeratePending (0x30c)
StateHistory[07] = DeviceNodeStarted (0x308)
StateHistory[06] = DeviceNodeStartPostWork (0x307)
StateHistory[05] = DeviceNodeStartCompletion (0x306)
StateHistory[04] = DeviceNodeStartPending (0x305)
StateHistory[03] = DeviceNodeResourcesAssigned (0x304)
StateHistory[02] = DeviceNodeDriversAdded (0x303)
StateHistory[01] = DeviceNodeInitialized (0x302)
StateHistory[00] = DeviceNodeUninitialized (0x301)
StateHistory[19] = Unknown State (0x0)
StateHistory[18] = Unknown State (0x0)
StateHistory[17] = Unknown State (0x0)
StateHistory[16] = Unknown State (0x0)
StateHistory[15] = Unknown State (0x0)
StateHistory[14] = Unknown State (0x0)
StateHistory[13] = Unknown State (0x0)
Flags (0x6c0000f0) DNF_ENUMERATED, DNF_IDS_QUERIED,
DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED,
DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS,
DNF_NO_UPPER_DEVICE_FILTERS, DNF_NO_UPPER_CLASS_FILTERS
CapabilityFlags (0x00002001) DeviceD1, WakeFromD3

 

[Ellowas]

i think your graphic driver requested some power mode and your gpu returned
Error code: (NTSTATUS) 0xc0000002 (3221225474) - {Not Implemented} The requested operation is not implemented.

the graphic driver just waited for a response and waited too long and caused a bugcheck.

most likely you need this video bios update:
https://www.msi.com/Laptop/GP62MVR-6RF-Leopard-Pro/support#firmware

Manufacturer Micro-Star International Co., Ltd.
Product Name GP62MVR 6RF
BIOS Version E16JBIMS.110
BIOS Starting Address Segment f000
BIOS Release Date 01/16/2018


or you can work around this problem by setting your notebook to run in high performance mode.

you will want to start cmd.exe as an admin and run
dism.exe /online /cleanup-image /restorehealth
(to fix your modified windows core files)

I think the update was successful based on how the .pdf guide looks, but what's the difference between BIOS, VBIOS, and UEFI? My BIOS—or UEFI which is what my Windows seems to call it—looks the same after the update. Is there a way I can check if the version changed?

Also, I ran that command you shared before I updated my VBIOS and this is what came of it:

This is what came of it after updating my VBIOS (nothing different, it seems):

Oh, and about the High Performance power plan, that's what my PC is currently using—been using it for a few years now with its adapter plugged in for gaming. Is that bad?

After doing all of the above (and waiting for moderator approval for my response...), I tested RimWorld again, and I unfortunately received another BSOD with what I think might be the same problem:

• https://files.catbox.moe/2874z1.dmp
• Spoiler: Event Logs Before BSOD

  Log Name:      System
  Source:        BTHUSB
  Date:          6/16/2022 2:07:59 AM
  Event ID:      34
  Task Category: None
  Level:         Warning
  Keywords:      Classic
  User:          N/A
  Computer:      Ellowas
  Description:
  The local adapter does not support an important Low Energy controller state to support peripheral mode.  The minimum required supported state mask is 0x2491f7fffff, got 0x1fffffff.  Low Energy peripheral role functionality will not be available.
  Event Xml:
  <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
      <Provider Name="BTHUSB" />
      <EventID Qualifiers="32773">34</EventID>
      <Version>0</Version>
      <Level>3</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2022-06-16T07:07:59.6428812Z" />
      <EventRecordID>102064</EventRecordID>
      <Correlation />
      <Execution ProcessID="4" ThreadID="416" />
      <Channel>System</Channel>
      <Computer>Ellowas</Computer>
      <Security />
    </System>
    <EventData>
      <Data>
      </Data>
      <Data>0x2491f7fffff</Data>
      <Data>0x1fffffff</Data>
      <Binary>00000000030028000000000022000580000000000000000000000000000000000000000000000000</Binary>
    </EventData>
  </Event>
  
  Log Name:      System
  Source:        Microsoft-Windows-Kernel-PnP
  Date:          6/16/2022 2:07:59 AM
  Event ID:      219
  Task Category: (212)
  Level:         Warning
  Keywords:     
  User:          SYSTEM
  Computer:      Ellowas
  Description:
  The driver \Driver\WudfRd failed to load for the device ACPI\ENE0110\5&33915dc8&0.
  Event Xml:
  <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
      <Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9c205a39-1250-487d-abd7-e831c6290539}" />
      <EventID>219</EventID>
      <Version>0</Version>
      <Level>3</Level>
      <Task>212</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8000000000000000</Keywords>
      <TimeCreated SystemTime="2022-06-16T07:07:59.4253432Z" />
      <EventRecordID>102061</EventRecordID>
      <Correlation />
      <Execution ProcessID="4" ThreadID="412" />
      <Channel>System</Channel>
      <Computer>Ellowas</Computer>
      <Security UserID="S-1-5-18" />
    </System>
    <EventData>
      <Data Name="DriverNameLength">25</Data>
      <Data Name="DriverName">ACPI\ENE0110\5&amp;33915dc8&amp;0</Data>
      <Data Name="Status">3221226341</Data>
      <Data Name="FailureNameLength">14</Data>
      <Data Name="FailureName">\Driver\WudfRd</Data>
      <Data Name="Version">0</Data>
    </EventData>
  </Event>

 

[johnbl]

change the memory dump type to kernel, so I can look at the USB subsystem and HID devices
and internal logs.

make sure you ran the vbios update as an admin
You have intel watch dog driver installed, go to Intel® Driver & Support Assistant
and see if there is a update.
----------
vbios is the bios on the video card
bios sets up the machine functions before the operating system loads,
UEFI is a updated more secure version of a BIOS a lot of system can run in both modes.

-------
old drivers to remove: download and run microsoft autoruns64 and disable these entries:

C:\Program Files (x86)\MSI\Dragon Center\winio64.sys Thu Jun 3 21:08:03 2010
C:\WINDOWS\SysWOW64\speedfan.sys Sat Dec 29 12:59:35 2012
C:\Program Files (x86)\MSI\Dragon Center\NTIOLib_X64.sys Tue Apr 12 00:04:16 2016
------------
graphics system timed out waiting for a power irp
irp is being held by
\Driver\HidUsb

3 devices waiting to wake up (these devices report they are waking for s4 sleep, powered down)
RzDev_0067.sys
SynTP.sys,
keyboard

I would be looking for a usb\hid hub that got powered down

Args: 00000000 00000000 00000000 00000000

[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]

0 1 ffff960333cd80a0 00000000 00000000-00000000 pending
\Driver\HidUsb
Args: 00000005 00000000 00000000 00000000
[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
0 0 ffff960333c37a00 00000000 00000000-00000000
Unable to load image \SystemRoot\System32\drivers\RzDev_0067.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RzDev_0067.sys
\Driver\RzDev_0067
Args: 00000005 00000000 00000000 00000000
[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
0 e0 ffff960333cb8ce0 00000000 fffff802587a1410-00000000 Success Error Cancel
Unable to load image \SystemRoot\System32\drivers\SynTP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SynTP.sys
\Driver\SynTP kbdclass!KeyboardClassPowerComplete
Args: 00000005 00000000 00000000 00000000
[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
0 e1 ffff960333cd9c80 00000000 fffff80242178b70-ffff960333be26a0 Success Error Cancel pending
\Driver\kbdclass nt!PopRequestCompletion

 

[Ellowas]

change the memory dump type to kernel, so I can look at the USB subsystem and HID devices
and internal logs.

make sure you ran the vbios update as an admin
You have intel watch dog driver installed, go to Intel® Driver & Support Assistant
and see if there is a update.

This is the .pdf installation guide for the VBIOS in the link you shared, and the first thing it wanted me to do was open CMD in administrative mode. Is there another way I should have installed it, or was that the correct or only way?

• https://litter.catbox.moe/wbb61i.pdf

I changed it from 'Automatic memory dump' to 'Kernal memory dump'. I don't know if it retroactively changes my previous crash .dmps to kernal-based ones, but I ran one of the games that causes my PC to experience a BSOD to make it create a new one:

• https://litter.catbox.moe/eq8l2r.dmp

No updates there. My Intel drivers were one of the first few things I checked—even uninstalled to reinstall a few to no avail.

----------
vbios is the bios on the video card
bios sets up the machine functions before the operating system loads,
UEFI is a updated more secure version of a BIOS a lot of system can run in both modes.

Ohh, I understand now, so VBIOS is just BIOS but for the GPU/graphics or video card.

Thanks for the clarification~

-------
old drivers to remove: download and run microsoft autoruns64 and disable these entries:

C:\Program Files (x86)\MSI\Dragon Center\winio64.sys Thu Jun 3 21:08:03 2010
C:\WINDOWS\SysWOW64\speedfan.sys Sat Dec 29 12:59:35 2012
C:\Program Files (x86)\MSI\Dragon Center\NTIOLib_X64.sys Tue Apr 12 00:04:16 2016

I disabled everything you've listed through Autoruns, and it seems like it successfully saved the changes. When I clicked the 'Save' icon, it wanted me to save a .arn file named after my PC somewhere. Is there anything in particular I need to do with that file?

------------
graphics system timed out waiting for a power irp
irp is being held by
\Driver\HidUsb

3 devices waiting to wake up (these devices report they are waking for s4 sleep, powered down)
RzDev_0067.sys
SynTP.sys,
keyboard

I would be looking for a usb\hid hub that got powered down

[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]

How do I find that particular USB/HID Hub, and what should I do with it once I find it?

I really should start learning how to read these files like all of you can; I just don't know where to start, lol.

 

[johnbl]

yes, you will want to start cmd.exe as an administrator
then run the procedures so you can see the results and confirm the install.

the dump on the server was a mini dump. kernel dumps are stored in a different location and are named memory.dmp by default.

 

[Ellowas]

yes, you will want to start cmd.exe as an administrator
then run the procedures so you can see the results and confirm the install.

the dump on the server was a mini dump. kernel dumps are stored in a different location and are named memory.dmp by default.

Then yeah, I followed the procedures correctly—started CMD as an administrative before the next steps and received the 'Update successful' line at the end that required me to reboot my PC. I just don't know how to check the current version of my VBIOS.

As for the MEMORY.DMP file, I searched earlier for where it could be found and I was told that it's normally located in %SystemRoot%\MEMORY.DMP—%SystemRoot% being the directory where the core of Windows is installed such as C:\Windows—however, I couldn't find that file in that directory. I could only find minidumps within its folder.

Is there some other location that particular .dmp file would be stored or are there other conditions I haven't met for my PC to create one?

Seems like the reason why my PC wouldn't create a MEMORY.DMP was this option (I allocated more space into my C: drive afterwards):

I forced (opened a game on the list in the main post) another BSOD just in case. Here is my MEMORY.DMP:

• https://drive.google.com/file/d/1Wjk2XRsdAtcp46iXkU9U68c-eam8xt71/view?usp=sharing

 

[johnbl]

see if you can find a update to these files:
ASMedia XHCI controller ( just most likely going to be the main cause of the problem)
it is the external chipset for your usb 3 ports and its extensions.

asmthub3 \SystemRoot\System32\drivers\asmthub3.sys Thu May 21 01:21:46 2020 (5EC63A1A)
fffff8047f340000 fffff8047f3b8000 asmtxhci \SystemRoot\system32\DRIVERS\asmtxhci.sys Thu May 21 01:21:18 2020

you might want to make sure that the usb 3 hub advanced properties, power management is set to not turn off the device to save power.

you might also move all device off of this hub and put it on a usb 2.2 hub to see if the problem goes away.

 

[Ellowas]

see if you can find a update to these files:
ASMedia XHCI controller ( just most likely going to be the main cause of the problem)
it is the external chipset for your usb 3 ports and its extensions.

asmthub3 \SystemRoot\System32\drivers\asmthub3.sys Thu May 21 01:21:46 2020 (5EC63A1A)
fffff8047f340000 fffff8047f3b8000 asmtxhci \SystemRoot\system32\DRIVERS\asmtxhci.sys Thu May 21 01:21:18 2020

Should I uninstall the drivers of these prior to updating the ASMedia XCHI Controller—if I can find a driver for them? They are the only ASMedia USBs I could find so far unless they're supposed to be the only ones:

Also, I updated my response before this one with my MEMORY.DMP.

 

[johnbl]

Should I uninstall the drivers of these prior to updating the ASMedia XCHI Controller—if I can find a driver for them? They are the only ASMedia USBs I could find so far unless they're supposed to be the only ones:

Also, I updated my response before this one with my MEMORY.DMP.

yes, update them if you can. also right mouse click and see if there is a power management tab where you can disable letting windows turning them off to save power.

 

[Ellowas]

yes, update them if you can. also right mouse click and see if there is a power management tab where you can disable letting windows turning them off to save power.

I uninstalled them (uninstalling the bottom one made both disappear), restarted my PC, and updated the one that remained with the ASMedia USB 3.1 Drivers (2016) from my manufacturer's website in the link you shared yesterday:

Anything else I should check, change, or test?

(I also want to add that the ASMedia USB Root Hub was the one with the 'Power Management' tab. I turned off the power saving option before I uninstalled the ASMedia USB 3.1 below it which made both disappear, but that one does not have a 'Power Management' tab—the one in the screenshot above.)

(These two have 'Power Management' tabs, and I just turned off their power saving options.)

 

[johnbl]

I uninstalled them (uninstalling the bottom one made both disappear), restarted my PC, and updated the one that remained with the ASMedia USB 3.1 Drivers (2016) from my manufacturer's website in the link you shared yesterday:

Anything else I should check, change, or test?

(I also want to add that the ASMedia USB Root Hub was the one with the 'Power Management' tab. I turned off the power saving option before I uninstalled the ASMedia USB 3.1 below it which made both disappear, but that one does not have a 'Power Management' tab—the one in the screenshot above.)

(These two have 'Power Management' tabs, and I just turned off their power saving options.)

if you uninstalled the hub, then plug and play may have detected the hardware and reinstalled the driver. Then you need to disable the power management function again. do you have any usb devices that were connected to the asmedia usb 3.1 hub? the intel hub is more likely to work correctly.

 

[Ellowas]

if you uninstalled the hub, then plug and play may have detected the hardware and reinstalled the driver. Then you need to disable the power management function again. do you have any usb devices that were connected to the asmedia usb 3.1 hub?

I'm actually not sure how to tell which one my ASMedia USB 3.1 hub, but I did make sure to unplug all of my peripherals before I uninstalled and update its drivers with a restart in between.

I have three USB hubs in my PC that are all occupied (a mouse, an USB dongle for my heatset, and a miniature desktop fan that is USB-powered), and two USB hubs have a 'SS' engraving before the USB symbol on the left side of my PC and the lone USB hub on the right side has only an engraving of the USB logo. The fan does not show up on the list as a 'USB Composite Device' since it's just a normal miniature fan, but there is a third device attached somewhere in my PC that still shows up as a 'USB Composite Device' when I unplug all of my peripherals. (Seems to be my PC's internal webcam—forgot about that.)

If it's the latter—the one without the 'SS' engraving, my USB dongle for my headset is connected to that one but it could be my PC's webcam. Also, I'm unfortunately still experiencing BSODs when trying to run RimWorld, so I guess it may still have something to do with the USB 3.1 hub or ASMedia?

I installed a debugging tool called 'USB Device Viewer' from Windows SDK, and this is everything that's connected—one is a list with my peripherals disconnected and the other list is with all of them reconnected. Unfortunately, I don't see anything recognizable to me as '3.1' under any of them:

• https://files.catbox.moe/j00jc6.txt
• https://files.catbox.moe/8wy5u3.txt

Also, I found ASMedia USB Root Hub drivers here among other ASMedia-related drivers. Are any one of these safe for me to use based on my OS's version?

 

[johnbl]

I'm actually not sure how to tell which one my ASMedia USB 3.1 hub, but I did make sure to unplug all of my peripherals before I uninstalled and update its drivers with a restart in between.

I have three USB hubs in my PC that are all occupied (a mouse, an USB dongle for my heatset, and a miniature desktop fan that is USB-powered), and two USB hubs have a 'SS' engraving before the USB symbol on the left side of my PC and the lone USB hub on the right side has only an engraving of the USB logo. The fan does not show up on the list as a 'USB Composite Device' since it's just a normal miniature fan, but there is a third device attached somewhere in my PC that still shows up as a 'USB Composite Device' when I unplug all of my peripherals. (Seems to be my PC's internal webcam—forgot about that.)

If it's the latter—the one without the 'SS' engraving, my USB dongle for my headset is connected to that one but it could be my PC's webcam. Also, I'm unfortunately still experiencing BSODs when trying to run RimWorld, so I guess it may still have something to do with the USB 3.1 hub or ASMedia?

I installed a debugging tool called 'USB Device Viewer' from Windows SDK, and this is everything that's connected—one is a list with my peripherals disconnected and the other list is with all of them reconnected. Unfortunately, I don't see anything recognizable to me as '3.1' under any of them:

• https://files.catbox.moe/j00jc6.txt
• https://files.catbox.moe/8wy5u3.txt

Also, I found ASMedia USB Root Hub drivers here among other ASMedia-related drivers. Are any one of these safe for me to use based on my OS's version?

when you remove a usb device you should go into windows control panel, device manager, find the menu option to show hidden devices. enable it and then go and delete the grayed out items in the list. This will remove the device driver associated with the port. (just to prevent problems)

you might consider going into bios and disable the asmedia hardware and move any devices to the other controller and reboot and see if it helps with the bugcheck.

 

[Ellowas]

when you remove a usb device you should go into windows control panel, device manager, find the menu option to show hidden devices. enable it and then go and delete the grayed out items in the list. This will remove the device driver associated with the port. (just to prevent problems)

you might consider going into bios and disable the asmedia hardware and move any devices to the other controller and reboot and see if it helps with the bugcheck.

This was all that shows with 'Show hidden devices' toggled:

The most concerning to me are the 'Unknown USB Devices' and the second 'USB Root Hub (USB 3.0)', but there unfortunately isn't another ASMedia-related driver to be seen. It's strange that my USB 3.1 would just vanish like that even with reinstalling drivers for it from my manufacturer's page, but I'm not too concerned about not having it—only if it's causing BSODs.

As for disabling ASMedia via BIOS, I looked through the options there but couldn't find anything named ASMedia—not even in my hidden BIOS options. Is there a specific category it would be under for MSi? Also, did you see my kernel MEMORY.DMP I edited in earlier?

 

[Ellowas]

I'm almost tempted to just reinstall Windows or reformat, but I don't know if either will fix my issue or if reformatting (backing up my important data will take a while—probably a day or three at most) is necessary for targeting drivers and power management issues.

 

[johnbl]

i did not see a memory.dmp file yet. only the minidump file.
just looked but I did not have access to the file

admedia would be listed under usb 3.x hardware in bios
be sure to delete all of the hidden devices, the drivers are still active after the device is removed and can cause strange problems. I used to see problems with the realtek 2.0 card reader driver.

 

[Ellowas]

i did not see a memory.dmp file yet. only the minidump file.
just looked but I did not have access to the file

admedia would be listed under usb 3.x hardware in bios
be sure to delete all of the hidden devices, the drivers are still active after the device is removed and can cause strange problems. I used to see problems with the realtek 2.0 card reader driver.

Whoops, sorry, I totally forgot there are privacy settings for shared Google Drive links that need to be changed.

Here it is: https://drive.google.com/file/d/1Wjk2XRsdAtcp46iXkU9U68c-eam8xt71/view?usp=sharing

As for my BIOs, these are all of the USB-related options I could find (sorry about the terrible pictures—no ability to take screenshots in there):

• BIOS (Normal)
• BIOS (Hidden Options)

 

[johnbl]

looking at memory dump now.
this is weird:
MEmuPush.exe running but shown as terminated
it was the "running process" at the time of the problem
looks like https://www.microvirt.com
some type of android emulator?

try uninstalling it.
will continue to see if I can see problems in memory dump.

some files show up as modified:
10 errors : pci (fffff80569a92124-fffff80569a92440)
10 errors : Ntfs (fffff8056a697194-fffff8056a6974a4)
10 errors : UsbHub3 (fffff8056a81e49c-fffff8056a81e7a8)
280 errors : HIDCLASS (fffff8057dbac8d0-fffff8057dbacc63)
8 errors : nt (fffff80565d31620-fffff80565d3162b)

the log for the pci bus indicates that it was shutdown and restarted:

usb: (most devices are ok but not these but these 3)
device suspended;
Desc: BisonCam, NB Pro
USB\VID_5986&PID_0683&REV_0304 BISON ELECTRONICS INC.
Desc: <none>
USB\VID_8087&PID_0A2A&REV_0001 Intel
Desc: MSI EPF USB
USB\VID_1770&PID_FF00&REV_0110 precisionWave Corporation

each of these devices have a huge log (21 million entries each)

first one looks like a webcam, second looks like the intel integrated GPU
third not sure the vendor and device are not registered in the database I look at.
google precisionWave Corporation looks like sound devices
it could be RGB keyboard lights driver.

looks like the pci bus powered down and could not power back up correctly
it called pci!PciPowerDownDeviceByPolicy before every thing stopped working.
the device that could not power back up correctly was
vendor =8086 = intel device = 1901
this is
6th-10th Gen Core Processor PCIe Controller (x16)
Vendor ID 8086 (INTEL CORPORATION) Device ID 1901
Subsystem Vendor ID 1462 (MICRO-STAR INTERNATIONAL CO., LTD. [MSI]) Subsystem ID 11D5

the system kept setting a timer to give the device time to wake up, the timer would expire and it set another one but the device never would wake up. (it is part to the main pci/e bus)

not sure how to fix this problem. the PCI/e bus is trying to start again and times out over and over.
maybe if you remove the MEmuPush.exe
maybe if you disable the three devices it might work. I just do not know.

or maybe you are right, it is time for a clean install.

with these new systems all of the usb traffic now goes though the PCI/e bus so an problems with a USB device can mess up your graphics and cause timeouts. Windows detects the timeouts and tries to fix them by resetting the device or the bus which I think is causing your three devices to get disconnected and then they are not getting the wake up signal. Looks like the bus branch they are connected to is not waking back up after being shutdown.
usb3 hub shows a bunch of errors like this:
hub1 port7 0xffff880f72706110 527: HUBPDO_CompleteWaitWake - WdfDeviceIndicateWakeStatus Failed 0xc0000010(STATUS_INVALID_DEVICE_REQUEST)


overclock driver still running.
disable nvidia share unless you are actively using it
-you also had a installer installing something. do you know what was being installed?

 

[Ellowas]

looking at memory dump now.
this is weird:
MEmuPush.exe running but shown as terminated
it was the "running process" at the time of the problem
looks like https://www.microvirt.com
some type of android emulator?

try uninstalling it.

Yeah, that's an Android emulator I used for certain games that seemed to troublesome to play on a phone or tablet.

I haven't used it in a while, so it can definitely go.

will continue to see if I can see problems in memory dump.

some files show up as modified:
10 errors : pci (fffff80569a92124-fffff80569a92440)
10 errors : Ntfs (fffff8056a697194-fffff8056a6974a4)
10 errors : UsbHub3 (fffff8056a81e49c-fffff8056a81e7a8)
280 errors : HIDCLASS (fffff8057dbac8d0-fffff8057dbacc63)
8 errors : nt (fffff80565d31620-fffff80565d3162b)

the log for the pci bus indicates that it was shutdown and restarted:

usb: (most devices are ok but not these but these 3)
device suspended;
Desc: BisonCam, NB Pro
USB\VID_5986&PID_0683&REV_0304 BISON ELECTRONICS INC.
Desc: <none>
USB\VID_8087&PID_0A2A&REV_0001 Intel
Desc: MSI EPF USB
USB\VID_1770&PID_FF00&REV_0110 precisionWave Corporation

each of these devices have a huge log (21 million entries each)

first one looks like a webcam, second looks like the intel integrated GPU
third not sure the vendor and device are not registered in the database I look at.
google precisionWave Corporation looks like sound devices
it could be RGB keyboard lights driver.

looks like the pci bus powered down and could not power back up correctly
it called pci!PciPowerDownDeviceByPolicy before every thing stopped working.

That's... highly concerning, and those five showed up as modified ? I'm not sure what that exactly means if not 'modified' as in tweaked in some way, but I don't know how to modify anything like that—unless a driver or update did it.

I never use the webcam and personally dislike laptops come installed with them. If there are millions of errors for each of those three devices, is there anything I can do to fix them if they are the causes of my BSODs? About that 'perecisionWave Corporation', I'm not finding much information about it either, aside from what you found, but I did find a .txt file with specifications of another MSI laptop (MSI GS60) with a similar USB port sporting it:

• [Port7] : precisionWave, PID=EF35 -----------------------------------------
  
  [Device Information]
    Device Manufacturer:                    precisionWave
    Product Name:                           precisionWave, PID=EF35
    Serial Number:                          -
    USB Version Supported:                  1.10
    USB Device Speed:                       USB 1.1 Full-speed
    Driver Description:                     Périphérique d’entrée USB (Translated: USB input device)
    Hardware ID:                            USB\VID_1770&PID_FF00
  [Driver Information]
    Driver Manufacturer:                    (Périphériques système standard)
    Driver Description:                     Périphérique d’entrée USB
    Driver Provider:                        Microsoft
    Driver Version:                         10.0.18362.175
    Driver Date:                            21-Jun-2006
    DeviceInstanceId                        USB\VID_1770&PID_FF00\MSI_EPF_USB
    Location Paths                          PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(7)

Based on their website, they seem to make hardware (chips, I think) and they mentioned USB a few times in some of their descriptions.

 

[johnbl]

Yeah, that's an Android emulator I used for certain games that seemed to troublesome to play on a phone or tablet.

I haven't used it in a while, so it can definitely go.



That's... highly concerning, and those five showed up as modified ? I'm not sure what that exactly means if not 'modified' as in tweaked in some way, but I don't know how to modify anything like that—unless a driver or update did it.

I never use the webcam and personally dislike laptops come installed with them. If there are millions of errors for each of those three devices, is there anything I can do to fix them if they are the causes of my BSODs? About that 'perecisionWave Corporation', I'm not finding much information about it either, aside from what you found, but I did find a .txt file with specifications of another MSI laptop (MSI GS60) with a similar USB port sporting it:

• [Port7] : precisionWave, PID=EF35 -----------------------------------------
  
  [Device Information]
    Device Manufacturer:                    precisionWave
    Product Name:                           precisionWave, PID=EF35
    Serial Number:                          -
    USB Version Supported:                  1.10
    USB Device Speed:                       USB 1.1 Full-speed
    Driver Description:                     Périphérique d’entrée USB (Translated: USB input device)
    Hardware ID:                            USB\VID_1770&PID_FF00
  [Driver Information]
    Driver Manufacturer:                    (Périphériques système standard)
    Driver Description:                     Périphérique d’entrée USB
    Driver Provider:                        Microsoft
    Driver Version:                         10.0.18362.175
    Driver Date:                            21-Jun-2006
    DeviceInstanceId                        USB\VID_1770&PID_FF00\MSI_EPF_USB
    Location Paths                          PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(7)

Based on their website, they seem to make hardware (chips, I think) and they mentioned USB a few times in some of their descriptions.

it used to be with old versions of windows it was ok to modify windows files, some drivers might still be doing this. it is just not good to try and debug problems related to PCI bus and USB when the files have been modified.

remove the nvidia share program. Just to see if you can prevent the graphics driver from hanging and the hardware from being reset.
(then the usb devices would not get disconnected and would not have to change the power state)

 

[Ellowas]

it used to be with old versions of windows it was ok to modify windows files, some drivers might still be doing this. it is just not good to try and debug problems related to PCI bus and USB when the files have been modified.

remove the nvidia share program. Just to see if you can prevent the graphics driver from hanging and the hardware from being reset.
(then the usb devices would not get disconnected and would not have to change the power state)

I wish I knew what exactly was installed that modified my USB's files in the terrible condition they're in now, so I'll know to avoid it in the future...

I don't have anything called NVIDIA Share (seems like something used for NVIDIA Shields) installed—just NVIDIA GeForce Experience which handles all of my NVIDIA driver updates (it also comes with a few other features like an overlay for NVIDIA Shadowplay).

 

[johnbl]

I wish I knew what exactly was installed that modified my USB's files in the terrible condition they're in now, so I'll know to avoid it in the future...

I don't have anything called NVIDIA Share (seems like something used for NVIDIA Shields) installed—just NVIDIA GeForce Experience which handles all of my NVIDIA driver updates (it also comes with a few other features like an overlay for NVIDIA Shadowplay).

the dism.exe /online /cleanup-image /restorehealth
should repair files on disk, then you reboot and they get loaded.
but often they get modified in memory after they are loaded.

 

[Ellowas]

the dism.exe /online /cleanup-image /restorehealth
should repair files on disk, then you reboot and they get loaded.
but often they get modified in memory after they are loaded.

I'm most likely going to get the same results as shown here, but I'll try it again and see what happens.

Unfortunately, every time I've tried that command and sfc /scannow, they would say that everything's fine—no errors, nothing that was changed or fixed, and so on. I'm not sure why when there's clearly a problem somewhere. If what's shown for the former does mean that it actually fixed something, is there a way to remove what was memorized to prevent what dism.exe fixed from being overwritten again?

Yup, same thing (tried PowerShell this time), but I'll restart and see what happens:

I'll also add this—trying to see if I still get BSODs per change I make from here:

All of my BSODs lately have been pointing at the Intel Processor Power Management thing—detailing everything you already mentioned about something (the USBs) holding it up, and the win32kbase.sys and Program.sys (or the winio64 I disabled yesterday) no longer show up as faults for a BSOD. Man, this is really a pain to be honest but at least we eliminated two faults (I hope—not sure if they'll resurface or not).

 

[Colif]

Unfortunately, every time I've tried that command and sfc /scannow, they would say that everything's fine—no errors, nothing that was changed or fixed, and so on. I'm not sure why when there's clearly a problem somewhere. If what's shown for the former does mean that it actually fixed something, is there a way to remove what was memorized to prevent what dism.exe fixed from being overwritten again?

dism fixes the image files. These files are used by windows to reset your PC and by SFC to check the PC. Often it helps to run dism before SFC since it can save time.