Have a VERY annoying problem with the computer. I don't know if it's a windows or hardware issue, so I'm starting the post in here incase it's a windows problem. If it's not I'll delete this and move it.
When I built this computer back in August everything was running fine, in fact perfectly. I left for vacation in September, came back a month later (Nov.) and everything wasn't as it should be. The computer desided it would like to start shutting itself down... well more like go into standby, where it can't be woken up. This only occurs when I'm playing a game.
It used to only occur when I played "Gunbound" and now months later it occurs during any game I play. I used to only get a message saying "Signal out of range" before the monitor would shut off (as if in standby, monitor is on but black screen with yellow light instead of green for on). Now it just goes into standby for no reason at any time it feels like it. Sometimes I get the "Signal out of range" message, but mostly it just goes into standby.
The computer is still running, LEDs are on, fans spinning, lights flashing, just no signal to the monitor. When I'm playing a game sometimes it freezes before it cuts out, other times it just cuts out.
I know it's been awhile dealing with this problem, but I don't know what to do to fix it, and I forgot this site. I have updated my drivers and tried switching my ram sticks (tried using just one and then tried with the other). I thought maybe my CPU was overheating, the HSF is seated fine, I even opened the side panel to let some of the hot air escape and use the fan on it to blow cool air against the CPU (this actually lowered overall temps of CPU and case). I relocated second fan (have 2 fans total blowing air in) to blow air also against the CPU and backside of GPU. I unplugged unnecessary LEDs, thinking the 400w PSU didn't have enough juice. I dusted the case and components inside.
I changed the refresh rate to 60hz from the desktop, I used ATI's catalyst program to force 60hz during games, I then did what microsoft said to do with forcing directx to use 60hz. This is all changed from allowing them to run default. Default is when the problems started, and after changing to 60hz the problem still occurs.
At the moment I can't think of anything else I've tried. If I do I'll add it or reply to a post that suggests something. Thank you in advance for any help any of you can offer.