I don't think 705 MHz on the core is a 2D speed though as my card seems to drops to 324 MHz core/810 MHz memory then 324 MHz core/324 MHz memory within a few seconds of quitting a game (it seems to drop to 2D speeds much quicker than my GTX 580 did). (Annoyingly though, it was stick at 1,006 MHz if I have a browser open with a Flash video playing) It's odd that the 705 MHz speed that my card stuck at was the misreported core clock reported in the leaks though, isn't it? It almost makes me wonder if there's a bug? FurtureMark's 3DMark11 for example shows my GTX 680's core clock as 705 MHz in the benchmarks I linked to above yet I'm pretty sure from the results that the card was running waaaaaaaaay above 1,006 MHz during the tests. I have seen a "driver not responding" error twice when I initially ramped the memory core offset up to +500 MHz but haven't seen a single error or artifact since with my more conservative core and memory overclocks. This card hasn't been out long so it may be that over time others come across this same issue. It may simply be a result of pushing the card beyond its TDP though, even with 132% power set, and not actually a bug per-se.