Getting Random BSOD on my PC I just built.

catsworth1

Reputable
May 8, 2015
7
0
4,510
Hello, recently built a new PC, but sometimes I'll get a BSOD. It's completely random, sometimes it'll run for 3 days before it'll happen, sometimes it'll happen after a week has gone by. It can happen either when I'm playing games or just randomly browsing the internet.

Here are the recent crash dumps I uploaded to mediafire.

Any help or suggestions would be appreciated.

If I need to post more info please let me know.

http://www.mediafire.com/download/5wovhzwbul7ehh8/crashdumps.rar
 
something corrupted memory, most likely
Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
ScpVBus.sys Sun May 05 14:31:26 2013
and the service PROCESS_NAME: ScpServer.exe


I would stop the service and remove the driver.
you can confirm the problem if you want. change your memory dump type to kernel,
Start cmd.exe as an admin, run
verifier.exe /standard /all
reboot your machine and wait for the next bugcheck. verifier will check all drivers and try to bugcheck at the time of corruption.

use:
verifier.exe /reset
to turn off verifier (you might have to go into safe mode if your machine bugcheck on boot)
 


Alright I'll give this a go and see if anything happens.
 
this bugcheck was a memory corruption in the tracking of how your physical memory is mapped to your pagefile.sys.
verifier debug flags were not set. \SystemRoot\system32\DRIVERS\ScpVBus.sys Sun May 05 14:31:26 2013
was still loaded.

you need to change your virtual memory type to kernel memory dump. This will make the new memory dump
c:\windows\memory.dmp and the file will be much larger.

You also need to run cmd.exe as an admin and then run
verifier.exe /standard /all

then reboot and wait for the next system crash. Verifier will crash the system and provide debug info on the driver with the problem. It will attempt to crash the system when a driver attempts to corrupt system memory rather than waiting for corrupted memory to cause a crash in some random component of windows.

using a kernel dump will also save internal error logs to the memory dump and save extra debugging info. (they are lost with a mini memory dump)





 



Could have sworn I did that, I'll make sure it gets done this time.
 
verifier flags are set ok, kernel memory dump is good now.
looks like ScpVBus.sys is still running and verifier flagged as a bad driver for various bugs. Maybe it is in the hidden driverstore and is being restored when you reboot.
\SystemRoot\system32\DRIVERS\ScpVBus.sys Sun May 05 14:31:26 2013

you can run cmd.exe as an admin and remove a package from the driverstore with the pnputil.exe command.
take a look at this:https://technet.microsoft.com/en-us/library/cc730875.aspx

attempt to remove it again, reboot then start cmd.exe as an admin and run
driverquery.exe
it will make a list of your drivers that are currently running, just confirm iscpvbus.sys is not in the list.


 


Alright I took care of it, it's not showing up in the driver query anymore. So at this point I'll just hang tight and see if I blue screen again.
 
Alright so it's been a while since I last posted here but it has been happening a few times again since I last removed that driver. Although every time I would get a blue screen it wouldn't leave a memory.dmp. It wasn't till yesterday that I realized it was because I didn't have enough space on my hard drive. Well this has been happening pretty frequent but still no rhyme or reason to it, it just seems to happen regardless of me playing games on it or not.

Here is the recent MEMORY dump

http://www.mediafire.com/download/x1l6s8n9p821l8b/732015crash.rar



Also to mention the error that comes up is usually different but the one today seems to be SYSTEM_SERVICE_EXCEPTION.

EDIT: So it happened again around 1:34 am. Was talking on skype while playing a game. Uploaded the memory dump.
http://www.mediafire.com/download/s0gdzc14mom11yz/july4crashdump.rar
 


Could you solve this issue? I'm having the same problem amd I don't know what to do. It's very annoying.
The worst part of this is that I have had the Scarlet Crush drivers for a while and I never had a problem until now, an it has never updated or something. Really weird stuff.
 
if I remember the uninstaller for this program really did not uninstall the driver and it would just corrupt things on each boot. Only critical corruptions will cause a bugcheck.

best to remove the driver from the driverstore
you can run cmd.exe as an admin and remove a package from the driverstore with the pnputil.exe command.
take a look at this:https://technet.microsoft.com/en-us/library/cc730875.as...

this will make sure the driver is removed, you can then confirm with the driverquerry.exe command.
start cmd.exe as an admin then run
driverquerry.exe -v >c:\outfile.txt
notepad c:\outfile.txt
then look though the list of drivers that are currently running on your machine to make sure it is really gone.