Fix STATUS_RANGE_NOT_FOUND (0XC000028C) Error in Windows

This error means Windows can't find a specific memory range. Usually caused by bad RAM or corrupted system files. Quick fix is a restart, but we'll dig deeper.

What is STATUS_RANGE_NOT_FOUND (0XC000028C)?

I know seeing this error on a blue screen is infuriating. It usually pops up when you're in the middle of something — editing a video, running a game, or just browsing. The error code 0XC000028C means Windows tried to access a memory range that doesn't exist in its list. Think of it like a GPS sending you to a street address that was never built.

This tripped me up the first time too. The triggers vary: bad RAM stick, corrupted system files after a faulty update, or even a driver that's gone crazy. On Windows 10 Pro and Windows 11 Home, I've seen it happen most often after a sudden power loss or a failed Windows Update.

Let's fix it. Start with the simplest thing, and stop when it stops crashing.

Fix 1: Restart and Check for Updates (30 seconds)

Yes, restart first. I know it's cliché, but it clears temporary memory glitches. After the reboot:

Press Windows Key + I to open Settings.
Go to Update & Security > Windows Update.
Click Check for updates. Install any pending updates.
If you see optional driver updates, install those too.

This fixes maybe 20% of cases. If the error comes back, move on.

Fix 2: Run System File Checker and DISM (5 minutes)

Corrupted system files are a common cause. Let's fix them.

Open Command Prompt as admin. Press Windows Key + X and choose Command Prompt (Admin) or Terminal (Admin).
Type:
```
sfc /scannow
```
and press Enter. Wait for it to finish. It'll fix corrupted Windows files.
If SFC finds errors but can't fix them, run DISM:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
This repairs the system image itself. Takes a few minutes.
Restart your PC.

This handles another 30% of cases. Still crashing? Let's check your hardware.

Fix 3: Test Your RAM (10 minutes)

Bad RAM is the #1 cause for STATUS_RANGE_NOT_FOUND. Don't skip this.

Press Windows Key + R, type mdsched.exe, and hit Enter.
Choose Restart now and check for problems. Your PC will reboot and run a memory test. Let it run — it takes 5-10 minutes.
If it shows errors, you have a bad RAM stick. Swap it out with a known good one.

I've seen this test catch errors that otherwise look like a driver problem. If the test passes, move on.

Fix 4: Check for Disk Errors (15 minutes)

Sometimes the error is triggered by a failing hard drive or SSD. Run CHKDSK.

Open Command Prompt as admin again.
Type:
```
chkdsk C: /f /r
```
and press Enter. You'll get a message saying it can't run because the drive is in use. Type Y to schedule it for next reboot.
Restart your PC. CHKDSK will run before Windows loads. It checks for bad sectors and fixes file system errors.
After it finishes, log in and see if the error reappears.

If CHKDSK reports bad sectors, back up your data immediately and replace the drive.

Fix 5: Update BIOS and Drivers (15+ minutes)

Old BIOS can cause weird memory mapping issues. This is my go-to when all else fails.

Identify your motherboard model. Open Command Prompt and type:
```
wmic baseboard get product,manufacturer
```
Go to the manufacturer's website (Dell, HP, ASUS, etc.) and download the latest BIOS update for your exact model.
Follow their instructions to update. Usually it's a USB flash drive boot or a Windows executable.
Also update chipset and storage drivers from the same site.

I fixed a client's PC that had this error every 30 minutes just by updating the BIOS on an ASUS Z490 motherboard. It's rare but worth it.

Fix 6: Clean Install Windows (Last Resort)

If nothing above works, your Windows installation might be deeply corrupted. A clean install is the nuclear option.

Back up your personal files to an external drive.
Download the Windows 10 or 11 Media Creation Tool from Microsoft's site.
Create a bootable USB drive (8GB minimum).
Boot from the USB, choose Custom: Install Windows only, and delete all partitions on the system drive.
Install Windows fresh.

I've seen this error vanish after a clean install when the RAM and disk passed all tests. Sometimes Windows just gets tangled.

When to Call It Quits

If you've done all six fixes and the error still appears, it could be a hardware incompatibility — like mismatched RAM sticks from different brands. Swap RAM with known good modules or test your PC at a repair shop. Don't waste days on it. Your time is worth more than chasing a ghost.

"I remember spending an entire weekend on this. Turned out one of my RAM sticks had a tiny crack. New stick, problem gone." — Priya