Windows 10: BSOD consistently every 6 hours.Estimation/roughly

I've been getting random BSOD's when playing games but it only seems to happen after a longer gaming session maybe like 6 hours into playing, it is pretty consist, on when it'll happen. The errors I've seen pop up are store_data_corruption and IRQL_NOT_LESS_OR_EQUAL.I've done alot to try to fix the issue like, running a memtest86 which came back with 0 errors, the cmd memorytest, reinstalled windows 11, done a stress test benchmark to check for overheating, also done the system scan and cmd scan for corrupted files, and also updated everything in my gigabyte control center. I'm sure there is m

:)

 

Consistent BSOD - DPC Watchdog Violation

I've been getting consistent blue-screens with DPC Watchdog Violation listed as the cause. I've been working on fixing it for nearly three days now, attempting the various solutions thrown across the internet.

Here's what I've tried so far:

• Uninstalling and reinstalling graphics drivers (also via safe mode)
• Uninstalling/disabling Nvidia audio drivers
• System restore to a point before the crashes
• Chkdsk /r (no errors)
• Memory test (no errors)
• Driver roll-backs

System information (custom set-up):

• Asus Rampage IV Extreme motherboard
• Intel i7-3960X CPU
• GEFORCE GTX 690 Graphics card
• 16GB RAM

The computer has been up and running for nearly 6 years now, without any large problems. It began on Windows 7, and was upgraded to Windows 10 shortly after its release. It has been running perfectly on 10 for several months.

The issues started following two major windows updates, which included driver updates, but rollbacks don't seem to fix the issue.

Here is a link to several of the most recent Minidumps that have been collected: Microsoft OneDrive

I've looked through the dump files with WinDBG and the like, but I either don't know what I'm looking for or it's not there.

I ran the computer for roughly 6 hours today while at work, with the Graphics Card disabled and several applications open and actively running, with video and the like. When I got back, it had still not crashed. This leads me to believe it's almost certainly
an issue with the card, but I can't figure out how to fix it. This leads me to the dreaded question: is this a hardware issue? If I need to replace the card, I will, but I'd like some consensus that that is indeed the issue before I make the investment.

Any insights or suggestions would be greatly appreciated. I'm almost sure there's other things I've tried that I forgot to list, but those are the big ones.

***Post moved by the moderator to the appropriate forum topic.***

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.

 

BSODs, even after fresh windows install

I will try the solutions you suggested, however when you say "log files" are you referring to the minidumps or the list of issues and BSODs I wrote? If its the list I wrote then all of those issues also occur without compiling/using rust, it is simply a way I've found to reliably check if I have solved the issues since so far I have had 100% consistency with being unable to compile. Otherwise after each step I would have to wait a few minutes to a few hours for a random BSOD or other issue to occur.

I also have another suspicion that the issue lies with one or more individual CPU cores, I will be running memtest86 on each core individually to see if there is a observed difference.

Any and all troubleshooting tips are highly appreciated.