Yeh got that exact issue on x570 master. Got me into a bootloop that managed to somehow reset the BIOS, loose all profiles but the bloatware that is W10 did actually manage to remove the update and get working again by it self.
Yeh got that exact issue. Got me into a bootloop that managed to somehow reset the BIOS, loose all profiles but the bloatware that is W10 did actually manage to remove the update and get working again by it self.
Some hardware apparently has that as a thing, if it's accurate then some earlier Gigabyte motherboards will reset the CMOS and load defaults after 4 loops.
Or it might report a overclock failure and prompt for entering the bios and suggest resetting to default. Had that on the X79 Intel system whenever the OS crashed for any reason.
(But just loading a saved bios profile will resolve that.)
About a year ago (sorry if not 100% correct cause of crazy times) I notified AMD and Gigabyte about problem. AMD didn't even replied and Gigabyte as usual: we cannot replicate....
Problem is Windows loads incorrect SSD driver. In my cause I use SATA RAID and 2 NVMe SSDs without RAID! But after update (AMD chipset) it also loaded NVMe RAID. This also happened few months ago when I updated AMD chipset drivers. My PC boots but second NVMe SSD is invisible (cause of RAID driver).
This is incorrect configuration (2 NVMe + SATA RAID):
And this is correct:
Notice difference how second SSD in correct case has driver "Standard NVME Express Controller". In bad case has AMD-RAID Bottom Device.
No they can't.
The bios doesn't track issues beyond Post, nothing beyond the boot loader can reset the bios (excepting the faulty gigabyte driver used in rgb fusion that can actually erase the bios flashrom itself)
JonasBeckman:
Or it might report a overclock failure and prompt for entering the bios and suggest resetting to default. Had that on the X79 Intel system whenever the OS crashed for any reason.
This only happens in the event cpureset fails amount to a successful post more than twice and its only a reset of the CPU/Ram configuration, not the storage configuration.
Ok so im full of crap am I?
Alright Mr Right about everything, if you say so o_O
You clearly applied manual intervention without realizing it,
the efi loader doesn't write back to the UEFI firmware that the boot succeeded or failed at all.
the efi sata or nvme module launches a libfat based driver to trigger the transition to the EFI boot loader which would be recorded as a success if the uefi firmware did log it, in the event that you even got to this error mesage.
At the point the device fails in the case of this driver, UEFI has finished post, transitioned to loading the boot device, succeeded in loading the nvme boot loader and used libfat to read and execute bootx64.efi, which then reads the bcd configuration with its own internal ntfs and begins loading ntoskrnl,
any fault at this point with a driver is not going to reset the BIOS, the failure occurs at the point where windows mounts the volume for boot because the controller driver doesn't know how to reinitialize the controller.
Curious why they aren't pushing v9.3.1.19 or newer.
If guess it depends on who you mean by "they"...
Presumably 9.3.0.221 is simply the driver that AMD has provided for publishing on Windows Update. Maybe it was the current driver at the time they decided to put something on Windows Update, maybe it wasn't but was considered a safer choice than the very latest driver, who knows.
From the perspective of Microsoft getting reports that this driver causes boot failures, it then probably just becomes a matter of either pulling the update or keeping it anyway, all this until AMD comes up with some form of "better idea".
Presumably 9.3.0.221 is simply the driver that AMD has provided for publishing on Windows Update. Maybe it was the current driver at the time they decided to put something on Windows Update, maybe it wasn't but was considered a safer choice than the very latest driver, who knows.
Vendors have no say what so ever in what Microsoft decides to put on WU, any driver that has been WHQL signed is a candidate.
The issue in this case turned out to be Microsofts own fault, the driver was intended for a subset of corporate deployments that don't routinely get updated by end users.
There were two posts about this on the r/AMD subreddit. For some reason, it seems only Gigabyte boards were affected as everyone with the issue had one of their X570 boards. No other motherboard brand users reported having the problem nor did any Gigabyte B550 or earlier generation users.
On digging into the driver itself, the afflicted release of the RCBottom driver has transitioned to using Wdf Directed Power framework, however AMD failed to declare "HKR,"WDF","WdfDirectedPowerTransitionEnable",0x00010001,1" in the Inf, so the attached device is stuck in a low powered state and thus unmountable.
v9.3.1.19 does not make this mistake, where v9.3.1.12 and older does.
Yep, I have this on my GB x570 master. I thought it's just a thing with aging hardware, as for some months I had another issue where when I press shutdown, the system actually restarts. Now I'm 99% sure it's also some driver issue, like this one, since I had no OC whatsoever other than XMP enabled and the after the last bios update I did the system ran fine for many months.
Is there a way to uninstall these drivers without causing further headache? As for me it's clearly too late and they are installed for a while.
Ok so im full of crap am I?
Alright Mr Right about everything, if you say so o_O
He stays correct though, there is no way the motherboard will reset the BIOS if it successfully gets past post.
Falling back to optimized defaults will only happen when the post itself is unstable, which does not include the boot drive nor Windows failing to load and going into a boot-loop.
Nothing beyond the boot loader can reset the bios (excepting the faulty gigabyte driver used in rgb fusion that can actually erase the bios flashrom itself)
Best way to use RGB fusion is to install it, set the lights and then uninstall it again. 😀
Reminds me, finally got my liquid freezer installed,
https://i.imgur.com/F58kBs1.jpg
pff how is this news? lenovo is out there bricking laptops with corrupted bios updates, no user intervention needed at all, in fact, 99% of users cant even stop it
even more baffling is the reaction from people, either "just send it back" or "constant bios updating is great cuz security"
Yeh got that exact issue on x570 master. Got me into a bootloop that managed to somehow reset the BIOS, loose all profiles but the bloatware that is W10 did actually manage to remove the update and get working again by it self.
same here, same board too, resolved itself thankfully.
And this is correct:
Notice difference how second SSD in correct case has driver "Standard NVME Express Controller". In bad case has AMD-RAID Bottom Device.