| Previous | Next |
| DRIVER_CORRUPTED_SYSPTES | POOL_CORRUPTION_IN_FILE_AREA |
DRIVER_INVALID_STACK_ACCESS
The result bug check has a value of 0x000000DC. This indicates that a driver accessed a stack address that lies below the stack pointer of the stack's thread.
Important
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
DRIVER_INVALID_STACK_ACCESS Parameters
None
Remarks
for it, The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.
Dump evidence
Preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line. - Find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with driver / stack / access.
- keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by this result before collecting the dump and event logs. Recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Distinctive failure boundary
This result identifies driver access outside a valid stack lifetime. Inspect the saved stack pointer, trap frame, thread transition, IRQL, and driver code that retained a pointer to stack storage after the owning frame or thread context ended.
Separating the result from neighboring bug checks
Look for asynchronous callbacks, DMA completions, work items, or deferred procedures that capture addresses of local variables. Preserve the original dump and use the documented parameters and stack to verify this distinction before changing drivers or platform configuration.
Looking for a different code? Search another status or error code.