Acer Aspire A715-74G-73R3 INACCESSIBLE_BOOT_DEVICE (does not boot)

visard
visard Member Posts: 2 New User
edited February 2022 in Aspire Laptops
Hello everyone,

today I decided to set up a dual boot with PopOS (system installed previously) and Windows 10 (the new system). After the installation of the system it didn't boot as expected, but displayed BSOD with INACCESSIBLE_BOOT_DEVICE error. After many hours of reading on various forums I learned that my BIOS was not working correctly and was advised to perform an update (biggest mistake of my life).

As you can probably guess, the update was not successful, BIOS is either completely bricked or it still can be reflashed using cold boot method. I could not find a jumper to switch on the motherboard so I guess the life of this laptop comes down to finding the correct name for .FD file which is to be copied on FAT32 flash drive. Is there any way to find the correct name for this file? I tried to download most versions of drivers for this model (Aspire A715-74G-73R3), unpack the .EXE file and obtain the .FD file there, but I couldn't find such file.

I did find "isflash.bin" in %appdata%/Local/Temp/ when starting the driver updater executable on incompatible device, but I have no idea what to rename it into. I noticed that every model has a different name of the .FD file and this solution rarely works but I feel like this is the last hope for my laptop.

Is there a way to find the name of this file or perhaps someone already knows it?


Best Answer

  • visard
    visard Member Posts: 2 New User
    Answer ✓
    Problem solved, I found the name of the .FD file inside isflash.bin using HxD Hex Editor (ctrl+F and insert .fd, it should give you the name inside the binary). I renamed the .bin file to the found .FD name with this extension and copied to my usb stick and did a cold boot.

    As of right now Boot Device Manager can't see the disk with Linux system but now that I have the access to boot and command line I can even reinstall the distro if need be :).

    Cheers

Answers

  • visard
    visard Member Posts: 2 New User
    Answer ✓
    Problem solved, I found the name of the .FD file inside isflash.bin using HxD Hex Editor (ctrl+F and insert .fd, it should give you the name inside the binary). I renamed the .bin file to the found .FD name with this extension and copied to my usb stick and did a cold boot.

    As of right now Boot Device Manager can't see the disk with Linux system but now that I have the access to boot and command line I can even reinstall the distro if need be :).

    Cheers

Categories