|
On July 30 2010 11:38 Ndugu wrote:Show nested quote +On July 30 2010 11:36 dybydx wrote:
shouldn't this be a bug of the video card themselves? i mean, if my CPU overheats/lights on fire from "working too hard", i''d flame the PC manufacturer for making failed product. This.
Yeah, seriously, you would think there would be a "hard cap" on the video cards to prevent shit like this. luckily my computer hasn't been acting too retarded except for the installation lololol
On July 30 2010 11:41 NB wrote:Show nested quote +On July 30 2010 11:36 dybydx wrote:
shouldn't this be a bug of the video card themselves? i mean, if my CPU overheats/lights on fire from "working too hard", i''d flame the PC manufacturer for making failed product. if you let your computer run an infinite loops without a break, it will broke eventually and that apply for every hardware.
Yeah I guess, hence over clocking.
|
On July 30 2010 11:36 dybydx wrote:
shouldn't this be a bug of the video card themselves? i mean, if my CPU overheats/lights on fire from "working too hard", i''d flame the PC manufacturer for making failed product.
if you let your computer run an infinite loops without a break, it will broke eventually and that apply for every hardware.
its like: while "1 is not 0", do "memory +1 byte" => no computer can endure that without a software to break the loop
|
On July 30 2010 11:36 dybydx wrote:
shouldn't this be a bug of the video card themselves? i mean, if my CPU overheats/lights on fire from "working too hard", i''d flame the PC manufacturer for making failed product.
No program is actually designed to use 100% of hardware capacities as it would almost instantly lock the computer/fry the components.
Ever had a loophole in a program almost freezing up your entire computer and having a process going thru the 99% bar ? Well there you go...
As an analogy, would you sue an oven company if your oven broke after you let it run for 1 straight week at maximum temperature ? Of course not, because even tho it's technically capable of it, it's not made to withstand such critical temperatures for THAT long.
This is just one more case of outrageously bad programming.
|
um shouldnt blizzard patch this instead of us doing and accidently fucking up the codes and cant you sew them for breaking your hardware?
|
Glad to know this is what happened to my 8800 GTS >.< Explains it pretty perfectly actually. It wasn't under warranty anymore so I took it as an opportunity to upgrade but still good to know what actually happened. Still really sucks though.
Just one question: is this is the official fix from Blizzard, or just a fix someone found out? Just curious
EDIT: Does anyone know if there is a way to get reimbursement or whatever from Blizzard over cards that fried from the game menu? I don't want to seem like I'm whining but I'm pretty furious right now that a simple programing oversight wrecked my card.
|
@NB,
if u set ur CPU to run an infinite loop or do "memory +1", it will not damage the hardware. sure, your CPU will be running at 100% capacity 24/7 but CPU's are designed to withstand that, and CPU's do have a powerdown mechanism to prevent permanent damage.
also if u do "memory +1", you will run out of memory space, at which pt ur suppose to get a blue screen or windows will kick intervene the program logic.
either way, software are not suppose to be able to damage hardware, except through excessive wear and tear usage.
|
is this the file path in windows 7? when i go to mine, i have a different variable.txt for each account.
ie. documents/sc2/accounts/0/variables.txt
documents/sc2/accounts/466645/variables.txt
do I place this code into both? or are these the wrong files.
thanks for the heads up!
|
On July 30 2010 11:44 perfectflaw72 wrote:
um shouldnt blizzard patch this instead of us doing and accidently fucking up the codes and cant you sew them for breaking your hardware?
Actually... If anyone wants new free hardware now is the time.
That statement just gave all the legal proof you need to pretend your computer parts were fried due to blizzards incompetent programming.
|
On July 30 2010 11:41 NB wrote:Show nested quote +On July 30 2010 11:36 dybydx wrote:
shouldn't this be a bug of the video card themselves? i mean, if my CPU overheats/lights on fire from "working too hard", i''d flame the PC manufacturer for making failed product. if you let your computer run an infinite loops without a break, it will broke eventually and that apply for every hardware. its like: while "1 is not 0", do "memory +1 byte" => no computer can endure that without a software to break the loop
Fortunately every CPU and BIOS worth their salt stop this from happening when it gets too hot. There's a PC Health section of every BIOS I can remember that you can set thermal maximum settings for your CPU. Now if only there was a standard attachment for video cards to do the same thing... :\
|
On July 30 2010 11:44 perfectflaw72 wrote:
um shouldnt blizzard patch this instead of us doing and accidently fucking up the codes and cant you sew them for breaking your hardware?
i believe when you agreed to the EULA, there is a section saying blizz is not responsible for any damage caused from the use of this software.
|
On July 30 2010 11:50 dybydx wrote:
i believe when you agreed to the EULA, there is a section saying blizz is not responsible for any damage caused from the use of this software.
EULA isn't a magic "no liability" card. In fact it can be debunked pretty fast by an amateur lawyer.
A) You have to buy the game
B) You can't test it without agreeing to the EULA
C) Agreeing to the EULA to enjoy the product YOU ALREADY PAID FOR fried one/some part(s) of your hardware
You could probably stretch it to reckless endangerment, mischievous behavior, intentional damage of property (as they just admitted they knew about it), arson (a long run but still) , etc...
Also, knowledgeably distributing faulty software breaches a shit-ton of trade/trade practices laws.
|
wait, we copy and paste it or we change the existing file ? i cant file the file on windows 7
|
can I set it to 75 instead of 60 because my monitor is 75hz?
|
I don't get how this is a "Bug"... GPUs that are adequately cooled won't overheat... under any kind of load. The lack of a frame-cap encourages overheating in systems that aren't cooled properly, but this problem is more hardware related.
|
Thanks for this man. Much appreciated. Although the two lines keep disappearing out of variables when I play.... T.T
|
So is the place im suppose to be adding this information in the variables notepad that has a bunch of crap in it. The very last one in my notepad says width-1280, so do I copy and paste under that?
|
On July 30 2010 11:58 Loser777 wrote:
I don't get how this is a "Bug"... GPUs that are adequately cooled won't overheat... under any kind of load. The lack of a frame-cap encourages overheating in systems that aren't cooled properly, but this problem is more hardware related.
A game that is going to allow your GPU to generate 350 frames a second or more really doesn't matter how well its cooled. Unless you're blowing an air conditioner directly in there, and still, probably only a mater of time.
|
Good to know. Personally I would have appreciated a heads-up before my video card fried, but maybe this can save someone else from the hassle I've been dealing with since yesterday afternoon.
Blizzard is SUPPOSED to use your graphics card. Sure it might not be reasonable to go balls out on rendering the menu but whatever.
Starcraft2 does not cause anything to overheat or fry, bad cooling does that.
|
On July 30 2010 11:58 Loser777 wrote:
I don't get how this is a "Bug"... GPUs that are adequately cooled won't overheat... under any kind of load. The lack of a frame-cap encourages overheating in systems that aren't cooled properly, but this problem is more hardware related.
GPUs aren't nearly as used as you think. There is absolutely no way any GPU could withstand 100% usage for very long, be it cooled with fan, water or liquid nitrogen...
|
On July 30 2010 12:02 Santriell wrote:Show nested quote +On July 30 2010 11:58 Loser777 wrote:
I don't get how this is a "Bug"... GPUs that are adequately cooled won't overheat... under any kind of load. The lack of a frame-cap encourages overheating in systems that aren't cooled properly, but this problem is more hardware related. GPUs aren't nearly as used as you think. There is absolutely no way any GPU could withstand 100% usage for very long, be it cooled with fan, water or liquid nitrogen...
Depending on your definition of "very long" i would like to hear the reasoning behind this.
|
|
|
|
|
|
EPT
