Question Restart-Loop even without SSD/Bootable USB

[glennlantern123]

A friend of mine got his PC down to my crib to see why his computer is restart-looping, I've tried every possible way to fix it like removing ram both ram and CMOS battery, removing ram one by one to see if one or the other is broken, also tried booting from Windows 10 USB with the SSD and also without the SSD. Without the SSD when I boot from the USB, it triggers the restart loop after the loading circle of Windows 10. With the SSD it triggers also at the loading circle of Windows 10 or 5 seconds after the "Automatic Repair..."

in addition: even without the SSD and Bootable USB, the restart loop is still present. Yet-I can still go to BIOS.

quick specs;
ryzen 3 3200G (using integrated gpu)
16gb ram
120 ssd
500gb hdd

Is the motherboard broken?

 

[Lutfij]

You forgot to mention the make and model of the PSU and it's age. Are you able to get into BIOS and remain there indefinitely? While here, can you check and see what your current BIOS version is?

 

[glennlantern123]

You forgot to mention the make and model of the PSU and it's age. Are you able to get into BIOS and remain there indefinitely? While here, can you check and see what your current BIOS version is?

Hello! Yes, I forgot to mention his PSU. It is a 500W Cougar STE Power Supply bought from 2020. It can remain in the BIOS (no restart or power off).

In terms of BIOS Version, it is (7C51v14), I'll try to update it to the new version which was released in 2022.

I'll be trying a different PSU first, I think this PSU is faulty. Thank you for your response.

 

[glennlantern123]

Update: As soon as I've changed the PSU to my extra one that is laying around and also tested it ON MY PC's PSU. The problem is still the same, Restart-Loop on its own Windows 10 (SSD) Restart Loop on Bootable USB (Windows 10) also tried (Windows 7) same result, triggers after the loading circle. but when there is no Bootable SSD/USB it just goes to BIOS and stays there.

 

[Bob.B]

Update: As soon as I've changed the PSU to my extra one that is laying around and also tested it ON MY PC's PSU. The problem is still the same, Restart-Loop on its own Windows 10 (SSD) Restart Loop on Bootable USB (Windows 10) also tried (Windows 7) same result, triggers after the loading circle. but when there is no Bootable SSD/USB it just goes to BIOS and stays there.

Wag.
Put a copy of memtest86 on a flash stick.
See if it will boot.

 

[glennlantern123]

Wag.
Put a copy of memtest86 on a flash stick.
See if it will boot.

Thank you I will be trying it out.

 

[glennlantern123]

Wag.
Put a copy of memtest86 on a flash stick.
See if it will boot.

Update: Got it to boot on memtest86 and even tested it out for a while, no restart-nor shutdown.

Can an overheating CPU cause this? I mean if it is the cause, it is not gonna be restart loop right? It should be shutting down if overheating is the cause.

 

[Bob.B]

Update: Got it to boot on memtest86 and even tested it out for a while, no restart-nor shutdown.

Can an overheating CPU cause this? I mean if it is the cause, it is not gonna be restart loop right? It should be shutting down if overheating is the cause.

A fair portion of the machine has to function for memtest to boot and run.

Boot it up and let it run for a while.....no errors allowed.

 

[glennlantern123]

A fair portion of the machine has to function for memtest to boot and run.

Boot it up and let it run for a while.....no errors allowed.

Understood, will try again in a while. Gave it a break.

 

[glennlantern123]

A fair portion of the machine has to function for memtest to boot and run.

Boot it up and let it run for a while.....no errors allowed.

So I left the computer to test after I got back from work the Computer is on and there is no display. I had to restart/shutdown the computer to get it to display again. I didn't really look out on the tests as I was at work.. but I'll try to wait so I can see the test finish.

 

[glennlantern123]

Memtetst86 found no Errors: 0, tested out a new DDR4 from the shop, tested out a different PSU, the only thing I haven't tested is the Motherboard. I've also replaced new thermal place.

So I think the Motherboard is faulty (?)

 

[glennlantern123]

I also tested out the RAMs that is in the faulty PC to a different PC, working fine.

 

[faalin]

If getting memory errors on the board, but moving the ram to another board and not getting errors means 1 of 2 things. Ether the board is bad or the CPU is bad as the memory controller resides on the CPU.


If you can try an swap out the cpu to anything else and see if you still get memory errors. If your still getting error i would point my finger at the board, if they go away then i would look at bent pins or re seating the cpu to see if the errors come back.

 

[glennlantern123]

If getting memory errors on the board, but moving the ram to another board and not getting errors means 1 of 2 things. Ether the board is bad or the CPU is bad as the memory controller resides on the CPU.


If you can try an swap out the cpu to anything else and see if you still get memory errors. If your still getting error i would point my finger at the board, if they go away then i would look at bent pins or re seating the cpu to see if the errors come back.

I found an extra CPU lying around at my friend's house, we will swap it out. Because I've already tried reseating the CPU, before I replaced the old thermal paste with a new one. If swapping CPU still won't work, we'll be getting a new board.

Thank you, I'll update if we have done it.

 

[glennlantern123]

re: the CPU was working on a different mobo before we bought one.

Update: So I bought a surplus motherboard that is working (tested on the shop before buying) and as soon as I transferred everything on the new motherboard (except HDD, SSD) I now face a new problem where it doesn't display (but the Fans and LEDs turns on etc etc) I already tried cleaning the RAM, reseating CPU, new thermal paste, no putting front pannel wires and turning it on using screw driver... this is hell of a PC of him. Haha!