I recently dl'd cpu monitoring software. I get a core voltage deviation alarm. My core voltage shows +1.84v. My cpu temp is 55 celcious. Should I be worried? If so, what can I do to remedy this? ty

Yes you should. Your cpu voltage should be 1.5v or 1.6v or 1.75v depending on when it was made. What motherboard do you have? Go into bios under PC health menu and see if it shows you at 1.85v. Also see if it has a vcore adjustment option (in frequency/voltage menu) and somehow if got taken off "default" and put at "1.85v".

Pardon my ignorance, but what is the pc health menu? My motherboard is an Asus, bought about a year and a half ago.

....God, another alarm for the main voltage when it goes to -10.00v help?

Cripes sorry for multi posts. Now another alarm. It says my cpu fan rpm is zero, but Im watching the fan spin right now. Theres only one fan over the cpu correct? Can I trust this software? Its called Hmonitor. Its shareware.

"Can I trust this software?"

No idea.

I'd download your manual from asus and find out how to check the voltage and temperatures in the bios.

The motherboard probably came with some sort of monitoring software that you might use instead of hmonitor.

Also you can try mbm5 and speedfan (google will find them) instead of hmonitor.

Okay, I tried Speedfan. It says basically the same thing. Is there a fan I'm missing here? Theres one over the power supply, One on the motherboard, and one over the cpu. They are all spinning, yet I get an alarm that says the rpm's are zero. Should I just clean them? They are a tad dusty.

Chris:

As far as the CPU fan warning, this could be caused by:

1. Not having the CPU fan plugged into the header (socket) specifically designated as being for the CPU fan, this includes having a CPU fan that only plugs into a molex (hard drive power connector) and does not have an additional lead to plug into the CPU fan header for the RPM signal.

2. Not having a CPU fan with the third wire (indicates RPM)

3. Having the a three wire fan plugged into the proper motherboard header, but the header is not getting the RPM signal.

Ty for the help. My cpu is running hot; around 65 celcious when gaming, hovers just below 60 otherwise. When I check my bios my core voltage is set to 1.75, but when I run the monitor programs it says the core voltage is 1.84. Do you know what could cause this and how to change it?

read hwood's post about the fan rpm issues. As long as they are all visibly spinning you're set, and its probably best to set aside fan rpm monitoring and focus on the temps and the voltages. Fan monitoring is unnecessary since its your temps and your fan noise that matter to you. The sensor that is reporting 0 rpms either has no fan in it or no rpm monitoring wire in it.

If you use mbm5 frome livewire.com you will have the chance to do a lot of reading on their site and the forums regarding how to set up the voltage and temperature sensors for your specific board. All these hw monitoring programs take a guess as to what sensor does what and they are often wrong and you have to assign the sensors yourself, which requires looking around livewire to find what they do. The first place to go is here

http://mbm.livewiredev.com/

and find your mobo on the mobo support list.

Then watch your vcore and temps using mbm5. Your temps are too high and as you say it could be because your voltage is too high.

I think I've dl'd enough monitoring programs, plus I installed the one that came with my motherboard. The fundamental question is; How do I change my core voltage?

I checked the bios on startup and it was set to 1.75, in fact, thats as low as it would go, but still, all the monitoring programas say its at 1.84. WTH!? Anyway, ty for the help.

If your board allows adjustment to vcore you do it in bios.

But since you've already said that the bios voltage shows 1.75v then you know that you do not need to adjust it since that is correct.

The problem is one of two things:

- your mobo is pumping up your vcore after windows loads. I've never seen this and have no idea what to do if this is what is happening.

- your monitoring programs are not reporting correctly.

mbm5 is far and away the best monitoring program, and has an extensive forum participation where you can see if others have had your problem. I think you have have not dl'd enough monitoring programs if you have not dl'd this one.

my two cents.