StarCraft II Melting PCs – Fix It, Quick!

If your computer is getting really hot while you play StarCraft II, it’s not because you’re blazing up – it’s because the game is roasting your machine alive.

Blizzard has confirmed the game has an overheating bug. Apparently, the game doesn’t cap the frame rate it uses when rendering its menus. So basically, the system goes crazy, overworking itself on rendering the menu, and that causes a big increase in heat.

So much so that if the problem isn’t dealt with, it can damage your computer.

There’s an easy fix, however.

Pop open this file: “DocumentsStarCraft IIvariables.txt.” Then drop the following two lines onto the bottom of the file:


Save the file and you’re done. According to Blizzard customer support, this change is only a temporary workaround, but it’s probably a fair assumption that there will be a patch to fix the program permanently pretty soon.

Until then, your best defense against StarCraft II-related spontaneous combustion is to remember the advice of Master Miller from Metal Gear Solid: “Take a break.” Your computer (and your bladder) will thank you.

Via Kokugamer.

Join the Conversation   

* required field

By submitting a comment here you grant GameFront a perpetual license to reproduce your words and name/web site in attribution. Inappropriate or irrelevant comments will be removed at an admin's discretion.

22 Comments on StarCraft II Melting PCs – Fix It, Quick!


On August 2, 2010 at 7:29 pm

i think it should be mentioned those tweaks wont save unless you change file to “read-ony” but on thast setting u cant change settings in game


On August 2, 2010 at 9:20 pm

How do you change the document to a read-only?


On August 2, 2010 at 10:08 pm

i dont find the place 4 the files , where are they…


On August 2, 2010 at 10:58 pm

Mine saved, it just re-alphabetized the file.


On August 2, 2010 at 11:06 pm

It saved fine without read-oly option.


On August 3, 2010 at 12:32 am

It sounds ridicullous. What’s the matter if your computer works on max when play SCII, or when you play any other game? It is the same as you are running Prime95 or Super PI to test your computer…


On August 3, 2010 at 1:00 am

@drako: Yes but, this is while you are running a video game on the scale of Starcraft 2. No, I’m not saying the game is a graphic hog, I’m saying people are playing it non-stop and at those temps… their hardware will fail.

And hard.


On August 3, 2010 at 4:46 am

check the variable.txt file after playing the game and see if it saved, you still might need to turn it to read only. Right click-properties, tick option


On August 3, 2010 at 12:23 pm

Sounds like a bunch of Hooey. You can’t tell me that SCII is that much harder on a system than today’s FPS. It doesn’t really look that great and there is less going on. I call this dog guck. Some one has dog gucked all over you. :)


On August 3, 2010 at 12:59 pm

change to read only – mouse2 > proporties > read onlt type!


On August 3, 2010 at 2:38 pm

Mayford5 You know nothing. This is a bug forcing your computer to render more information then is there at a much higher rate. It has nothing to do with if its more graphically intense than a FPS. Not to mention SC2 is more graphically intensive than an FPS under its highest load.


On August 3, 2010 at 5:15 pm

I don’t think this bug affects every video card. I run a ATI 5970 with an LCS. I never saw my temps get higher than 65C. maybe the heat is only on Nvidia cards.


On August 3, 2010 at 10:45 pm

Truth also knows nothing, it isn’t forcing anything. It’s allowing the graphics card to render a simple scene (the menu) as many times as the manufacturer of that card has allowed it to. If there is insufficient cooling for the graphics card it can overheat.

The only time this happens is when there is a design flaw with either the card or drivers (possible) or the user previously only played games which do not stress their system (i.e. still playing starcraft 1), start playing a game that does (starcraft 2) and suddenly discover that their inadequate ventilation causes their card to overheat and may cause damage (or simply shut it down).

Try reading the comment threads on the slashdot article sometime, many of the intelligent posters there point out why this simply a high-end game identifying flaws in the users’ system that would have been uncovered by running any other high-end game at maximum settings:


On August 3, 2010 at 11:41 pm

Pathetic pcs! Burn! Overclock your video cards and set it on ultra settings without the proper hardware and cooling system for your system. Then you deserve to smell the roasting aroma of a burning video card. booohoo booohooo!


On August 4, 2010 at 2:49 am

@BurnVideoCardBurn it’s not the graphics of starcraft, there’s no v-sync in the menu, so your video card can over heat by rendering it really fast


On August 4, 2010 at 11:45 pm

I got the file open but I dont see anything about framerate or a framerate cap


On August 4, 2010 at 11:47 pm

Ah, drop them in, thought I was altering something, nvm.


On August 6, 2010 at 5:29 am

wut a load of sheet


On August 6, 2010 at 8:26 am

I don’t see frameratecapglue or
frameratecap in the file


On August 9, 2010 at 10:48 am

@MoneyBagz you ADD them to the file, of course they’re not there, if they were there wouldn’t have been a bug.


On August 10, 2010 at 7:45 am

I have a Mac, should this concern me?

Ignorance is Bliss

On August 11, 2010 at 6:08 pm


Apparently you think all video gamers are genius level people. I hate to burst your bubble but his is not the case.

Regardless of if your hardware is SUPPOSED to have a failsafe or not does not take away from the fact that Blizzard has a bug within their game that CAN destroy your hardware.

I have an “open box” designed case with 8 fans and a liquid cooling system running ONE ATI 4870 and there is no dust whatsoever in my case and SC2 after leaving my game on the menu while eatting lunch fried my card so bad I could literally smell it when I got back.

The card I owned had a failsafe that I’d personally set at 83*C and had the newest drivers. Unfortunately the failsafe somehow didn’t kick in.

And as for your comment about other “high-end” games? Well all I have to say about that is, you’re an idiot sir. I am a graphic designer that renders High Def graphics for hours on end on my machine and am constantly pushing this machine to the limits. Occassionally it will lock up on me (failsafe) if things get to warm, maybe happened 2 times ever but I’ve never had issues with any other “high-end” game or program. I can even run furmark/3dmark at max cap for hours with no problems and yet SC2 fries my card… hmmmmm sounds like it’s more than just a little problem… MAYBE JUST MAYBE the bug knocks off your failsafe… oh yes, you must have forgotten that when SC2 locks up it doesn’t shut the computer off/down it remains on the locked up screen and continues to render the same image millions of times, therefore bypassing failsafes and ruining hardware.

Blizzard should have a class-action suit filed against them for negligence and false representation of system requirements.

End of story.