ALCPU Forums

Coretemp currently reads the bus as fixed to 172MHz on my FX-8150+990FX system, whereas it should read 200MHz, this leads to incorrectly reported core clocks. Other applications, such as HWiNFO, reads the correct 200MHz and correct core states.

Clock multiplier looks to be read normal (range 7x-19.5x all core, 21x peak up to 4 cores).

Final note; it's due to FSB detection being disabled in the advanced options, which is _required_ on the majority of processors, or at least AMD ones. Likely need a fixed refresh for the bus value, else any clock readings will always be incorrect. I don't remember FSB detection being so expensive in previous versions either...

Edit; ok actually, it's not 100% related to FSB detection, if it's enabled and coretemp is restarted it will use almost a full core of CPU time (~10%), be very unresponsive, but also still be locked at 172MHz. Even if the FSB detection is turned off and on again the clock will still be incorrect, but while off coretemp uses no CPU time and is responsive. Firing a refresh does nothing and is permanently locked to 172MHz, have not tested a reboot yet...

CPU: amd fx 9590

mobo: gigabyte 990 fxa-ud7

core temp is reporting a lower turbo frequency than is expected. confirmed frequency with AMD over drive.
core temp is showing 4721 MHz while AMD overdrive is showing 5022 MHz.

http://i.imgur.com/xK2KWRk.png

its hard to capture as one updates faster than the other.

It seems like an issue with Core Temp detecting the bus speed (188mhz) incorrectly. Is this a consistent problem or does it only occur some times?
Also does the bus speed change if you press F5 (refresh)?

Hi, basically RC8 does not display the correct temperature. It is locked at 16 degrees and never changes. Afaik, nothing past RC5 works for this hardware (acer v3-551g-x419 | Trinity A10-4600m w/7660g and 7670m (dual gfx)). I've been using RC5 which seems to work. Here are both register dumps. If anyone sees this and wants the RC5 exe i have it.

Thanks. It looks like there is a problem with Kaveri.
It'll be fixed in the upcoming release.

I am using Core Temp 1.3 on an A8-4500M and it incorrectly (or not at all) reports voltages below 0.8V. the FSB is listed as 66.67MHz rather than 100MHz.

Please attach a screenshot and a register dump (Tools menu)

Files attached. Voltage should read 0.75V at this point (P6 state) but reads 1.55V. FSB is actually around 100MHz.
I noticed that CPU-Z also reports 1.55V for under 0.8V but AMD OverDrive reports the correct voltages.

Sorry, but I don't see anything.

I'll try again...

Thanks. It worked this time.
I assume that other tools detect the frequency correctly at 100MHz?

Correct.

I posted a similar post a few days ago and it looks like it has been lost.
HP Pavilion Notebook 17-g121wm dual boot
Using High Performance power plan in both 1607 and 1703
Core Temp 1.7
Core Temp reporting correctly in Windows 10 1607 14393.1198 Core Temp reporting incorrectly in Windows 10 1703 15063.296 CPU-Z reporting correctly in Windows 1703 15063.296 It appears that Core Temp 1.7 has a bug in seeing the Bus Speed correctly in Windows 1703 15063.296.

HP on May 17, 2017 released a BIOS update F.45 Rev A for the HP Pavilion Notebook 17-g121wm. The Base Speed is now reporting correctly. The bug appears to have been in HP BIOS and not in Core Temp.
Core Temp reporting correct frequency in Windows 1703 15063.296

Thanks for the update.

First time posting - Not sure whether its best to create a new bug or bump this one as this is exactly the same as what I am experiencing.

In the past core temp refreshed as my Ryzen 1700 (Crosshair VI Hero MB) changed clock speed but now it gets stuck at max. Only major change was a clean install of the latest version of Windows 10.

Windows task manager shows the correct clock speed and power settings are correct to let it clock up and down as required.

I use coretemp with rainmeter to show live stats and miss the clock speed being displayed just

Refreshing sometimes shows lower speeds but also shows crazy high speeds at times which aren't correct.

Any ideas on how to fix?

This is a known issue, and it will be fixed in the next release.

I am using coretemp 1.12.1 on a Ryzen 3 2300U with Integrated VEGA 6 graphics.

When I open coretemp the frequency shown is incorrect, it also doesn't seem to update in real time, each time I close and open the program the reported frequency changes.

I have attached a screenshot and a coretemp-dump to this post.

I have same BUG in Athlon 200GE.
My PC is OverClocked to 3875Mhz.
But CoreTemp is Say 3200Mhz.
Multipule display is good.
but BaseClock is Bad.
other software(Ex:CPU-Z) is say BaseClock good.
I hope Fix it.

I sent both of you a PM, please look.

I'll try and get the information you require tonight.

Fixed with the new build you sent over to me.

Great, thanks for testing. Can you please post a screenshot and register dump from the working build?

sorry I'm late
My PC's CPU changed to ryzen 5 1600x.
Now,I Rechange to Athlon 200GE and setting.
I try New build.
Sorry,Not Fixed.
picture is CoreTemp with task manager and CPU-Z.
thanks to Fixing.

You are not using the latest test version, please use the one from my last PM.