In my case, I'm 99% sure that it's not the overclocks, it's the drivers. The first thing I always do when there is an issue, is go to a safe clock setting and test. Whatever this bug is, it's been in every driver release since after 13.12. For me, it isn't just flash and html5. As I mentioned earlier, it happened a few times while gaming. Also, I use this machine 12+ hours per day so there has been lots of times to experience blue screens. Lastly, everything is still fine since switching back to 13.12. It's a video driver bug.
Yes, even overclocked I'd not had a problem with the 13.12WHQLs...same bat-games, same-bat OS. Sometimes, in order to enhance performance between driver releases they may tighten internal timings on certain things, and *if* my cpu has an overclocking problem that isn't obvious, a different driver may bring it to the fore. But it is equally likely it could just be a bug, as you say. So far, though, not a single 14.4WHQL blue screen running everything I can throw at it.
I suppose if I was in the mood I could test my hypothesis by ramping the cpu clock back up to where it was with the attendant voltage kick, but really the ~6% or so in added performance just isn't that important to me--plus I don't feel like repeating anything I've already been through.
I do not know if it's the overclock or the fact, like Toad suggested, that I had installed the 14.4WHQL's twice (one install right on top of the first) that has made the difference. Either way--there's a bug here somewhere because it doesn't happen under any conditions with the 13.12WHQLs.
Still, I'm too timid to try an *uninstall* yet...
Crazy, man--since 2002 this is the first time I've ever been leery of uninstalling an ATi-driver/Catalyst install...!
Update: OK, today's Memorial day (in the US) and I've some extra time--hope everyone is enjoying this holiday. So this morning I braced myself and
attempted to uninstall the 14.4WHQLs, again--which had this time been installed after having first removed the 13.12's via amdcleanuputility.exe, as I report above. Even under ideal installation procedures, uninstalling the 14.4WHQLs once again
killed my USB ports upon reboot after the uninstall! I sent in
my own ticket this time.
Installed the 13.12's and everything is running like a top--and the 13.12's can be safely uninstalled in my system,
either from the Catalyst Manager's
Express Uninstall option, or through use of the
amdcleanuputility.exe! With the 13.12's neither of those options creates a system with no USB access after reboot! But it happens every time with the 14.4WHQLs installed. I'll be sticking with the 13.12's until AMD can sort this out.
Update 2: I am glad to be able to say that
this problem is completely *gone* from the 14.6b's! Have installed/uninstalled as usual, using Express Uninstall through the Catalyst Manager, and it's working perfectly--just like it does in the 13.2's! Good deal! I wish I knew what went wrong in the 14.4WHQLs, but whatever it was it is no longer a problem running the 14.6b...! Almost forgot to mention that I repeated the install/uninstall process *three times* (I like to be thorough)--which is why I am completely satisfied that the 14.6b's don't have the same problem.
Update 3: AMD has
finally explained what happened. It's a bit late, of course, unless you are still running the 14.4WHQLs--obviously the change was carried forward in the 14.6b's...
Update 4: Unfortunately, the above info is incorrect. I performed an uninstall of the the 14.6b's in preparation for the 14.6 RC2 installation, and just out of curiosity I installed the supposedly "fixed" 14.4WHQL's again, to see if they'd uninstall without hosing my system. Well, the answer is no, they won't. After they appeared to uninstall successfully in my system, upon reboot my system was hosed and had to be System Restored--all USB ports dead--no keyboard, mouse input possible--locked out. Again. I have consigned the 14.4WHQLs to the waste bin of history.
No such problems with the 13.12's and <, and no such problems with the 14.6's both the b1 and the RC2. That is one strange bug.
because I agree with your statement
because I agree with your statement 
