My PC keeps crashing ?
My PC keeps crashing ?
I've been searching for a week without success. I just set up a new system:
Motherboard: Arorus Elite AX Z690 with bios f27
CPU: Intel 13600k
Cooler: Arctic liquid freezer ii 280
GPU: RX 6900XT
RAM: 32 GB Patriot DDR5 5600
PSU: 750 Watt MSI MPG A750GF Modular 80+ Gold
No overclocking or undervolting has been done. All default XMP and resizable bar settings are active.
In Event Viewer I found:
"Event 6008 - The previous system shutdown at 8:13:48 PM on 10/25/2023 was unexpected"
I've uploaded my .DMP files and hope someone can help identify the issue.
Have you visited the product page for your motherboard, navigated to the Support section, and updated the drivers for audio, chipset, LAN, and WLAN/Bluetooth? If not, you should. What Windows version are you using? Which drive is hosting it, and where is the connection made? Which precise memory kit model do you have, and in which slots—number one being nearest to the CPU socket, number four closest to the motherboard edge—are they installed?
I have saved all the drivers from the motherboard site except for WLAN, Bluetooth and Intel graphics. I downloaded the newer versions from the Intel site. The specific RAM model is Patriot Viper VENOM DIMM Kit 32GB, DDR5-5600 in slots 2 and 4. My operating system version is 22H2 (0S Build 22621.2428) installed on the C drive of a WD Black SN770 WDS100T3X0E 4.0 x4 (NVMe) hard drive, with a 1 TB SSD in the CPU M.2 slot.
Additionally, in the "View Reliability history I see" section, there are frequent hardware issues (LiveKernelEvent a1000001a and 117, 1a8, 1b8). There are also several Kernel Processor Power warnings (Processor 19 in group 0 is limited by system firmware. It has been in this reduced performance state for 71 seconds since the last report). Information (not warning or error): HAL 16 (The iommu fault reporting has been initialized.) Please note, my PC always shuts down when I play CS2. I only play CS2 and League of Legends; I also run ASTR for two users, with the second user just browsing. UPDATE: here’s what I have tried so far without success—reinstalled Windows, installed all chipset drivers, reinstalled graphics drivers via DDU, and updated BIOS.
No, I mean Windows 10 or 11, and did you choose the CORRECT Windows version (10 or 11) when you downloaded the drivers from the motherboard product page, because they are not always inter-compatible. In fact, a LOT of them are either Windows 10 or Windows 11, but not both.
IDK, because I've never used it, but I have at least SOME suspicion that ASTER might be relevant here as well. Multi-seat or similar applications can sometimes create problems in gaming scenarios. But, that's kind of just a guess. You might want to do a clean install, NOT install ASTER, and see if you still have the same issue. I think it's at least possible it might be reserving some hardware resources for the second user that are needed for the 1st user, but again, totally not any kind of certain about that.
@Colif
might be able to run your dump and see what he comes up with.
Report
- click run as fiddle to read (it's mostly for me)
File: 102223-11859-01.dmp (Oct 23 2023 - 00:20:05)
BugCheck: [
CLOCK_WATCHDOG_TIMEOUT (101)
]
Likely cause: Unknown_Image (Process: System)
Status: 0 Day(s), 0 Hour(s), 00 Min(s), 28 Sec(s)
File: 102223-10796-01.dmp (Oct 23 2023 - 00:17:07)
BugCheck: [
CLOCK_WATCHDOG_TIMEOUT (101)
]
Likely cause: Unknown_Image (Process: OLEDDisplaySer)
Status: 0 Day(s), 0 Hour(s), 00 Min(s), 31 Sec(s)
File: 102223-10250-01.dmp (Oct 23 2023 - 00:17:51)
BugCheck: [
CLOCK_WATCHDOG_TIMEOUT (101)
]
Likely cause: Unknown_Image (Process: svchost.exe)
Status: 0 Day(s), 0 Hour(s), 00 Min(s), 25 Sec(s)
From memory, clock watchdog timeouts are hardware.
@ubuysa
may find more details than I do.
The process referenced was the victim, not the cause.
I checked my system performance and saw extremely high temperatures at 100 degrees. After taking off the cooler, I noticed the thermal paste was only applied to the lower half of the component. I reapplied it, and the system seems to be functioning properly now. It might have been the stress from CS-GO before the system was under heavy load that caused issues. The system didn’t crash during the benchmarks I ran (Cinnabench 2024), though it did shut down randomly during games, especially after the first or second game. Thanks for your time and assistance—I hope everything is working correctly now.
Did you verify that the plastic protective film was still attached to the base of the water block? Even if it was, most coolers include one and often have the thermal interface material already applied.
It might look better now, but I strongly suggest you thoroughly clean all the existing TIM from both the CPU heat spreader and the bottom of the water block using 91% isopropyl alcohol and a lint-free cloth or paper coffee filter. After that, apply fresh paste to the top of the CPU heat spreader. Use about a third the size of a #2 pencil eraser as a guideline for the amount needed.
For better results, opt for a quality paste such as Thermal Grizzly Kryonaut or Arctic MX6, but don’t overdo it—just enough is enough.
Great job figuring this out, no puns intended. LOL.
Update: the issue remains unresolved. Here is another DMP file for reference:
https://www.dropbox.com/t/In0p1wGvnFqmnXnf
Thank you very much. I have already completed all these steps and cleared everything. The thermal readings in the game stay below 62 degrees, which is excellent. However, after finishing a game session, my PC shut down again. I’m curious if this is related to CS2. I’ve used DDU and reinstalled the graphics driver recently. Some people recommend changing the launch options to (-vulkan), though I’m unsure if that would help since I have an AMD GPU. Others suggest using the -dx11 launch command. I’ve uploaded the new DMP file.
How is it shutting down? Are you playing and it just disappears, starts over, or does it freeze and then stop responding? What exactly happens or doesn’t happen? If it simply cuts power and turns off without any freeze, error, or other issues, that’s likely a problem with the PSU or motherboard.