BSOD mainly while playing CSGO, have DMP files

Hey all,

So lately in the past couple weeks outta nowhere I've been not being able to play CSGO because it will just crash and BSOD after a while of playing (like 10-30 minutes). However, while playing any other game like Overwatch or Rust it doesn't crash at all and the BSOD issue doesn't occur. So I just decided "fine, I won't play CSGO", but now it just happened whilst browsing the internet a couple weeks after CSGO bsod became a regular thing. I have the dump files and this is a formal request for help, so thanks to anyone that reads the files and can give me any info on what I can do. Thank you

-Frank

Hey thanks for the reply bro,

here's my specs: Gyazo - b0f847f58869ba1816632eb7146acfe8.png

The temperatures are completely fine, however it appears to be two situations where I bluescreen: while doing windows disk cleanup, and also while playing csgo. I have no idea why this happens it doesn't really make sense to me. I'm doing the SFC /scannnow command now, aswell as a disk check. I'll get back to you after I've done that. Are my specs the problem? I don't think they would be as I played csgo for a few thousand hours before with this specs but maybe somethin got damaged idk. Generally my PC isn't very clean though, if I run disk cleanup it commonly BSOD and if I play CSGO it will BSOD. All other games work completely fine though.

ICIT2LOL said:

Hello and welcome 877spy mate first some system specs please no good unless we know what we are working with System Info - See Your System Specs post them here or better still update your profile info.

Now you can start by checking the temps on the machine use this Speccy - Free Download - Piriform I always use the piriform site not keen on the FileHippo.

Run these too for another start point
SFC /SCANNOW Command - System File Checker
Disk Check < if necessary include the /f and /r in the command line as per Option2 > in safe mode if need be

Hey bro,

I did the sfc scannow and a bunch of corrupted files were found and repaired - hopefully this fixed it. I'm gonna use whocrashed now and give another update to the thread thanks for the help mate

ICIT2LOL said:

Hello and welcome 877spy mate first some system specs please no good unless we know what we are working with System Info - See Your System Specs post them here or better still update your profile info.

Now you can start by checking the temps on the machine use this Speccy - Free Download - Piriform I always use the piriform site not keen on the FileHippo.

Run these too for another start point
SFC /SCANNOW Command - System File Checker
Disk Check < if necessary include the /f and /r in the command line as per Option2 > in safe mode if need be

"Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 12/20/2016 1:18:50 PM your computer crashed
crash dump file: C:\Windows\Minidump\122016-65707-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F64180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. "

This is what I got from whocrashed, but I don't know what to do to fix it..

ICIT2LOL said:

Ok mate sorry late reply but that is what the debugger results come like and really doesn't mean a great deal to me.

The ntoskrnl.exe dump is an often posted one and it can like that report says be just about anything. Now be careful about using software that do things for you not that I think the one you used is particularity crappy but a lot can and it is best left alone unless you are really sure of the program.

Now I think it would be a really good idea to run the chkdsk I linked before too because that will find and fix and/or repair the filing system.

Okay I got some news on the entire thing. After running Drivermax to update my drivers, I think I've found the problem, when I update my sound driver that was last updated 2011 because my motherboard is really old to the 2016 one, I bluescreen instantly. I also bluescreen when I run CSGO and voice chat gets activated, probably being caused by the corrupted/faulty 2011 audio driver. I don't really know what to do as whenever I try to touch the 2011 driver I BSOD and if I try to update it with drivermax my PC won't even turn on without bluescreening and I have to system restore. I have however recieved a useful BSOD now which I think will give us alot more info (im gonna attatch it now.) DM log collector wasn't working as it didn't put a zip on my desktop so I used an alternative "Seven Forums collector" and I've uploaded that zip file instead containing the same kind of info that I think you wanted. It also contains my latest BSOD Crash dump file which I think is useful this time, heres a screenshot of WhoCrashed which shows a new bugcheck and shit

Gyazo - 8d1b6b6ff33b833a7e3f7103eab53e46.png
Gyazo - 2407992c7ca488157d694d25453da636.png <(Apparently the "viahduaa" one is the cause of the problem and it's the 2011 almost definately ****ed/faulty audio driver. If I try and update though I just BSOD constantly and can't launch my PC without BSOD, or if I try and touch it or do anything, but if I leave it in it's current state I can't play CSGO without BSOD and I also can't do much stuff related to my audio. I'm not sure if I'm right on this being the case but I don't know, I'm also not sure how I can go about updating or fixing this driver to stop BSOD.)>
Gyazo - 85470d4384f292ab5c8d523e42a58355.png

P.S. I couldn't find the Memory.dmp kernal file but hopefully this is enough new news or info to not need it. Please help, thanks. p.s.s happy christmas amigos

Hey, here's a screenshot of my systeminfo:
Gyazo - e3fb187100074c0c1a0b8e9c4e0f1d09.png

I've also retried uploading the zip file.