search

austinulmer / open-hardware-monitor

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

Phenom II X6 1090T wrong core clock #205

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The CPU temperature is now correct. (same as AIDA64)

I still get random clocks for bus speed instead of the stock one.(200Mhz)

I enable Cool'n'Quiet and disable C1E.

Original issue reported on code.google.com by haras...@gmail.com on 3 May 2011 at 12:43

Attachments:

GoogleCodeExporter commented 9 years ago 
The clock calculation uses a few measurements made during the starting of the 
Open Hardware Monitor and some measurements made in real-time. Do the clocks 
change (from right to wrong and back) while the Open Hardware Monitor is 
running, or are they always wrong (and only restarting the Open Hardware 
Monitor changes anything)?

Can you also save a few reports (maybe 3) and attach them (File -> Save 
Report...)?

Original comment by moel.mich on 3 May 2011 at 12:59

GoogleCodeExporter commented 9 years ago 
The display for the bus speed doesn't change while running. When it gets the 
proper bus speed it will always display them properly until I end the process.

Original comment by haras...@gmail.com on 3 May 2011 at 1:18

Attachments:

GoogleCodeExporter commented 9 years ago 
Ok, then the initial bus clock estimate fails, or is not accurate enough (this 
is done right after the start of the process).

Is the bus clock correct (or at least more often correct) if you start the Open 
Hardware Monitor when your system is idle and no other hardware monitoring 
tools (CPU-Z, CoreTemp, ...) are running?

Original comment by moel.mich on 3 May 2011 at 2:12

GoogleCodeExporter commented 9 years ago 
I had the same issue with my X4 945. It happend when I start 
open-hardware-monitor when a VM is running in VMWare.

If you start open-hardware-monitor before running the VM everything is fine.

Original comment by MagicAnd...@live.com on 3 May 2011 at 6:22

Attachments:

GoogleCodeExporter commented 9 years ago 
Shingo, can you confirm this on your system?

Original comment by moel.mich on 3 May 2011 at 6:29

GoogleCodeExporter commented 9 years ago 
>Is the bus clock correct (or at least more often correct) if you start the 
Open Hardware Monitor when your system is idle and no other hardware monitoring 
tools (CPU-Z, CoreTemp, ...) are running?

Nope. The bus clock seems to be rather correct when the system is stressed. 
(Prime95, x264, etc.)

Original comment by haras...@gmail.com on 3 May 2011 at 10:20

Attachments:

GoogleCodeExporter commented 9 years ago 
>Can you also save a few reports (maybe 3) and attach them (File -> Save 
Report...)?

I was kind of sleepy and forgot to make a report for it, sorry.

Original comment by haras...@gmail.com on 3 May 2011 at 10:51

Attachments:

GoogleCodeExporter commented 9 years ago 
Issue 207 has been merged into this issue.

Original comment by moel.mich on 5 May 2011 at 8:40

GoogleCodeExporter commented 9 years ago 
Is this a new problem with Open Hardware Monitor 0.3.0 Beta, or does the 
version 0.2.1 Beta (download from here: 
http://open-hardware-monitor.googlecode.com/files/openhardwaremonitor-v0.2.1-bet
a.zip) also show the wrong bus speed reading?

Original comment by moel.mich on 5 May 2011 at 8:44

GoogleCodeExporter commented 9 years ago 
The 0.2.1 beta shows random base clocks, too.

Original comment by haras...@gmail.com on 5 May 2011 at 10:55

Attachments:

GoogleCodeExporter commented 9 years ago 
Thank you for the test. To better locate the source of the problem I have 
created a special version where additional information is written to the 
report. 

http://openhardwaremonitor.org/files/openhardwaremonitor-v0.3.0.4-alpha.zip

Can all that have the problem please test once more with this version and 
attach a report?

Original comment by moel.mich on 5 May 2011 at 5:03

GoogleCodeExporter commented 9 years ago 
Here's the report from 0.3.0.4 -- still reporting 841MHz as the minimum clock 
speed of the Phenom, and its max as 3469MHz, where it should be 800 and 3300MHz 
respectively.
And yes, 0.2.1 reported the same clocks, more or less...

Original comment by ska...@yahoo.co.uk on 5 May 2011 at 6:52

Attachments:

GoogleCodeExporter commented 9 years ago 
same here

Original comment by haras...@gmail.com on 6 May 2011 at 12:00

Attachments:

GoogleCodeExporter commented 9 years ago 
Thank you for the new reports. The problem could be the new "Core Performance 
Boost" which is similar to Intel "Turbo Boost". I have created a new version 
where "Core Performance Boost" is disabled for a short moment during start up 
to measuring the clock speed. 

http://openhardwaremonitor.org/files/openhardwaremonitor-v0.3.0.5-alpha.zip

Please post again a report with this version.

Original comment by moel.mich on 8 May 2011 at 4:43

GoogleCodeExporter commented 9 years ago 
So, I tried the latest version, started it multiple times and it worked 
perfectly for my CPU.

I think this problem is now resolved.

Thank you very much.

Original comment by haras...@gmail.com on 8 May 2011 at 5:27

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Thank you for the feedback. This issue has been fixed with r314.

Original comment by moel.mich on 8 May 2011 at 10:12

GoogleCodeExporter commented 9 years ago 
Same here. Clocks are much better now.

Original comment by ska...@yahoo.co.uk on 8 May 2011 at 11:18

Attachments: