The most common reason for this issue is that Windows blocks the driver because it’s on Microsoft’s list of risky drivers. Other reasons can include interference from your antivirus software or trying to run the updater from an external drive or a drive that isn’t using the NTFS file system. In this article, we will discuss different ways to solve this error.
1. Disable Driver Verifier
Driver Verifier is a built-in troubleshooting tool for Windows 7, 8.1, and 10. Its primary purpose is to ensure that both Microsoft and third-party drivers are working properly by putting them under extra pressure, exposing any potential errors or incompatibilities. While Driver Verifier is great for finding driver problems, it can conflict with BIOS update tools, especially since many BIOS flashing utilities are basic scripts that motherboard manufacturers don’t often update. Because of this, most BSODs that appear during BIOS updates—especially those referencing Amifldrv64.sys—are actually caused by Driver Verifier. If this scenario applies to you, the solution is simple: disable Driver Verifier while updating your BIOS, and re-enable it once the update is complete. Since the steps are a little different depending on whether you can boot into Windows, we’ve included two sections—one if you can access your desktop, and another if you can only access the Windows Recovery menu. Use the first guide if you can get to your Windows desktop, or the second if you need to do this from the Recovery menu.
1.1. How to Disable & Enable Driver Verifier via Driver Verifier Manager
1.2. How to Disable & Enable Driver Verifier via Windows Recovery
If you’re still having the same issue after disabling Driver Verifier, try the next method below to fix the amifldrv64.sys BSOD.
2. Use System Restore
amifldrv64.sys is commonly associated with the MSI Live Update tool. If you get a BSOD linked to this file after a failed BIOS update, your computer may not be able to boot properly. In this case, you can use System Restore to bring your PC back to a point before the BIOS update attempt. Follow this article to see how to use System Restore, even if you can’t log into Windows normally. If System Restore doesn’t help or you don’t have a restore point available, move to the next step below.
3. Uninstall the MSI Live Update Program
If the BSOD points to amifldrv64.sys or NTIOLib_X64.sys, but you can still boot into Windows, the problem may lie with the MSI Live Update program. Many users have stopped the BSOD crashes by simply uninstalling Live Update. Removing it will mean you lose automatic BIOS and chipset detection, but it’s better than dealing with frequent crashes.
4. Create a Bootable BIOS Update USB
If you get a BSOD while updating your BIOS from within Windows, you might have better luck using a bootable USB flash drive. Although flashing the BIOS from the OS seems easier, it’s riskier and can cause major problems—including making your PC unbootable. You can usually avoid these issues by creating a bootable USB for your BIOS update and installing it from your computer’s initial boot screen. Each motherboard manufacturer has their own BIOS update method and specific tools, but here are some general steps: Important: Always check your motherboard’s official documentation for exact instructions for BIOS updates via USB.
5. Reinstalling the WiFi Adapter Driver
If the problem started right after a BIOS update (or a failed attempt), you should also check your WiFi adapter driver. Sometimes, a BIOS update can cause the WLAN driver to act up. Many users have solved this issue by reinstalling their WiFi adapter driver through Device Manager.
6. Perform a Repair Install
If none of the above solutions have worked, you may need to restore your Windows system files to rule out any OS corruption. The best way to do this is a repair install (also known as an in-place upgrade). You’ll need compatible installation media to start. Here’s how to create installation media for Windows 7 or Windows 10.
