Daily BSOD...

ThatCreeper · 29 Sep 2015

Alright, thanks. Configured the driver stuff and will now wait 24 hours.

ThatCreeper · 29 Sep 2015

Okay, I restarted my PC and instantly got a BSOD - multiple times. I couldn't get into my PC so I had to use the system restore. Where do we go from here?

**axe0** · 29 Sep 2015

ThatCreeper said:

Okay, I restarted my PC and instantly got a BSOD - multiple times. I couldn't get into my PC so I had to use the system restore. Where do we go from here?

Check in {Windows partition}\Windows\Minidump\ for dumps created on the time of the crashes.
I doubt that there are any since you did a restore, but please check to be sure.

ThatCreeper · 29 Sep 2015

Oh, was I not meant to restore? Should I have used the Windows disc to repair?

**axe0** · 29 Sep 2015

ThatCreeper said:

Oh, was I not meant to restore? Should I have used the Windows disc to repair?

It was prefered to use the repair media to get a command prompt and enter "verifier/reset" (without quotes)
That should have solved the problem.

ThatCreeper · 29 Sep 2015

I will try again? I'll do the driver thing again...

**axe0** · 29 Sep 2015

It looks like we have a winner in the dump file from today

SCP Virtual Bus driver is the cause.
Please check here if there are driver updates available

Code:

*** WARNING: Unable to verify timestamp for ScpVBus.sys
*** ERROR: Module load completed but symbols could not be loaded for ScpVBus.sys

3: kd> lmvm ScpVBus
start             end                 module name
fffff880`043f0000 fffff880`043fe000   ScpVBus  T (no symbols)           
    Loaded symbol image file: ScpVBus.sys
    Image path: ScpVBus.sys
    Image name: ScpVBus.sys
    Timestamp:        Sun May 05 23:31:26 2013 (5186CFAE)
    CheckSum:         0000E3B0
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

ThatCreeper · 29 Sep 2015

So that's the one, ay? Appreciate the help. I always get different STOP BSOD messages such as volmgr.sys and various other .sys BSOD... could there be more that we don't know about?

Thank you.

EDIT: I no longer use that on this PC so is there anyway I can remove/delete the driver?

EDIT 2: I also tried that command you said, I typed verifier/reset into the CMD and it come up as nothing. No error, ect. That didn't work because once I typed it in I rebooted my PC and got hit with another BSOD.

**axe0** · 29 Sep 2015

The driver is located at

Code:

c:\windows\system32\drivers\

If you are sure you have removed the program, you can manually remove it.

Ai, I did not expect that

Please use the restore point to get back into windows.

ThatCreeper · 29 Sep 2015

Yeah, I got back into the PC. Isn't there a way to do a restore without it deleting the minidump? Isn't that above minidump old?

I also just deleted the driver - but I have a feeling I'll get hit with another BSOD sometime soon. We'll see.

Cheers, Axe. You've been a great help.