temperatures

hi all, i have the following issue, when i start windows 7 ultimate my cpu in idle is 34 to 37 celcius , 2% cpu use, full load goes up to 50 celcius (games like fear series, cod 2 4 and 6,crysis etc) , 65% cpu use ,ok, idle again goes to 34 as stated, but when it comes out of suspension the temps in idle are 49 celcius, 2% cpu use and never go down, if the cpu was in use after suspension ok that could be a reazon , but is only 2% use .
i checked all the processes and they are the same as before going into suspension. then in full load(after coming out of supension) it goes up to 65 celcius(gaming).
i restart windows and again in idle is 34 celcius , what is going on here?
can anyone help me?
why i suspend it? , cause i have an htpc, it takes 2 seconds to be ready again, with gygabite ga-ma780-gpm-ds2h amd 5000+ be (overclocked to 3ghz for my games) 2g ram, maxorb fan (full speed) , 3 back fans, another over integrated hd3200 graphic card, mozart htpc vfd and remote control case and vizio 42 inche hd tv as monitor.
any ideas?

Overclocking.

but if the problem is overclocking before supension cpu is 34 celcius, i play my games and is no more than 50 celcius , after games it comes down to 34 and the cpu is still overclocked, so?
if i dont overclock my temp is just 28 celcius but to run games nicely need more juice and 34 is not bad at all.

i have one front fan forgot to mention it,and my cpu fan as mentioned is a maxorb, thermal grease is good(cheked and re aplied yesterday) remember the high temps problem comes only after windows comes back from sleep not before. my guess is that after coming from suspension windows is not loading something, what , i dont know.
i dont have 3 back fans , only 2 60 mm 4000 rpm in the back and one floating over integrated graphic, is noisy but when playing my gameswith the high volume of 5.1 speakers can not hear the fans at such speeds.

dguys , guys, i guess i did not explain myself very clear in this matter, my problem is not if the cpu reaches 50 in load, that is normal , my problem is and please read carefully :first i turn on windows from scratch, ok , in idle the micro goes to 34 degrees, ok, when loaded goes to 50 as is supoused to be , i'm clear with that.
i stop gaming it goes to idle 34 , which is normal again. now if i put my system is sleep mode or suspension it Goes to sleep as is supoused to do it, fine so far.
NOW I COME BACK FROM SLEEP MODE AND THE TEMP IN IDLE IS 49 DEGREES AND STAYS THERE , WHY?, BEFORE SLEEP MODE IDLE WAS 34 , AFTER SLEEP MODE IS ALMOST 5O AND DONT GO DOWN , SO THE PROBLEM WITH THE TEMP IS WHEN COMING BACK FROM SLEEP MODE. IF I TURN OFF THE PC THEN BACK ON , IDLE AGAIN IS 34 DEGREES SO YOU SEE, IS A COOL TEMP, I PUT IT BACK INTO SLEEP MODE AGAIN, AND WHEN I AWAKE IT BACK AGAIN THE TEMP GOES TO 49 AND DONT GO TO 34. THE PROBLEM IS COMING BACK FROM SLEEP MODE, WINDOWS IS DOING SOMETHING THAT IS KEEPING MY MICRO AT 49 DEGREES AFTER SLEEP MODE.

First:
Do not rely on idle temps very much. They can often be inaccurate, sensors stick etc at the lower end. you will have more accurate temps the closer to TjMAX you are.

Load temps are the most important.
If you can run something like Prime 95, and the temps stay as they should under full load, I would not worry as its likely a mis-interpretted reading, or sensor sticking at idle.

Having said that:

It likely could be a software issue if its only showing after a sleep.

What utility are you using to monotor temps?

When this happens,and you get high idle temps being reported;
If you immediatly reboot and go to PC Health in Bios, what do your bios say the Temp is?
Is it normal there?
i know you said its normal once you reboot, but just curious what the bios is actually saying. They will be more accurate for the most part than software in windows.

It's easy, try another program to monitor your temperature to see if this is the case or a false positive from the program you are using now... GL :)

polarbear said:

It's easy, try another program to monitor your temperature to see if this is the case or a false positive from the program you are using now... GL :)

I'll second that - use HWInfo32 in my drivers guide sig.