TUF GAMING B650-PLUS WIFI Version 3281 <- BAD UPDATE! STAY AWAY!

[StarMaster21]

First going to say it because I don't know how many other people are having the same problems as me but enough is enough with ASUS BUGGY BIOS UPDATES! Don't use EA Flash use the Flash Back USB port and FB Button on the back of the MOB less bugs but still buggy. 

My BIOS is: Version 3281

14.81 MB
2025/08/21
SHA-256 ：DE21B21A4F6031E0DD1B68AA0583711E45CB9D2C4FB343A963F1230C6DE33127
"1. Improved system performance
2. Improved device compatibility"

My Specs:
MOB: TUF GAMING B650-PLUS WIFI 
CPU: AMD 7600X
GPU: RTX 5060 TI 16GB
RAM: CORSAIR VENGEANCE DDR5 RAM 32GB (2x16GB) 6000MHz CL30 - Grey (CMK32GX5M2B6000Z30)
Main Boot Drive: Crucial P310 1TB 2280 PCIe Gen4 3D NAND NVMe M.2 SSD – Up to 7,100 MB/s – CT2000P310SSD801
Game Drive: Crucial P310 4TB 2280 PCIe Gen4 3D NAND NVMe M.2 SSD – Up to 7,100 MB/s – CT4000P310SSD801
Old Main Boot Drive: Crucial P3 Plus 1TB PCIe Gen4 3D NAND NVMe M.2 SSD, up to 5000MB/s - CT1000P3PSSD8 (Holds Bootstrap to load my Windows 10 os from this drive or other main one)
PSU: CORSAIR RM1000x Fully Modular ATX Power Supply - 80 PLUS Gold - Low-Noise Fan - Zero RPM - Black
OS: Windows 10 Home (Build 22H2)

Extra: 
Case: 4000D AIRFLOW Tempered Glass Mid-Tower ATX Case — Black
CPU Cooler: iCUE H100x RGB ELITE Liquid CPU Cooler

With my system specs out of the way now. Version 3281 is buggy BIOS update for TUF GAMING B650-PLUS WIFI. What are my main problems? I will list down below for you all to see/read.

Buggy Problems:

1. Stuck on BIOS loading screen that it doesn't want to load my OS at all until i hit the reset twice then power the system off then back on to load into windows.

2. EXPO: Turn of right now because I have spent weeks trying to find root cause of these bugs and well ****** it's ASUS sucks at releasing good BIOS updates. 3281 should be pull from the list, its bad update. IF ASUS you are reading STOP IT ALREADY! Get your act together and release stable BIOS updates that aren't causing bug problems. 

When I was on 3208 BIOS I never had loading problems with BIOS being stuck their or loading into windows at all until I updated the BIOS to 3281 giving me problems left and right. 

I have one question can I update my BIOS back to Version 3208 using the flash back button on the MOB? YES OR NO? I asked around because some of the updates had Note: This BIOS version cannot be rolled back to previous versions. <- SO asking about this and i need real answer before trying it without risky of my mob getting ruined. If it risk i going to need to buy the same motherboard again then which i can't right now. 

Update: I also perform a full NVRAM Rebuild using this and still had the same problems.

How to Perform a Full NVRAM Rebuild (Not just CMOS clear)

Here is the correct sequence:

1. Shut system down

Turn off PC and switch off PSU.

2. Press and hold the power button for 15 seconds

This drains residual power from the board’s VRMs and chipset.

3. Clear CMOS (rear I/O button)

Press the Clear CMOS button on the back panel for 5 seconds.

4. Remove the motherboard battery

This step is what clears the deeper NVRAM layers.

Remove the side panel

Find the small silver coin-cell battery

Remove it

5. Wait 5–10 minutes

During this time the board loses:

Boot manager tables

Device configuration

ACPI data

Memory context restore data

PCIe lane training information

This is the actual NVRAM wipe.

6. Reinstall the battery
7. Boot system → Go into BIOS

It may take slightly longer to boot the first time.
This is normal — the board is rebuilding all initialization data.

8. Load BIOS defaults (F5)

This reinitializes all firmware tables.

Why that? 

All my main problems i didn't say before.

A full NVRAM rebuild means completely erasing and regenerating the motherboard’s non-volatile memory configuration data — not just clearing BIOS settings.

On ASUS AM5 boards, especially the TUF B650 series, this is critical because corrupted NVRAM can cause:

Windows not loading at all <- Problem I had

Random USB dropouts <- rarely

Ethernet disconnecting <- happens a lot after turn the pc on or restart it happens randomly plus mouse jumps around too

Blue screens <- Happens sometimes and annoying

Boot loops <- VERY rare i got this

Device initialization failures

“Stuck on ASUS logo” behavior <- Yes a few times since this bios update

A simple “Clear CMOS” does not fully wipe NVRAM.

A full rebuild forces the motherboard to regenerate all boot, hardware, and firmware configuration tables from scratch.

[Silent_Scone]

Hi @StarMaster21 

Since you’re getting BSODs while already in Windows (not just hanging at the ASUS logo), this looks like a wider stability issue rather than purely a boot/UEFI handoff problem. To narrow it down:

1) When it hangs on the ASUS logo:
 Can you still enter BIOS (Del/F2), or is it frozen?
–Which Q-LED is lit/stuck (CPU / DRAM / VGA / BOOT)?

2) Minimal-boot test (important):
1 RAM stick in slot A2
Only one NVMe installed (the actual Windows boot drive)
Temporarily remove the “bootstrap” NVMe
Unplug all USB except keyboard/mouse (no hubs/front USB if possible)

3) BSOD evidence (this will tell us if it’s CPU/IMC vs storage/driver):
Zip and share C:\Windows\Minidump\*.dmp
Tell us the bugcheck code (e.g. 0x124 / 0x1A / 0x3B etc.) and any “WHEA-Logger” events (17/18/19) in Event Viewer
Reliability Monitor screenshot also helps

If we see WHEA 0x124 / WHEA-Logger cache/bus/interconnect, that points more toward CPU/IMC/SoC/PCIe stability. If it’s storage/NVMe timeouts or driver faults, we’ll go that route instead.

Since this isn't a widespread issue, I wouldn't be too quick to infer "buggy BIOS". People tend to jump straight to this with anything they do not understand or can't narrow down. Moreover, the bulk of changes comes from AMD AGESA.

[StarMaster21]

First read my post again because your 100% wrong. The problems came from what said the first time and it relates to BIOS updates being bad from asus fully. IT doesn't take much brain cells to see it.

[StarMaster21]

 Read what I said as the core issue was clearly stated from the beginning. The problems I am experiencing are the result of ASUS BIOS updates themselves, not user configuration or misunderstanding. There is a clear and ongoing pattern of instability and regressions introduced by recent BIOS releases.

Multiple BIOS versions have exhibited bugs that impact system stability and reliability. This points to inadequate validation and quality assurance prior to release. A BIOS update should not introduce new problems, especially on enthusiast-class hardware where stability is critical.

This is not an isolated incident, and it is becoming increasingly difficult to trust new BIOS releases. ASUS needs to improve its testing and release process to prevent customers from acting as de facto beta testers for production firmware.

I would appreciate an official response acknowledging these issues and outlining what steps are being taken to address the ongoing BIOS instability.

[Silent_Scone]

My reading comprehension is spot on, thanks!  Right now, you’re asserting a conclusion (“BIOS is the cause”) without providing the evidence that would let anyone distinguish otherwise, just anecdotal comments about regression and validation out of frustration instead of any substance. 

Just to clarify on the technical side: a large portion of what changes between AM5 BIOS versions is AMD’s AGESA/SMU firmware, which the motherboard vendor integrates. So a regression appearing “after an ASUS BIOS update” doesn’t automatically mean “ASUS wrote buggy code”. 

The reason I’m asking for Q-LED state and dump/WHEA data is simple: those are the fastest ways to prove what is failing and where. If this truly is a BIOS regression, those details will support that and give something actionable.

From your lengthy post, it's difficult even to ascertain if the behaviour persists at Optimised Defaults;“I also perform a full NVRAM Rebuild … and still had the same problems.”

There is ambiguity here whether you left everything at defaults afterwards or changed things again by enabling EXPO. You've not even provided any evidence to suggest the DRAM is even stable, which should be troubleshooting 101. 

In short, I'd suggest asking for help rather than asserting you understand the root problem without being able to resolve it. Sorry if that's not what you wanted to hear.

[StarMaster21]

I respectfully disagree with that characterization. The conclusion that the BIOS is the root cause is not based on anecdote or frustration, but on a process of elimination informed by controlled changes and repeatable behavior.

Prior to updating, I was running BIOS version 3208 with no POST delays, no BIOS hangs, and no issues loading into Windows. Those problems began only after updating to BIOS version 3281. No other variables were introduced during that transition. Hardware remained unchanged, firmware settings were revalidated, and operating system integrity was confirmed.

Additionally, I performed a full NVRAM rebuild specifically to rule out corruption, as NVRAM inconsistencies are a well-documented cause of initialization and boot anomalies following firmware updates. The issues persisted after the rebuild, further narrowing the fault domain.

At this point, the regression is both version-specific and reproducible: stable behavior on 3208, instability on 3281. That differential alone constitutes substantive evidence of a BIOS-level issue. The intent here is not to bypass troubleshooting steps, but to avoid rehashing already completed diagnostics and focus on resolving the actual point of failure efficiently.

If there is a specific test or data point that would meaningfully differentiate an alternative cause, I am open to it—but dismissing the BIOS as a factor without addressing the clear regression between versions is not a technically sound position.

[Silent_Scone]

I’d start out by updating your UEFI to the latest version, and then providing answers and information outlined in my initial post if still experiencing issues. A poor assumption on my part to assume you were testing on the most recent firmware. Any reason why you haven’t updated? 3281 has an outdated AGESA revision.

EDIT: Yes, you can use USB Flashback.