Random BSOD While Doing Just About Anything On My PC

Hi. About one or or two times a day for the past week or so, I've been experiencing BSOD and I'm not really sure what the problem is because this is a new PC and of course, there shouldn't be anything wrong with it.

Initially, I thought something about minecraft was causing it so I uninstalled it but there were still crashes. It's crashed while watching YouTube, or when im playing any other game so I don't think it's any specific game that is causing it.

Attached is a picture of what i believe is the actual crash occuring in the event handler, but I could be wrong.

Any feedback would be appreciated.





System Spec
Computer type:
PC/Desktop
OS:
Windows
CPU:
AMD Ryzen 3600x
Motherboard:
ASUS ROG Strix x570e
Memory:
Corsair Vengeance LPX (2x8)
Graphics Card(s):
EVGA NVIDIA RTX 2060 Super
Monitor(s) Displays:
ASUS VG248QE
Screen Resolution:
1920 x 1080
Hard Drives:
Samsung 860 EVO (1 TB)
Samsung 860 EVO (250 G)
PSU:
Corsair RM850x
Cooling:
Corsair H100i
Browser:
Chrome
Antivirus:
Just the one that comes with windows

That indeed is one of the BSOD errors
Note that the bugcode is 265 - converting it to hex makes it a 109 (which is what the Error Reports show and the lone memory dump shows)

This driver dates from 2013. You should uninstall the program associated with it (and ensure that the driver is gone after a reboot). If you need this program, check to see if you can find/download a W10 compatible version.

Beyond that, if the BSOD's continue, please run Driver Verifier according to these instructions: Enable and Disable Driver Verifier in Windows 10
Ensure that you've captured a minidump (they're saved in dated format in C:\Windows\Minidump) so that you can zip it up and upload it.

You may also want to try these free hardware diagnostics (in case the problem is caused by a hardware problem):
1) Memtest86 (not 86+): MemTest86 - Official Site of the x86 Memory Testing Tool

2) SeaGate SeaTools for Windows (test ALL hard drives - HDD/SSD/USB/etc): How to use SeaTools for Windows | Seagate Support US

3) Intel Processor Diagnostic Tool: Download Intel(R) Processor Diagnostic Tool
Disregard if not using an Intel processor

4) Furmark stress test for GPU: FurMark > Downloads
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

5) OCCT: OCBASE / OCCT
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

Good luck!

jdc1 said:

This driver dates from 2013. You should uninstall the program associated with it (and ensure that the driver is gone after a reboot). If you need this program, check to see if you can find/download a W10 compatible version.

Thanks for the reply @jdc1
What driver are you referring to?

How old is your new system?

As much as it would be nice to solve this, if you have the chance to exchange it for a new system, I would do so.

Oh my, sorry for the stupid mistake! I forgot to paste the name of the driver into my post

Rerunning the dump file now..........

The driver is:

Code:

ScpVBus.sys                 Sun May  5 17:31:26 2013 (5186CFAE)
Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller

Looks like a USB Shock controller - likely for a PS2/3 emulator.
Any idea about what this is?

If not, post back and we'll see about removing it in a different way.

jdc1 said:

Looks like a USB Shock controller - likely for a PS2/3 emulator.

@jdc1 I did download this program called inputMapper so i could use my playstation controller while i played certain games that supported it. Though, I don't remember if i was getting these BSOD before or after the fact. @ranchomirage I just built this PC a week ago. I had help building it so I dont think anything is messed up that involves the hardware. It's possible but just unlikely. Though if one of my parts is faulty, lets say my ram for instance, I could understand that. I'm just hoping this is just a simple driver issue. That'd be much more simple than having to send the ram sticks back in the mail and wait on new ones, etc.



I've uninstalled inputMapper using windows's uninstall method. Though, I am not sure where to find the ScpVBus.sys. After i uninstalled input mapper, i opened up task manager and looked through the processes and services tabs and couldnt find anything that even came close to ScpVBus.sys so then i opened device manager and searched around with no luck either.

Am I looking in the wrong spots? Or, do you think the driver disappeared when i uninstalled inputMapper, I didnt think it was gonna be that simple.

If Input Mapper is a reliable, well designed program - then it's uninstaller should take care of everything for you.
If it's not, then there may be problems - but we'll deal with them if/when they arise. Meanwhile, just assume all went well and see if it stops the BSOD's. If not, then zip up and upload the contents of the C:\Windows\Minidump folder after the next BSOD and upload it with your next post.

To find the ScpVBus.sys driver (if it's still on the system):
Open File Explorer and search the C; drive for ScpVBus.sys
It should be in C:\Windows\System32\Drivers (and may be in other locations)
As long as you're out looking for it - if you find any, rename them to ScpVBus.BAK

You can also open up msinfo32.msc
Then expand the Software Environment category (in the left side pane)
Then select System Drivers and you'll be able to see the driver.

jdc1 said:

If Input Mapper is a reliable, well designed program - then it's uninstaller should take care of everything for you.
If it's not, then there may be problems - but we'll deal with them if/when they arise. Meanwhile, just assume all went well and see if it stops the BSOD's. If not, then zip up and upload the contents of the C:\Windows\Minidump folder after the next BSOD and upload it with your next post.

To find the ScpVBus.sys driver (if it's still on the system):
Open File Explorer and search the C; drive for ScpVBus.sys
It should be in C:\Windows\System32\Drivers (and may be in other locations)
As long as you're out looking for it - if you find any, rename them to ScpVBus.BAK

You can also open up msinfo32.msc
Then expand the Software Environment category (in the left side pane)
Then select System Drivers and you'll be able to see the driver.

Thank you for the help. @jdc1

I looked in the drivers folder located in System32. I renamed it to ScpVBus.BAK. Now I should just wait and hope that i dont blue screen anymore?

If I do, I will refer back to this thread and post another zip of what happened. Hopefully everything is good now and I dont see any more BSOD.

See if you can identify the software on the computer:

Scp Virtual Bus Driver

Scarlet.Crush Productions

404 Not Found

Search the rest of the C: drive for more copies of it and rename any that you find. Software Protection May try to replace it with another copy

Then wait and see if the BSODs recur