BIOS update on my ASUS ROG Strix B550-F Gaming has gone a bit pear.....

Soldato
Joined
2 Jan 2004
Posts
7,794
Location
Chesterfield
Basically I’ve been having an intermittent problem with connecting to some online games with some friends and so I thought I should check and update the BIOS version for the motherboard in case there were any fixes – I managed to do this via the “USB BIOS Flashback Tool” and while the update seems to have worked I’m having difficulty booting into Windows again – I get an error message saying “CPU Fan Error”

I’ve done a bit of Googling and it appears as though the BIOS thinks the CPU fan isn’t connected/running - this does make sense because I've got an iCue H100i AIO cooler! (so I assume there isn't a fan speed to record?) - sorry if this is a bit vague but I bought the motherboard, CPU and cooler already assembled so had no involvement with the original setup!

I’ve tried going into the “Q-Fan” settings and followed various advice to try and get the BIOS to ignore this but then when I save and exit, it just boots me back into the BIOS again (albeit this time, without the “CPU Fan Error” message!?!?)

Can anyone give me a bit of guidance as to how to get my PC booting back into Windows again??

Thanks for any help....
 
Flashing the bios will reset your settings. So it is possible you'll need to set things up again. I have mine all noted down, so everytime I do a BIOS update, I just plumb them back in.

Have you checked that the cables are still seated correctly in CPU_FAN and the pump is in AIO_PUMP headers?

You mention Q-Fan, did you tell it to perform a test to discover the RPMs?

I have an AIO on the same board, I'll go check my settings for you see if I can spot anything obvious.
 
I'm pretty sure the H100i would still have a cable connected to the CPU fan header on the board. I thought Q-Fan was only for changing fan profile? I could be wrong.

Have you checked your boot priority is set right and the CPU fan error isn't just a red herring?
 
So under Monitor within the BIOS, does it report rpm for Cpu fan speed and AIO pump speed? As I say you could go into Q-Fan configuration and then select Q-Fan tuning at the top.

I have my cpu fan control and aio pump control both set to "auto". AIO pump fan Q-Fan source is set to "Cpu".
 
Thanks for the replies, it turns out there was a setting that needed checking - "launch CSM" as the m.2 drive wasn't listed as a bookable drive!

There is a cable from the AIO to the motherboard but nothing plugged into the CPU fan header - in the end I plugged the rear exhaust fan in, checked the boot drive bit above and its booted into windows! (So I assume I can plug the rear fan back in where it was and just set the BIOS to ignore the CPU fan speed and it should work?)
 
CSM? Really? Is your boot drive an old Windows 7 drive or something? (formatted MBR?)

The only way I can get my PC to boot into Windows is by enabling CSM - otherwise it just loops back to the BIOS!?!?!

I can't seem to get the m.2 drive to show in the boot options at all - and yet if the CSM option is enabled, it boots into Windows just fine??? I did find a post on reddit saying that it's something to do with the drive not having a signed UEFI driver and that I need to somehow convert my drive to GPT from MBR - this all sounds waaay over my head though!
 
The only way I can get my PC to boot into Windows is by enabling CSM - otherwise it just loops back to the BIOS!?!?!

I can't seem to get the m.2 drive to show in the boot options at all - and yet if the CSM option is enabled, it boots into Windows just fine??? I did find a post on reddit saying that it's something to do with the drive not having a signed UEFI driver and that I need to somehow convert my drive to GPT from MBR - this all sounds waaay over my head though!

My understanding is that this usually happens if the drive was originally formatted by an old version of Windows, or as an additional disk in a pre-existing install. It's unusual that a brand new boot drive with a fresh install of Windows 10/11 would be unbootable without CSM.
 
I know it's the most painful route but sometimes the fastest way to fix issues like this is to drop in a brand new with a fresh install of Windows and go from there. Over the years I've found messing around looking for the right setting is often wasted time. Learnt that from the IT guys at an old job, to time wasted diagnosing, just reimage the machine and away you go. Another reason I have all data on a separate drive to my Windows installation.
 
I have no problem with a fresh install but in all honesty it's only a couple of months ago that I did one, so I'm not entirely sure why/how I've ended up with the "MBR" type? (In all the reformats I've done over the years I don't ever recall being asked the question???)

*edit*

When I did the BIOS update it did tell me that I needed to re-enable NVME RAID Mode - but I just assumed that this was if I was running my drives in RAID - but having just enabled that option, the drive is now showing as a bootable drive in the BIOS?? Does that sound right to anyone??
 
Last edited:
I have no problem with a fresh install but in all honesty it's only a couple of months ago that I did one, so I'm not entirely sure why/how I've ended up with the "MBR" type? (In all the reformats I've done over the years I don't ever recall being asked the question???)

*edit*

When I did the BIOS update it did tell me that I needed to re-enable NVME RAID Mode - but I just assumed that this was if I was running my drives in RAID - but having just enabled that option, the drive is now showing as a bootable drive in the BIOS?? Does that sound right to anyone??

About MBR/GPT, I don't think it matters that much, tbh. If it's working now, then it is fine.

NVME raid: I think I read about that somewhere, but I can't explain why.
 
When I did the BIOS update it did tell me that I needed to re-enable NVME RAID Mode - but I just assumed that this was if I was running my drives in RAID - but having just enabled that option, the drive is now showing as a bootable drive in the BIOS?? Does that sound right to anyone??
Bit late on this one but I think NVME raid or indeed most motherboard raid is usually an all or nothing setting. So you've got some disks of whatever type connected to the motherboard in a raid config so you set raid to enable. Your boot disk might still just be a single disk but because you've got raid enabled it gets set as a raid disk. If this is the case, sometimes turning off raid stops the single disk from being recognised as a boot disk. Sometimes the raid controller has it's own sata headers and then you don't get this.
 
Bit late on this one but I think NVME raid or indeed most motherboard raid is usually an all or nothing setting. So you've got some disks of whatever type connected to the motherboard in a raid config so you set raid to enable. Your boot disk might still just be a single disk but because you've got raid enabled it gets set as a raid disk. If this is the case, sometimes turning off raid stops the single disk from being recognised as a boot disk. Sometimes the raid controller has it's own sata headers and then you don't get this.

Thanks for the reply - as it happens I've only recently installed Windows 11 and that needed secure boot to be enabled and I've managed to fumble my way through it OK!

As an aside, how on earth did you stuble across a random 3 year old thread???

Do you just trawl through old topics and set out to help like a cyber-batman?? :D
 
Thanks for the reply - as it happens I've only recently installed Windows 11 and that needed secure boot to be enabled and I've managed to fumble my way through it OK!

As an aside, how on earth did you stuble across a random 3 year old thread???

Do you just trawl through old topics and set out to help like a cyber-batman?? :D
lol - I cannot stop laughing

So I was searching for bios related stuff under motherboards and your post came up near the top. I looked at the date but not the year and thought "12th of June, well, I'm only about 5 days late to the party" 2022 lol
 
Back
Top Bottom