» Sat Feb 19, 2011 4:50 am said:
Correct me if I'm wrong, but isn't RROD most likely to happen due to overheating?
Correct me if I'm wrong, but isn't RROD most likely to happen due to overheating?
Freddo
You're indeed correct. Software can't ruin hardware, it's impossible.
RROD (and Error E74) happens because the graphic chip in the 360 gets too hot and create solder issues with the motherboard. The exact same reason why the PS3 get YLOD as well. If you have an older 360 or PS3 model, this is bound to eventually happen. The hardware simply generate too much heat to be confined in a relatively small box. The newer models is much more energy efficient and generate noticeably less heat, though, so they are more reliable, but it might still happen in some extreme cases.
In any case, RROD is a wellknown 360 issue and Microsoft happily deal with it, so contact the Microsoft support and they will help you.
RROD (and Error E74) happens because the graphic chip in the 360 gets too hot and create solder issues with the motherboard. The exact same reason why the PS3 get YLOD as well. If you have an older 360 or PS3 model, this is bound to eventually happen. The hardware simply generate too much heat to be confined in a relatively small box. The newer models is much more energy efficient and generate noticeably less heat, though, so they are more reliable, but it might still happen in some extreme cases.
In any case, RROD is a wellknown 360 issue and Microsoft happily deal with it, so contact the Microsoft support and they will help you.
you better call and let blizzard know that there was a bunch of people that scammed them that played starcraft 2 then.
Blizzard Offers Fix for StarCraft Computer-Melting Bug
John Funk | 29 Jul 2010 4:33 pm
Filed under: john funk, blizzard, bug, overheating, starcraft 2
image
StarCraft II is the hottest game of the season in more ways than one - but luckily, there's a fix to stop your graphics card from burning itself up.
Are you playing StarCraft II? Judging by the "approximately 1,000,000 people on Battle.net" I saw last night, you aren't alone. However, a small portion of the thousands upon thousands of StarCraft II buyers (including a staffer at GameInformer) have been confronted with a nasty problem - the game makes their graphics card work itself to death.
The issue deals with the game's interactive menu screens that pop up between missions, where Jim Raynor can explore his flagship and chat with crew. While the rest of the game has limits on what can be rendered, the menu screens have no framerate cap whatsoever, and some computers will interpret this to mean "go hog wild." Rendering framerates of over 200 frames per second for extended period of times means that computers with insufficient ventilation melt themselves into oblivion. And that means you can't play SC2, and we don't want that.
While Blizzard will be patching in a fix, there's a manual workaround that you can set up in the meantime - open your Documents|StarCraft II|variables.txt file, and add in the lines:
frameratecapglue=30
frameratecap=60
This will cap the framerate at a nice consistent 60 FPS and keep your computer happy and healthy while you slaughter the hell out of those nasty Zerg. Obviously, this isn't an issue that affects all computers or all hardware since hundreds of thousands of people are playing just fine - but there's no harm in taking a precaution or two.
source: http://www.escapistmagazine.com/news/view/102465-Blizzard-Offers-Fix-for-StarCraft-Computer-Melting-Bug
i wouldnt say a piece of software couldnt melt a gpu in a console if the coding is off, like in starcraft 2, and we all know the coding has proven to be way off in this title.
