Machine halts and reboots following a repeated audio cycle yet remains unaffected by the crash screen.
Machine halts and reboots following a repeated audio cycle yet remains unaffected by the crash screen.
Hello, I just reinstalled a fresh Windows system, but faced my first issue right away—my computer would freeze in a split second and a looping sound would play. Eventually it would lock completely during a game, repeat the loop, then restart. There was no overheating, and my BIOS settings were up to date (version 3 years ago). I had previously overclocked the CPU before, pushing the LLC frequency up to around 6, hoping for stability, but my processor was in poor condition and needed at least 4700MHz. It was running under 1.35V. Later I noticed the default BIOS was reporting a voltage of 1.357V, which was odd. I also remembered an XMP profile enabled, possibly contributing to the problem. Even though it was set to 4600MHz, that seemed risky for stability. Still, my motherboard was handling such high voltages on its own. I set XMP as it was installed three years ago, thinking it only affected RAM. After some testing with Intel diagnostics, MemTest, and the diagnostic tool, everything looked clean—no hardware damage detected. However, I suspect the issue might have been caused by the XMP profile. It’s strange how a motherboard could behave like this.
I tried overclocking again, pushing LLC to 6 and 1.35V, hoping for better performance in games. But even then, stability remained an issue. I wanted to play Resident Evil 4 Remake, but it suffered from performance drops and my CPU was maxed out. Eventually, I reached a point where the PC would freeze completely, requiring a restart.
Despite these problems, I really enjoyed gaming again—especially with burnout—and it felt great not in years. However, I still faced sound loops and freezing episodes. Right now, my CPU is running at a maximum of 1.243V under load on the stock 4.3GHz processor. I’ve attached a minidump file from Windows (no BSOD), but I’m unsure if it contains private data.
I saw a link to a code snippet about a bug (0x00000133) and noted it might indicate a faulty CPU. I considered replacing it, though it seemed like a good deal at the time—only $50. It’s possible someone might be interested in getting it for an older system. I’m thinking of buying an I3 7100 for just a penny, even though it seems unbelievable. Why would anyone sell it for such a low price if it works? The auction account looks legitimate.
Is there any chance the CPU is faulty?
I’d begin by running stress tests on both CPU and GPU using tools like OCCT, Cinebench, and CPU-Z. I usually start with a simple CPU-Z check to confirm stability and acceptable temperatures. Then I run Cinebench for at least 20 seconds to ensure the system remains responsive without crashes—either a full freeze or reboot. Next, I test the GPU with Furmark and some random games to assess its performance. If any issues arise during these tests, I examine CPU usage spikes with Processor Lasso to detect voltage problems. Should the system still fail under load, I might reseat the processor as a final verification. All these steps help confirm whether my hardware is still reliable.