My 1st guess would be a hardware (GPU-level) issue, possibly something wrong with the RAM on the card itself or something worse (GPU core failure, things like this), or GPU overheating. Given how shoddy video cards are today (in my experience) and how many I've seen fail at the hardware level, this is my first choice.
My 2nd guess would be a corrupted driver or a driver that isn't properly working with your exact model of card. One such possibility for driver corruption could be unreadable LBAs/sectors on a hard disk (where the OS chooses to ignore the I/O error, which AFAIK Windows does not do) -- SMART attributes would prove this -- or alternately bit rot
(undetectable without a checksumming filesystem). If you've uninstalled and reinstalled the drivers -- or better yet, done a full format/clean install of the entire OS (I strongly recommend this) -- then that can be ruled out.
My 3rd guess would be a broken/buggy video driver, specifically if the system is being put into sleep or standby or "hibnerate" states. Most issues relating to sleep/standby/hibernate happen after a resume, and these are all driver-level bugs.
Regarding #1: Windows Vista onward makes determination difficult, since many pieces of the desktop and windows are hardware-accelerated (i.e. 3D, since the entire desktop/UI is now DirectX), which means hardware/driver-level features are heavily used in comparison to XP (where most everything is GDI+ and only a few things are offloaded onto the hardware). This is why on Vista onward you'll see video card memory being heavily used (140MB+ in some cases) in the desktop with no games running, while on XP you'll see maybe at most 20MBytes in the exact same conditions.
You've got almost (?) perfectly diagonal
lines showing up; since GPUs today focus primarily on 3D, the way you get a rectangle (e.g. a window) is to align 2 triangles
then map a single texture across both of those rectangles and draw onto the texture (i.e. the texture is your 2D "screen" or "window" or "surface"). Possibly different parts of the window (menu bar, etc.) use separate polygon pairs -- I do not know.
What's shown above seems to indicate one of the triangles' texture mapping may be broken.
I cannot explain the "weird jagged lines" especially in the upper right of the picture -- if you moved a window around or jiggled it and it left "trails" of its contents, then that may explain it. Combine that with my above description of combined triangles and it might explain the rest.
The tools I know of for testing video cards (RAM and other features) are all Windows-based tools, which means if your GUI isn't usable/readable these utilities are essentially worthless. The tools I've used are OCCT
, Artefact Tester
, and Video Memory Test
. The latter tool requires very specific checkbox/options to be set else you can get false positives.--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer.