I'm very pleased AMD is finally addressing their Graphics Drivers. I went with a Kepler GPU because after 2 AMD cards and constant driver issues I wanted something that just worked and Nvidia offered that. :/

Most will have a different experience by just changing one component between two exact same systems; some people have problems and some don’t with exact same hardware. I can tell you I had a terrible experience with nvidia 670, it was a stuttering mess I tell you. EVGA mass called shipments back because of this (Google it), but that dont mean the same experience for all (as above). Just have a look at the forums below and realize that both are having problems.

I know exactly what you mean, where it kinda slows down (like rubber banding or something) then speeds right back up. This is not limited to ATI, I first noticed it on Need for Speed games on my x1300 then 7900GS. This is probably an example of coding being the culprit.

New Member

No problem with my 7970 IceQ His, it never heats and yet I also amd fx 8350 and at all as I overclock to 4.6 ghz without any problems and does not heat up that much even with the fan original, the only problem AMD chips currently have drivers ...

I looked at the youtube latency thing and saw nothing that I can discern as micro stutter.
If so both cards had it and none of them seemed to be worse than the other.
Plus Skyrim does have a micro stutter on Windows 7 even when I use an HD4850 if I don't use windowed mode with SWB mod.

Either way AMD see it to be a serious enough issue and enough to work on it.
Maybe this will resolve the more significant DX9c issue which some people are plagued with still.

Maybe it's certain monitors which bring out the problem more than others?

It's due to VGA memory management. It's even worse in crossfire, because the effect doubles, leaving what appears to be worse performance than a single card, even though the actual frame rate is higher.

And frankly, this problem is present in ANY high-end card from AMD, since 2900XT. I can't comment on anything other than high-end cards, because that's all that I have used.

What is even funnier, is that I can run 5760x1200(6912000 pixels) far easier than 2560x1600 (4096000 pixels). This was the key indicator that memory management, to me, was at fault, but since I've brought up this issue for years now, and none have seemed to care, I haven't reported this fact to anyone but a few users here.

How is it possible, that rendering 50% more pixels in Eyefinity performs better than 50% less pixels on a single monitor?

There's more to this than anyone wants to admit, unfortunately.

Truly, I dunno know WTF is the problem, really, but there HUGE issues here. I almost bought a GTX690, because I'm sick of AMD and their issues as well, but I feel I need I need GTX690 performance because of problems with performance on AMD cards.

I looked at the youtube latency thing and saw nothing that I can discern as micro stutter.
If so both cards had it and none of them seemed to be worse than the other.
Plus Skyrim does have a micro stutter on Windows 7 even when I use an HD4850 if I don't use windowed mode with SWB mod.

Either way AMD see it to be a serious enough issue and enough to work on it.
Maybe this will resolve the more significant DX9c issue which some people are plagued with still.

Maybe it's certain monitors which bring out the problem more than others?

While HT can cause stuttering in some games/applications, it isn't the case here. I've tried testing with HT both on and off and the same results. Granted, I haven't once noticed stuttering and am going by what the frametimes/FRAFS viewer say .

Correct. Generally, one will notice it if it is above 80ms and if a few happen at around the same time. Guild Wars 2 is one of those games that has a large issue with latency, however it still seems rather smooth.

Correct. Generally, one will notice it if it is above 80ms and if a few happen at around the same time. Guild Wars 2 is one of those games that has a large issue with latency, however it still seems rather smooth.

So the problem can be mitigated by throwing lots of horsepower at it, making the overall processing time shorter, thus reducing the "really big" delays, which would tend to show up as little hitches in the movement.

That's not so bad then and helps to explain why AMD didn't bother fixing it for a year. Still naughty of them though, tsk.

So the problem can be mitigated by throwing lots of horsepower at it, making the overall processing time shorter, thus reducing the "really big" delays, which would tend to show up as little hitches in the movement.

That's not so bad then and helps to explain why AMD didn't bother fixing it for a year. Still naughty of them though, tsk.

Calin gives a good answer. I'm going to run a couple "non-intensive" games and see what comes up. AMD states (and I believe them) that this issue has to do with how memory (controller I assume) is being utilized with GCN.