cancel
Showing results for 
Search instead for 
Did you mean: 

PC turns off abruptly at startup or reboot

trumpy81
Level 7

GDay All,

I have an Asus ROG Strix X570-E Gaming board with 5013 BIOS and AMD R9 3900X running Win10/11 Pro that is exhibiting strange behaviour.

When I start the PC from cold all is fine until I get to the Windows Boot Menu (Dual Boot) and select the OS to boot into. Most of the time all is well, but occasionally, Windows will start to load and then the PC shuts down with a pop from the speakers, no power LED etc. It then restarts on it's own and most of the time it will boot into Windows as per normal.

Also, if I reboot from Windows, it shuts down as per normal but then, towards the end, it powers off with a pop from my speakers, no power LED etc. before it restarts itself and boots as per normal.

It does not matter if I boot into Windows 10 or Windows 11.

Anyone have any idea what may be causing this?

262 Views
4 REPLIES 4

TumKo
Level 8

You need to use, ROG STRIX X570-E GAMING BIOS 4021 AGESA V2 PI 1.2.0.3 Patch C. If your processor 3000 series. If your processor 5000 series use the latest

Thanks for the reply Tumko.

At the time I posted I was on BIOS 5020 but I have since updated to the latest 5021.

I suspect that my graphic card drivers for my RX 5700 XT were to blame for the issue, since my computer started freezing up and then the graphics card drivers would report an error and the PC would unfreeze at that point.

Of course it may have been a combination of the BIOS and the graphics drivers, but both have been updated now.

The PC has been stable for the last week or so, with no sudden power offs, but I will keep monitoring it and see if the problem returns.

Again, thanks for the reply and the info, I will certainly keep it in mind should I have any more issues.

 

 

 

I also have an asus rog 5700 xt and there are no such problems but I have a 5950x

Yeah I think it was a combination of the graphics drivers and the BIOS version I was using or it may have been something else entirely.

In any case, it seems to be fixed now after I updated the BIOS and the graphics card drivers.