"inaccessible boot device" after updating pci root complex (windows 11)

Beni Elishackove 0 Reputation points
2023-03-24T15:24:39.7066667+00:00

Hello

I am having an issue with those two driver updates from Intel

PCI\VEN_8086&DEV_A70DDesc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A70D "Intel(R) PCIe RC 010 G5 - A70D" ver 10.1.49.7

PCI\VEN_8086&DEV_A74DDesc%=Needs_NO_DRV,PCI\VEN_8086&DEV_A74D "Intel(R) PCIe RC 060 (x4) G4 - A74D" ver 10.1.49.7

After updating those drivers from the default Microsoft PCI Express Root Port driver I get a blue screen with the error "Inaccessible boot device"

Safemode won't work and I tried diskpart the "active" command doesn't work on GPT disks only on MBR

After the update, it seems that even diskpart doesn't recognize the attributes of the disks like it was before not at all

A system restore is needed to remove those inf updates and go back to the normal Microsoft PCI Express Root Port driver and the system goes back to booting as it did (without the intel inf updates)

from my understanding, those drivers must be installed during the OS installation process by adding the drivers to the setup.

can it be done after windows got installed with a normal Microsoft driver and not the intel inf one?

Please guide me on how to get windows to boot after updating to intel inf 10.1.49.7 (from Intel inf ver 10.1.19284.8351)
Thanks in advance Beni.

Windows for business | Windows Client for IT Pros | Devices and deployment | Other

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Newest
Most helpful Newest Oldest
  1. tommy 0 Reputation points
    2026-09-21T01:19:09.9466667+00:00

    Target thread:

    https://learn.microsoft.com/en-us/answers/questions/1192909/inaccessible-boot-device-after-updating-pci-root-c

    Thanks for documenting the exact A74D device ID and Intel INF version. Your report helped me recover an NVMe SSD that had disappeared from Windows.

    My setup was an ASUS PRIME B760M-K D4, Windows 11 Pro 25H2, and an Intel SSDPEKNW010T8. The parent device was Intel(R) PCIe RC 060 (x4) G4 - A74D, using raptorlakesystem.inf version 10.1.49.7. Its INF entry selected Needs_NO_DRV, and no service was bound to that parent device.

    BIOS and Windows Recovery Environment could detect the SSD, and WinRE successfully read an entire approximately 1.78 GB file. Normal Windows and Safe Mode could not enumerate the SSD. The installed Windows also did not enumerate its NVMe controller. SFC/DISM found no corruption, and manually starting stornvme did not restore detection.

    What worked on my machine:

    1. Open Device Manager > System devices.
    2. Locate Intel(R) PCIe RC 060 (x4) G4 - A74D and verify its hardware ID is PCI\VEN_8086&DEV_A74D.
    3. Choose Update driver > Browse my computer for drivers > Let me pick from a list of available drivers on my computer.
    4. Keep Show compatible hardware checked and select the Microsoft PCI Express Root Port entry.
    5. Complete the change, restarting if Windows requires it, and check disk detection again.

    After this change, the parent device used pci.inf with service pci and problem code 0. The Intel NVMe controller reappeared with status OK, and the original NTFS volume and drive letter returned. I did not delete the chipset driver package, replace system .sys files, format the SSD, or reinstall Windows.

    This is a confirmed recovery on my machine, not proof that every A74D/Needs_NO_DRV configuration is faulty. My SSD had disappeared during normal use rather than immediately after a known driver update, so the original trigger remains unknown. My OS was on a separate SATA SSD; this procedure was not tested on a machine whose inaccessible NVMe was its Windows boot disk. Do not force a non-compatible driver or apply the change to unrelated PCIe ports. Back up important files once access returns.

    Was this answer helpful?

    0 comments
  2. Limitless Technology 45,246 Reputation points
    2023-03-27T12:08:30.31+00:00

    Hello there,

    The INACCESSIBLE_BOOT_DEVICE bug check often occurs because of a boot device failure. During I/O system initialization, the boot device driver might have failed to initialize the boot device, typically a hard disk.

    File system initialization might have failed because it didn't recognize the data on the boot device. Repartitioning the system partition, changing the BIOS configuration, or installing a disk controller can also cause this error.

    This error always occurs while the system is starting. This error frequently occurs before the debugger connection is established, so debugging can be difficult. The OS might not be accessible and the error logs might be empty, as the OS hasn't booted far enough to start those subsystems. The following sections explain resolutions for both situations, if you're unable to boot Windows and if you're able to boot Windows. https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/debugger/bug-check-0x7b--inaccessible-boot-device.md

    Hope this resolves your Query !!

    --If the reply is helpful, please Upvote and Accept it as an answer–

    Was this answer helpful?

    0 comments