Hopefully I did this right.
Yes, that was perfect. Unfortunately it had no trace of ScpVBus. it shows in drivers.txt with a 2013 date. I think it may haave something to with a Xbox controller but not sure.
Try running sfc /scannow from a Elevated Command Prompt. See if it gets any errors and if so what they are.
"Windows Resource Protection did not find any integrity violations". So it says.
Hmmm, the last dump you uploaded did not have Driver Verifier enabled.
Can you try enabling it again and pay close attention to Step 2, 3 and 4.
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.
Driver Verifier - Enable and Disable in Windows 10
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.
Always create a Restore Point prior to enabling Driver Verifier.
What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
Last time I ran the verifier, I chose to go back to a restore point. This time I disabled it through the command prompt. Otherwise, it throws me into an endless BSOD loop. Here's the latest file.
Please run pnputil one more time and upload the resultant txt file.Code:Unable to load image ScpVBus.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ScpVBus.sys *** ERROR: Module load completed but symbols could not be loaded for ScpVBus.sys Probably caused by : ScpVBus.sys ( ScpVBus+b174 )
See here: Occasional BSOD / freeze - Windows 10 Forums
If the Scarlet driver doesn't show, install Everything Search. Let it start after install to built it's index (take 10 seconds or so usually) then search for ScpVBus.sys. See where it's located.
Yep, the Scarlet Crush driver is in there. Also, a quick Googlin' leads me to believe that this particular driver is something to do with DS4 Windows, a program that lets a PS4 controller read like an Xbox controller. I'll uninstall that and see if it helps - though, no "natural" BSODs for a few days now.
Think I got it uninstalled. Found some folders for scpvbus.sys, so yeah, that program might be the culprit. Dunno why it started acting up so suddenly.
Yes, the Scarlet stuff is Xbox related.
Problems probably started because of a Windows Update that changes some somethign in the OS code.
Let's hope that resolves the problem.
Spoke too soon. Just had a BSOD, this time "kmode_exception_not_handled (rtwlanu.sys)".