Question BSOD in Windows 10

Sam.R

Honorable
Aug 15, 2015
75
0
10,640
Okay so for quite some time now ive been suffering with BSOD on a daily basis, i have made a couple of posts on here but nobody seems to be able to help me. Last week i got a BSOD and my pc became unrecoverable and i had to reinstall Windows to get it up and running again. Since doing this my pc is working but im still suffering with BSOD. I've been trying to diagnose the problem but I have no idea what is causing them, yesterday i got a blue screen with the code DPC_WATCHDOG_VIOLATION. I googled this and it said something like memory drivers probably need updating etc so i have done this. The very next day i got the blue screen with code WHEA UNCORRECTABLE ERROR, as far as im aware this could be anything. Im not the best on pc but googled some stuff on how to check for bad drivers, and it said to run something called verify. I created a restore point and ran it to check my drivers and it came back with a blue screen saying something about my corsairdriver.sys64 failed or something. I have no idea if that means this is the bad driver or what? I have also looked at my reliability monitor and in the critical bit corsair drivers are always there. Every time ive had system blue screen a corsair service has flagged up an issue in the reliability montior. Should i just throw away my corsair headset or is this not what's causing my blue screens?

Sorry for the very long explanation but nobody has been able to help me and im sort of just trying to figure it out with not much idea.

My pc specs are;

GTX 970
CPU I7-4790k
RM850 PSU (Corsair)
Ripjaws x RAM, 2x8gb
Gigabyte Z97X-GAMING 7 MOBO
Samsung 850 EVO SSD (OS Drive)
Sandisk SSD Plus
and the headset in question is Corsair HS70 SE Wireless
 

Ralston18

Titan
Moderator
Look in Event Viewer - any errors there?

If the Cosair headsets work on another computer do not throw them away.

Try other known working headsets on your computer.

If the BSODs persist then try updating video and audio drivers.

The Windows 10 built in troubleshooters may find and fix something.

And running "sfc /scannow" (without quotes) via the command prompt may find and fix some problem.

https://support.microsoft.com/en-us...er-tool-to-repair-missing-or-corrupted-system
 

Colif

Win 11 Master
Moderator
Can you follow option one on the following link - here

and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link here and I will get someone to convert file into a format I can read


Are you overclocked as WHEA errors can be caused by that. Also caused by overheating, overclocking software, and pretty much any hardware on PC. They errors called by CPU but not necessarily caused by it.
 

Sam.R

Honorable
Aug 15, 2015
75
0
10,640
Look in Event Viewer - any errors there?

If the Cosair headsets work on another computer do not throw them away.

Try other known working headsets on your computer.

If the BSODs persist then try updating video and audio drivers.

The Windows 10 built in troubleshooters may find and fix something.

And running "sfc /scannow" (without quotes) via the command prompt may find and fix some problem.

https://support.microsoft.com/en-us...er-tool-to-repair-missing-or-corrupted-system
Hello,
the headset works perfectly fine it was just strange how event viewer was throwing up problems with it just before blue screens.

All my drivers are up to date, i even went in a checked a lot of them myself to see if i could find any newer ones and i couldnt.

Windows 10 troubleshooter didnt help at all i tried this.

I just ran sfc / scannow and it didnt find anything
 

Sam.R

Honorable
Aug 15, 2015
75
0
10,640
Can you follow option one on the following link - here

and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link here and I will get someone to convert file into a format I can read


Are you overclocked as WHEA errors can be caused by that. Also caused by overheating, overclocking software, and pretty much any hardware on PC. They errors called by CPU but not necessarily caused by it.
Hello,

here is the link https://transfernow.net/747h88j183bk
 
Please do the following to provide additional information
  • Go to https://www.sysnative.com/blogs/download/sysnativebsodcollectionapp-exe/ and download the SysnativeBSODCollectionApp.exe
  • Run the tool and give it approx. 10-20 minutes to finish, on some machines it may take some time
  • When the tool is finished, it will have created a zip file on your desktop and open the desktop folder and a file called BSODPostingInstructions.txt. Upload the zip file ton onedrive, google drive or dropbox and post a share link.
 

Sam.R

Honorable
Aug 15, 2015
75
0
10,640
Please do the following to provide additional information
  • Go to https://www.sysnative.com/blogs/download/sysnativebsodcollectionapp-exe/ and download the SysnativeBSODCollectionApp.exe
  • Run the tool and give it approx. 10-20 minutes to finish, on some machines it may take some time
  • When the tool is finished, it will have created a zip file on your desktop and open the desktop folder and a file called BSODPostingInstructions.txt. Upload the zip file ton onedrive, google drive or dropbox and post a share link.
Hello,

I take it i need to wait until i get a blue screen again before i send this file? at the moment it just contains instructions on how to post my file
 
What I saw in the eventlogs was a couple of different BSOD crashes
1 0x124
2 0x199
1 0xc4
1 0x133

The variation and timeframe is worrying, all almost within 24h. From that point it's almost certain that there's an underlying hardware problem.
Unless there's someone here who can very easily track down what hardware part(s) is causing this, I think this is best tackled by eliminating hardware parts and since the Corsair headset and video are involved I think a logical step would be to eliminate those as a starting point.
 

Sam.R

Honorable
Aug 15, 2015
75
0
10,640
What I saw in the eventlogs was a couple of different BSOD crashes
1 0x124
2 0x199
1 0xc4
1 0x133

The variation and timeframe is worrying, all almost within 24h. From that point it's almost certain that there's an underlying hardware problem.
Unless there's someone here who can very easily track down what hardware part(s) is causing this, I think this is best tackled by eliminating hardware parts and since the Corsair headset and video are involved I think a logical step would be to eliminate those as a starting point.
The corsair headset is newish, i was having BSOD before i got it but it wasnt as frequent. I also already know that i get BSOD without my graphics card installed. The problem i have is its probably then going to be the motherboard or the CPU? If so, the socket my motherboard has is now discontinued which means either way i am going to have to buy a new cpu and motherboard. Unless you think it could be another component?
 

Colif

Win 11 Master
Moderator
Try running this on CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

If you haven't already, run memtest on ram - Try running memtesst86 on each of your ram sticks, one stick at a time, up to 8 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

Motherboard is hard to test, its normally last after you check everything else

.
Wish I had never seen 0x124 before, otherwise known as WHEA error
can't say I seen this one before - https://docs.microsoft.com/en-us/wi...r/bug-check-0x199--kernel-storage-slot-in-use
I seen this before - https://docs.microsoft.com/en-us/wi...heck-0xc4--driver-verifier-detected-violation
and last one is https://docs.microsoft.com/en-us/wi...bugger/bug-check-0x133-dpc-watchdog-violation

axe, what bios number is he using? Newest bios is F8, updating to it might fix errors.
 

Sam.R

Honorable
Aug 15, 2015
75
0
10,640
Try running this on CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

If you haven't already, run memtest on ram - Try running memtesst86 on each of your ram sticks, one stick at a time, up to 8 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

Motherboard is hard to test, its normally last after you check everything else

.
Wish I had never seen 0x124 before, otherwise known as WHEA error
can't say I seen this one before - https://docs.microsoft.com/en-us/wi...r/bug-check-0x199--kernel-storage-slot-in-use
I seen this before - https://docs.microsoft.com/en-us/wi...heck-0xc4--driver-verifier-detected-violation
and last one is https://docs.microsoft.com/en-us/wi...bugger/bug-check-0x133-dpc-watchdog-violation

axe, what bios number is he using? Newest bios is F8, updating to it might fix errors.
Hello,

Sorry for delayed response been working etc and not had much time to try and fix this issue. Appreciate you guys helping me out :)

I just ran the CPU test you recommended and it passed all the tests it did - temps did reach 100C though i dont know if this is normal?

Having trouble running memtest, dont know how to mount iso files proper i dont think xD sorry

Although i have tried running with 1 stick of ram and switching them before and i still got the blue screen.

I honestly believe the issue is either my motherboard or CPU. I remember once before i couldn't get my blue screen to go away and i turned off the onboard processor and underclocked my CPU in the BIOS and it let me back on. I have no idea why turning off my onboard proccessor or underclocking my CPU would help at all but it got me back on my pc, although i was still getting the blue screens.