Hello. Apologies for the long post I just wanted to include all information from this weird issue in hopes of figuring out the problem.
TLDR at the bottom.
SPECS:
At the beginning of last month, I was playing Marvel Rivals and when I exited the game, I got a BSOD. I thought that was strange but after that I no more crashes or weirdness happened... until yesterday. Yesterday, I was playing Balatro and watching a YouTube video, when out of nowhere my computer force-restarted.
It didn't BSOD the first time so I didn't get a dump file so I couldn't see any potential error. After that, I re-installed my GPU drivers using DDU (In safe mode) and ran furmark and the accompanying CPU burner to quickly see if it was a PSU issue.
I ran furmark and cpu burner for 30 mins and everything seemed fine, until I stopped furmark and cpu burner and then windows instantly BSODed this time with the following error: Kernel Security Check Failure. I installed and used bluescreen view to check the dump file and the item that failed was noskrnl.exe. I researched this and found that the kernel crashing is commonly associated with memory issues. I ran memtest86 and it completed with 0 errors and passed.
My next order of business was to update the BIOS to the newest available version. After that, I re-enabled EXPO and things seemed to be working again for the time being. I then re-seated my ram just in case and used DDU again to uninstall the current drivers and use a previous version for troubleshooting purposes.
Now today, I tried the furmark + cpu burner test combo again to see if those worked, and unfortunately the system hard-restarted again without a BSOD the moment I pressed "stop" on cpu burner.
I started furmark again when the system restarted but this time used cinebench 30-min benchmark to stress the cpu and noticed something possibly concerning regarding my temps.
I know the max temp of the 7900x is 95C which is why I was concerned to see on HWInfo64 that during the stress test, the CCD2 Tdie was briefly at 100.6C! and then went back down yo around 88-95C (sometimes 96C).
The weird thing though is that HWInfo64 did not report any thermal throttling due to the temperature. After the cinebench benchmark was done, the system force-restart crashed again.
I had a hunch that the issue was due to thermals, but it only occurred when the stress tests STOPPED. Furthermore, the second time was when the computer wasn't under any heavy load (playing balatro and watching youtube). Additionally, no thermal throttling was reported by HWInfo64.
I have also done the classic dism /online /cleanup-image /restorehealth and sfc /scannow to no avail.
TLDR:
TLDR at the bottom.
SPECS:
- Computer Type: Desktop
- GPU: RTX 4080 Super Founders
- CPU: RYZEN 9 7900x
- Motherboard: ASUS ProArt X670E-CREATOR WiFi
- BIOS Version: 2704
- RAM: CORSAIR Dominator Titanium 64GB DDR5 6000MHz C30
- PSU: Seasonic Prime TX 1000W
- Case: Antec Flux Pro
- Operating System & Version: WINDOWS 11 PRO 24H2 (Current update: KB5048667 as newer updates have current unresolved issues)
- GPU Drivers: GEFORCE GAME READY DRIVER - WHQL Driver Version: (Prev: 566.36/Current: 566.14)
- Chipset Drivers: AMD X670E CHIPSET DRIVERS VERSION 6.10.17.152
At the beginning of last month, I was playing Marvel Rivals and when I exited the game, I got a BSOD. I thought that was strange but after that I no more crashes or weirdness happened... until yesterday. Yesterday, I was playing Balatro and watching a YouTube video, when out of nowhere my computer force-restarted.
It didn't BSOD the first time so I didn't get a dump file so I couldn't see any potential error. After that, I re-installed my GPU drivers using DDU (In safe mode) and ran furmark and the accompanying CPU burner to quickly see if it was a PSU issue.
I ran furmark and cpu burner for 30 mins and everything seemed fine, until I stopped furmark and cpu burner and then windows instantly BSODed this time with the following error: Kernel Security Check Failure. I installed and used bluescreen view to check the dump file and the item that failed was noskrnl.exe. I researched this and found that the kernel crashing is commonly associated with memory issues. I ran memtest86 and it completed with 0 errors and passed.
My next order of business was to update the BIOS to the newest available version. After that, I re-enabled EXPO and things seemed to be working again for the time being. I then re-seated my ram just in case and used DDU again to uninstall the current drivers and use a previous version for troubleshooting purposes.
Now today, I tried the furmark + cpu burner test combo again to see if those worked, and unfortunately the system hard-restarted again without a BSOD the moment I pressed "stop" on cpu burner.
I started furmark again when the system restarted but this time used cinebench 30-min benchmark to stress the cpu and noticed something possibly concerning regarding my temps.
I know the max temp of the 7900x is 95C which is why I was concerned to see on HWInfo64 that during the stress test, the CCD2 Tdie was briefly at 100.6C! and then went back down yo around 88-95C (sometimes 96C).
The weird thing though is that HWInfo64 did not report any thermal throttling due to the temperature. After the cinebench benchmark was done, the system force-restart crashed again.
I had a hunch that the issue was due to thermals, but it only occurred when the stress tests STOPPED. Furthermore, the second time was when the computer wasn't under any heavy load (playing balatro and watching youtube). Additionally, no thermal throttling was reported by HWInfo64.
I have also done the classic dism /online /cleanup-image /restorehealth and sfc /scannow to no avail.
TLDR:
- BSOD after exiting marvel rivals
- BSOD while playing balatro and watching youtube
- Force-restart crash after stopping CPU burner
- BSOD after stopping CPU burner
- Force-restart crash after cinebench 30 min benchmark completed
- High peak temperatures on CCD2 of 100.6C; no thermal throttling reported
- System ALWAYS crashes AFTER CPU benchmark/stress test is completed/stopped, not during.
- DDU (twice, two different driver versions)
- DISM and SFC commands
- Re-seated ram
- Updated BIOS
- Ran Memtest86; no errors