
Knowing which of these three classes your bug fits in can provide a clue, as different types of driver errors can lead to the different classes. Still others are seemingly random and impossible to tie to any definite set of preconditions. Others are situational and "tend" to occur with certain programs loaded, certain load levels, or certain periods of time passing. Some GPU lockups are triggerable and easily reproduced. In some cases the driver can trigger a reset from software and the user might notice only a brief glitchiness (or maybe nothing at all), but in other cases it cannot and the graphics system remains in its bad state. If the video driver gives bad data to the GPU, the GPU can get stuck and must be reset. It has memory structures and registers which it uses to produce graphical effects. The Graphical Processor Unit (GPU) is a hardware component on the video card or integrated into the CPU. Screen still updates (look at clock), but can't be interacted with - could be an input bug, not a GPU freeze.

This usually indicates a client application is making too many X requests (See X/Troubleshooting/HighCPU). X CPU or memory load is high, making system laggy or freeze up.

Xlist blank freezes update#

Register Dumps for -ati (pre-r5xx chips).Register Dumps for -ati (r5xx and newer chips).
