PC wont turn off after bios update

Beardineo

Beardineo

Beardineo

Associate
Joined
3 Apr 2021
Posts
8
I have a frustrating one. I have a gigabyte x570 elite motherboard with a 3700x cpu (wanting to upgrade to a 5700x3D), and I appear stuck on bios version F11 (which means I can't get newer CPU), which is from 2019 (2024 F40 is available, so I am multiple versions behind).

If I install ANY higher bios version, the pc fails to shutdown or reboot from windows 10 (latest updates installed). If goes through the turn off process, looks like it's got there with screen turning black.... but then just sits there with fans spinning. I revert back to baseline F11 version and everything is fine.

I've tried things like fast boot off, ErP disabled, different power plan settings, latest chipset drivers and nothing works, I'm really stumped. Gigabyte support were less than helpful and said they couldn't reproduce so it was my issue without offering anything to try. Anyone else had this and has any ideas to help me upgrade? I'm not sure if it's a bios setting or something in windows, since both work on the baseline.
 
First thing: if you force a shutdown when in the UEFI setup (hold the power button until it dies), does it turn off completely?

If you do a soft shutdown from the OS and it only stays on this way, try to remove all of your peripherals and see if it will power off that way. Total bare bones - even disconnect the keyboard and mouse. Shutdown with a single press of the power button when in Windows.

Failing that, start looking at your BIOS settings around power and standby states. Is everything on auto?
 
Thank you for the suggestions.

Yes I can force a shutdown or restart with the buttons, that's the only way I can reboot or switch off currently.

I removed everything plugged in, network cable and anything wireless, and it still occurs.

Everything is set to defaults in the bios, there are not too many power options with gigabyte to be honest.

Considering it only goes wrong when I do the bios, it leads me to think it's a bios option not windows, unless there's an os setting that's doing it than was harmless with F11.

Anything else you can suggest?
 
Disable CSM and then use UEFI shell to shutdown with reset -s that should be a good test.

Have you also tried a different OS? You can use a live DVD/ISO for Ubuntu, as an example. Trying safe mode is also another idea. You need to isolate whether this is related to the BIOS version in isolation or if there is just a compatibility issue once it's updated. If it's the latter, you need to find what is causing the incompatibility and I'm leaning towards that if Gigabyte stated that they couldn't repro.
 
So I disabled CSM. When entering the bios now none of the drives are listed or available in the boot sequence to be selected (they appear under Sata/nvme however so I know they are still connected). it's also a lot more sluggish to move a around with the mouse in the bios. Is any of this expected?
 
Last edited:
Beardineo said:
So I disabled CSM. When entering the bios now none of the drives are listed or available in the boot sequence to be selected (they appear under Sata/nvme however so I know they are still connected). it's also a lot more sluggish to move a around with the mouse in the bios. Is any of this expected?
Click to expand...

Yes, it's using the UEFI driver for graphics. Your partitions are MBR and won't work with CSM disabled. This is to identify what's causing the issue - it's not permanent. Enable CSM support once again and your drives will come back.

Press Ctrl+Alt+F6 (or F5, one of them) to lower the UEFI resolution. It will run much better.
 
Last edited:
Thank you for your patience - I have tried a few things

  • I moved Windows to GPT and am now running in UEFI mode instead of legacy bios - this made no difference with CSM on or off. (Fast Boot in the Bios is off)
  • I unplugged literally everything other than the monitor over DP, pressed the power button once, shutdown was initiated, but it didn't completely switch off (same as before)
  • I loaded up windows boot media -> and from the installation menu I pressed shutdown. This worked and it switched off properly. This suggests to me its not the bios itself and something in my windows installation that is causing it.

Couple of things I have noticed that might hint to something. When I am shutting down, all the RGB mobo lights, RAM RGB and case fan lights switch off, except for the wraith prism RGB. (all the fans still spin however). I am on the latest wraith prism version and I updated RGB Fusion 2.0 to latest version, but same issues.
When i inevitably have to press the case restart button when its clear it hasn't turned off, on booting into windows, there is no sign of an unsuccessful shutdown, so i am pretty sure its exiting windows and just failing at the final hurdle.

Is there anything else you can suggest from the info above? any event logs to check etc.
 
I just tried a fresh install of windows 10 on a spare drive and its shutting down properly - so its clear its my windows or some software I have installed over time that is the culprit, but weirdly only affected by bios versions over F11.

Anything i can do to salvage the situation - I've had my machine for sometime and i really don't want to start over if i cant be helped :(
 
Thank you for the suggestions. Fast start up is off, and getting into safe mode when you can't shutdown is harder than you would think.

I think I will concede and just resort to a full reinstall and move on, it will probably take less time (and is probably overdue anyway)
 
Beardineo said:
Thank you for the suggestions. Fast start up is off, and getting into safe mode when you can't shutdown is harder than you would think.

I think I will concede and just resort to a full reinstall and move on, it will probably take less time (and is probably overdue anyway)
Click to expand...
Did you manage to update the bios with full reinstall?
 
So updating to bios was never the issue and I could always do that fine, the problem was (my) windows didn't play ball. I bit the bullet and a few days later a fresh install sorted it
 
You must log in or register to reply here.
Back
Top Bottom