SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

Code: 0xc1 (193)

As HRESULT:

S: 0 (Success)
C: 0 (Microsoft-defined)
N: 0 (Not an NTSTATUS value)
Facility: 0x000 (FACILITY_NULL: Default)
Code: 0x00c1 (193)

As NTSTATUS:

Sev: 0 (STATUS_SEVERITY_SUCCESS)
C: 0 (Microsoft-defined)
Facility: 0x000 (Default)
Code: 0x00c1 (193)

Parameters

Parameter	Description
Address that the driver tried to free	Reserved
Address that the driver tried to free	Bytes requested
Address that the driver tried to free	Address where bits are corrupted
Address that the driver tried to free	Address where bits are corrupted
Current IRQL	Pool type
Current IRQL	Pool type
Address that the driver tried to free	Address where one bit is corrupted

Description

The SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION bug check has a value of 0x000000C1. This indicates that the driver wrote to an invalid section of the special pool.

Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Cause

A driver has written to an invalid section of the special pool.

Resolution

Obtain a backtrace of the current thread. This backtrace will usually reveal the source of the error.

For information about the special pool, consult the Driver Verifier section of the Windows Driver Kit.

Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.

Associated Modules

Module	Code	Found in	Description
EventCreate.exe	0xc1	78.11011	%1
KernelBase.dll	0xc1	78.1	%1 is not a valid Win32 application.
dsreg.dll	0xc1	1011	The repair join information operation completed successfully. Tenant ID: %1 Device ID: %2 Join UPN: %3 Join Type: %4 (%5) Request Id: %6 Time: %7 Http Status: %8
kernel32.dll	0xc1	78.11011	%1 is not a valid Win32 application.
nslookup.exe	0xc1	78.11011	%1!d! day
webservices.dll	0xc1	78.11011	There was an error closing the TCP socket.
6 entries