Computer Freeze/Crash While Playing Games

[maxin11p]

I will be playing a game. After 30-45 minutes, my monitor displays "no signal" and the audio repeats the last millisecond until I turn off the computer using the button. I have tried messing with the cables, nothing happened. Funnily enough, this once happened while I was Skyping and I was able to continue to continue the conversation without a problem (only my game audio had glitched out, Skype worked and my USB mic continued to function). But according to him, I had left the Payday game I was in.

This is not an overheating issue. I played TF2 (one of the games this occurred with) for about half an hour with a temp reading program open and task manager. My processor never went above 50% and the temps were slightly below 50C the whole time (I quit after half an hour, I didn't crash at that time). All of my drivers are up to date, all of the updates from Windows Update have been installed and the computer is otherwise well maintained. This computer was used by my mother to play Sims 2 and 3 and she never had any problems whatsoever playing them. It was passed directly to me and the only changes I made before installing my games was uninstalling hers.

I have played TF2, The Forest, Gmod, and Payday: The Heist on this computer. It has happened with all of these games except Gmod, but I only played that for about 10 minutes.

What is wrong here? And how fix?

[DaveLembke]

All these games are playing through Steam Client.

My guess is that there is an issue with the Steam Client. Have you uninstalled the Steam Client and downloaded and installed clean again to see if this will fix this?

Also... is this the same system you have in your Computer:Specs link of your profile at CH?

I have had some issues with Steam Client, and uninstalling, rebooting system, and then installing clean fixed this.

[maxin11p]

Yes, those are the specs of the system I'm speaking of.

I uninstalled Steam, restarted, re-installed, downloaded and installed Payday, and...the problem was not fixed. The same exact thing happened. It was a good idea, though.

[patio]

Check your connection speeds vis speedtest.net.

[maxin11p]

[DaveLembke]

I would run a test looking for disconnects.

If you run this as a batch file by copy pasting it into notepad and then save this as PingTest.bat you can run this for as long as you want and see the results as to if there are lost packets, serious latency, etc

Code: [Select]

@echo. Ping Test Running - Press CTRL + C or [ X ] out to exit
ping www.google.com -t >>PingLog.txt
From the location that you run this a file named PingLog will be written, so if you run this from desktop, you will see a text file appear with info. When you exit this batch routine, you will have Min, Max, Avg stats and other info for a lost packet count etc.

So after running this for say 30 minutes, close the batch routine and open the text file and scroll to the bottom of the text file to see the summary info.

Please copy/paste the summary info here if you need clarification as to what you are looking at or attach the text file if its small enough to attach.

[maxin11p]

There's no summary in the .txt file?
This is the last few lines, the last one shown here is the final line in the file.

C:\Users\max\Desktop>ping www.google.com -t  1>>PingLog.txt
 Ping Test Running - Press CTRL + C or [ X ] out to exit

C:\Users\max\Desktop>ping www.google.com -t  1>>PingLog.txt
 Ping Test Running - Press CTRL + C or [ X ] out to exit

C:\Users\max\Desktop>ping www.google.com -t  1>>PingLog.txt
 Ping Test Running - Press CTRL + C or [ X ] out to exit

C:\Users\max\Desktop>ping www.google.com -t  1>>PingLog.txt
 Ping Test Running - Press CTRL + C or [ X ] out to exit

C:\Users\max\Desktop>ping www.google.com -t  1>>PingLog.txt
 Ping Test Running - Press CTRL + C or [ X ] out to exit

C:\Users\max\Desktop>ping www.google.com -t  1>>PingLog.txt
 Ping Test Running - Press CTRL + C or [ X ] out to exit

C:\Users\max\Desktop>ping www.google.com -t  1>>PingLog.txt

I copied and pasted your code into a bat file. Nothing was modified. I ran this for about 30 minutes. (8:01 - 8:31 EST)

[DaveLembke]

Hmm... You should have gotten something like below. *Note: I had to ping local 127.0.0.1, because I am on a LAN that doesnt allow pings to and from the outside world from work computer.

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
    Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
  Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
  Control-C

If you open up the PingLog.txt file it should look like what I had above vs what you have below which shows 7 instances.

Running the batch script as I shared it without any alterations gives me the following results on Windows 7 64-bit Home Premium... Once again the info I have here shows unreachable and yours should show successful pings with ms responses like the one above that I did to home IP, but you dont want to ping home at 127.0.0.1, you need to ping www.google.com which will give you the most acurate results for for internet connection because google is well established to give you a good baseline of your internet connection with multiple points of presence.

Pinging www.google.com [74.125.239.50] with 32 bytes of data:
Reply from 74.125.239.50: Destination net unreachable.
Reply from 74.125.239.50: Destination net unreachable.
Reply from 74.125.239.50: Destination net unreachable.
Reply from 74.125.239.50: Destination net unreachable.
Reply from 74.125.239.50: Destination net unreachable.
Reply from 74.125.239.50: Destination net unreachable.
Reply from 74.125.239.50: Destination net unreachable.

Ping statistics for 74.125.239.50:
    Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Control-C

[maxin11p]

I had quite a few more than 7 instances, I just didn't include them since it all said the same thing. Those were the last few lines.

Your script doesn't output for me what you expect it to. No idea why (probably my incompetence). But I tried pinging Google from CMD and this is what I got.

Sent = 591, Recieved = 591, Lost = 0
Min = 55ms, Max = 194ms, Average = 64ms

This is basically how it looked the whole time:

[maxin11p]

I'm just giving up on this computer. Thanks for helping anyways, guys.

[DaveLembke]

Do you have another computer in the home that can play these games?

That computer seems like a nice computer to give up on so early.