Windows 10: BSOD after closing CS:GO or Dota 2

That part was meant for you *Tongue

 

It just crashed again after closing CSGO.

 

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.

 

So now I'm just waiting for it to crash. Then what?

 

When you get a crash, just run the DM Log Collector tool and upload the zip file.
If you can't login back, follow the instructions for disabling verifier.
If there are problems with disabling verifier please let me know, also let me know what you have tried.

 

So it's been 24 hours already with the driver verifier. Should I keep it running for another 24? Do you believe something will change? It hasn't crashed (neither because of the verifier, or the usual unknown cause).

 

I hope this answers your question.
If you'd like, you could of course run dota 2 or cs:go and see if it crashes again after closing.
Keep in mind that if the system crashes it doesn't have to be verifier that is causing the crash.
Keep also in mind that if you decide to play, your pc could become extremely slow in performance.

 

I played CSGO yesterday and didn't experience any drop in performance (maybe a few fps dropped here and there but that's all).

 

Ok, no crashes with the driver verifier for 48 hours *sarc

 

I know it is odd, but driver verifier sometimes stabilizes the system. Verifier is sometimes used for extreme unstable systems to upload the logs for the investigation.






Diagnostics Test

Clean boot
Please try the following:

• Open taskmanager
  • Go to the tab startup
  • disable everything
• Search msconfig and open it
  • Go to the tab services
  • Check 'hide microsoft services'
  • Uncheck all other services
  • Click apply and click ok
• Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.
If the problem still persist, try booting in safe mode and see if the problem still persist






Diagnostics Test

System File Check
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.

 

Yeah, I think I remember using sfc/scannow when I previously investigated this issue. Same result now, it says "Windows Resource Protection found corrupt files but was unable to fix someof them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios."

I've uploaded the log here.
Later edit: I've also disabled almost everything from startup, now it looks like this: Attachment 48106
Also the only running services at startup are these: Attachment 48107

 

Code: 2015-11-14 16:52:00, Info CSI 00005406 [SR] Cannot repair member file [l:56{28}]"Clip_480_5sec_6mbps_h264.mp4" of Microsoft-Windows-WinSATMediaFiles, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-11-14 16:52:00, Info CSI 00005407 [SR] This component was referenced by [l:200{100}]"Microsoft-Windows-WinSATMediaFiles-Package~31bf3856ad364e35~amd64~~10.0.10240.16384.WinSATMediaFiles" 2015-11-14 16:52:01, Info CSI 00005408 Hashes for file member \??\C:\WINDOWS\Performance\WinSAT\Clip_480_5sec_6mbps_h264.mp4 do not match actual file [l:56{28}]"Clip_480_5sec_6mbps_h264.mp4" : Found: {l:32 b:df1w7EwIacUAKiPvWmDIBpKa7ybbsloAZ59LxSi6Al0=} Expected: {l:32 b:uu68C3gMLMbnYTX7dvNZypvFGKcPRJgbBhUgAPkKhAk=} 2015-11-14 16:52:01, Info CSI 00005409 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-winsatmediafiles_31bf3856ad364e35_10.0.10240.16384_none_cd6acd7602723095\Clip_480_5sec_6mbps_h264.mp4 do not match actual file [l:56{28}]"Clip_480_5sec_6mbps_h264.mp4" : Found: {l:32 b:df1w7EwIacUAKiPvWmDIBpKa7ybbsloAZ59LxSi6Al0=} Expected: {l:32 b:uu68C3gMLMbnYTX7dvNZypvFGKcPRJgbBhUgAPkKhAk=} 2015-11-14 16:52:01, Info CSI 0000540a [SR] Could not reproject corrupted file [ml:68{34},l:66{33}]"\??\C:\WINDOWS\Performance\WinSAT"\[l:56{28}]"Clip_480_5sec_6mbps_h264.mp4"; source file in store is also corrupted[/quote] Please try following command in admin command prompt
Code: DISM /Online /Cleanup-Image /RestoreHealth[/quote] If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial

 

Error: 0x800f081f


The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.


The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

This is what I get when I run DISM. Also, I don't have a (mounted) Windows 10 ISO, as I've upgraded from Windows 7.

 

Just follow the instructions, read the tutorial and use the provided links in the tutorial.

Read carefully.

 

Ok I didn't notice there was a link with Windows 10 ISO. Anyway, I got the same message using Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:F:\sources\install.wim:1 after downloading and mounting the Windows ISO.