Windows 10: Recent BSOD Issues

300. I set my fps limit to 300, and it pretty much doesn't dip below.

I should clarify I meant to say that the timing of the bsod was random. I didn't mean that the bsod come consistently after hours of gaming. Actually, I did not crash at all today and I played about 3 hours. Yet at least. Today was a good day.

 

I suggest to focus on the total description of the OP, not only the first post.
Every description need to be used for a patern.

 

Please try 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" after the second SFC, 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. Finished the 2nd scan. It DID say that the scan didn't not find any integrity violations. The first scan however did find issues, but I suppose it managed to fix them. Would you like me to upload the file still?

 

A file isn't necessary with a no integrity violations result *Smile

Please test your system, if any bluescreen occurs let me know with

• an uploaded zip from the dm log collector
• a description of what happened and what you were doing

 

Sure. I know for a fact that the driver verifier throws the bsod at me. I think I will run it again to test. I'm not entirely sure what a dm log collection is but I'll handle that if it's necessary. Going to run the verifier.

 

The dm log collector is the tool from the BSOD Posting Instructions *Wink

 

Ah. I probably should have recognized that.

So, I ran the verifier again. Seems the same problem persists, especially with the clipsp.sys file(?).

I'll try to provide some detail:

I run the verifier through the CMD prompt by typing: "verifier".

I pick settings, and test all drivers.

I restart, it begins the verifying. After a few minutes, it BSODs. It reboots, and then continues the process(I assume). It BSODs again after a few minutes(both times it gives a driver verifier detected violation citing the clipsp.sys.). It reboots again after that, and goes into an automatic repair system restore.

System Restore completes. Verifier is no longer running, I'm back at my desktop.

Now I'm here. I'll attach the new DM Log.

It's 6:20 in the morning, so I'm probably going to be in bed before you reply. I'll check back tomorrow and hopefully we can get this sorted out. I appreciate your help.

 

What settings do you choose?
We (the team) suggest to choose following settings

• I/O Verification
• Force pending I/O requests
• IRP logging

Driver Verifier - Enable and Disable in Windows 10 - Windows 10 Forums

Warning Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Booster and DriverMax Agent, please remove them as it may cause trouble.

 

I was doing:

Create Custom Settings -->

Everything except Randomized Low Resource Simulation and DDI Compliance Checking -->

Then I would choose Automatically select all drivers installed on this computer.

Perhaps tomorrow I should run with your suggested settings and see how it goes.

 

The marked part is where it mostly goes wrong, you then also choose the drivers of Windows what explains why clipsp.sys is being flagged
FYI, some information about this driver: Driver Reference Table - clipsp.sys
With driver verifier one normally chooses everything but Windows drivers.

 

Ah. My mistake. Perhaps the original sfc scan you had me do fixed my original problem and now I've had you chasing ghosts. I will run the verifier as you suggested tomorrow and see if that causes me any issues.

 

Oh, and as for the programs mentioned to update drivers, I did try one. It updated a few drivers, and immediately caused my PC to go into a bsod loop. I system restored in safe mode and immediately removed that atrocious program. Lol.

 

Ok, you might still encounter BSOD errors (Due to Windows.Old files, I don't recommend touching that folder). Tell us if you encounter any BSOD errors. Most likely not *Smile

 

And BTW, download updates from both Windows Update and your Manufacturers Website if Windows Update can not Update your Drivers or Anything else.

 

Wanted to wait a few days before posting, but it would appear that my issue has been fixed. I haven't had a BSOD in a few days now. If anything changes, I suppose I'll just come back. Happy Holidays and Thank You