cpu temp.volts

valo123

Member
Nov 15, 2007
74
0
0
I have my C2D overclocked to 2.93ghz. My core Voltage is set to 1.325 in the bios but shows up as 1.280V in cpu-z. Which is correct? And what would you suggest setting it as for my OC.

Also, i think my temps might be a little high, my speedfan 4.33 temps are as follows.
System: 23C
CPU: 25C
AUX: 43C
HDO: 25C
Temp1: 36C
Core 0: 20C
Core 1: 22C

These are all idle temps, I'm not sure what AUX, HDO, or Temp1 are. Can anyone let me know if any of these are too high? My computer blue screened a few minutes ago, I think the temps may have gotten too high and a BIOS option (though i'm not sure which) shut the computer down for safety reasons.

Thanks in advance
 

sutahz

Golden Member
Dec 14, 2007
1,300
0
0
My guesses:
AUX = PWM (maybe chipset ooo or PSU possibly)
HDO is HD0 => your hdd's temp
Temp1 = CPU's case temp

BIOS setting of 1.325V shows up as 1.28V in CPU-Z due to BIOS setting and actual voltage never being equal (actually lower in every example I've seen). It does seem a little low though. Maybe your PSU is providing ~11.5V on the 12V line which drops your Vcore even more then normal. Maybe Vdroop is still enabled.
But yeah, I really doubt your BSOD was due to temp. Probley due to an unstable overclock.
 

valo123

Member
Nov 15, 2007
74
0
0
So should i up the cpu core volts even more in my bios? What's normal temp for a psu or a mobo? Also, i just checked the cpu temp in my bios, it's 37C, is that a bit much idle?

Since I'm OC will more volts lesson the strain thus reducing temps?

Thanks
 

BonzaiDuck

Lifer
Jun 30, 2004
16,783
2,114
126
Hard to keep track of particulars surrounding these matters.

I THOUGHT that CPU_Z was reporting the CPU_VID.

And it IS true that there is usually a discrepancy between "set," "monitored," and "actual" VCORE voltages (or any other voltages, for that matter.)

Double-check your BIOS voltage monitor to see what it says.

WHICH C2D, and which stepping, are you using? I have an E6600, which needed setting to a 1.40 to 1.44V Vcore just to get it to 3.33 Ghz. Hold on a minute -- let me check my "over-clocking" logs:

For an over-clock of 3.285 GHz, FSB= 1460, DDR=730, I show a vCore requirement of 1.4375V for the E6600. I don't think this is the G0-stepping of the C2D line.

Also, your mobo and BIOS version might be relevant to guidance here. I have the 680i chipset. I cannot be certain, what differences -- IF ANY -- would exist between a VCORE requirement on an Intel chipset and an nVidia chipset for stable over-clocks at a particular speed -- there may, in fact, be none.

I'm only guessing that your VCORE setting is "in the ball-park" for that over-clock level, but maybe it's a couple notches too low, and that might explain your BSOD problem. Also, your memory voltage, latency settings, make and model and over/under-clock setting, would be helpful.
 

valo123

Member
Nov 15, 2007
74
0
0
it's an e6750. The memory is 1.90V 888mhz (OC) 5-5-5-15. Its set at 888 because the only option lower than that is 720mhz. I'm not sure how to check the stepping. Speed fan is obviously low, that's why i'm worried about that 43C AUX. It's too low to be one of those absurd readings speedfan is famous for so i'm assuming it's a correct reading of my mobo or psu
 

BonzaiDuck

Lifer
Jun 30, 2004
16,783
2,114
126
Sorry -- I do this "afterthought" thing.

The temperature reading in BIOS is the TCASE temperature.

If room ambient is around 21C or 70F, I WOULD say your temperature is too high, but it depends, again, on the processor model, and therefore the degree to which it's over-clocked. 2.93 GHz is hardly anything for an E6600, but starting from (what is it?) 1.8 GHz and an E6300, that's quite a jump.

Off top of my head, a 25% OC to any given Intel C2D or C2Q is "mild" -- "easy." It may require more voltage, but idle temperatures should be lower than motherboard temperatures as measured by TCASE. TCASE is reported in BIOS. The core temperatures reported by CoreTemp should be not far off from 10 to 15C higher (average) than TCASE -- at idle, or at load.
 

BonzaiDuck

Lifer
Jun 30, 2004
16,783
2,114
126
YEAH. E6750 (correct me if wrong, people) is a "G0" stepping.

And starting at 2.66 Ghz going to 2.93 Ghz, you've hardly OC'd it at all.

You mention SpeedFan. Get the latest (even BETA) version of CoreTemp.

Whether there have been revisions to SpeedFan to keep up with newer mobos and CPUs, do not depend on Speedfan to assess temperatures. Look first at the BIOS Temperature monitor. If there is a utility that comes with the mobo, like nVidia Monitor for nVidia chipsets, it should report TCASE. CoreTemp should report the core temperatures accurately.

If the core values shown by CoreTemp are in the 30's or even as high as 40C at room-ambient 70F, you can be pretty sure that TCASE is 10C lower.

SpeedFan MAY be more reliable for Intel chipsets, but even the P35 and X38 hotdogs posting here these days rely solely on CoreTemp.

If the Core values are close to what I'm suggesting above, your BSOD is more likely a result of voltage that is too low, FSB speed that is too high for the memory, timings that are too tight, or something along those lines. Your memory voltage, for instance, may be too low.

 

valo123

Member
Nov 15, 2007
74
0
0
I can't use coretemp, it won't work with my version of vista. Thanks for your help. So if cpu-z is reading the voltage of my cpu core wrong does that mean it's just an inaccurate reading or is my voltage really what it states. If cpu-z is right and my voltage is actually what it states should I continue to up the voltage in my bios till cpu-z reads the correct voltage?
 

BonzaiDuck

Lifer
Jun 30, 2004
16,783
2,114
126
Also, advise you -- please get over obsession with pushing memory speed to its (so-called) Mhz spec.

FIRST -- Set everything -- or almost everything -- back to default in the mobo. Start with the E6750 at its 333 Mhz x 8 speed = 2.66Ghz. The FSB manual setting for mobo should be 1,333 or 1,334. The unlinked memory speed should be 667.

That's a manually-set stock setting, assuming mobo is spec'd at 1,333 like the processor.

Depending on how your BIOS is organized, you would then increase FSB and memory speeds in small increments, so that FSB = 2 x RAM speed -- moving up from 1,334 / 667 to (say) 1340 / 670, then . . .. 1360 / 680 . . . . etc. (these increments are probably too large, because you want to get a good handle on min. required VCORE and memory voltage.)

This is a "1:1" CPU / RAM ratio. Do this first -- worry about using different divider-ratios later, or tweaking the latency settings on the RAM. I don't care if your memory is spec'd at 800 and you wind up with a 720 memory setting -- you can tweak the latencies tighter and still get the same memory bandwidth and latency.

What is make and model of your memory modules?
 

BonzaiDuck

Lifer
Jun 30, 2004
16,783
2,114
126
OK -- VISTA -- no CoreTemp.

Get Everest Ultimate -- even the trial version.

It's reported temperatures are equivalent to Coretemp-- with one exception that does not make it "inaccurate: Since it is monitoring fan speeds, voltages, and every (freakin') thing else -- it increases activity in Core #0 and shows that core fluctuating to temperatures higher than what coretemp would report. Focus on the other three to get an "average."
 

BonzaiDuck

Lifer
Jun 30, 2004
16,783
2,114
126
For Monitored voltage, look at BIOS voltage monitor, or use a utility like Everest Ultimate.

I don't know what features are disabled in the trial version of Everest. Latest release is about $30 to buy.

See what Trial version offers.

Not sure of anything else, except that people running VISTA I've spoken with on forums over last year used Everest in lieu of CoreTemp.

Check motherboard maker's web-site forums to see if BIOS revisions resolved any discrepancies in "set" versus monitored voltage, or whether there was ever an issue such as that.

My (purchased) version of Everest shows voltages, temperatures and fan-speeds under an item called "sensors." "over-clock" -- another item -- will show OC settings, memory latencies and speed and FSB and CPU_FSB speeds.
 

BonzaiDuck

Lifer
Jun 30, 2004
16,783
2,114
126
I'm sorry -- I said "focus on the other three . . . . " I have quad-core on my mind.

Same principle applies with Everest and dual-core.
 

valo123

Member
Nov 15, 2007
74
0
0
Hey, thanks for all your help, I just downloaded everest and the cpu temp is at 34C idle, does that sound about right? I'm not sure how to upgrade my bios, my mobo is IP35 Abit with a ICH9R chipset. I checked the abit website and the links don't work. Also, what are the steps I should take before installing a new bios update?

 

valo123

Member
Nov 15, 2007
74
0
0
Ok, i just got the ultimate version now. The cpu temp is listed as 26C but the Core 1 is 35C and Core 2 is 36C, that doesn't seem right. The PWM is 41C is that too high? Also, the Voltage to the cpu core is 1.313, does that sound right?

Thanks
 

BonzaiDuck

Lifer
Jun 30, 2004
16,783
2,114
126
Set everything back to "auto" or default settings.

In fact, just clear the CMOS after making note of your last stable manual settings.

DO NOT use any Windows-based BIOS update program. If the mobo has a menu-item that allows you to update BIOS from there, use it. If it requires a floppy or bootable CD with a "flash" utility, use that.

Your safest bet, while it would cost you, is to assess if your motherboard has a socketable PLCC BIOS chip. Then, after finding the BIOS download and version info at the ABIT web-site, go to www.BIOSMan.com and order the PLCC chip -- flashed with the BIOS version you want -- for some $25. It includes an annual subscription for exchangeable PLCC chips for further BIOS upgrades.

IF you want to save the $25 (maybe it's $27, can't remember) -- check the forums at ABIT web-site for any problems people had with flashing BIOS before doing anything else. Also, the web-search at ABIT will give you an idea how recent your current BIOS is. If reasonably current, you can avoid doing it for a while, anyway.

Don't know why ABIT web-site BIOS downloads and other pages "don't work" for you. See how you make out with another computer -- perhaps a local friend using different ISP. YOu might try corresponding with BIOSMan tech-support, and see if they can oblige you in some way.
 

BonzaiDuck

Lifer
Jun 30, 2004
16,783
2,114
126
NO!! I know I posted a lot of verbiage here -- you may have missed what I said.

26C for TCASE CPU temperature is normal. At that TCASE, the TJunction core temperatures 35C and 36C are also normal.

The voltage sounds as if it's in the ball-park, and anyway, it's significantly below the retail-box "Maximum" voltage. that spec is probably 1.35V. Fact is, some motherboards will default it to approx. 0.02V higher -- some will default to lower. But that's an "idle" reading, anyway. there is probably a "VDroop" or voltage-droop with your motherboard, so that at load usage, the idle monitored value drops in the neighborhood of by 0.03V.