What does BSOD 277 (AGP_INTERNAL) mean?

 
Could be also:
ConstantTypeOS
ERROR_EA_TABLE_FULLWin32 errorWindows
STATUS_CACHE_PAGE_LOCKEDNTSTATUSWindows
Previous Next
VIDEO_SHADOW_DRIVER_FATAL_ERROR VIDEO_TDR_FAILURE

AGP_INTERNAL

AGP internal platform failure for AGP_INTERNAL

AGP_INTERNAL is bug check code 0x00000115. This is a legacy graphics bus bug check. It belongs to the AGP support code rather than to modern PCIe GPU scheduling or TDR recovery.

How to read it in a dump

  • The relevant components are the display miniport, AGP/chipset driver, firmware configuration, and graphics aperture mappings.
  • Use the stack to separate AGP support from general display driver failure.
  • If seen on modern hardware, consider virtualization, emulation, or stale compatibility drivers.

What to check

  • Check chipset and display drivers, firmware, AGP aperture settings, and system memory stability.
  • Look for neighboring AGP bug checks if multiple dumps exist.
  • Avoid treating it as ordinary application graphics failure.

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 “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 agp / internal.
  • 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.