- Nov 4, 1999
- 24,151
- 516
- 126
Whilst running OCCT CPU test (not linpack option) to test stability I noticed that the CPU was being throttled, multiplier drops to x6, & vcore drops too, FSB doesn't change, it starts after less than a minute & then goes up & down in fairly regular intervals (throttling last about 30s, full speed mostly lasts 30s, but sometimes a bit longer).
In the bios I have disabled C1E & EIST so their should be no CPU speed drop from those, aside from which OCCT runs the CPU at 100% load.
Peak CPU temperature on the hottest core is 56C (checked with speedfan & realtemp) when running OCCT upto the point the CPU is throttled, then it drops of course. This naturally is a long way from the temperature throttle point (realtemp says '44' away) employed by Intel in their Thermal Monitoring protection. Yet if I disable that option in the bios, throttling doesn't happen!
Why is it throttling when the CPU is not getting too hot?
AFAIK Intel's specs for TM only monitor CPU temps, does Asus add monitoring of other chips? VRMs???
Btw all voltages are at default (auto) bar vRAM at 1.5v. FSB 365 MHz, PCIE 106 MHz (had to increase that to get FSB over 343 MHz!). OCCT loaded vcore is 1.144-1.152v (via CPU-Z).
I have used my IR thermometer on the NB heatsink & it showed a temp of ~60C at the hottest point when running OCCT (& when not throttled). It's rather hot but didn't seem to bad to me, besides which, AFAIK TM doesn't monitor that, right?
Does not throttle running SETI, even when Milkyway@home is running on the GPU too.
Since found it does throttle running Asteroids@Home, that is better optimised & the rig draws more power & the CPU runs 3-4C hotter than Folding@H or SETI.
Any idea what's going on? (oh & yea I know this mbrd is a POS, stuck with it
).
Googling didn't turn up much, though 1 guy had the same problem with Prime95 - http://www.tomshardware.co.uk/forum/278526-29-thermal-monitoring - he never got a proper answer.
The rigs specs.
Q9550 @3.1 GHz, 365 MHz FSB, all voltages are on auto which are the default setting (have confirmed by measuring power draw from wall), bar vRAM 1.5v. 8 GB DDR3 1333 RAM is underclocked @1168 MHz, HD 4830, 1TB HDD, Win 7 Ult 64bit.
Btw reposted here because I only got 1 reply in the mbrd section, hoping they'll be more informed people here
.
Going by the 1 reply I did get http://forums.anandtech.com/showthread.php?t=2365659 , I've since downclocked it to 2994 MHz & I still get throttling with OCCT! Though it's not as often (I can post a graph if anyone really wants it).
I've now pointed my IR thermometer on the 2 visible VRMs* (3.1 GHz, running Asteroids@home), one's on ~51C the other 48C. This seems to be roughly bourn out by touching it
, it's hot to touch but I can keep my finger on them for a few seconds. So not terribly hot, those are ok temps aren't they?
*I believe they're the VRMs anyway, black little boxes about 1cm across, under the HSF retention bracket.
What do you folk reckon?
In the bios I have disabled C1E & EIST so their should be no CPU speed drop from those, aside from which OCCT runs the CPU at 100% load.
Peak CPU temperature on the hottest core is 56C (checked with speedfan & realtemp) when running OCCT upto the point the CPU is throttled, then it drops of course. This naturally is a long way from the temperature throttle point (realtemp says '44' away) employed by Intel in their Thermal Monitoring protection. Yet if I disable that option in the bios, throttling doesn't happen!
Why is it throttling when the CPU is not getting too hot?
AFAIK Intel's specs for TM only monitor CPU temps, does Asus add monitoring of other chips? VRMs???
Btw all voltages are at default (auto) bar vRAM at 1.5v. FSB 365 MHz, PCIE 106 MHz (had to increase that to get FSB over 343 MHz!). OCCT loaded vcore is 1.144-1.152v (via CPU-Z).
I have used my IR thermometer on the NB heatsink & it showed a temp of ~60C at the hottest point when running OCCT (& when not throttled). It's rather hot but didn't seem to bad to me, besides which, AFAIK TM doesn't monitor that, right?
Does not throttle running SETI, even when Milkyway@home is running on the GPU too.
Since found it does throttle running Asteroids@Home, that is better optimised & the rig draws more power & the CPU runs 3-4C hotter than Folding@H or SETI.
Any idea what's going on? (oh & yea I know this mbrd is a POS, stuck with it
Googling didn't turn up much, though 1 guy had the same problem with Prime95 - http://www.tomshardware.co.uk/forum/278526-29-thermal-monitoring - he never got a proper answer.
The rigs specs.
Q9550 @3.1 GHz, 365 MHz FSB, all voltages are on auto which are the default setting (have confirmed by measuring power draw from wall), bar vRAM 1.5v. 8 GB DDR3 1333 RAM is underclocked @1168 MHz, HD 4830, 1TB HDD, Win 7 Ult 64bit.
Btw reposted here because I only got 1 reply in the mbrd section, hoping they'll be more informed people here
Going by the 1 reply I did get http://forums.anandtech.com/showthread.php?t=2365659 , I've since downclocked it to 2994 MHz & I still get throttling with OCCT! Though it's not as often (I can post a graph if anyone really wants it).
I've now pointed my IR thermometer on the 2 visible VRMs* (3.1 GHz, running Asteroids@home), one's on ~51C the other 48C. This seems to be roughly bourn out by touching it
*I believe they're the VRMs anyway, black little boxes about 1cm across, under the HSF retention bracket.
What do you folk reckon?
Last edited: