STATUS_THREADPOOL_HANDLE_EXCEPTION (0xC000070A) – Fix It Now

What Actually Causes 0xC000070A

Let's cut the crap. STATUS_THREADPOOL_HANDLE_EXCEPTION with code 0xC000070A is a Windows bugcheck that happens when a thread pool wait operation fails because the handle it's waiting on is corrupted or invalid. The kernel literally throws its hands up. I see this most often on Windows 10 21H2 through 22H2, and it's crept into Windows 11 too.

The three things that trigger it, in order of frequency:

1. Bad RAM – faulty memory corrupts the handle table in the kernel. This is the #1 cause.
2. Corrupt drivers – especially third-party antivirus, VPN adapters, or old graphics drivers that mangle I/O completion ports.
3. Disk corruption – a failing SSD or HDD can cause the storage stack to return garbage handles.

Don't bother reinstalling Windows first. That's a waste of time. Start here.

Cause #1: Faulty RAM – Run MemTest86

I've seen this exact bugcheck pop up on machines with one bad stick of RAM. The error happens randomly – during a game, during a compile, even at idle. The handle that the thread pool is waiting on gets corrupted because a bit flips in memory.

The fix: Download MemTest86 (the free version is fine) and boot it from a USB stick. Let it run for at least 4 passes – that's about 4-6 hours. If you see even one red error, that stick is toast. Replace it.

If you're in a hurry and just need to confirm it's RAM, run Windows Memory Diagnostic:

mdsched.exe

But I don't trust that tool for a final verdict. It misses subtle errors. MemTest86 is the standard.

Pro tip: If you're on a laptop with soldered RAM, this is a motherboard issue. Warranty claim or new machine.

Cause #2: Corrupt Drivers – Use Driver Verifier

When it's not RAM, it's almost always a driver that's corrupting the thread pool's handle table. I've seen this with:

• Old NVIDIA drivers (versions 470.x and earlier on Win11).
• AVG or Avast antivirus – they hook into kernel handles aggressively.
• Any VPN that installs a TAP adapter (OpenVPN, NordVPN, etc.).

The fix: Run Driver Verifier (verifier.exe) to stress-test your drivers.

1. Open Command Prompt as Admin.
2. Run verifier.
3. Select Create custom settings → Next.
4. Check Special pool, Force IRQL checking, Pool tracking, Deadlock detection.
5. Select Select driver names from a list.
6. Pick all non-Microsoft drivers (sort by Provider – anything not Microsoft).
7. Reboot. The system will run slow, but if it crashes again, the bugcheck will name the driver in the Verifier log or the minidump.

To stop Verifier: boot into Safe Mode, run verifier /reset.

If you can't even boot normally, use Safe Mode to uninstall the suspect driver. For graphics, use DDU (Display Driver Uninstaller) in Safe Mode to nuke the old driver, then install the latest from the manufacturer.

Cause #3: Failing Disk – Check with CHKDSK and SMART

Less common, but I've fixed this bug on three machines where the SSD was dying. When the storage subsystem returns corrupted data for a file handle, the thread pool throws 0xC000070A.

The fix: Check your disk health first.

wmic diskdrive get status, model

If any disk shows Bad, replace it. Otherwise, run CHKDSK:

chkdsk C: /f /r

This will require a reboot. Let it run – it can take hours on a large drive.

Also check the System Event Log for Event ID 7 (disk error) or Event ID 55 (file system corruption). If you see those, your disk is on the way out.

Quick-Reference Summary Table

Start with MemTest86. I'd put money on it being your RAM. If not, Verifier. If still broken, replace the drive. Good luck – you'll fix this in an afternoon.