Golgatha
Lifer
So I've been experimenting with running the GPU2 folding console client on my secondary 4870 since it has active cooling (primary card is passive and just gets too hot for Folding@Home) on it. Not thinking, I left it running overnight and my son started up Command and Conquer 3 like he does nearly every morning (raising that boy right aren't I? LOL!!) and he had been playing without issue for at least 30min. When I came down in the morning, he wanted to play Raiden Fighters on the XBox 360, so I had him close the game out and proceeded to get his game out. As soon as he closed the C&C3 game out I got a continuous beep coming from my motherboard like the Core i7 CPU was overheating (heard this before when I tried running Folding@Home on all 8 threads, and my CPU really did have some heat issues with that running on a Zalman 9500). I had OCCT open at the desktop from the night before (was monitoring GPU temps to make sure I was using the correct 4870 card: -force ati_R700 - gpu 1 console switch) and my CPU and GPU temps were normal when the game closed out. I thought it might be a bug with the GPU2 client (when checking the GPU2 console client, it had happily folded overnight and during my son's gaming with no errors), so I closed out the GPU2 client and the continuous beep ceased. Opening the GPU2 client back up caused the beeping to resume.
Even though my CPU and GPU temps were ok, could the chipset be overheating and that's what is causing the continuous beep, since the GPU2 client is stressing out the chipset with all the data (thinking about this question, I will try opening the GPU2 client when I get home before rebooting to see if the beeping is just a software bug)? Could someone else with C&C 3 and GPU2 Folding@Home please open the program up, run the game, and then close it to see if there is any beeping? I will try rebooting and will see if it was just from closing out the C&C 3 program. I'll also see if the issue is repeatable after rebooting (i.e. fire up GPU2 client, run game, then close it again to see if continuous beeping starts up). Just wondering if anyone had some insight, can reproduce the problem (ASUS P6T motherboard FWIW) in the same manner, or has had a similar problem when leaving the GPU2 client up and running then closing any other games?
Even though my CPU and GPU temps were ok, could the chipset be overheating and that's what is causing the continuous beep, since the GPU2 client is stressing out the chipset with all the data (thinking about this question, I will try opening the GPU2 client when I get home before rebooting to see if the beeping is just a software bug)? Could someone else with C&C 3 and GPU2 Folding@Home please open the program up, run the game, and then close it to see if there is any beeping? I will try rebooting and will see if it was just from closing out the C&C 3 program. I'll also see if the issue is repeatable after rebooting (i.e. fire up GPU2 client, run game, then close it again to see if continuous beeping starts up). Just wondering if anyone had some insight, can reproduce the problem (ASUS P6T motherboard FWIW) in the same manner, or has had a similar problem when leaving the GPU2 client up and running then closing any other games?
