Question Random half-shutdown New Build PC

[jhal86]

- AMD Ryzen 7 7700X CPU 8 Core / 16 Thread - Max Boost
- Gigabyte B650 GAMING X AX ATX Motherboard For AMD Ryzen 7000 Series CPUs - AMD B650 Chipset
- G.SKILL Flare X5 32GB DDR5 Desktop RAM Kit 2x 16GB - 5600MT/s - CL36 - 1.2V - 36-36-36-89
- Cooler Master MWE Gold 850W Power Supply 80 Plus Gold
- Cooler Master MasterLiquid Lite ML240L V2 240mm AiO Water Cooling with aRGB Fans
- Gigabyte NVIDIA GeForce RTX 4070 Gaming OC 12GB GDDR6X

Hi All. I built a new PC for the first time 2 months ago. Before this, I had installed, swapped, and added parts, so I was not a complete noob.

After the installation, all was fine, except maybe once a week the build would randomly half shut down. What I mean by this, is the PC would be none non-responsive, the screens turn off in standby mode, the keyboard and mouse no response, the power button non-responsive, but the AIO and other fans still spin constantly with AIO fan lights on, the motherboard shows a constant red CPU light.
This can only be remedied by flicking off the PSU switch for 5 seconds for it to power off fully, on again, and then the power button to boot back on. It's also possible not to wait for five seconds, switching the PSU switch off and on it will boot back up (this doesn't feel right to me).

Over these last 2 months, the half shutdown is happening more regularly, a lot more since I've been playing Starfield (happens with other games). There is no pattern, I can play for 20 mins, a whole day, 1 hour, 3 hour, or 47 mins, it has no prejudice. I've monitored the temps and my build will never go over 85c, the problem will happen no matter what the temp is. It's only happened once while using desktop apps but 99% of the time it will be while in a game. I've left Furmark running for an hour, with no half reboot. I've read a few issues with this board but you could type: " any motherboard model + issue" and there will be something.

BIOS drivers up to date
GPU Bios and drivers up to date
Plugged in the monitor into integrated graphics during half shutdown - no response (also disabled IG)
Secured all internal components
Removed and resecured AIO - not too tight, not too loose.
Tried XMP on and off
User benchmarks benchmark doesn't pick up my GPU (Could this be related?)

I've searched forums and the closest I've found is this, but my RAM seems fine. Does anybody know the issue or have any suggestions?

Thanks in advance.

 

[Lutfij]

Welcome to the forums, newcomer!

You mentioned swapping parts, did you migrate the OS drive from your older build onto the new? If so, you should reinstall the OS.

Did you clear the CMOS after verifying that the BIOS was flashed to the latest version. BIOS don't have drivers, it's a firmware. As for your AIO, try just having the block on the processor without much force while the PC is laying flat/on it's side.

 

[jhal86]

Thanks for your quick response Lutfij.

My bad, I meant Bios firmware, and yes I can verify it's the latest version. I have just loosed the AIO block a wee bit more; I will see if this helps.

I am using my old OS drive and reinstall was done.

 

[jhal86]

Yesterday since loosening the AIO and leaving a game running most of the day, there was no half-shutdown. However, this morning after a few hours the half-shutdown happened again.

Next, I will try using one only RAM stick; 16GB.

 

[jhal86]

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?

 

[SkyNetRising]

Does anybody have any other ideas?

I'd suspect PSU.
Transient power spikes may trigger PSU protections kicking in.
Try reducing GPU power target in MSI afterburner.

Also check CPU and GPU temperatures.

 

[pete_101]

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've got the mATX version of your board, so I assume it shares most of the same issues. I had all sorts of RAM related issues early on as I had XMP and not EXPO, but I found some BIOS versions were better than others. I then replaced the RAM and that fixed my issues, but I see you also have Flare X5, and I don't think it comes in XMP, only EXPO?

Anyway, I flashed the BIOS many times to find one that worked stable, you might have to as well.

 

[jhal86]

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.