F5F Stay Refreshed Hardware Desktop The new PC switches on and off, yet the BIOS remains functional.

The new PC switches on and off, yet the BIOS remains functional.

The new PC switches on and off, yet the BIOS remains functional.

C
COLIN20052012
Posting Freak
Find
857
10-19-2018, 12:33 PM
#1
This machine was assembled on April 28 and functioned properly at first, installing Windows, updates, and drivers without trouble. After that, it operated smoothly until May 6 when random shutdowns began shortly after launching into Windows. The issue worsened over time, lasting only in safe mode. I restored the system by wiping the SSD and performing a fresh installation, which eventually succeeded. However, the PC would shut down repeatedly, sometimes displaying the Gigabyte logo before exiting or entering Windows installation via USB.

I suspected file corruption since the same USB had been used on three other systems. I created a bootable image using Microsoft’s official tool and completed another clean install, but the problem persisted. Eventually, it started shutting down earlier, showing the Gigabyte brand and attempting to load before failing. Trying a live Linux distribution also failed to boot Windows through USB.

Occasionally, the system would enter BIOS and remain active, with stable CPU temperatures around 40°C. Specifics include:

- Ryzen 5 5600G processor
- Stock cooler included
- Gigabyte B450M DS3H V2 BIOS (latest version F63a)
- 8GB 3200MHz DDR4 RAM
- 240GB A400 SSD
- 2TB WD Blue storage
- EVGA BR 450W 80+ Bronze power supply

I tested various Windows versions, booted into live Linux, reset RAM, swapped CPU, changed motherboard, used different drives, and even removed front panel cables. I also disabled the C state, reset CMOS, replaced the PSU, and tried a different CPU model.

I disabled XMP settings, swapped the CPU to a Ryzen 5 2600 + GT 1030 (boot behavior unchanged), pulled the motherboard out of its case, and attempted a BIOS flash, which caused shutdowns. I edited the notes on May 11, 2022, under Reiss’ authorship.
Reply
Reply
C
COLIN20052012
10-19-2018, 12:33 PM #1

This machine was assembled on April 28 and functioned properly at first, installing Windows, updates, and drivers without trouble. After that, it operated smoothly until May 6 when random shutdowns began shortly after launching into Windows. The issue worsened over time, lasting only in safe mode. I restored the system by wiping the SSD and performing a fresh installation, which eventually succeeded. However, the PC would shut down repeatedly, sometimes displaying the Gigabyte logo before exiting or entering Windows installation via USB.

I suspected file corruption since the same USB had been used on three other systems. I created a bootable image using Microsoft’s official tool and completed another clean install, but the problem persisted. Eventually, it started shutting down earlier, showing the Gigabyte brand and attempting to load before failing. Trying a live Linux distribution also failed to boot Windows through USB.

Occasionally, the system would enter BIOS and remain active, with stable CPU temperatures around 40°C. Specifics include:

- Ryzen 5 5600G processor
- Stock cooler included
- Gigabyte B450M DS3H V2 BIOS (latest version F63a)
- 8GB 3200MHz DDR4 RAM
- 240GB A400 SSD
- 2TB WD Blue storage
- EVGA BR 450W 80+ Bronze power supply

I tested various Windows versions, booted into live Linux, reset RAM, swapped CPU, changed motherboard, used different drives, and even removed front panel cables. I also disabled the C state, reset CMOS, replaced the PSU, and tried a different CPU model.

I disabled XMP settings, swapped the CPU to a Ryzen 5 2600 + GT 1030 (boot behavior unchanged), pulled the motherboard out of its case, and attempted a BIOS flash, which caused shutdowns. I edited the notes on May 11, 2022, under Reiss’ authorship.

Reply
Reply
K
kitkat7650
Member
Find
211
10-19-2018, 05:07 PM
#2
For documentation purposes, I’ll share the resolution here. Testing the CPU on another motherboard produced consistent results. It appears the CPU failed, causing damage to the MBO as well. During closer examination, one of its lines was found faulty and now overheats, worsening the loop boot problem. The fix involves swapping out both the motherboard and the CPU. I’ve attached a photo highlighting the affected area.
Reply
Reply
K
kitkat7650
10-19-2018, 05:07 PM #2

For documentation purposes, I’ll share the resolution here. Testing the CPU on another motherboard produced consistent results. It appears the CPU failed, causing damage to the MBO as well. During closer examination, one of its lines was found faulty and now overheats, worsening the loop boot problem. The fix involves swapping out both the motherboard and the CPU. I’ve attached a photo highlighting the affected area.

Reply
Reply