- Software and digital services
- Operating system
BAD_POOL_CALLER
Windows BAD_POOL_CALLER: invalid kernel memory pool request
Risk level
Medium
Proceed carefully and stop if the check is unclear.
Urgency
High
Quick answer
A kernel thread requested or freed pool memory improperly, for example by freeing the same block twice. Start by undoing the last driver or driver-bundling program you installed and bring Windows and your drivers up to date.
Safety first
Stop and check this first
- Rolling back drivers, uninstalling programs or restoring the system can cost you recent data: copy your documents and photos off the system drive first.
- Do not turn on Driver Verifier for every driver at once: Microsoft warns it can make the PC unusable and produce more dumps.
Safe checks you can perform
- What you installed right before the stops
- Windows Update and maker drivers
- Built-in RAM test in Windows
- Restore point from before the first crash
Leave these tasks to a qualified professional
- Do not attempt this professional task: Driver Verifier using memory pool options
- Do not attempt this professional task: Case with the driver vendor
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Driver Verifier using memory pool options
What they doA technician enables Driver Verifier with the memory pool options on a small group of suspect drivers so the next crash names the culprit.
They must show youthe dump produced with Verifier active and the driver named in the !analyze -v output.
In writingwhich drivers were verified, which one was identified and confirmation that Verifier was turned off at the end.
Case with the driver vendor
What they doOnce the driver is identified, its vendor or your PC maker should supply a fixed version or explain how to disable the service in the meantime.
They must show youthe driver version they recommend and its compatibility with your Windows version.
In writingthe case number, the fixed version and whether any service should stay disabled.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
What you installed right before the stops
- Who:
- you, after copying your documents to another drive or the cloud.
- How:
- review in Settings the apps and driver updates from the days before the first crash; uninstall the newest one that installs its own drivers, such as antivirus, VPN or peripheral utilities, or roll the driver back in Device Manager.
- Result that matters:
- finding out whether the stop depends on one specific software change.
- If the blue screens stop, that program or driver was the source and you should wait for a fixed version from its maker.
- If they continue, reinstall it if you need it and move on to updates.
- Evidence to keep:
- name and version of what you removed or rolled back and the date of the change.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Windows Update and maker drivers
- Who:
- you, with the PC online.
- How:
- go to Settings, Windows Update and select Check for updates until nothing is pending; then download the latest drivers from the website of your PC maker or of each component.
- Result that matters:
- ruling out a fault that Microsoft or the maker has already fixed.
- If after updating it does not return over several days of normal use, the update solved the problem.
- If it comes back with everything current, keep the dump and move on to the memory test.
- Evidence to keep:
- screenshot of the update history and the driver versions installed.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Built-in RAM test in Windows
- Who:
- you, closing every program first.
- How:
- in the Control Panel search type Memory, open Diagnose your computer's memory problems and accept the restart; back on the desktop, check the System log in Event Viewer and find MemoryDiagnostics-Results.
- Result that matters:
- confirming or clearing physical memory as a suspect.
- If memory errors appear, stop testing drivers and ask for a hardware check.
- If none appear, the trail leads back to drivers and dump analysis.
- Evidence to keep:
- screenshot of the diagnostic result with its date.
Evidence: Bug Check 0xC2 BAD_POOL_CALLER
Restore point from before the first crash
- Who:
- you, with a backup of your personal files done.
- How:
- from Recovery options use System Restore and pick a point created before the first blue screen; if Windows will not stay up, boot into Safe Mode first.
- Result that matters:
- returning to a system state that had no stops.
- If the PC stays stable, something installed after that point caused the crash; reinstall slowly, one item at a time.
- If it crashes anyway, hand the case to a technician with the saved dump.
- Evidence to keep:
- date of the restore point used and the result after a few days.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x000000C2
- 0xC2
- BAD POOL CALLER
- STOP 0x000000C2
- stop code BAD_POOL_CALLER
What it means
According to Microsoft, bug check 0x000000C2 fires when the current thread makes a bad request to the kernel memory pool. The usual reasons are asking at an IRQL that is not allowed or freeing the same allocation twice; parameter 1 says which violation it was, such as 0x06 or 0x07 for an already freed block or 0x08 for an allocation at an invalid IRQL. Driver code is usually behind it, though Microsoft also asks you to rule out physical memory. The code on its own does not show that any part is broken.
Warnings and stop conditions
- Mediumsource verified
Rolling back drivers, uninstalling programs or restoring the system can cost you recent data: copy your documents and photos off the system drive first.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors
- Mediumsource verified
Do not turn on Driver Verifier for every driver at once: Microsoft warns it can make the PC unusable and produce more dumps.
Evidence: Stop code error or bug check troubleshooting (IT professionals)
Symptoms and causes
Probable causes · in order
- A driver mishandling memoryCommon
Microsoft attributes the stop to invalid requests by the current thread, typically a wrong IRQL or a double free of the same allocation, and asks you to locate the driver.
Evidence: Bug Check 0xC2 BAD_POOL_CALLER
- Recently updated software or driverCommon
The guide for professionals says to contact the software or hardware vendor after recent changes and, if no update exists, to disable the related service.
Evidence: Stop code error or bug check troubleshooting (IT professionals)
- Faulty physical memoryPossible
For cases with pool corruption, Microsoft recommends running Windows Memory Diagnostic to isolate RAM as a possible cause.
Evidence: Bug Check 0xC2 BAD_POOL_CALLER
Virtual technician
Does BAD_POOL_CALLER still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Stop code error or bug check troubleshooting (IT professionals)
Microsoft · 2026 · official_doc
- 2
Troubleshooting Windows unexpected restarts and stop code errors
Microsoft · 2026 · official_doc
- 3
Solución de problemas de reinicios inesperados y errores de código de detención de Windows
Microsoft · 2026 · official_doc
- 4
Bug Check 0xC2 BAD_POOL_CALLER
Microsoft · 2026 · official_doc
Was this entry useful?