| Previous | Next |
| INVALID_AFFINITY_SET | INVALID_PROCESS_ATTACH_ATTEMPT |
INVALID_DATA_ACCESS_TRAP
INVALID_DATA_ACCESS_TRAP is bug check 0x04. Microsoft describes it as an incorrect data access trap and marks the stop as very infrequent. The individual reference does not publish stable meanings for parameters 1 through 4, so the bug-check value does not itself reveal the accessed address, access type, or faulting instruction.
Use the captured trap context
The word “trap” is meaningful as a failure category, but it is not a substitute for the processor state stored in the crash dump. Use the debugger's analysis and symbolized stack to determine what context is actually available. Do not copy the parameter layout from IRQL_NOT_LESS_OR_EQUAL or another memory-access stop.
Diagnostic steps
- Preserve the exact architecture, build, and all four raw arguments.
- Run
!analyze -show 0x04and then!analyze -von the original dump. - Follow the stack and any debugger-reported trap/context information to the responsible execution path before changing drivers or hardware.
References
- Microsoft: Bug Check 0x04 INVALID_DATA_ACCESS_TRAP
- Microsoft: analyze bug check data
- Microsoft: !analyze extension
Looking for a different code? Search another status or error code.