| Previous | Next |
| SHARED_RESOURCE_CONV_ERROR | QUOTA_UNDERFLOW |
KERNEL_APC_PENDING_DURING_EXIT
The result bug check has a value of 0x00000020. This indicates that an asynchronous procedure call (APC) was still pending when a thread exited.
Important
KERNEL_APC_PENDING_DURING_EXIT Parameters
| Parameter | Description |
|---|---|
1 |
The address of the APC found pending during exit |
2 |
The thread's APC disable count |
3 |
The current IRQL |
4 |
Reserved |
Cause
The key data item is the APC disable count (Parameter 2) for the thread. If the count is nonzero, it will indicate the source of the problem.
The APC disable count is decremented on the KERNEL_APC_PENDING_DURING_EXIT path each time a driver calls KeEnterCriticalRegion, FsRtlEnterFileSystem, or acquires a mutex.
The APC disable count is incremented on the path each time a driver calls KeLeaveCriticalRegion, KeReleaseMutex, or FsRtlExitFileSystem.
Because these calls should always be in pairs, the APC disable count should be zero when a thread exits. A negative value indicates that a driver has disabled APC calls without re-enabling them. A positive value indicates that the reverse is true.
If you ever see this error, be very suspicious of all drivers installed on the machine -- especially unusual or non-standard drivers.
This current IRQL (Parameter 3) should be zero. If it is not, the driver's cancellation routine may have caused this bug check by returning at an elevated IRQL. In this case, carefully note what was running (and what was closing) at the time of the crash, and note all of the installed drivers at the time of the crash. The cause in this case is usually a severe bug in a driver.
Resolution
for it, The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.
Looking for a different code? Search another status or error code.