Core Temp 歷史版本列表
- 2024 軟體跟著走
- 性能測試
- 版本數量 144
- Arthur Liberman
- 免費軟體
- 評價 80 分
更新時間:2017-02-19
更新細節:
What's new in this version:
- Fix: Runaway memory leak on some machines
- Fix: Bus clock detection on Apollo Lake processors
- Fix: Occasional 'to TjMax' appearing on some cores on Intel processors. Improved, hopefully fixed
- Change: Subversion will now be shown in the title and About dialog if it's not 0
- Known issues: Some systems running Windows 10 Anniversary may still have driver load failure
更新時間:2016-11-22
更新細節:
What's new in this version:
- Fix: Runaway memory leak on some machines
更新時間:2016-11-21
更新細節:
What's new in this version:
New:
- Support for Intel Kaby Lake, Apollo Lake and Avoton processors
Fixed:
- Incorrect multiplier on 45nm and early 32nm Core series processors
- Sometimes power consumption doesn't work on supported processors
- In cases where both IA and GT power figures are N/A, Uncore displays the same value as Package
- Incorrect VID on Intel processors
- Inaccurate TjMax on Silvermont based (22nm Atom) processors
- Incorrect VID on AMD Trinity and newer processors
- Corrected Lynnfield recognition of i5 760, i7 870S
- Crystal Well and Haswell-ULT code names added for the Haswell generation
- VIA Eden X4 was incorrectly named VIA QuadCore
Updated:
- G15 applet will be named 'Core Temp' from now on, without the version number
更新時間:2016-10-14
更新細節:
What's new in this version:
- New: Power measurements for IA Cores, GT (Graphics core), Uncore and DRAM for Intel Sandy Bridge, Silvermont and newer processors
- Fix: Version 1.4 crashing on Intel processors without Hyperthreading
- Fix: Correct TjMax for Silvermont (22nm Atom based) and newer processors
- Fix: Dual and quad core VIA CPU support. Corrected VID detection for newer Nano processors and added support for 28nm CPUs
- Fix: Crash when logging is enabled on machines with 20+ cores
- Fix: AMD Carrizo temperature detection
- Fix: Corrected Xeon D codename to Broadwell-DE
- Known issues: Some systems running Windows 10 Anniversary may still have driver load failure