Fixing KERNEL APC PENDING DURING EXIT (0X00000020) Stop Code on Windows 10 & 11 Step by Step
The KERNEL APC PENDING DURING EXIT (0x00000020) stop code, also known as a Blue Screen of Death (BSOD), is an error that can suddenly appear on Windows 10 or Windows 11, causing your system to crash and restart. This error typically occurs when the kernel detects an issue with asynchronous procedure calls (APCs) while processing them, often related to hardware conflicts, corrupted system files, or driver problems. While frustrating, this issue is usually fixable with the right troubleshooting steps.
In this guide, well walk you through what causes this error, how to identify it, and most importantlyhow to resolve it effectively using safe and tested methods. Whether you’re experiencing frequent crashes or just a single occurrence, following these steps will help stabilize your system and prevent future occurrences.
—
What Causes the KERNEL APC PENDING DURING EXIT (0x00000020) Error?
The 0x00000020 error is a critical system failure that usually happens when:
- Corrupted or outdated device driversEspecially graphics, network, or storage drivers.
- Faulty hardware componentsSuch as RAM, hard drives, or overclocked CPU/GPU.
- Malware or system file corruptionDue to incomplete updates, improper shutdowns, or disk errors.
- Incompatible software or driversNewly installed programs or drivers that conflict with Windows core functions.
- Overheating or power issuesEspecially in laptops or systems under heavy load.
This error often appears during normal operation, gaming, or when accessing certain applications. It can also be triggered after a Windows update, so its important to check for system integrity and driver compatibility.
—
How to Fix KERNEL APC PENDING DURING EXIT (0x00000020) Step-by-Step
Lets go through the most effective solutions in order of simplicity and impact. Start with the easiest steps first, as they often resolve the issue without needing advanced tools.
—
###
1. Restart Your Computer
The simplest stepbut sometimes overlooked. A forced restart can clear temporary glitches that trigger this error.
- Hold down the power button for 510 seconds to force a shutdown if Windows doesnt respond.
- Wait 30 seconds, then press the power button to turn your PC back on.
- If the error reappears after booting, proceed to the next steps.
—
###
2. Check for Hardware Issues (RAM and Storage)
Faulty RAM or a failing hard drive can cause this BSOD repeatedly. Run diagnostics to rule out hardware problems.
#### **Check RAM with Windows Memory Diagnostic**
- Press Win + R, type
mdsched.exe, and press Enter. - Select Restart now and check for problems (recommended).
- The tool will test your RAM. If errors are found, consider reseating the RAM or testing with a different stick if you have multiple modules.
#### **Run CHKDSK to Check Disk Errors**
- Open Command Prompt as Administrator: Press Win + X, then select Terminal (Admin).
- Type the following command and press Enter:
chkdsk C: /f /r - If prompted, type Y to confirm. The scan will run on the next restart.
- After rebooting, check for any reported errors in Event Viewer (search for “chkdsk” in the log).
—
###
3. Update or Roll Back Drivers
Outdated or incompatible drivers are a leading cause of this BSOD. Focus on these key components:
#### **Update All Drivers via Windows Update**
- Press Win + I, go to Update & Security > Windows Update.
- Click Check for updates. Install any available driver or optional updates.
- Restart your PC after updating.
#### **Manually Update Problematic Drivers**
If you suspect a specific driver (e.g., GPU, chipset), use Device Manager:
- Press Win + X, then select Device Manager.
- Expand categories like Display adapters, Sound, video and game controllers, or System devices.
- Right-click the device (e.g., your GPU), select Update driver > Search automatically for drivers.
- If no updates are found, try rolling back the driver:
- Right-click the same device and choose Properties.
- Go to the Driver tab and click Roll Back Driver (if available).
#### **Use Manufacturers Tools**
For graphics drivers (NVIDIA, AMD), use their official software (e.g., GeForce Experience) to update or reinstall drivers.
—
###
4. Run System File Checker (SFC) and DISM
Corrupted system files can trigger this error. Use these built-in tools to repair them.
#### **Run SFC Scan**
- Open Command Prompt as Administrator.
- Type the following command and press Enter:
sfc /scannow - Wait for the scan to complete (may take several minutes). Restart if prompted.
#### **Run DISM Repair**
- In the same Command Prompt window, type:
DISM /Online /Cleanup-Image /RestoreHealth - Wait for the process to finish (this may take longer than SFC). Restart your PC afterward.
—
###
5. Check for Malware and Overheating
Malware or overheating can mimic this error. Take preventive steps:
#### **Scan for Malware**
- Open Windows Security (press Win + I > Update & Security > Virus & threat protection).
- Click Quick scan. If threats are found, follow the removal steps.
- For deeper scans, use Microsoft Defender Offline:
- Go to Virus & threat protection > Scan options.
- Select Microsoft Defender Offline scan and run it.
#### **Monitor System Temperature**
- Use third-party tools like HWMonitor or HWiNFO to check CPU/GPU temperatures.
- Ensure no core exceeds safe limits (e.g., under 85C for CPUs, 90C for GPUs). Clean dust from fans if needed.
—
###
6. Test for Overclocking or BIOS Issues
If youve overclocked your CPU/GPU or have custom BIOS settings, revert to defaults:
- Restart your PC and enter BIOS (usually by pressing F2, F12, DEL, or ESC during boot).
- Look for options like Load Optimized Defaults or Reset to Defaults. Select it and save changes.
- Disable XMP/DOCP (if enabled) under RAM settings.
—
###
7. Perform a Clean Boot to Isolate Software Conflicts
A clean boot starts Windows with only essential drivers, helping identify if third-party software is causing the issue.
- Press Win + R, type
msconfig, and press Enter. - Go to the Services tab. Check Hide all Microsoft services, then click Disable all.
- Go to the Startup tab, click Open Task Manager, and disable all startup items.
- Restart your PC. If no BSOD occurs, a third-party program is likely the culprit. Re-enable services/apps one by one to identify the offender.
—
###
8. Reset or Reinstall Windows (Last Resort)
If all else fails, a clean install may be necessary.
- Back up your files using an external drive or cloud storage.
- Create a Windows installation media (USB) using the Media Creation Tool.
- Boot from the USB, select Repair your computer > Troubleshoot > Reset this PC, and choose Remove everything. This keeps files if you opt for “Keep my files” (not recommended here).
- Follow on-screen instructions to complete the setup.
—
FAQ: Common Questions About KERNEL APC PENDING DURING EXIT (0x00000020)
Q: Will this error damage my hardware?
A: No, a BSOD doesnt physically harm your hardware. However, frequent crashes can lead to data loss or wear over time, so addressing the root cause is important.
Q: Should I replace my RAM if CHKDSK finds errors?
A: If CHKDSK reports bad sectors but no other issues are found, try reseating the RAM. Only consider replacement if errors persist after multiple tests or if you see physical damage (e.g., bulging capacitors).
Q: Can I prevent this error in the future?
A: Yes! Regularly update drivers, avoid overclocking unless necessary, and use reliable antivirus software. Also, keep your system clean by removing unused programs and monitoring temperatures.
Q: Why does this happen after a Windows update?
A: Updates can introduce compatibility issues with existing drivers or system files. Rolling back the update (via Settings > Update & Security > Recovery > Go back) may help, but test thoroughly afterward.
Q: Is this error related to my SSD/HDD?
A: Possibly. If your storage device is failing, you may see this error during heavy I/O operations (e.g., large file transfers). Test with chkdsk and manufacturer diagnostics (e.g., Samsung Magician for SSDs).
—
Final Notes
The KERNEL APC PENDING DURING EXIT (0x00000020) error is usually fixable with patience and systematic troubleshooting. Start with simple steps like restarts and driver updates, then move to deeper diagnostics if needed. If the issue persists after trying all methods, consider hardware testing or professional support.
If youve successfully resolved this error using these steps, share your experience in the commentsyour feedback helps others facing the same challenge! For ongoing issues, check Microsofts official support page or seek help from community forums like Microsoft Answers.
Stay proactive with regular maintenance (updates, malware scans, and hardware checks) to keep your system stable. Happy computing!
Last Updated: December 13, 2025
Tested on: Windows 10 (22H2) & Windows 11 (23H2)