| Previous | Next |
| END_OF_NT_EVALUATION_PERIOD | SYSTEM_LICENSE_VIOLATION |
INVALID_REGION_OR_SEGMENT
The result bug check has a value of 0x00000099. This bug check indicates that ExInitializeRegion or ExInterlockedExtendRegion was called with an invalid set of parameters.
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.
INVALID_REGION_OR_SEGMENT Parameters
None
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 region / or / segment.
- 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 invalid memory region or segment state. Inspect the virtual-address region, section or segment object, VAD/PTE state, and the operation that changed the mapping. Corruption here concerns memory-manager bookkeeping, not an ordinary invalid user handle.
Separating the result from neighboring bug checks
Compare mapping creation, protection changes, truncation, image loading, and teardown around the address named by the dump parameters. 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.