[Predator Helios Neo 16] Updating to Bios 1.17 caused BSOD

Faust
Faust Member Posts: 48 Devotee WiFi Icon

BSOD error is "inaccessible boot device".

I can get around it only by disabling ReBar. While I don't remember if it was enabled prior to the update, I am 100% sure I've never touched this option before.

ReBar can be pretty important for some games. So I'd rather keep it enabled.

Answers

  • AnhEZ28
    AnhEZ28 ACE, Member Posts: 5,066 Pathfinder

    In the BIOS, navigate to Main tab, and press CTRL + S to reveal the VMD controller. Disable that and enable the ReBar to see if it makes any difference.

    Please remember to include @AnhEZ28 when you want to reply back to my comment so that I can check your response.
    Thank you and have a nice day!
  • StevenGen
    StevenGen ACE Posts: 14,610 Trailblazer

    Your PHN16-72 model last bios version 1.17 should not be having any BSODs with the "inaccessible boot device" as bios version 1.17 hasn't updated anything else except "Update Copilot key for long press behaviour" which should NOT cause that BSODs, troubleshoot all the things listed below as it should fix your PHN16-72 model to boot, if it doesn't then your boot M.2 SSD drive is faulty, so replace the oem M.2 SSD with a new M.2 SSD drive like a Samsung 990 Pro + Heatsink, as that is the quickest and best quality drive for your PHN16-72 gaming laptop, as the oem Hynix or other that Acer use as an M.2 SSD boot drive might have overheated as its got no heatsink and these laptops perform much better with an M.2 SSD drive with a heatsink. Good luck and hope this helps you to solve this problem.

    Inaccessible Boot Device error can be caused by several reasons listed below so check all those things listed below:

    • Corrupt, incompatible, unstable, or outdated driver software
    • Malware or viruses
    • Hardware incompatibility, especially of storage devices
    • Loose cables or hardware defects
    • Windows updates
    • Missing, corrupted, or misbehaving filter drivers that are related to the storage stack
    • File system corruption
    • Changes to the storage controller mode or settings in the BIOS
    • Using a different storage controller over the default driver from Windows
    • Faulty hard drive

    If this answers your question and solved your query please "Click on Yes" or "Click on Like" if you find my answer useful👍