Windows 10: Computer bsod, freezes, and turns off randomly

That was the latest version listed for your card when I searched. Doing it now I'm coming up with different versions.
Do you have Nvidia Geforce Experience installed? If not, install it and see what it says about a driver?

 

Yes, I have it installed. It says the version you told me to install is old.

I had the last version installed (368.39) prior to the latest crashes.

 

If it BSODs again, re-run DM_Log_collector then let's try Driver Verifier:

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

Warning:
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.

 

The computer just randomly turned off, no BSOD. Should I run Driver Verifier? Or should I wait for a BSOD?

 

Nevermind, just got a BSOD. Dump file:

Attachment 86192

I am going to run Driver Verifier.

Thanks

 

I ran Driver verifier and the computer would BSOD as soon as I booted it (before log in screen). Here are the dump files:

Attachment 86198

 

The 6/21 @ 5:51 dump points to the Nvidia driver:

Code: fffff801`01ae9178 fffff800`08afa6ebUnable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x22a6eb[/quote] The 6/21 @ 6:18 indicates ScpVBus.sys
Driver Description: Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
I don't know what this is but it's quite old, dated 5/5/2013.

Open a Elevated Command Prompt then run the following commands.

driverquery > RunningDrivers.txt
pnputil -e > oemDdrivers.txt

Zip the two output .txt files

From File Explorer, select RunningDrivers.txt and oemDdrivers.txt. Right click on them and select Send to then Compressed (zipped) folder. Call it MoreDrivertInfo.zip.

Upload and attach here please. Not sure this will help but I'm hopeful.

Meantime, see if you can find anything like Scp Dual Shock 3 Virtual Bus Driver on your PC.
It may have something to with a Playstation.

 

Here is the zip file:

Attachment 86211

I installed some software a long time ago (1.5 years+ ago) that was supposed to connect a playstation controller onto a computer. It did not work, so I uninstalled everything (or I thought so...). I can't find anything as of now.

 

Install Everything Search and let it start after install, then enter ScpVBus.sys in the input area at the top. It will show you where it's located. Should be in C:\Windows\system32\drivers.

You could try pnputil -d C:\Windows\system32\drivers\ScpVBus.sys from a Elevated Command Prompt, see if that deletes it for you.

 

I found it and deleted it. I will let you know what happens. Thanks again for your help *Smile

 

Another BSOD.


Attachment 86234

 

The oemDrivers.txt you uploaded still shows Scarlet Crush. If you ran that before you removed the SCP stuff, can you run it again and upload the zip.

Code: Published name : oem3.inf Driver package provider : Scarlet.Crush Productions Class : Universal Serial Bus devices Driver date and version : 05/05/2013 1.0.0.103 Signer name : Bruce James Published name : oem35.inf Driver package provider : Scarlet.Crush Productions Class : System devices Driver date and version : 05/05/2013 1.0.0.103 Signer name : Bruce James[/quote]

 

Here it is:

Attachment 86422

 

The SCP stuff (Scarlet.crush) is still there. Let's see if we can get rid of it permanently;

Open a Elevated command Prompt.
Type pnputil.exe -d oem3.inf and press Enter.
That should get rid of it. Run pnputil -e > oemDdrivers.txt again and post the output txt file.

 

I did what you said and here is the text file: Attachment 86520

I got another BSOD after outputting this text file. Dump files:

Attachment 86522