Can't read CPU temp with Win 10

[howward]

I just upgraded my older system to Win10, and now I'm looking to OC it. I've tried HWMonitor, CoreTemp, SpeedFan (and maybe one or two others), but none of them report CPU core temperatures. For instance, HWMonitor reads 0 deg C for all 4 cores, though it gives reasonable seeming readings for TMPIN0 and TMPIN1 (both about 40C). I've also tried AMD OverDrive, but it tells me that it "cannot detect supported AMD chipset".
My system:
AMD Phenom X4 925
MSI NF750-G55 with NVIDIA nForce 750a chipset
12 GB PC1333 (2X4GB and 2X8GB)
Samsung SSD 850 EVO 500GB
Toshiba HDWD130 3TB
Radeon 4850 PCIe 1GB
(The two disks are new - I know they outclass the rest of my system.)
BIOS gets a good read on CPU temp. Does anyone have a good idea for reading it within Win10?

 

[GhislainG]

Why not use the more accurate AMD Overdrive to check the thermal margins? They should be 10°C or higher at full load; at 0°C or less the CPU throttles.

 

[Manish Tewari]

I just upgraded my older system to Win10, and now I'm looking to OC it. I've tried HWMonitor, CoreTemp, SpeedFan (and maybe one or two others), but none of them report CPU core temperatures. For instance, HWMonitor reads 0 deg C for all 4 cores, though it gives reasonable seeming readings for TMPIN0 and TMPIN1 (both about 40C). I've also tried AMD OverDrive, but it tells me that it "cannot detect supported AMD chipset".
My system:
AMD Phenom X4 925
MSI NF750-G55 with NVIDIA nForce 750a chipset
12 GB PC1333 (2X4GB and 2X8GB)
Samsung SSD 850 EVO 500GB
Toshiba HDWD130 3TB
Radeon 4850 PCIe 1GB
(The two disks are new - I know they outclass the rest of my system.)
BIOS gets a good read on CPU temp. Does anyone have a good idea for reading it within Win10?

OK, I found out how to autostart Core Temp using the Task Scheduler as shown in the first post on this page: ALCPU Forums Vista - Guide

He says to do the following, and it worked perfectly, (though when I opened Task Scheduler it gave me about 20 successive Error messages that I had to clock OK on before I could actual reach the Task Scheduler).

- Run core temp and disable 'Start Core Temp with windows' enable 'start minimized'
- Enable 'enable plugins' if using the vista sidebar gadget or anything that needs CT access.
- all other options are at the discretion of the user.
Click OK.
- Remove the program from the Startup folder or any RUN/STARTUP registry key. - Disabling 'start CT with Windows' should actually have removed the registry key entry anyway.
- Move Core Temp.exe to a directory that is NOT 'Programs x86' or anywhere else controlled by Windows. I created a directory in my 'Users/my login name' directory called 'startupapps' and put 'Core Temp.exe' in there. (Note: strictly speaking this is not required, but some have reported they needed to do this so I simply wrote what I tested and checked as working.)
- Launch the Task Scheduler (Control Panel -> Administration Tools -> Task Scheduler)
- From the Actions panel on the right, select Create Task...
- Give the Task a description of 'CoreTemp' (or anything else you feel like if you want to be cryptic)
- Go to the Security Options on the General tab
- Select an user account with administrative privileges
- Select the radio button Run only when user is logged on
- Check the box Run with highest privileges
- Go to the Triggers tab and click New...
- In Begin the task, select At log on
- In the Settings options, select All users
- In the Advanced Settings options, check the box Enabled
- Click OK to close the dialog
- Go to the Actions tab and click New...
- For Action, select Start a program
- In the Settings options, browse for the Program/Script you want to execute on startup
- Click OK to close the dialog
- Go to the Settings tab
- Check the box Run task as soon as possible after a scheduled start is missed
- Uncheck the box Stop the task if it runs longer than
- Click OK to save and close the task properties
- Logout.
- Login.
- Wait - Core Temp will eventually load - usually instantly, but may be up to 30 seconds or so.

- Core Temp will now start when you login *without* any request for permissions even when UAC is enabled.

Though he wrote this for the Windows Vista OS, it work(s) perfectly for Windows 10 Pro too!

The Core Temp 1.0 RC7 (allegedly written specifically for Windows 10) can be found here:
https://www.oboom.com/JUGD1GRV/Core%...01.0%20RC7.rar

 

[howward]

Why not use the more accurate AMD Overdrive to check the thermal margins? They should be 10°C or higher at full load; at 0°C or less the CPU throttles.

I tried AMD Overdrive - for unknown reason, it gives the error message "cannot detect supported AMD chipset" and goes no further.

 

[howward]

I just upgraded my older system to Win10, and now I'm looking to OC it. I've tried HWMonitor, CoreTemp, SpeedFan (and maybe one or two others), but none of them report CPU core temperatures. For instance, HWMonitor reads 0 deg C for all 4 cores, though it gives reasonable seeming readings for TMPIN0 and TMPIN1 (both about 40C). I've also tried AMD OverDrive, but it tells me that it "cannot detect supported AMD chipset".
My system:
AMD Phenom X4 925
MSI NF750-G55 with NVIDIA nForce 750a chipset
12 GB PC1333 (2X4GB and 2X8GB)
Samsung SSD 850 EVO 500GB
Toshiba HDWD130 3TB
Radeon 4850 PCIe 1GB
(The two disks are new - I know they outclass the rest of my system.)
BIOS gets a good read on CPU temp. Does anyone have a good idea for reading it within Win10?

OK, I found out how to autostart Core Temp using the Task Scheduler as shown in the first post on this page: ALCPU Forums Vista - Guide

He says to do the following, and it worked perfectly, (though when I opened Task Scheduler it gave me about 20 successive Error messages that I had to clock OK on before I could actual reach the Task Scheduler).

- Run core temp and disable 'Start Core Temp with windows' enable 'start minimized'
- Enable 'enable plugins' if using the vista sidebar gadget or anything that needs CT access.
- all other options are at the discretion of the user.
Click OK.
- Remove the program from the Startup folder or any RUN/STARTUP registry key. - Disabling 'start CT with Windows' should actually have removed the registry key entry anyway.
- Move Core Temp.exe to a directory that is NOT 'Programs x86' or anywhere else controlled by Windows. I created a directory in my 'Users/my login name' directory called 'startupapps' and put 'Core Temp.exe' in there. (Note: strictly speaking this is not required, but some have reported they needed to do this so I simply wrote what I tested and checked as working.)
- Launch the Task Scheduler (Control Panel -> Administration Tools -> Task Scheduler)
- From the Actions panel on the right, select Create Task...
- Give the Task a description of 'CoreTemp' (or anything else you feel like if you want to be cryptic)
- Go to the Security Options on the General tab
- Select an user account with administrative privileges
- Select the radio button Run only when user is logged on
- Check the box Run with highest privileges
- Go to the Triggers tab and click New...
- In Begin the task, select At log on
- In the Settings options, select All users
- In the Advanced Settings options, check the box Enabled
- Click OK to close the dialog
- Go to the Actions tab and click New...
- For Action, select Start a program
- In the Settings options, browse for the Program/Script you want to execute on startup
- Click OK to close the dialog
- Go to the Settings tab
- Check the box Run task as soon as possible after a scheduled start is missed
- Uncheck the box Stop the task if it runs longer than
- Click OK to save and close the task properties
- Logout.
- Login.
- Wait - Core Temp will eventually load - usually instantly, but may be up to 30 seconds or so.

- Core Temp will now start when you login *without* any request for permissions even when UAC is enabled.

Though he wrote this for the Windows Vista OS, it work(s) perfectly for Windows 10 Pro too!

The Core Temp 1.0 RC7 (allegedly written specifically for Windows 10) can be found here:
https://www.oboom.com/JUGD1GRV/Core%...01.0%20RC7.rar

Thanks for the potential fix, however, my problem isn't getting Core Temp to run - it's that Core Temp shows core temperatures to be 0 deg C. I did run through the Task Scheduler procedure and Core Temp loaded, but showed 0 0 0 0 in my task bar for the four cores.

 

[GhislainG]

Why not use the more accurate AMD Overdrive to check the thermal margins? They should be 10°C or higher at full load; at 0°C or less the CPU throttles.

I tried AMD Overdrive - for unknown reason, it gives the error message "cannot detect supported AMD chipset" and goes no further.

I just realized your old system doesn't use an AMD chipset. Windows 10 provides no benefits on such an old system.

 

[howward]

Solved! In the BIOS Cell menu I changed NVidia Core Calibration from "Auto" to "Disabled" and temperatures now show up inn HWMonitor (and probably all the other ways to obtain this).

 

[GhislainG]

You deserve the best solution!