Fix ERROR_RANGE_NOT_FOUND (0x00000284) – 3 Causes

You're staring at a blue screen or app crash with 0x00000284 — ERROR_RANGE_NOT_FOUND. I've seen this pop up on Windows 10 build 1909 and later, sometimes in Windows 11 22H2. The culprit is almost always a registry hive that got mangled, a driver that left a bad memory range, or a Windows update that didn't play nice. Let's fix it in order of likelihood.

1. Corrupt Registry Entries (Most Common)

This error usually means something in the registry's range list — a structure that tracks memory or resource allocations — got orphaned or overwritten. Apps like Adobe Premiere, SQL Server, or even the print spooler can trigger it when they try to read a range that doesn't match any existing entry.

Fix: Restore a clean registry backup or rebuild affected keys

1. Press Win + R, type regedit, hit Enter.
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management.
3. Look for any subkey named RangeList or VirtualRangeList. If you see garbage data (like all zeros or impossible values), right-click it and delete it. Only delete if you have a backup or system restore point.
4. Run a System Restore to a point before the error started: type rstrui in Run, pick a restore point from last week.

# Alternative: Use DISM and SFC to repair system files (run as admin)
dism /online /cleanup-image /restorehealth
sfc /scannow

Don't bother manually editing the RangeList keys unless you know exactly what you're doing — one typo and you're reinstalling. SFC and DISM handle 80% of registry corruption cases. Reboot after both complete.

2. Faulty Driver Installation (Second Cause)

A driver that didn't install cleanly — especially for network adapters, USB controllers, or graphics cards — can write a bad memory range into the system's I/O resource list. I've seen this most often with Nvidia driver 528.49 on Windows 10 22H2. The error appears when you launch a game or run a GPU-accelerated app.

Fix: Roll back the driver or clean reinstall

1. Open Device Manager (devmgmt.msc).
2. Find the device that was updated recently. Look for a yellow exclamation mark.
3. Right-click → Properties → Driver tab → Roll Back Driver. Reboot.
4. If rollback is grayed out, uninstall the device (check Delete the driver software for this device) and reboot. Windows will reinstall the generic driver.

Skip third-party driver uninstallers — they often leave junk behind. Use Display Driver Uninstaller (DDU) in Safe Mode for GPU drivers. It's the only tool I trust for a full wipe.

3. Windows Update Glitch (Third Cause)

Less common but still real: a cumulative update that messes with the memory management stack. The error 0x00000284 showed up after KB5023778 on some Windows 11 22H2 systems. It's a known issue Microsoft acknowledged in late 2023.

Fix: Uninstall the problematic update

1. Go to Settings → Windows Update → Update history → Uninstall updates.
2. Find the most recent cumulative update (look for Security Update for Microsoft Windows or 2023-[month]).
3. Select it → Uninstall. Reboot.
4. Pause updates for a week to see if a new patch resolves it.

If you can't boot into Windows, use the Advanced Startup (press F11 during boot) → Troubleshoot → Advanced Options → Uninstall Updates. No need to dig through Safe Mode unless you're already there.

Quick-Reference Summary Table

Start with the registry fix — that's the one I see nine times out of ten. If it's not that, move to drivers. The Windows update issue is rarer but easy to check. You won't need to reinstall Windows unless you've tried all three and still get the error. In that case, run chkdsk c: /f to rule out disk corruption, then consider a repair install using the Windows Media Creation Tool. That's a last resort, but it works.