What does BSOD 260 (AGP_INVALID_ACCESS) mean?

 
Could be also:
ConstantTypeOS
STATUS_REPARSENTSTATUSWindows
Previous Next
MUP_FILE_SYSTEM AGP_GART_CORRUPTION

AGP_INVALID_ACCESS

AGP aperture access violation for AGP_INVALID_ACCESS

AGP_INVALID_ACCESS is bug check code 0x00000104. This legacy graphics/platform bug check belongs to the AGP era. It points to invalid access through the graphics aperture or address-translation path used by AGP display hardware and drivers.

How to read it in a dump

  • The failing driver is likely a display miniport, chipset, or AGP filter component on older systems.
  • AGP aperture configuration, GART mappings, and firmware/chipset settings are the key context.
  • Do not treat it as a modern DXGK TDR code; it is a bus/aperture mapping failure.

What to check

  • Check the display driver, chipset/AGP driver, BIOS AGP aperture settings, and hardware stability.
  • Look for memory corruption near graphics mappings.
  • On modern systems, confirm that the code is not from a virtualized or compatibility environment.

References

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 “An invalid AGP memory access was detected.”; 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 agp / 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.


Looking for a different code? Search another status or error code.