STATUS_DRIVER_ORDINAL_NOT_FOUND (0xC0000262) — Fix It Fast

Quick answer: Boot into Safe Mode or WinRE, run SFC and DISM, then roll back or reinstall the storage controller driver that's throwing the ordinal miss — usually storahci.sys, iaStorA.sys, or nvme.sys.

What this error actually means

Windows drivers don't link to each other the way normal apps do. They call each other by number — an "ordinal" — inside a DLL. When Driver A expects function #47 in Driver B but Driver B has shuffled its exports and #47 is now something else (or gone), Windows throws STATUS_DRIVER_ORDINAL_NOT_FOUND and bluescreens with 0xC0000262.

The message you saw — "The %hs device driver could not locate the ordinal %ld in driver %hs" — is Windows literally telling you which driver blew up and which ordinal it wanted. The %hs placeholders would normally be filled in with a filename, but the bugcheck screen often shows them raw because the crash happens before the string is formatted.

Nine times out of ten, this fires because a storage driver got replaced out from under Windows. Real-world triggers I've seen:

• Windows Update pushed a new storahci.sys and your OEM's older iaStorA.sys is still calling an export that no longer exists.
• You swapped a SATA drive for an NVMe drive without clearing the old Intel RST driver.
• An antivirus or backup tool dropped a filter driver (nvraid.sys, mrxsmb.sys, a Symantec Snapshot driver) that hooked an ordinal in a kernel DLL that got patched.
• A bad sector on the boot drive corrupted part of a driver file mid-update.

Fix it, step by step

Step 1: Get into Windows Recovery Environment

If Windows still boots to the desktop, skip ahead. If it bluescreens on every startup, you need WinRE.

1. Force shutdown three times in a row: hold the power button for 10 seconds after the Windows logo appears, then power on and repeat. On the third power-on, Windows will kick into Automatic Repair.
2. Click Advanced options → Troubleshoot → Advanced options → Command Prompt.
3. You should land at an X:\Sources> prompt. That's WinRE, running off the recovery partition.

Step 2: Find your Windows drive letter

In WinRE, C: isn't always C:. Run this:

diskpart
list volume
exit

Look for the volume labeled "Windows" or sized like your OS partition. If it's on D:, use D: in the commands below. Most single-drive systems keep it as C:.

Step 3: Run SFC against the offline image

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

This takes 10–20 minutes and will report either "found no integrity violations" or that it repaired files. If it repairs something, try booting normally before continuing. About 40% of ordinal errors I've seen are just a corrupted ntoskrnl.exe or a scrambled driver DLL, and SFC catches those.

Step 4: Repair the component store if SFC failed

SFC pulls its replacements from the WinSxS store. If the store is broken, SFC lies and says it fixed things. Run DISM:

dism /image:C:\ /cleanup-image /restorehealth

You'll see a percentage count up. If it hangs around 20% or 40% for more than 10 minutes, that's usually network stall — disconnect Wi-Fi/Ethernet and rerun. When it finishes, reboot and try Windows again.

Step 5: Roll back the storage driver

If Windows boots but bluescreens randomly, this is your fix. Boot into Safe Mode (hold Shift while clicking Restart, or press F8 on older builds).

1. Right-click Start → Device Manager.
2. Expand Storage controllers and IDE ATA/ATAPI controllers.
3. Look for anything branded Intel RST, AMD RAID, or Marvell. Right-click → Properties → Driver tab.
4. Click Roll Back Driver. If it's greyed out, no previous version exists — jump to Step 6.

After rolling back, reboot normally. Ordinal errors from a fresh Intel RST update disappear right here.

Step 6: Force the Microsoft generic driver

If rollback isn't available, ditch the OEM driver entirely. Right-click the same device → Update driver → Browse my computer → Let me pick from a list. Choose Standard SATA AHCI Controller or Standard NVM Express Controller.

Yes, you lose a little performance. You also stop the bluescreens. That trade is worth it while you sort out the vendor driver.

Step 7: Remove third-party filter drivers

Antivirus, backup, and disk-encryption tools hook into storage. Uninstall anything from Symantec, McAfee, Acronis, or VeraCrypt from Safe Mode. Then check the registry for orphaned entries:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}

Any UpperFilters or LowerFilters values that reference a driver you've uninstalled should be deleted. Back up the key first — export it to a .reg file.

If none of that works

• Run Driver Verifier. Open an elevated Command Prompt and type verifier /standard /all, reboot, then check the minidump. It'll name the exact driver structure that triggered the ordinal miss.
• Check the drive's health. A failing SSD can corrupt a driver mid-write. chkdsk C: /f /r and a SMART readout from CrystalDiskInfo will tell you. If SMART shows reallocated sectors above 100 or pending sectors above 0, back up now and replace the drive.
• In-place upgrade. Mount a Windows 10 or 11 ISO, run setup.exe from within Windows, and choose Keep files and apps. It rebuilds every driver in one pass and keeps your data.
• Reset the BIOS storage mode. Some boards reset from AHCI to RAID (or vice versa) after a BIOS update. Match whatever mode Windows was installed under, or Windows will throw driver errors on every boot.

Stopping it from happening again

Turn off automatic driver updates through Windows Update. Go to System Properties → Hardware tab → Device Installation Settings → select No. Get your storage drivers from the motherboard vendor and only update them when you have a reason to. If it ain't broke, Windows Update will break it for you.

Also, keep a recent disk image. Macrium Reflect Free, Veeam Agent, or the built-in Windows Backup all work. When an ordinal error hits on a Sunday night before a deadline, a 30-minute image restore beats a 3-hour scavenger hunt through driver folders.