search

xuantl / open-hardware-monitor

Automatically exported from code.google.com/p/open-hardware-monitor
0 stars 0 forks source link

Wrong FSB clock detected - Core 2 Duo T6570 (laptop) #309

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
My CPU's FSB is 200 MHz, Open Hardware Monitor 3.2 and 4.0 both sometimes show 
incorrectly 190 MHz. Sometimes it is displayed correctly: When Open HW Monitor 
starts while CPU utilization is high, it displays the correct value of 200 MHz, 
if it starts while CPU utilization is low, it displays the wrong value of 190 
MHz. This of course affects the CPU speed displayed. According to CPU-Z, my FSB 
is always 200 MHz (~199 MHz), disregarding CPU utilization.

Original issue reported on code.google.com by dexto...@gmail.com on 11 Jan 2012 at 1:53

Attachments:

GoogleCodeExporter commented 9 years ago 
Can you attach a report saved when the value is 190 MHz as well?

Original comment by moel.mich on 11 Jan 2012 at 12:01

GoogleCodeExporter commented 9 years ago 
Here you go.

Original comment by dexto...@gmail.com on 11 Jan 2012 at 9:11

Attachments:

GoogleCodeExporter commented 9 years ago 
Same here with a an Asus V1S laptop (Core 2 Duo, T7500 and 183 vs 200 Mhz FSB)
Thanks to this ticket, I could exactly understand and confirm this issue.

Adding both OHM and CPU-Z reports, if it may help (CPU-Z reports are strictly 
identical, no matter what OHM detects).

Notes:

1. I've installed OHM (as well as iasl builds) on Vista OEM from Asus-provided 
DVD.
   I only use this OS as a "witness", so it's really Asus' 2007 default system config
   with all provided drivers and updates, plus all Windows Updates applied.

2. Reason behind my Vista tests is to compare/understand better a (random) ACPI 
issue
   I have with Linux kernel, which is EC-related (some bogus "127" temperature value)
     https://bugzilla.kernel.org/show_bug.cgi?id=15946
   => Apart from this, all is fine here under Fedora 16, including FSB readings :)

3. But my issue also occurs under Vista's memory test program, *not* in Vista 
itself.
   (Vista's safe mode has always given a BSOD on this hardware, nothing else !)
   Hence, Asus ACPI driver might achieve some workaround on this.
   => Could be in your way, too ?

4. Since latest Windows Update, Asus' own hardware monitor utility named 
"NBProbe",
   suddenly stopped to work (not a big loss, it was rather useless anyway).
   That issue looks strictly related to its GUI code (.Net maybe ? who cares).
   Asus apparently never provided any NBProbe update for this (EUR 1600) hardware.
   => OHM is twice helpful here :)

Thanks for your work. Don't buy anything from Asus!
Feel free to ask more infos/readings from either of my OS.

Original comment by public....@xapaho.com on 23 Jul 2012 at 12:43

Attachments: