| Previous | Next |
| AGP_GART_CORRUPTION | KERNEL_EXPAND_STACK_ACTIVE |
AGP_ILLEGALLY_REPROGRAMMED
Unauthorized AGP hardware reprogramming for AGP_ILLEGALLY_REPROGRAMMED
AGP_ILLEGALLY_REPROGRAMMED is bug check code 0x00000106. This bug check indicates that Windows detected AGP hardware configuration being changed outside the expected graphics/chipset ownership path. It is a platform/driver integrity issue in the legacy AGP stack.
How to read it in a dump for AGP_ILLEGALLY_REPROGRAMMED
- The suspect component can be a chipset driver, display miniport, firmware path, or low-level utility touching registers.
- The question is who changed AGP configuration and whether that change races the graphics stack.
- It is not a normal display mode-set error.
What to check for AGP_ILLEGALLY_REPROGRAMMED
- Review low-level graphics/chipset utilities, unsigned drivers, overclocking tools, and firmware updates.
- Check whether the system is old AGP hardware, a VM, or an emulator presenting AGP-like state.
- Use a full dump to inspect the graphics and bus-driver stack.
References for AGP_ILLEGALLY_REPROGRAMMED
Dump evidence for AGP_ILLEGALLY_REPROGRAMMED
For AGP_ILLEGALLY_REPROGRAMMED, 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_ILLEGALLY_REPROGRAMMED, allStat summarizes the condition as “The AGP HW has been reprogrammed by an unauthorized agent.”; 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_ILLEGALLY_REPROGRAMMED
- Run WinDbg
!analyze -v, then inspect the documented meaning of each AGP_ILLEGALLY_REPROGRAMMED parameter instead of relying only on the probably-caused-by line. - For AGP_ILLEGALLY_REPROGRAMMED, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with agp / illegally / reprogrammed.
- For AGP_ILLEGALLY_REPROGRAMMED, 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_ILLEGALLY_REPROGRAMMED before collecting the dump and event logs. For AGP_ILLEGALLY_REPROGRAMMED, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Dump evidence for AGP_ILLEGALLY_REPROGRAMMED
For AGP_ILLEGALLY_REPROGRAMMED, 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_ILLEGALLY_REPROGRAMMED, allStat summarizes the condition as “The AGP HW has been reprogrammed by an unauthorized agent.”; 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_ILLEGALLY_REPROGRAMMED
- Run WinDbg
!analyze -v, then inspect the documented meaning of each AGP_ILLEGALLY_REPROGRAMMED parameter instead of relying only on the probably-caused-by line. - For AGP_ILLEGALLY_REPROGRAMMED, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with agp / illegally / reprogrammed.
- For AGP_ILLEGALLY_REPROGRAMMED, 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_ILLEGALLY_REPROGRAMMED before collecting the dump and event logs. For AGP_ILLEGALLY_REPROGRAMMED, 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.