If a driver works perfectly fine on one PC, and fail on the other that is identicial in hardware setup, then there can be 3 reasons, both are independent of the driver itself. A)Setup, B)Software conflict, C)Defective Hardwares.
A bug in driver may cause the card to overheat, but not fry it unless it is changes the voltage going into the card. During SC2 beta, AMD or Nvidia, video cards were being fried. It was said that the menu screen is to be blamed, which blizzard put a FPS cap on it. The driver in question, 196.75, was released in between these time and many experience overheating. Some people realized that the video card was overheating because the fanspeed reminds at 30-40% at max after the new driver. Some even claimed that the temp increased through Liquid Cooling and some claim that temp reminds high even after rollback. There were a few reports stated that their cards were killed due to the driver and therefore Nvidia decided to pull the driver out as a precaution. I was one of the earlier beta tester and was actively trolling the forum at the time. Granted the menu screen does make my video card hot, 82c after leaving the computer on at the menu screen for 6 hours regardless of which drivers (that is because I have really long breaks in between games and do not feel like logging out).
Here is the official thread from nvidia forum for 196.75. Mods at Nvidia forum redirected all threads about overheating to this thread.
The problematic driver was out in Mar 2, 2010, and Incgamers.com made a claim about 196.75 kills video card on Mar 3, 2010. That is, within 24 hours they are able to identify the source of death is indeed a bug within the driver. Of course quickly many sites repeat this finding. Interestingly, cards were still being fried by the menu screen of SC2 that is not using 196.75.
The original link
http://starcraft.incgamers.com/blog...ivers-starcraft-ii-beta-rip-pc-graphic-cards/ was no longer available, but you will be able to dig back the source.