There are several blue screen errors like 0x80070017 error, hal.dll BSOD error, and one of them is amifldrv64.sys. Before we talk about amifldrv64.sys BSOD error, let’s try to understand the following question: what is amifldrv64.sys?
Amifldrv.sys is a sys file created by MSI (American Megatrends, Inc) for foreigners. The file is usually located in the `c:WindowsTemp` folder and is 13864 bytes (13KB) in size. It is a safe file, as it currently contains no negative comments.
If you try to update the BIOS directly from the operating system, remember that this is not the best approach and that this procedure alone can lead to various BSODs due to conflicts between the two third-party drivers. If possible, try to update the BIOS version from a flash drive.
What causes Amifldrv64.sys BSOD during a BIOS update
There are several possibilities here. First, you are updating the BIOS through your computer’s operating system and there are conflicts between the two. Second, the driver check is a threat to your computer’s driver, causing some BIOS flashing utilities to fail.
Third, crashing your machine can also cause an amifldrv64.sys BSOD error. Finally, the Wi-Fi adapter driver can also cause conflicts that lead to amifldrv64.sys bluescreen error. We now offer solutions to these possible problems.
Fix amifldrv64.sys BSOD error during BIOS update
Disable Driver Verifier
Driver Verifier is a built-in diagnostic tool that is present in Windows 7, Windows 8.1, and Windows 10. Its main purpose is to verify both Microsoft native drivers and third-party drivers. It works by putting drivers under a lot of stress to make incompatible or outdated drivers behave badly.
Use the first guide if you can access the Windows menu, or the second if your computer can no longer boot through the recovery menu.
Disable and enable driver checking through the Driver Checker Manager
- Press the Windows + R key to open the “Run” dialog box. Then type “verifier.exe” in the text box and press Enter to open the Driver Verifier utility.
Note: When prompted in the UAC (User Account Control) window, click Yes to grant administrator privileges.
- While in the Driver Verifier Manager window, select “Delete existing settings” (under “Select a task”) and click “Finish”.
- Now that Driver Verifier is disabled, restart the computer and try updating the BIOS again.
- If you are able to perform the installation without any problems this time, follow these steps to re-enable the Driver Verifier.
- Press the Windows + R key to open the Run dialog box. Then in the text box enter “verifier.exe” and press Enter to open the Driver Verifier utility.
- When you return to the Driver Verifier Manager utility, under “Select a task”, check the “Create custom settings (for code developers)” box and click “Next” to move to the next menu.
- After proceeding to the next menu, make sure that the boxes associated with Default Settings, IRP Log, and forced pending I/O requests are checked. Then click Next to move to the next screen.
- On the next screen, select the Select Driver Name from the List check box and click Next to move to the next menu.
- Once you see the list of drivers, click once on Vendors to sort the list by the manufacturer. Then start checking any drivers that are not provided by Microsoft Corporation. When you are finished with the entire list, click Finish and click OK on the final confirmation prompt.
- Restart your computer. After your computer restarts, the driver scan must be enabled again.
To disable and enable driver scanning with Windows Restore, follow these steps
- Insert the installation media that is compatible with your version of Windows, restart your computer, and press any key when you are asked if you want to boot from the installation media.
- Once you reach the first Windows installation screen, click Repair Computer (at the bottom left of the screen). This will take you directly to the recovery menu.
- Note: You can also force an advanced recovery menu (without the installation media) by forcing 3 consecutive computer shutdowns – rebooting/stopping the computer during the boot process.
- While in the recovery menu, click Troubleshooting, then Advanced Options in the list of troubleshooting sub-items.
- In the Advanced Options menu, click Command Prompt to open the advanced CMD prompt.
- You will then be prompted to select your account and enter the associated password.
- After this and successful access to the extended command line, enter the following command and press Enter to disable Driver Verifier:
verifier / reset.
- Close the extended CMD prompt and restart your computer. On the next boot, follow the motherboard manufacturer’s instructions to update the BIOS version and see if the process now works smoothly.
- Whatever the result, follow the steps below to re-enable the driver verifier and set it up as before.
- Follow steps 1 through 4 to return to the extended CMD prompt. This time, type “Verifier” and press Enter to open Driver Verifier.
- In the Driver Verifier Manager window, select “Create custom settings (for code developers)” and click “Next” to go to the next window.
- When prompted next, make sure the Check I/O / Forced Delayed I/O Requests (*) and PIR Logging (*) checkboxes are checked. When all important settings are enabled, click Next to move to the next menu.
- When you get to the next screen, check the box associated with the Select Driver Names from List option and click Next to move to the next menu.
- When you get to the next screen, click on Vendor to arrange everything in alphabetical order, then check all drivers that are not signed by Microsoft Corporation. Once you’re done, click Finish to complete the process.
- Finally, you will be asked to reboot your computer for the changes to take effect. To do this, click OK and wait for your computer to reboot.
- If the same problem continues to occur even after disabling the driver check, an alternative way to fix amifldrv64.sys BSOD can be found below.
Using System Restore
Note that amifldrv64.sys is usually associated with MSI Live Update agent and the associated BSOD (blue screen of death) usually appears after a BIOS update failure. If this has happened in your scripts, it is likely that you will not be able to boot your computer properly.
In this case, a viable solution is to use the System Restore utility to restore your computer to the state prior to attempting the BIOS update. If you’ve already tried this without success or if you don’t have a suitable snapshot of the restore, move on to the next solution.
Remove the MSI Live Update program
If the BSOD points to amifldrv64.sys or NTIOLib_X64.sys files, but the BSOD does not happen during boot (you skip the boot sequence), it is very likely that random BSOD crashes are caused by MSI Live Update.
Several users affected by this problem have reported that they finally managed to prevent BSODs after uninstalling the Live Update program.
If you get rid of it, you will lose the ability to automatically update BIOS and chipset drivers, but if you can get some stability, that’s better than frequent BSOD crashes.
Here’s a quick guide to uninstalling the MSI Live Update program:
- Press the Windows + R key to open the “Run” dialog box. On the next screen, type “appwiz.CPL” and press Enter to open the “Programs and Features” menu.
- While in the “Programs and Features” menu, scroll down the list of installed applications and find the MSI Live Update program.
- When you see it, right-click on it and select “Remove” from the new popup menu that appears to get rid of it.
- In the uninstaller, follow the instructions on the screen to complete the uninstall, then reboot the computer to see if the frequent BSODs stop on the next startup.
If the problem persists, proceed to the next method described below.
Installing the WiFi adapter
If the problem occurs immediately after a BIOS update (or after a failed attempt), you should also check the WiFi adapter driver. It turns out that a failed BIOS update can also affect the WLAN driver.
We were able to identify several user reports confirming that this particular culprit caused the problem in their case in each case, reinstalling the WiFi adapter driver via Device Manager fixed the problem.
Here’s a quick guide to reinstalling the WiFi adapter driver through Device Manager to stop any BSODs pointing to amifldrv64.sys or NTIOLib_X64.sys:
- Press the Windows + R key to open the “Run” dialog box. Then type “devgmt.MSC” and press Enter to open the Device Manager. When prompted, click “Yes” to open the Device Manager with administrator privileges.
- Once in Device Manager, scroll down the list of installed devices and expand the drop-down menu associated with network adapters.
- Then, in the list of available subtitles, right-click on the entry associated with your WiFi driver and select Properties from the new pop-up menu that appears.
- While in the WiFi driver properties window, select the “Driver” tab in the menu above, and then click “Uninstall Device” to remove it from your computer.
- When prompted, click Remove again to confirm the operation and then wait for it to complete.
- When the process is complete, restart your computer so that the operating system can replace the missing WIFI driver with a generic equivalent.
- On the second reboot (once your Internet connection is working again), Windows will update the WIFI driver to the latest version according to the motherboard manufacturer.
- After reinstalling your WI-Fi driver, repeat the action that caused the BSOD to check if the problem is fixed.
Frequently Asked Questions
In some situations, an outdated BIOS can cause a BSOD error due to certain incompatibilities. So try a BIOS update.
- Reset the CMOS.
- Try booting into safe mode.
- Change the BIOS settings.
- Flash the BIOS again.
- Reinstall the system.
- Replace the motherboard.
sys is a sys file created by MSI (American Megatrends, Inc) for foreigners. The file is usually located in the "c: WindowsTemp" folder and is 13864 bytes (13 KB) in size. However, some Windows users suffer from the blue screen of death associated with amifldrv64.
A Windows PC factory reset will only fix some minor driver issues. Resetting your PC will not fix a serious problem, such as outdated drivers. Also, if the cause of BSOD is hardware-related, rebooting your PC will not help.