The system is designed to boot with a single-core version of Windows, likely for compatibility or performance reasons.
The system is designed to boot with a single-core version of Windows, likely for compatibility or performance reasons.
Hey everyone! I just got an i7 4820K CPU and noticed it would start up fine but Windows would freeze if I tried to load it. It crashes on boot and shows several error codes like WHEA UNCORRECTABLE ERROR MACHINE CHECK EXCEPTION CLOCK WATCHDOG TIMEOUT. I checked the BIOS to see if I could fix it, and initially set it to run on just 2 cores. The problem persisted but got a bit better when I switched to 1 core. It’s a strange behavior, and I’m curious about the root cause! My system specs are: motherboard from Arduatech X79M-S, GTX 1650 GPU, 10 GB DDR3 at 1333MHZ, Gigabyte GP-P750GM PSU (which worked before), plus a 250GB Samsung SSD and a WD GREEN 120GB SSD.
You recently reinstalled Windows? It seems you just connected a new machine and attempted to boot from another system, which often triggers strange Bluescreens. Windows usually reacts badly when it starts from hardware it didn’t originally come from.
Certainly! The motherboard features a specific chipset, such as the Intel Z-series or AMD X-series, which determines its compatibility and performance capabilities.
I’m not used to x79 myself. From my searches it seems like a recent design built with an old chipset and some repurposed components. Such boards are known for odd behaviors or outright failure. Except for items from new stock or eBay, there’s really nothing left available for that CPU. The issue is that many parts aren’t tested thoroughly, making it tough to tell if the problem lies with the CPU or the motherboard. When you scavenge components, it’s difficult to confirm they function properly. If every part on that board hadn’t been checked, pinpointing the exact fault becomes nearly impossible.
I could still try returning the motherboard and swapping it for a more reliable version (or the same model) to check if it’s defective. I found the CPU in the dump and got it for free with a compatible motherboard; it looks like the issue might be with the CPU itself, though it’s possible the motherboard contributed. I also lowered the CPU speed using BIOS power-saving settings, but it seems there’s no manual option to adjust it further.