Fix STATUS_INVALID_LDT_DESCRIPTOR (0xC000011A) on Windows

First: Check for outdated or buggy software (most common cause)

In my experience, this error is almost always tied to an old program that's trying to do something low-level with the CPU. The LDT (Local Descriptor Table) is a Windows internals thing—ordinary apps don't touch it. So when you see 0xC000011A, it's usually a program that's either ancient, poorly coded, or using a compatibility hack that Windows 10/11 doesn't like anymore.

I had a client last month whose accounting software from 2009 kept crashing with this error every time they tried to print a report. The fix was simple: update the software. The vendor had a patch that specifically addressed LDT handling on modern Windows.

What to do:

1. Update the application that's crashing. Check the vendor's website manually—don't rely on the built-in updater, it might be broken.
2. If no update exists, try running the program in compatibility mode. Right-click the .exe, go to Properties > Compatibility, and try Windows 7 or Windows XP SP3.
3. If compatibility mode doesn't help, uninstall the program and look for an alternative. You're wasting time if you keep fighting it.

Also, check Event Viewer. Open it, go to Windows Logs > Application, and look for errors around the time of the crash. The source will tell you exactly which app is at fault.

Second: Corrupt system files (DLL and SFC)

Sometimes the LDT issue isn't the app itself—it's a corrupt system DLL that the app depends on. Windows has a built-in tool for this, and it's free. Run it. It takes a few minutes, but it's worth doing before you go down the rabbit hole of reinstalling things.

sfc /scannow

Run that from an elevated Command Prompt (right-click Start > Command Prompt (Admin)). It'll scan all protected system files and replace any that are corrupted. If it finds issues and fixes them, reboot and try again.

If SFC doesn't find anything, use DISM to repair the system image:

DISM /Online /Cleanup-Image /RestoreHealth

This is slower—might take 15-20 minutes—but it fixes underlying corruption that SFC can't touch. I've seen DISM alone resolve this error on a Windows 10 machine that had been running for years without an update.

Third: Outdated or conflicting drivers

Less common, but I've seen it. A driver—especially a graphics driver or a virtualization driver—can interfere with LDT operations. The error might appear when you launch a game or a VM software like VMware or VirtualBox.

Here's the thing: you don't need to update every driver you own. Just focus on the ones that matter for this error. Start with graphics drivers, since they're the most likely to be loaded when the error hits. Go to the manufacturer's site (NVIDIA, AMD, Intel) and download the latest version. Don't use Windows Update for this—it's often behind.

If you're using VMware or VirtualBox, also check for updates. Those tools install kernel-level drivers, and an old version can easily trigger 0xC000011A. I had a user whose VirtualBox 6.0 crashed with this error every time they started a VM. Upgrading to 7.0 fixed it completely.

To see if a driver is at fault, do a clean boot. That loads only essential drivers, and if the error goes away, you know it's a driver conflict. Use msconfig, disable all non-Microsoft services, and restart.

Quick-Reference Summary Table

If none of that works, you might be dealing with a deeper issue like a failing CPU or a motherboard that's about to die—but that's rare. Give these a try first, and you'll likely get it sorted without pulling your hair out.