I had to stop running F@H on my PC recently. It is a new system that I just build a couple of months ago and everything was running fine on it. One morning everything was fine, I had to reboot and now I'm getting overheating messages from my temperature monitoring software that I never got before.
If I turn off F@H, the warnings go away. Nothing has changed as far as the computer goes, it wasn't even moved. I should also mention that I ran the computer for a couple of weeks with these errors because at the time they didn't go away after I stopped F@H (and didn't start until it did). That combined with the fact that I was having no other issues you'd expect from overheating, like the machine locking up, and I figured it was just a false alert.
Hopefully the people here that are more knowledgeable than me can tell me what to do.
I would check to make sure all of your cooling equipment is working properly (all fans are on, etc). Has the ambient temperature in the room changed recently? If it was colder during winter maybe you didn't get the messages because of that?
You might have dust or dust bunnies covering your air intake. If you have been running F@H a lot, it would have been sucking in a lot of air. Check to see that there isn't a lot of dust on your air intake area and open the case and check for dust. If a machine is really dusty it can overheat.
Are you getting marginal warnings (1 degree over) is it like 10-15 degrees past the threshold?
All the fans are spinning and the room temperature has remained pretty constant. The machine doesn't look dusty, but I'll blow it out with the air compressor to make sure.
The software I'm using is the Intel Desktop Utilities which came with the motherboard. It doesn't tell me the temp of the processor exactly, instead it has something called the Processor Thermal Margin. Normally it sits around 32 degrees Celcius. According the software, the lower numbers are worse. 20 degrees is where the scale turns yellow and then 5 and below is red. Originally running F@H would lower the number a bit, but still in the green. Now it immediately pegs it all the way to 0. Sometimes when I stop F@H it stays pegged at 0, sometimes it goes back to normal. If I reboot the machine while it has been pegged at 0, when it restarts it is right back at 32.
Yeah, they are changing the code. It is linked off of the front page. I haven't figured out if I'm going to keep using the sig I have - it kind of annoys me that it is going to be broken on all of my old posts once he updates the code.
I might have to figure out how hes doing it and set it up with our stats.
For those on Facebook, a F@H appication is available, for display of one's work units and progress. There's even a section to view your status on our team, as well, as well as your progress compared to everyone on facebook who's running F@H (and has the app).
If anyone's interested, they can check it out here (facebook.com).
is it the - ""An iPod has been detected, but it could not be identified properly" error? That could be a number of things - even the USB-to-iPod cable. Which generation of iPod Nano is it? And what the version of iTunes you are using?...