Giblet wrote:Try in a diffrerent browser first, to make sure it's not the browser. I understand you think you made no changes, but 99% of the time, the user s wrong, and something was (has) changed. Due diligence needed.
The graphics in Java are not 3d or hardware related. It's just a CPU telling the vid card what pixels to draw.
I would first try a standard WEBKIT browser, like Chrome or Safari. The GTX 260 and the 8600 are not that different internally. Even so, the 2d crap has long been perfected.
If Firefox has an issue, then reinstalling the exact same browser isn't exactly a good recipe for problem fixing.
Lastly, if your vid card is running too hot, which is common, then it will start giving artifacts, or put data in the wrong place on the screen.
I would get a program like ntune, and clock down your GPU. Java is surprisingly CPU dependent as well, so any overclocks you may have done could be pages of memory to shift.
AS well, the FIA programmers aren't the best. There was more than once that I realized the live timing froze, and I had to do a browser refresh.
If you are on a wifi or other connection that is intermittent (even if it seems constant) it can also cause problems.
I am one of the better PC techs around, I can likely help to a solution. Hard to test with only one race left.
The more I think about it, HEAT is your enemy. You just chucked in a few hundred million new heat sources.
Get another fan, check your temps.
He replaced the graphics card... Let the guy try new drivres before he pops the box open again. Trying some new browser, even if that's iExploder, is a good idea.
If he went GTX he obviously has some serious 3D going on there, and if the board holds 3D fine it won't bend it's knees with live timing and putty ftp.
About OC giving this kind of artifact due to bad memory paging, this is the biggest BS I've read ever.
BOFH standard. The thing will BSOD 1.000.000 times before it fails like that.
BTW,
comedy gold