System halts briefly for a second or two before restarting, tends to happen when idle.
System halts briefly for a second or two before restarting, tends to happen when idle.
I need assistance, my computer is frequently failing. I've been working on fixing it for months but haven't found a solution. It suddenly freezes after just a moment, then the screen goes black and it restarts. The issue seems to occur more often when idle rather than under heavy use, especially if a game like Minecraft is running. Crashing happens only once or twice a week with a game, but multiple times daily otherwise. I ran virus scans and cleared startup items, but nothing was detected. Stress testing tools didn’t help either. At this point, replacing parts might be necessary to determine if the problem is hardware-related. I don’t have spare components or funds to test them, and no nearby friends have similar equipment. This situation is really frustrating.
Apply safe voltage and clock settings for the CPU and secure it. The issue should disappear, though the CPU may remain faulty.
I aim to verify for any damaged Windows files. Start by launching Command Prompt—search for cmd in Windows search and run it with admin privileges. Then execute sfc /scannow and hit enter. The system will automatically detect and repair corrupted or missing files. Once the scan finishes, it will indicate whether any issues were found and if they were resolved. Restart afterward to confirm everything is working properly.
Check the stock clock and voltage settings; since there were no issues previously, you can confirm those values are appropriate for your current operation.
You tried a voltage of 1.1V and reduced the clock speed to 2.7GHz instead of the standard 3GHz. It worked fine, so you might not need to lower it further unless you want to optimize performance or stability.
Check if the voltage and clock values are feasible for the chip. It might fail due to a faulty OC. Look at the event viewer after a crash to understand what happened.
WHEA-Logger with Event ID 18, showing three similar messages: "A fatal hardware error has occurred." Reported by component: Processor Core Error. Details reveal different Processor APIC IDs—15, 2, and 0. The other error comes from Microsoft-Windows-Kernel-Processor-Power, indicating a firmware issue on processor 1 in group 0. It suggests checking the manufacturer for updated firmware. I see enough of these to reach processor 15. It's unclear if such errors appearing more than 40 minutes post-crash is typical.
It's still referred to as overclocking within my group. Are you confident about your setup? On the hardware info page, you should notice a steady clock and a static 1.100 CPU Core Voltage SVI2 TFN. If the OC method didn't resolve the issue, consider increasing the voltage to 1.2. If you prefer not to adjust it or it keeps restarting, you'll likely need to replace the processor or initiate an RMA.
From HWinfo, the voltage mostly reads 1.1, though it wasn't constant—it fluctuated between 1.14 and 1.18, sometimes spiking up to 1.2. After overclocking, I used the BIOS to adjust the Tweaker settings, set the CPU frequency to 2700MHz, and manually adjusted the core voltage to 1.1000V. Then I changed the SOC voltage to 1.2. I'm now waiting to check if any crashes occurred.