Hi, I have this strange problem that I don't know how to fix. When I'm playing Team Fortress 2 my pc will just "die" randomly. My monitor says *no signal*, there's no audio coming from my speakers but the fans and leds are still on which is quite odd. Would anyone have any idea why it does that? It's quite an old system but so far its running strong Windows XP XP2 8800 GTS 320 AMD64 3200+ 2GB Kingston RAM Asus A8N-SLi Audigy 2 Thanks. Please let me know if you need more info.
could be power supply unit. what is your current power supplys power output? Have you done any overclocking? have you tried re-installing the game? have you also tried re-installing graphics card drivers? does this happen on any other games?
Hi, sorry for the late reply. Lets see, my regular psu has a 450 watt output, I also have a dedicated vga psu which delivers 250 watt (thermaltake power express) and have been working fine so far for years. Also no overclocking, gpu is actually 'underclocked' by 200mhz as I don't need full power in most cases. Drivers are up-to-date but I recently tried to rollback to previous graphics drivers in an attempt to identify the problem with the random "turn off" thing. I've played Mass Effect and it lost power once during that time. Maybe I should get into another game and see if it happens there too, the only problem is that its completely random when it shuts off etc. Hope that answers everything you need
Im thinkin its the gpu power supply unit is at fault because you've got two power supply units one for the main board and one for the gpu, the gpu psu could not be supplying enough power when gaming therefor causing random shut offs. If you where to have one power supply unit for the entire system It would most likely shut the entire system down. but since you've got a seperate power supply unit for your gpu it will shut the gpu down and keep the motherboard powered.
Hmm odd thing, I've been playing TF2 for 3 hours now and it was rock solid as it used to be. This was after I rolled back to previous nvidia drivers (from 185.85 to 182.50) so I'm thinking new ones are flawed in some strange way. If it happens again though I'll look for new parts, its time to upgrade anyway I think. Thanks for the help!
Ah yes, it was the driver. I've seen people with the same problem after updating to that driver. Honestly I didn't know a driver could mess things up THAT much ..