System restarts occur during gameplay yet remain stable under stress tests.
System restarts occur during gameplay yet remain stable under stress tests.
Hi, I set up my PC eight months ago and have been facing this issue consistently. In games, a sudden black screen appears, followed by a reboot into Windows. The main hints are a critical error code (41 - Kernel-Power) in the Event Viewer and a serious hardware warning (193 - LiveKernelEvent) in the Reliability History. After using a driver verifier to force a BSOD, I collected four minidumps. Here are my system details:
- RAM: MSI PRO B650-s
- CPU: AMD Ryzen 5 7600X
- GPU: NVIDIA GeForce RTX 4070
- RAM Kit: Corsair 32GB DDR5 5600MT/s CL40 Vengeance RGB Grey EXPO
- Cooler: Endorfy Fera 5
- Storage: Apacer AS2280Q4X 2TB
- PSU: GIGABYTE P750GM
Additional info: The PC has been taken to two repair shops, both times no reboots occurred. I’ve already swapped out the PSU. My CPU temperature peaks at 96°C, but before any shutdown temps are typically around 85°C, suggesting it’s not overheating.
I’d appreciate any advice or suggestions.
If you need to check it, these references all point to HIDCLASS.sys—the HID driver. HID stands for Human Interface Device, which includes keyboards, mice, touchpads, and game controllers. The Driver Verifier is generally not helpful; it works only in very specific cases for capturing events, and for most issues it offers little value. Many websites, forums, and articles suggest using it, but they often lack proper guidance. It’s meant to help developers spot coding errors quickly, not to troubleshoot general problems. I can picture a scenario where an HID device causes the PC to crash, which would be rare. Could you highlight recent events from the past two to three days (excluding crashes), then right-click and save? Upload the .evtx file as you did with the dump files. If the logs are just Kernel-Power events, they probably won’t reveal much since those only record power states like holding the power button. We might find more useful information if we look for patterns in those specific events.
I regret the delayed reply; I completely overlooked your response. Here are some warnings and mistakes encountered during the incident. Error details: error1.evtx, error2.evtx, error3.evtx, error4.evtx, error5.evtx, warning1.evtx, warning2.evtx, warning3.evtx, warning4.evtx, error1_1033.MTA, error2_1033.MTA, error3_1033.MTA, error4_1033.MTA, error5_1033.MTA, warning1_1033.MTA, warning2_1033.MTA, warning3_1033.MTA, warning4_1033.MTA.
I don’t understand what MTA files are. I was trying to export everything from the past few days, not just specific events. There are errors from various sources, some not really important. It’s hard to grasp the situation without a complete event log. The warnings apply to device VID_03F0&PID_0B92, which is an HID device—possibly causing the BSODs. Checking the USB database shows HP as the vendor, but no matching product ID was found for the hardware part. Searching the ID returns one result, suggesting it’s a Kingston HyperX Cloud II. Since HP acquired HyperX years ago, that makes sense. Currently, the likely culprit seems to be the headset. If you remove it, do the BSODs stop? I also noticed some shutdowns, restarts, or freezes in the logs—those might not be connected to this issue.
Sorry, I didn't notice you ran Driver Verifier and the dump files don't resemble crashes initiated by driver verifier. Typically you encounter a specific crash message and see related activity in logs, which isn't the case here. I'm going to withdraw all statements about that situation. Driver verifier crashes are generally not helpful. There seems to be no cause for restarts. Power appears to be the likely culprit. If I say power, it could be related to the PSU, power cable, power strip, or inconsistent wall power.