Crappy Video Game Broke my Computer

rwmj5

Junior Member
Dec 24, 2004
22
0
0
Yesterday I downloaded the demo of Bet on Soldier, a crappy, futuristic first person shooter with mediocre graphics and laughably poor voice acting. There were a couple of other problems with the game: waypoints on the map which the characters were saying were yellow were actually green, and after I shot one particular enemy, he stood upright in mid air instead of falling to the ground. Point is, this game was not quite ready for prime time, and was pretty unstable, as can be expected since it is only a beta and the game is supposed to be released at the end of the month.

I had gotten through about 3 minutes of the game, when all of a sudden, as I pressed the Use key to operate one of the games ammo stations, the screen went black, then it was garbled a little bit, and for about 5 seconds after that the sound just kept looping and then my computer rebooted. When it rebooted, the entire screen was just garbled graphics. So I turned my computer off and restarted. This time, the command line boot screen text was fine, but as soon as I got into windows there was distortion again. Picture the sort of colorful blocky garbled crap you would see if an old arcade game you were playing just f'ed up. What I am seeing now is basically red vertical lines running down the screen, and in some windows, there is a fairly solid pink or red textured fill across the entire window.

I uninstalled the drivers, and when I use just the default windows VGA drivers, there is no distortion. Of course, those drivers suck and my computer is as slow as hell. I tried reinstalling the latest drivers, and also tried installing older drivers but still have the same problem. If the display on 2D windows is readable but with a lot of colorful distortion, 3D games are totally undecipherable. So the question is, could that game actually have screwed up my graphics card somehow? Could it have just corrupted some setting in windows or is there a chance that it actually damaged the hardware? I have an MSI 6600GT PCI express and I was not oveclocking it or otherwise messing with it in any way. Does anyone have any idea how I might go about fixing this?

 

imported_zenwhen

Senior member
Jun 5, 2002
302
0
0
You mean your video card went bad while you were playing a bad game. A piece of code cannot destroy an otherwise perfectly good piece of hardware. Your video ram is bad. You need to RMA.
 

mOeeOm

Platinum Member
Dec 27, 2004
2,588
0
0
I highly doubt a game can kill a card...anyways you can try

1) Reset CMOS.
2) Remove the video card from the slot and put it back in.
3) If might be the card dying..RMA?

If you don't want to RMA, the extreme case you can do is reformat...but the first two should fix it.
 

rwmj5

Junior Member
Dec 24, 2004
22
0
0
reset my bios-no change. Unplugged and replugged in the card- no change. If it were a problem only with the video ram itself, why did it crash at the exact instant I hit the 'E' key to go into some complicated display within the video game. Also, why was the display garbled during the the first boot up sequence after the computer crashed and not on any subsequent restarts. Also if it were a problem with the video ram why is the display not corrupted at all when I am using the default windows VGA driver.
 

rwmj5

Junior Member
Dec 24, 2004
22
0
0
Originally posted by: zenwhen
A piece of code cannot destroy an otherwise perfectly good piece of hardware.

but what if the voice acting was really REALLY bad...

hahaha
 

imported_g33k

Senior member
Aug 17, 2004
821
0
0
Its probably a coincedence that it corrupted during gameplay. It's normal for bad video cards to display 2d properly but at the same time cannot display 3d.
 

jasonja

Golden Member
Feb 22, 2001
1,864
0
0
Originally posted by: zenwhen
You mean your video card went bad while you were playing a bad game. A piece of code cannot destroy an otherwise perfectly good piece of hardware. Your video ram is bad. You need to RMA.

Well I don't know about that.... ATI Tool and other similar "code" that overclock a video card can certainly destroy hardware. But it's unlikely that game code could destroy a video card.
 

grimlykindo

Senior member
Jan 27, 2005
546
0
0
Have you watched your GPU temps?

Cronicles of Riddick is what fried my Leadtek 6600gt. My temps were already too high, but this particular game made my card get even more hot that ususal. I had already beat farcry and HL2 on my 6600gt before playing Riddick. Everytime I played riddick I would get artifacts until I opened my side panel. NO OTHER GAME DID THIS!?!?!

So one night I had Riddick on pause to go to the bathroom and when I came back my comp had rebooted and ruined my card. Luckily had the Newegg RMA filed soon and I got a refund and bought a X800XL.

So basically if a certain game runs your video card Hotter than any other program, then it could technically "BREAK YOUR COMPUTER" (overheat your video card)
 

Peter

Elite Member
Oct 15, 1999
9,640
1
0
It's more like "crap hardware broke on demanding game". Most of the time it's insufficient thermal solutions.
 

rwmj5

Junior Member
Dec 24, 2004
22
0
0
I have played Doom 3 for many hours with no problems, and my room was actually fairly cool (probably 65 degrees) at the time it happened. I guess it may have stressed my video card more than other games have, or just stressed it in different ways. I did check the nvidia gpu temp display right after it rebooted and it was like 40 degrees below the threshold so I don't know if it was overheating by itself that caused the problem. I can keep listening to arguments about how its physically impossible for software to mess up hardware, but I honestly know that if I never installed this game and just kept playing Doom and Half Life, my graphics card would never have f'ed up like this.
 

ddogg

Golden Member
May 4, 2005
1,864
361
136
40 degrees below the threshold?? what was the threshold? i hope not 135C? if thats the case your card may have fried...just RMA it back to them.
 

BrokenArrow

Senior member
Jan 30, 2004
582
0
0
Holy crap! If your threshold is like mine at 135C, then that means it was at 95C? That is WAAAYYY over the top hot! I'd say you had a hardware failure. Ouch!
 

rwmj5

Junior Member
Dec 24, 2004
22
0
0
apologies. I didnt remember exactly what the threshold was. The temperature of the core was 40 degrees C. I saw 135 or 140 in the panel and I probably converted the 40 C to 100F in my head and then when I tried to go back and remember what the max temp was I guess I thought it was in F. No there was no thermal problem with the core, I remember specifically that it was waaay below the threshold, I just got my numbers mixed up.