| Previous | Next |
| AGP_INVALID_ACCESS | AGP_ILLEGALLY_REPROGRAMMED |
AGP_GART_CORRUPTION
AGP GART corruption for AGP_GART_CORRUPTION
AGP_GART_CORRUPTION is bug check code 0x00000105. The GART maps graphics-aperture addresses to physical memory for AGP devices. This bug check means Windows detected corrupted translation state in that mapping path.
How to read it in a dump for AGP_GART_CORRUPTION
- The display miniport, chipset/AGP driver, firmware settings, or memory corruption can be involved.
- The crash should be analyzed as an address-translation corruption, not simply as a rendering failure.
- Modern PCIe GPUs normally use different mechanisms, so this is usually legacy or compatibility hardware.
What to check for AGP_GART_CORRUPTION
- Check system memory, chipset drivers, display drivers, and BIOS AGP settings.
- Look for DMA or driver writes that could corrupt mapping tables.
- Compare with AGP_INVALID_ACCESS and AGP_INTERNAL for neighboring failures.
References for AGP_GART_CORRUPTION
Dump evidence for AGP_GART_CORRUPTION
For AGP_GART_CORRUPTION, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. For AGP_GART_CORRUPTION, allStat summarizes the condition as “The Graphics Aperture Redirection Table (Gart) is corrupt.”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for AGP_GART_CORRUPTION
- Run WinDbg
!analyze -v, then inspect the documented meaning of each AGP_GART_CORRUPTION parameter instead of relying only on the probably-caused-by line. - For AGP_GART_CORRUPTION, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with agp / gart / corruption.
- For AGP_GART_CORRUPTION, 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 AGP_GART_CORRUPTION before collecting the dump and event logs. For AGP_GART_CORRUPTION, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Dump evidence for AGP_GART_CORRUPTION
For AGP_GART_CORRUPTION, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. For AGP_GART_CORRUPTION, allStat summarizes the condition as “The Graphics Aperture Redirection Table (Gart) is corrupt.”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for AGP_GART_CORRUPTION
- Run WinDbg
!analyze -v, then inspect the documented meaning of each AGP_GART_CORRUPTION parameter instead of relying only on the probably-caused-by line. - For AGP_GART_CORRUPTION, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with agp / gart / corruption.
- For AGP_GART_CORRUPTION, 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 AGP_GART_CORRUPTION before collecting the dump and event logs. For AGP_GART_CORRUPTION, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.