Love it...
Steve merely suggested it could be overheating #6. That doesn't make it a fact (or a non fact).
I'm not taking that approach as the timing seems a little odd, same time as a software upgrade (although who knows it could be overheating for all I know)....
BTW it's a misconception that because a driver works for app X it will work for app Y, or even a revision of the same app. And drivers can run hardware to be hot (not saying that's going on either).
So everything has dependencies and no you can't really jump to any conclusions. The best guess so far IMHO has been ndivia drivers and the driver update util I have suggested should sort this (amongst updating other drivers that could be a problem). It could even be firmware.
But as no info has been supplied really (see Bob's post) we are all guessing.