STATUS_INVALID_LDT_OFFSET (0xC0000119) – Nuke & Clean

Quick answer (advanced users): Run sfc /scannow, DISM /Online /Cleanup-Image /RestoreHealth, then chkdsk c: /f in Safe Mode. If that doesn't fix it, run Driver Verifier for 24 hours. Still broken? Wipe the drive and clean install Windows from a USB.

What exactly is this error?

0xC0000119 – STATUS_INVALID_LDT_OFFSET. That's a blue screen of death that pops up when a program tries to load something into something called the Local Descriptor Table (LDT) at an address that doesn't exist or isn't allowed. Think of the LDT as a map of memory segments for old-school programs. If a driver or a piece of malware tries to read a segment number that's out of bounds, Windows panics and crashes.

I've seen this most often on Windows 10 machines (version 1903 and up) after a driver update gone wrong, or on systems infected with a rootkit that hooks into low-level memory. It's rare on Windows 11 because Microsoft tightened up the kernel, but it can still happen if you're running legacy software or a faulty chipset driver.

Before you start

Write down your Windows license key if you don't have a digital license linked to your Microsoft account. Back up your personal files to an external drive or cloud – use a Linux live USB if Windows won't boot. This error can damage data if you ignore it.

Step-by-step fix

Step 1 – Boot into Safe Mode with Networking

If your PC can still boot normally, great. If not, force it into recovery:

1. Turn the PC on, and as soon as you see the Windows logo, hold the power button to forcibly shut down.
2. Do this three times. On the fourth boot, Windows should say "Preparing Automatic Repair." Let it run.
3. Click Advanced options > Troubleshoot > Advanced options > Startup Settings > Restart.
4. After the restart, press 5 or F5 to select Safe Mode with Networking.

Expected result: You'll see a black desktop with "Safe Mode" in each corner. Networking works so you can download tools if needed.

Step 2 – Run System File Checker and DISM

These two tools check and repair Windows system files. Run them in this order:

1. Right-click the Start button and choose Command Prompt (Admin) or Windows Terminal (Admin).
2. Type sfc /scannow and press Enter. Let it finish – it might take 15 minutes. It'll say either "Windows Resource Protection did not find any integrity violations" or it found corrupt files and repaired them.
3. If it found anything, run DISM /Online /Cleanup-Image /RestoreHealth next. This command pulls clean files from Windows Update. It needs internet, so make sure you're in Safe Mode with Networking.
4. After DISM finishes, run sfc /scannow a second time. The first repair may have left some files inconsistent.

Expected result: Both commands should complete without errors. If they fail, you might have a deeper corruption – skip to the alternative fixes.

Step 3 – Check the hard drive for errors

The LDT error can also come from a bad sector on the disk where the page file lives.

1. In the same admin command prompt, type chkdsk c: /f /r. The /f fixes errors, /r locates bad sectors and recovers readable info.
2. It'll ask if you want to schedule the check at next reboot. Type Y and press Enter.
3. Restart the PC normally (not Safe Mode). The disk check will run before Windows loads. It can take an hour or more on a big drive.

Expected result: After the check, Windows boots. If chkdsk found and fixed errors, the BSOD might be gone. If it reports massive corruption, your drive may be dying – back up everything now.

Step 4 – Run Driver Verifier

This is the nuclear option for pinpointing bad drivers. Warning: Driver Verifier can cause repeated crashes if you have a bad driver. That's the point – it will tell you exactly which driver is the culprit.

1. In admin command prompt, type verifier and press Enter.
2. Select Create standard settings, click Next.
3. Select Automatically select all drivers installed on this computer, click Finish.
4. Restart the PC. Let it run normally for 24 hours. If a driver causes the BSOD, the error screen will show the driver name (like nvlddmkm.sys for NVIDIA, or rt640x64.sys for Realtek).
5. Write down the driver name. Then boot back into Safe Mode, open Device Manager, find that device, right-click and select Update driver or Uninstall device (check "Delete the driver software for this device").

Expected result: If no driver is flagged after 24 hours, your drivers are clean. The problem is elsewhere.

Alternative fixes if the main steps fail

Option A – Roll back recent driver updates

If you just installed a new driver before the BSOD started:

1. Boot into Safe Mode.
2. Open Device Manager.
3. Find the device you updated (often graphics card, network card, or chipset).
4. Right-click it, choose Properties, go to the Driver tab, click Roll Back Driver.
5. If the button is grayed out, you can't roll back – you'll need to download the previous driver version from the manufacturer's site and install it manually.

Option B – Clean install Windows

This is the most reliable fix. It wipes everything and starts fresh.

1. On another PC, download the Windows Media Creation Tool from Microsoft's site.
2. Use it to create a bootable USB drive (at least 8GB).
3. Boot your broken PC from that USB (you may need to change boot order in BIOS – typically pressing F2, F12, or Del at startup).
4. On the install screen, click Install now, accept the license, then choose Custom: Install Windows only (advanced).
5. Delete all partitions on the target drive. Yes, all of them. Then click Next. Windows will create the necessary partitions automatically.
6. Follow the prompts to set up Windows. This takes about 30-60 minutes.

Expected result: A completely fresh Windows installation. The BSOD will be gone unless your hardware is physically damaged.

Option C – Check for malware with a bootable scanner

Sometimes rootkits cause this. A bootable antivirus can find them.

1. On a working PC, download a bootable antivirus like Kaspersky Rescue Disk or Bitdefender Rescue CD.
2. Burn it to a USB (using Rufus) or CD.
3. Boot your broken PC from that media. It'll load a Linux environment with the scanner.
4. Run a full scan. This can take hours but catches deep infections.

Expected result: If malware is the cause, the scanner will clean it. After that, try booting Windows normally.

Prevention tips for next time

• Never install drivers from random sites. Only download from the hardware manufacturer (NVIDIA, AMD, Intel, Realtek) or Windows Update.
• Keep Windows fully updated. Microsoft releases patches for kernel vulnerabilities monthly. Enable automatic updates.
• Run a full antivirus scan weekly. Windows Defender is fine, but add a second opinion scan with Malwarebytes every month.
• Don't use system cleaners like CCleaner. They delete registry entries that are needed for the LDT. I've seen CCleaner cause this exact error.
• If you're running old software (like a 16-bit DOS program), use a virtual machine instead of running it directly on Windows. That software is what messes with the LDT.

I've fixed this error maybe thirty times in my career. Nine times out of ten, it's a bad driver that Driver Verifier catches. But when it's not, a clean install is the only sensible path. Don't waste days trying every obscure registry hack – start clean.