fatal1ty z68 professional gen3 bios update: one reboot later, inaccessible_boot_device

Solvedasrockbsodraidstorage-driver15 replies · 479 views · started
Accepted solution by Omar Kaur — hmmm before any repair, back up: boot from a Linux live USB or attach the drive to another PC and copy important files. then experiment…
  1. ok so i installed ASRock Fatal1ty Z68 Professional Gen3 Bios 2.20 on my editing workstation because the support page lisetd it as recommended :D The installer finished, asked for a reboot, and since then I get this every single time:

    Your PC ran into a problem and needs to restart. We're

    Your PC ran into a problem and needs to restart. We're
    just collecting some error info, and then we'll restart for
    you.
    42% complete
    For more information about this issue and possible fixes, visit
    our support site.
    
    If you call a support person, give them this info:
    Stop code: IRQL_NOT_LESS_OR_EQUAL
    

    it goes to teh blue screen, collects info, restarts, and after a few attempts lands in Automatic Repair, which can't repair anything, i didn't touch any BIOS settings... my files are on that drive and i realy don't want to reinstall Windows. is there a way to undo a storage driver from outside Windows? pls tell me there is.

    5
  2. what does teh stop code say exactly? 😅 INACCESSIBLE_BOOT_DEVICE or something else?

    3 2 helpful
  3. respectfully disagree, i tried that and it made asrock worse idk maybe im wrong lol

    9 0 helpful
  4. ahh classic check BIOS SATA/NVMe mode. If the new driver installed for RAID/RST mode and the BIOS is in AHCI (or vice versa), Windows cant find its boot disk. Dont flip modes randomly, but note what its set to. worked for me anyway 🤷

    1 0 helpful
  5. boot to teh recovery Command Prompt and list third-party drivers in the offline image:

    dism /image:C:\ /get-drivers
    

    find teh storage/RAID entry by its provider and date (oemXX.inf), then remove it:

    dism /image:C:\ /remove-driver /driver:oemXX.inf
    

    The drive letter can differ in WinRE, so check with dir C:\ or diskpart > list volume first.

    2 1 helpful
  6. ok but is bsod even worth bothering with or should i just leave it ?

    0 1 helpful
  7. oh ive been there lol once ure back in Windows, check the event logs and the vendors release notes. RAID/RST packages are often model-specific; the version for ur board should come from teh PC or motherboard makers support page.

    day one patch is bigger than the actual game, classic

    thumbsup

    5 2 helpful
  8. yeahhh honestly just reset teh settings and save yourself the pain lmk how it goes

    lol

    11 2 helpful
  9. yeahhh honestly just reset teh thermal paste and save yourself the pain lmao +1 same here

    1 0 helpful
  10. hmmm bump... still happening with raid for me hope that helps :)

    2 8 helpful
  11. hmmm is raid even worth bothering with or should i just leave it ??

    1 0 helpful
  12. hmmm from teh recovery environment (Troubleshoot > Advanced options), try Uninstall Updates first if it was delivered through Windows Update, then System Restore if any point exists... restore points are often created automatically before driver installs. good luck man!

    thinking

    1 0 helpful
  13. Accepted solution

    hmmm before any repair, back up: boot from a Linux live USB or attach the drive to another PC and copy important files. then experiment without fear.

    the real fix was the friends we made along the way

    0 4 helpful
  14. @okaur omg finally removed the new oem.inf with DISM from teh recovery command prompt and Windows booted on the first try, backed everything up immediately... thank you!

    10 2 helpful

Reply to this topic

Sign in or create an account to reply.