Question Random half-shutdown New Build PC
Question Random half-shutdown New Build PC
I recently assembled a new PC two months ago. Prior to this, I had installed, replaced, and added various components, so I wasn’t entirely a beginner. After setup, everything seemed normal except occasionally, once a week, the system would unexpectedly shut down halfway. This meant the PC remained unresponsive—screens would turn off in standby, keyboard and mouse wouldn’t react, power button didn’t work, yet fans and the AIO continued spinning with lights on, and the CPU display stayed constantly red. Only fixing this required turning off the PSU switch for five seconds, then restarting, or switching it off and on again. It doesn’t seem to matter how long I wait. Over the past two months, these random shutdowns have increased, especially while playing Starfield (and other games). The issue appears unrelated to temperature, staying under 85°C even during long gaming sessions. I’ve tested Furmark for an hour without any half-reboots. Some forum discussions mention similar problems, but my RAM looks normal. Could you help identify the problem or suggest solutions? Thanks in advance.
Welcome to the forums, newcomer! Have you replaced any components and moved the OS drive from your previous setup to the current one? If yes, consider reinstalling the operating system. After flashing the BIOS to the latest version, did you reset the CMOS? Remember, BIOS doesn't require drivers—it's firmware. For your AIO, try placing the block on the processor gently while the PC is resting or lying flat.
Thank you for your prompt reply Lutfij.
Correct, I intended to refer to Bios firmware and confirmed it's the most recent version.
I just slightly adjusted the AIO block; I'll check if it improves things.
I'm using my old OS drive and the reinstallation was completed.
Yesterday when we adjusted the AIO and kept the game running for most of the day, there was no partial shutdown. But this morning, after some time, the partial shutdown occurred again.
So I've been using 1x ram stick (16gb) for the past 2 weeks and the system has crashed 3 times. Not sure how this relates as I should be allowed to have 32gb's, I'm starting to think that it could be the motherboard, so I'll do a warranty claim and replace it; hopefully this is the solution.
Does anybody have any other ideas?
I assume the mATX version of your board matches most of the same problems. Initially, I faced various RAM issues because I used XMP instead of EXPO, but switching to some BIOS versions helped. After replacing the RAM, my problems improved. However, you also have a Flare X5 model, which seems to only support EXPO and not XMP? It might be worth trying different BIOS settings as well.
Hi all,
To give you an update: I took the motherboard back to the retailer who on inspection said that there was a pin missing in the CPU holder. They sent it to their own repair people who advised that it needed to go back to Gigabtye in Melbourne. After about 1.5 months of waiting, I finally got the motherboard back with the missing pin repaired. No problems happened for the first week, I bench-tested it with high usage CPU games such as Scum, Stellaris, and Starfield but after this, the same issue happened and kept happening more frequently.
Out of frustration, due to the CPU light on the motherboard going red when the "Half reboot" happens, I went into the BIOS and started looking around the Advanced CPU settings, and changed things one at a time. At first, I disabled "Slow slew rate" which did absolutely nothing, and then next on the list I disabled "CSM Support".
Since I did this on the 17th of March my system hasn't half rebooted since, even when playing the same games. When I looked up what CSM Support does, I saw that it has something to do with legacy operating systems, MBR partitions, and the contemporary UEFI environment. It has nothing to do with the CPU as far as I'm aware so I am not sure if this is just a fluke or just the longest I haven't experienced the "half reboot" in almost 3 weeks.
Could anybody please shed some light on this? I'm stoked that it seems to have fixed the issue and hopefully help anybody else in the future.