Daily BSOD...

[ThatCreeper]

I have had many issues with BSOD over the last few years with my current PC. As of recent, I would usually get 2-3 BSOD a month. Now it happens often... daily, in fact.

The PC I use is a custom built PC and is intended for gaming. I cannot game due to the BSOD and when it happens, the BSOD usually deletes the game save of the game I was playing. I need some help with this - it'd be much appreciated.

 

[axe0]

Hi ThatCreeper,

Welcome to the 7forums.

It seems there is only 1 dump file in the attached zip file.
Please check {windows partition}\windows\minidump and check if there are more recent dump files saved.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 7 tutorial

Please move some files from D partition to increase the free space to at least 10-15%.
Every partition needs at least 10-15% free space so Windows can do its thing in the background.

   Warning

Less free space could cause BSOD's

.

 

[ThatCreeper]

Hi there,

yes, my Windows settings are configured correctly so that it makes minidumps... but it still has issue of keeping minidumps. Sometimes when I get a BSOD, it'll make a minidump but most times it will not. The only minidump in the folder is this one that I will attach to this post.

Also, my D partition has 64GB left. Is that not enough space?

Thanks for the reply.

Edit: And I remember posting on here before, way back, and nobody could help me in terms of the minidumps. Nothing worked. The minidumps that did go through would usually be corrupt. I've reinstalled Windows so many times in the past also.

 

[axe0]

I cannot read the dump files either.
This could be due to hardware problems.
I guess you have tried sfc?

 

[ThatCreeper]

SFC?

Also, just wanted to make it known that it cannot be due to RAM. I have tested the RAM a lot in the past - it all checks out to be good. No errors.

I hope to finally get to the bottom of this, if it is hardware or driver related, ect.

Appreciate the help.

 

[axe0]

System File Check a.k.a. Windows Resource Protection.
It scans through the system files for any corruption, missing files and / or other problems.

Please do the following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[ThatCreeper]

Hi,

I did the sfc/scannow and all checked out fine. What are the chances of driver verifier screwing up my Windows, data, ect.?

 

[axe0]

Driver verifier only stresses the drivers.
However, because it may sometimes hard to disable it, that is why it is recommended to have rescue media and a restore point

 

[ThatCreeper]

I already have my Windows 7 disc - can I not just use that to repair if something goes wrong? I also just created a restore point. Am I set to try the driver verifier now?

Appreciate the help.

 

[axe0]

That is the rescue media we mean

Yes

 

[ThatCreeper]

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

 

[ThatCreeper]

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]

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]

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

 

[axe0]

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]

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

 

[axe0]

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

*** 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: [U]ScpVBus.sys[/U]
    Timestamp:        [COLOR="Red"][U]Sun May 05 23:31:26 2013[/U][/COLOR] (5186CFAE)
    CheckSum:         0000E3B0
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[ThatCreeper]

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]

The driver is located at

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]

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.