Poker Night killed my computer?

Xadera · 12-08-2010, 01:13 AM

I started up Poker Night for the first time since the update. I played just fine before. I play through several hands. Then I get to a point where 3 of the NPCs and myself go all in. Game stops.

I try ctrl+alt+del, I hit alt+tab, I try everything to get out. I can see my mouse when it goes over the hidden task bar and background windows, but can't seem to get out. So, I hit the power button on my computer.

Turn it back on. Screen doesn't come up and I hear 1 long beep followed by 3 short ones. Not good at all. I google it, check my motherboard manual, get the beep code for an AMI board.

Memory test failure - A fault has been detected in memory above 64KB

WTF?!

I google some solutions. Best start is to try and reinstall all my sticks. Not much of a problem. I try to test it out and see if reinstalling them all.

Now my desktop computer won't even post... It makes this horrid sound, like certain fans aren't even going or certain things aren't even working.

I'm really shaky and tired, so I can't go back in and retry tonight. I'm gonna try to get a good night's sleep so I can have a more steady hand tomorrow. I really don't want my $1200 machine to have been killed by a $5 game due to some jarate-poor coding...

I'm posting now to see if anybody else has had this problem and get any ideas on what to do. For those computer junkies out there, would my computer make that sound if the memory wasn't reinstalled correctly or something? And for those legal savants, would I be able to approach Tell-Tale for damage liability? Not that I'm going to right away, going to check my computer first, but I'm sufficiently jarateed enough to keep it in mind.

furrykef · 12-08-2010, 01:19 AM

I think you're confusing cause and effect. That is, I think it's more likely that your computer died, causing Poker Night to freeze, rather than Poker Night freezing and killing your computer. In particular, a game or any other program causing permanent damage to RAM or other system components should be impossible, no matter how "jarate-poor" its coding may be.

No idea on the cause of, or solution to, your problem, though...

Xadera · 12-08-2010, 01:27 AM

Well, it happened precisely when the 3rd NPC attempted to go all in. From what I remember reading (I'm not in the mood to go searching for it again), such a thing happening in game caused many people's games to crash.

Now, I don't know for certain that it was the cause. It is possible that it's just the straw that broke the camel's back, somehow. I'm thinking it is also possible that the memory error was some lingering bits from the game and my collective system that made my RAM confused, and that I just messed something up inside temporarily when I reinstalled them. I won't know until I make another attempt tomorrow. I'll leave this thread up in case anybody has word about it happening, I'm going to try and get some sleep.

If I manage to get my computer working tomorrow, I'll delete this thread. And I don't think I'll be opening Poker Night again for a looong time ^^;

Maurog · 12-08-2010, 01:29 AM

Quote:

Originally Posted by Xadera

Screen doesn't come up and I hear 1 long beep followed by 3 short ones.

The last time that happened to me, it meant my video card exploded. Well, not exploded per se, but all the capacitors were burst and I had to replace it. I recommend visually checking your video card for burst capacitors, and maybe trying to start the computer with it removed or something.

TB_ · 12-08-2010, 02:03 AM

The game runs hot, VERY hot. Good chance you fried your card.

ScoutPark · 12-08-2010, 04:58 AM

I would guess that the awesomeness of four all ins at once overheated the computer's hard drive.

furrykef · 12-08-2010, 05:05 AM

Quote:

Originally Posted by ScoutPark

I would guess that the awesomeness of four all ins at once overheated the computer's hard drive.

Don't ever watch Casino Royale on that computer, then. 'Cause one of the players to go all-in is James Bond.

furrykef · 12-08-2010, 03:43 PM

By the way, if it turns out it was the video card or something like that, I would blame the video card, not Poker Night. Video cards should be designed such that they cannot be pushed beyond their limits. In other words, if the game tries to do something too intense, the card should just reject it, instead of doing it anyway and frying itself.

Xadera · 12-08-2010, 07:45 PM

Quote:

Originally Posted by Maurog

The last time that happened to me, it meant my video card exploded. Well, not exploded per se, but all the capacitors were burst and I had to replace it. I recommend visually checking your video card for burst capacitors, and maybe trying to start the computer with it removed or something.

Well, I took your advice and checked the video card. There was a burst capacitor. I looked through the beep code lists again and even though my board is AMI, Asus can use the Award codes, and 1 long 3 short corresponds to a bad/missing graphics card.

The horrid sound turned out to just be a fan I knocked while fixing the memory and the lack of beeps on startup was because I put the memory back in the wrong slots. Now it's beeping 1 long 3 short again, with the card removed. So, the error definitely was the card.

Now, since I have a decent PSU and have had no other problems, it is possible the capacitor was defective from the beginning and this was just a coincidence/breaking point. I just find it a little suspect that I've had the card for 2.5 years now without problems until that one moment in Poker Night, which has been known to cause crashes. The game is even more suspect with all the other crashes it has been known to cause and another thread about a card dying while playing with it.

I'm able to RMA my card with the manufacturer, though, so I should be fine. I'm just going to avoid playing Poker Night for a long time.

12-08-2010, 01:13 AM	#1
Xadera Join Date: Jul 2010 Reputation: 183 Posts: 150	Poker Night killed my computer? I started up Poker Night for the first time since the update. I played just fine before. I play through several hands. Then I get to a point where 3 of the NPCs and myself go all in. Game stops. I try ctrl+alt+del, I hit alt+tab, I try everything to get out. I can see my mouse when it goes over the hidden task bar and background windows, but can't seem to get out. So, I hit the power button on my computer. Turn it back on. Screen doesn't come up and I hear 1 long beep followed by 3 short ones. Not good at all. I google it, check my motherboard manual, get the beep code for an AMI board. Memory test failure - A fault has been detected in memory above 64KB WTF?! I google some solutions. Best start is to try and reinstall all my sticks. Not much of a problem. I try to test it out and see if reinstalling them all. Now my desktop computer won't even post... It makes this horrid sound, like certain fans aren't even going or certain things aren't even working. I'm really shaky and tired, so I can't go back in and retry tonight. I'm gonna try to get a good night's sleep so I can have a more steady hand tomorrow. I really don't want my $1200 machine to have been killed by a $5 game due to some jarate-poor coding... I'm posting now to see if anybody else has had this problem and get any ideas on what to do. For those computer junkies out there, would my computer make that sound if the memory wasn't reinstalled correctly or something? And for those legal savants, would I be able to approach Tell-Tale for damage liability? Not that I'm going to right away, going to check my computer first, but I'm sufficiently jarateed enough to keep it in mind.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

12-08-2010, 01:19 AM	#2
furrykef Join Date: Jan 2010 Reputation: 65 Posts: 461	I think you're confusing cause and effect. That is, I think it's more likely that your computer died, causing Poker Night to freeze, rather than Poker Night freezing and killing your computer. In particular, a game or any other program causing permanent damage to RAM or other system components should be impossible, no matter how "jarate-poor" its coding may be. No idea on the cause of, or solution to, your problem, though...

12-08-2010, 01:27 AM	#3
Xadera Join Date: Jul 2010 Reputation: 183 Posts: 150	Well, it happened precisely when the 3rd NPC attempted to go all in. From what I remember reading (I'm not in the mood to go searching for it again), such a thing happening in game caused many people's games to crash. Now, I don't know for certain that it was the cause. It is possible that it's just the straw that broke the camel's back, somehow. I'm thinking it is also possible that the memory error was some lingering bits from the game and my collective system that made my RAM confused, and that I just messed something up inside temporarily when I reinstalled them. I won't know until I make another attempt tomorrow. I'll leave this thread up in case anybody has word about it happening, I'm going to try and get some sleep. If I manage to get my computer working tomorrow, I'll delete this thread. And I don't think I'll be opening Poker Night again for a looong time ^^;

12-08-2010, 02:03 AM	#5
TB_ Join Date: Mar 2010 Reputation: 23 Posts: 253	The game runs hot, VERY hot. Good chance you fried your card.

12-08-2010, 04:58 AM	#6
ScoutPark Banned Join Date: Apr 2010 Reputation: 63 Posts: 936	I would guess that the awesomeness of four all ins at once overheated the computer's hard drive.

12-08-2010, 03:43 PM	#8
furrykef Join Date: Jan 2010 Reputation: 65 Posts: 461	By the way, if it turns out it was the video card or something like that, I would blame the video card, not Poker Night. Video cards should be designed such that they cannot be pushed beyond their limits. In other words, if the game tries to do something too intense, the card should just reject it, instead of doing it anyway and frying itself.