0XC000070F: Thread Pool Released During Callback
This Windows bug check means a thread pool was freed while a thread was still posting a callback to it. It's almost always a driver or antivirus conflict.
Cause 1: Corrupt or outdated display drivers (real fix 9 times out of 10)
When I see 0XC000070F in crash dumps, the display driver is almost always the culprit. Specifically, win32kbase.sys and dxgkrnl.sys are flagged in the stack. Those are tied to your graphics driver. The thread pool gets yanked away when the driver does something stupid—like freeing memory it shouldn’t while another thread is still using it.
Step-by-step fix
- Boot into Safe Mode with Networking. On Windows 10/11, hold Shift while clicking Restart, then go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 5.
- Once in Safe Mode, open Device Manager. Right-click Start > Device Manager.
- Expand Display adapters. Right-click your GPU (NVIDIA, AMD, or Intel) and choose Uninstall device. Check the box “Delete the driver software for this device” if it appears. Click Uninstall.
- Reboot normally. Windows will install a generic Microsoft Basic Display Adapter driver. This isn’t ideal for gaming, but it’s stable. If the blue screen stops, you’ve found the cause.
- Now go to your GPU manufacturer’s site (NVIDIA, AMD, or Intel) and download the latest driver. But don’t install it yet. Use Display Driver Uninstaller (DDU) in Safe Mode to completely scrub the old driver. Then install the fresh one.
- If the latest driver still crashes, roll back to a version from 3-6 months ago. I’ve seen this happen with NVIDIA 5xx series drivers on Windows 11 22H2. Go to the NVIDIA driver archive and grab version 527.56, for example.
Expected outcome after DDU + fresh install: The error should disappear. If it doesn’t, move to cause 2.
Cause 2: Antivirus software interfering with thread pool management
Third-party antivirus programs—especially Norton, McAfee, and Webroot—have a bad habit of hooking into system thread pool routines. When the AV tries to scan or block a callback, it can accidentally release the pool. The error message will still show 0XC000070F, but the crash stack will point to ntoskrnl.exe plus a driver like mwac.sys (Malwarebytes) or SymELAM.sys (Norton).
Step-by-step fix
- Boot into Safe Mode (same method as above).
- Open Control Panel > Programs and Features. Uninstall your antivirus completely. Don’t just disable it—uninstall.
- Reboot normally. If Windows Defender kicks in and the crashes stop, you’ve found the culprit.
- Switch to Windows Defender as your primary AV. For Windows 10/11, it’s more than enough for most people. If you need a third-party tool, try Bitdefender Free—I’ve seen far fewer thread pool issues with it.
Expected outcome: After uninstalling the third-party AV, the blue screen should not return. If it does, move to cause 3.
Cause 3: Faulty USB device or driver (especially older USB 2.0 hubs)
This one’s sneaky. A USB device—like a printer, external hard drive, or even a cheap USB hub—can trigger the thread pool release if its driver has a race condition. I’ve fixed this on a Dell Optiplex 7080 that kept crashing with 0XC000070F until the user unplugged an old USB 2.0 memory card reader.
Step-by-step fix
- Shut down the PC. Unplug all USB devices except mouse and keyboard.
- Boot up. Use the PC normally for a few hours. If no crash, shut down again and plug in one device at a time, testing each for a day.
- When you find the offending device, check the manufacturer’s site for a newer driver. If no driver exists, replace the device.
- If you can’t isolate the device, try updating the USB host controller driver. In Device Manager, expand Universal Serial Bus controllers. Right-click each entry named “USB Root Hub” or “USB Composite Device” and choose Update driver > Browse my computer > Let me pick > Microsoft USB Root Hub (standard).
Expected outcome: After removing the offending USB device, the error stops. Replace the device to confirm.
Quick-reference summary table
| Root Cause | Fix | Tools Needed |
|---|---|---|
| Corrupt display driver | Uninstall GPU driver in Safe Mode, DDU clean, reinstall latest or older stable version | DDU, driver installer from GPU vendor |
| Third-party antivirus | Uninstall AV in Safe Mode, switch to Windows Defender | Control Panel |
| Faulty USB device/driver | Remove all USB devices, test one by one; update USB host drivers | Device Manager |
Still crashing? If none of these fix it, you’re looking at a corrupted Windows system file or a failing hard drive. Run sfc /scannow in an admin Command Prompt, then dism /online /cleanup-image /restorehealth. If that passes, run chkdsk c: /f and let it check for bad sectors. I’ve seen 0XC000070F from dying SSDs too—especially older Crucial drives.
Was this solution helpful?