Solved: BAD POOL CALLER (0X0000006D) BSOD Crash on Windows 10/11

Solved: BAD POOL CALLER (0X0000006D) BSOD Crash on Windows 10/11

The BAD_POOL_CALLER (0x0000006D) Blue Screen of Death (BSOD) is a frustrating error that can occur in Windows 10 or 11, often leading to system crashes and data loss if not addressed. This error typically indicates a problem with memory management, where the system attempts to access invalid memory addresses. While it may seem technical, this guide will walk you through understanding, diagnosing, and fixing this issue without requiring advanced technical skills.

What Does BAD_POOL_CALLER (0x0000006D) Mean?

The BAD_POOL_CALLER error occurs when Windows tries to use memory that has already been freed or is corrupted. This can happen due to hardware issues, driver conflicts, faulty RAM, or system file corruption. Unlike some BSOD errors, this one doesnt always provide a clear cause in the error log, making it tricky to pinpoint the exact issue.

Common Causes of BAD_POOL_CALLER (0x0000006D)

The following are the most common reasons for this BSOD:

  • Faulty or incompatible drivers, especially graphics, storage, or network drivers.
  • Corrupted system files due to improper shutdowns, malware, or failed updates.
  • Bad RAM (Random Access Memory) or hardware issues, such as failing hard drives.
  • Overclocked hardwareg that isnt properly stabilized.
  • Conflicting software, including third-party applications or Windows updates.

Step-by-Step Fixes for BAD_POOL_CALLER (0x0000006D)

Method 1: Run System File Checker (SFC) and DISM

Corrupted system files can trigger this error. Use Windows built-in tools to repair them:

  • Press **Win + X** and select **Terminal (Admin)** or open Command Prompt as Administrator.
  • Run the following commands one by one, pressing Enter after each:
    DISM /Online /Cleanup-Image /RestoreHealth
    sfc /scannow
  • Restart your PC and check if the issue persists.

Method 2: Check for Faulty Hardware (RAM)

Faulty RAM can cause memory-related BSODs. Test it using Windows Memory Diagnostic:

  • Press **Win + R**, type mdsched.exe, and hit Enter.
  • Select **Restart now and check for problems** (this will reboot your PC).
  • Follow the on-screen instructions. If errors are found, consider replacing your RAM.

Method 3: Update or Roll Back Drivers

Outdated or conflicting drivers often trigger this error. Heres how to fix them:

  • Press **Win + X** and select **Device Manager**.
  • Expand categories like **Display adapters**, **Storage controllers**, or **Network adapters**.
  • Right-click each device, choose **Update driver**, then **Search automatically for drivers**.
  • If the issue started after a recent update, right-click the driver and select **Properties** > **Roll Back Driver** (if available).

Method 4: Run CHKDSK to Check Disk Errors

Corrupted storage can also cause this BSOD. Use CHKDSK to scan your hard drive:

  • Open Command Prompt as Administrator.
  • Run:
    chkdsk C: /f /r

    (Replace **C:** with the correct drive letter if needed.)

  • Press **Y** to confirm, then restart your PC.

Method 5: Test for Overclocking Issues

If youve overclocked your CPU/GPU, reset BIOS settings to default:

  • Restart your PC and enter BIOS (usually by pressing **Del** or **F2** during boot).
  • Reset all overclocking settings to default.
  • Save changes and exit. Monitor for stability.

Method 6: Check for Malware or Conflicting Software

Malware or conflicting programs can corrupt system files. Run a full scan:

  • Open **Windows Security** > **Virus & threat protection** > **Quick Scan**. Wait for results.
  • If no threats are found, try disabling recently installed software to check for conflicts.

Preventing Future BAD_POOL_CALLER Errors

To avoid this BSOD in the future:

  • Keep Windows and drivers updated via **Settings > Update & Security**.
  • Avoid abrupt shutdowns; always use **Shut down or Restart** properly.
  • Regularly run sfc /scannow and chkdsk C: /f to check for corruption.
  • Monitor hardware health using tools like Windows Memory Diagnostic.

FAQ: Common Questions About BAD_POOL_CALLER (0x0000006D)

  • Is this error hardware or software-related?

    It can be either. Faulty RAM, graphics cards, or hard drives are common hardware causes, while driver issues or corrupted files are software-related.

  • Will a clean install fix it?

    A clean install is a last resort but may resolve deep system corruption. Back up your data first using File History or cloud storage.

  • Can third-party tools like CCleaner help?

    CCleaner can remove junk files, but its not a direct fix for BSODs. Focus on driver updates and system file repairs instead.

  • Why does this happen after a Windows update?

    Updates sometimes introduce bugs or conflict with existing drivers. Rolling back the update or waiting for patches often helps.

Final Thoughts

The BAD_POOL_CALLER (0x0000006D) BSOD is usually fixable with patience and systematic troubleshooting. Start with system file repairs, check hardware health, and update drivers before considering deeper solutions. If the issue persists after trying these steps, consult Microsoft Support or a professional technician for advanced diagnostics.

By following this guide, you should be able to resolve the error and prevent future crashes. Always back up important data to avoid losing progress during troubleshooting!

Last Updated: December 13, 2025

Tested on: Windows 10 (22H2) & Windows 11 (23H2)

Leave a Comment