BSOD 0x107 (KERNEL_EXPAND_STACK_ACTIVE): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: A thread was terminating or calling out while an expanded kernel stack was active.

Could be also:
Constant	Type	OS
STATUS_SOME_NOT_MAPPED	NTSTATUS	Windows

Previous	Next
AGP_ILLEGALLY_REPROGRAMMED	THIRD_PARTY_FILE_SYSTEM_FAILURE

KERNEL_EXPAND_STACK_ACTIVE

Expanded kernel stack still active for KERNEL_EXPAND_STACK_ACTIVE

KERNEL_EXPAND_STACK_ACTIVE is bug check code 0x00000107.

Some kernel paths temporarily expand a thread stack for complex callouts. This bug check indicates the thread tried to terminate or make a Win32 callout while that expanded stack state was still active, suggesting broken stack/lifetime ordering.

How to read it in a dump

Identify the thread, expanded-stack state, and callout path.
Graphics, file-system, registry, or callback-heavy drivers can create deep stack paths.
Stack usage and cleanup order matter more than raw memory usage.

What to check

Inspect stack expansion frames and the driver just above the kernel transition.
Look for callbacks that terminate a thread or call out while cleanup is incomplete.
Use verifier and stack usage analysis for suspect drivers.

References

Looking for a different code? Search another status or error code.