Please help, something is wrong

hi all,

i just noticed today that my RMclock Temp settings are way off. it displays that my cpu is idling at 22-25 C but i know that can't be right since my normal idle is 45-48C (i've turned off rmclock and back on multiple times with same faulty readings). The computer itself physically feels about the same in terms of warmth as before. My fans usually come on medium at above 48 and high above 60 but now it comes on high at the apparent reading of "40" and medium at "32". Also, the fan stays on high-med during startup whereas before it blows high for 2 seconds right at the beginning then drops to low throughout start up. This is why i can't really tell if it is a software or hardware problem.

i was thinking of what could have caused this and i can only think of the fact that my symmantec anti vi picked up this thing: http://www.symantec.com/security_response/writeup.jsp?docid=2002-101518-4323-99
with autoprotect and supposidly deleted it, although that happened on the 24th and i'm just noticing the problem now.

another thing is that i did some registry cleaning with spybot last night and that may have caused the problem, although i ddint see anything related to rmclock in the cleaned files. Also, i have done plenty of registry cleaning with crap cleaner for the last two weeks without this problem.

i tried to do a system restore to last wednesday but it did not work... another problem.

i'm thinking of reinstalling rmclock to see if that helps. i also have a registry backup that crap cleaner created that i could use, but i don't know how (import using regedit?).

any more suggestions would be great guys.

sorry for the long post, but thanks in advance for your help.

 

maybe try speedfan it can detect my laptops temp might be able to yours if you register to get beta 4.27 or somthing it has better support for internal temps.

 

RMclock shouldn't be running from any registry keys other then to start with windows. The application itself can run from any location you copy and paste it to. That shouldn't be a problem.

Try running bitdefender.com's free online virus scanner. Might give you something your scanner isn't seeing.

Try comparing readings for temp using something like Sensorsview Pro ( http://fileforum.betanews.com/detail/SensorsView_Pro/1132663939/1 )

Report back if any of this helps.

 

"sorry, some sensors not detected" was a balloon tip that came up right after i started sensorsview up. the only T readings i get are HD0 and GPU, no CPU.

edit

i tried speedfan too and it only detected the HD0, no cpu either.

edit 2

i ran bitdefender until it found the trojan in my symmantec antivirus quarantine folder. BD tried to disinfect it but failed and tried to delete it but i'm not sure if it was successful or not because of the ambiguity of the report... so anyways, i booted into safemode and the comp is currently running a full symmantec antivirus scan in safemode. i'm hoping that will completely clean out the system. as for the T readings, i am still baffeled. doesn't seem like this trojan could be causing an incorrect cpu reading because i think ive checked the cpu reading after the infection and it was fine until today....i'm 80% sure on that.

 

You could also try Core Temp to compare temperature readings.

 

ok well safemode scan of fully updated symantec antivirus turned up nothing. i isntalled core temp and it is giving me the same temps that rmclock is giving me: idling around 24C. This can't be right though because for the last three months that i've been using RMclock, i have always been idling around 46C... is there a hardware sensor that these programs are getting these readings from? if there is, could it be fried? I mean so far my computing hasn't really been impacted that much... I ran CS:S for about 30 min fine... this is kind of worrisome still though.

anymore ideas?

thanks so far for all your help guys.

 

Have you updated the BIOS or drivers or anything lately? RMClock just picks the registers that are supposed to be reporting the temperature, and says "I think this is the CPU temp, this is the graphics chip temp", etc. It is possible (and I've seen it happen many times) that it can get it wrong, because the order of the registers is different, or one stopped being reported, whatever.

 

i'm currently using the 111A bios that i flashed to from 103A around the middle of december so no, i have not updated the bios recently. i think i'm with you though on the fact that this is just a misread....it hasn't really impact when my fans come on or off or anything upon more usage and experience with it in the last day, so i guess everything is fine except for the fact that the temp reading is wrong. i contacted PN tech support and they didn't have an answer either... should i reformat and reinstall windows and everything sometime in the future? would that even help?

 

You could use a linux boot disk and try seeing what one of the linux sensor apps say, but I wouldn't bet it's something goofed in windows. Maybe.. just maybe your chipset drivers... I'm honestly not that familiar with thermal reporting for Intel chipsets..

 

What!?! The Intel guy is not familiar with that? Just kidding .

I think Pita is on to something about the misreads though. Perhaps something's calibration is off. I know with Riva Tuner (the only GPU temp I can get for my HEL80), I have to offset the temperature by 200 degrees Celsius to get something reasonably accurate.

A reinstall might do the trick if you're up to it. But I also like what pyro suggested about doing the chipset first.

 

Lol... don't even get me started on that...

Atleast I'm honest enough to fess up to it? To be fair... it's not a lack of knowledge, it's a lack of interest and lack of having anything to do with my job requirements

 

well... this misread isn't really bothering me so far as i can tell so i'm just gonna leave it be. I was planning on reformatting and reinstalling this summer to clean up the system a bit so i'll just do it then. thanks for the input guys

 

update: i did a fan clean out yesterday using an air duster (and boy was there a lot of dust in the vents), so before i started i unplugged the AC and took out the battery and held the power button for 10 sec to drain the remaining juice. So after the cleaning and everything and starting the lappy back up, my Temp readings from RM clock are now back to normal. I guess the temp monitor has electricity dependent memory then?

 

It could be that the dust was insulating the sensor, so it didn't heat up as much as it should have. That's the most logical explanation... was your system running slow at all before you cleaned it out?

Take it as a sign to clean it out a little more often

 

system was not running slow prior to the clean out. what you're saying makes sense, but i don't see how dust could have insulated the temp sensor by ~20C, especially overnight since the T misread happened the day after i shut it down the night before.... hehe oh well at least it's back to normal

 

Glad to hear you've got that sorted out. And, as Pita recommended--definitely clean it out more often .