More likely disabling graphics acceleration in the browser, or Windows display adapter settings, would yield results.
I had a laptop GPU once that borked a whole row, something like 32 pixels wide, most of the way across the screen. Fortunately that was the school laptop which I took in to IT and they swapped the card.
Also seen, I forget if it was the same one or what, but I've seen "dead pixels" even when plugged into a CRT. Toasted frame buffer, obviously, or something with the same effect.
GPU RAM should show up on the system bus AFAIK (or be mappable as such), but I suppose it may still be inaccessible to a RAM tester. Even then, I suppose the access pattern might still not be the same as the GPU core does, and it could be a pattern-dependent error. (Heh, I wonder, with a carefully crafted shader, can you arrange texture buffers in such a way that row hammer is induced?)
GPU being output only, I suppose bit error rates, stuck bits, ECC, etc. aren't very important for the most part. Perhaps that's changing with the increasing value of GPGPU applications?
Tim