G73 Heat/SC2 problem?

So, I got my copy of Starcraft 2 yesterday (yay!) and decided to start with the campaign, just so that I could finish with the story.

However, after some minutes with those between-mission-cutscenes, the computer shut down and refused to restart for some tens of seconds. I restarted it, happened again after some minutes, I switch to low-medium settings, still happens.

Now, this only occurs during the cutscenes and the mission I'm currently at, normal vs AI works fine. The right fan (from the front) is also going really loud and spewing out hot air, so I believe that the issue is overheating and then shutting down for safety, and just to the sure ran a Furmark test and it showed 105C as highest (I closed the test after since I didn't want to risk anything), with an average of 97 I think.

So, what should I do to resolve this problem?

 

Youre not making much sense here, you do realise that? - max means you let it run for long enough to see it wont go higher, but you say you shut it down after seeing 105C. You also didnt mention how fast it got to that temperature (the time displayed in furmark).
It sounds like an overheating issue though. To be sure run furmark and let it reach its max temperature, if it will shutdown you will know fure sure its the heat (if you have bios prior to 209 its supposed to be 106C, at 209 the thermal shutdown limit is 110C).
If so, you have two choices; if you feel up to it repaste yourself to see if it will help (dissasembly video on youtube) or if its just a bad gpu running too hot itself youll have to rma it.

 

Hah, sorry. I shut down the test too fast because I feared that it would shut down. But 105C was the Max temperature that was displayed until I stopped, that's what I meant.

Okay, tried it again. It died, but I checked the Excel log to get some numbers.

I only had Chrome, MSN, Steam(Background, no games) and Anti-virus running, except the usual background applications (I guess?)

Start - 88 degrees

29sec - 100 degrees.

90sec - 110 degrees

91sec - 107,5degrees

92sec - 99 degrees

After this is shut down.

I'll RMA it then, since I'll just wreck something with my buttersfingers. But thanks for your help!

 

Sounds weird - 111 is the tjunction shutoff point. Maybe run furmark and watch it at 91-92 seconds? Or OCCT if you want to punish your GPU.

 

Here is a fix I got from another thread, can't find it now though.

Find your variables.txt file and add these 2 lines that will limit your framerate. The #'s can be whatever you want.

frameratecap=50
frameratecapGlue=50

The problem is that the game doesn't limit itself, so without those lines it's like your GPU is running a stress test whenever you are between missions with triple digit frame rates. So your GPU is being really stressed and I had temps nearing 100 C, now Im getting high 80's and low 90's.

 

What temp monitoring tool are you using?

The memory I/O gets about 10-15* warmer than the Shader, and if you're monitoring that you will freak out prematurely. Go download HWinfo32.

 

In some models.

 

Only if you have a bad pads application, my memory IO was almost 10C hotter than the core before, but after i reapplied new paste and pads properly myself its only around 3-4C hotter.

 

How is this supposed to help to cap the fps at 50? Demanding new games will run well below that fps with high settings and heat up the gpu more than any old game running at 200+ fps. I just dont see your logic. And theres an easyer way to do this - its called vsync and will limit the game at 60fps (the screen refresh rate).

 

Um I don't really see your logic lol? Those lines cap your fps at 50 during cutscenes and in between missions. And the G73 is powerful enough that if you don't put those lines in variables.txt, during cutscenes and in between missions you will get triple digit framerates and your GPU temps will skyrocket atleast for me and apparently the OP. V-sync may work I haven't tried, but this works for sure, lowered the temps I was getting by 7-10.

 

This is a confirmed issue with Blizzard:

http://gameinformer.com/b/news/arch...rd-confirms-starcraft-ii-overheating-bug.aspx

Recommendation in your variables.txt is:

frameratecapglue=30
frameratecap=60

VSync ON does *NOT* resolve the issue.

Cheers,
Kermee

 

Cheers. I'll try that too. But it's still going to the service due to heating issues nontheless. 110C in Furmark wasn't that good.

 

Whell i dont have problems with SC2 overheating and i havent done the above.

Anyway, the OP isnt having problems becouse of cutscenes, but is rather having a more serious general overheating problem.

 

Would you guys also consider furmark at 101 (max), with the card at 830 core and 1110, thermal issue?

Also I am worried with my cpu, if i run intelburn test torture mode for some mins the cores stay at 86/87. With the twin turbo enabled from bios they go to 93/94 after 6 mins or so and then each core throttles to 990ish mhz for 15 sec, it gets fresh goes full speed again (1.73 ghz in each) and another 6 mins till it reaches the previous temp again.

I dunno if these values are normal or not, I have some applications that still only like single threads and being overclocked helps a bit, while gaming though I see my cpu around 75 and iddle 48ish.

Ps: room temp around 27 c.