I did numerous searches and can't find anything via search on this so I thought I'd throw it out there...
In a new system that I have Core Temp and Core Temp Gadget installed on under Win 7, the CPU usage is a constant 15-20% no matter what, until I close the "Gadget" option then the CPU usage drops to 0-1%. I've tried different sampling rate settings, etc. and the issue seems to be the graphics section of Gadget that shows the CPU usage bars, but that doesn't seem like it should use this high of CPU usage on an 8-core FX-8350 CPU running @ 4.0+ GHz. The 15-20% is actually an average of the 8-cores as Task Manager would show. If you observe the constant load cycling in Core Temp, you can see that most of the time only four cores are doing most of the work and they show as much as 45% load, which is absurd for a Gadget function.
Not sure how many folks are using the Gadget option, which is nice but it uses more resources than I desire so I will not be using it unless there is a reasonable fix. BTW, I am using the V2.7 just in case there are other versions.
Excessive CPU usage with "CT Gadget"
Re: Excessive CPU usage with "CT Gadget"
Nothing on this issue - The Coolest?
-
The Coolest
- Site Admin
- Posts: 3379
- Joined: Tue Feb 18, 2003 7:48 pm
- Location: Tel Aviv, Israel
- Contact:
Re: Excessive CPU usage with "CT Gadget"
No one has reported such an issue with the gadget, and it has many thousands of users. It shouldn't use more than 1-2% of CPU.
Try to uninstall it and reinstall it again?
Try to uninstall it and reinstall it again?
Main rig:
AMD Ryzen 9 5950X (True Spirit 140 Direct) / Mobo: Asrock Fatal1ty X470 / EVO 970 500GB + WD Blue 250GB + HDD / GPU: Dell RX 570 4GB / Mem: 2x16GB DDR4-3200 G.Skill 32GTZKW TridentZ - 32GB total / PSU: Seasonic Prime Ultra Gold 650W
NAS:
Core i7 2600K 3.4GHz @ 4.3GHz (Scythe Mugen2) / Mobo: Biostar TP67XE / 2x Inland Pro 120GB + HDDs / GPU: ATi Mach64 VT2 / Mem: 4x4GB DDR3-1600 G.Skill 8GBXL RipJawsX - 16GB total / PSU: Seasonic S12II 620W.
Secondary rigs:
Core i3 7130U / MiniPC / SanDisk SDSSDP-128G / GPU: Intel HD 620 / Mem: 1x8GB DDR3L-1600
Xeon X3430 2.40GHz @ 3.06GHz or Core i3 540 3.06GHz @ 4.0GHz (Freezer 7 Pro) / Mobo: MSI H55M-ED55 / PNY CS1111 240GB / GPU: ATI FirePro V3800 / Mem: 4x2GB DDR3-1600 G.Skill 4GBRL RipJaws - 8GB total / PSU: Seasonic S12II 620W
AMD Phenom II X4 B93 / Mobo: ASUS M2A-VM / GPU: ATI Radeon Xpress X1250 / Crucial M4 120GB / Mem: 2x2GB DDR2-800 - 4GB total / PSU: Antec 380W.
Core Temp - Accurate temperature monitor for Intel's Core/Core 2 and AMD64 processors
AMD Ryzen 9 5950X (True Spirit 140 Direct) / Mobo: Asrock Fatal1ty X470 / EVO 970 500GB + WD Blue 250GB + HDD / GPU: Dell RX 570 4GB / Mem: 2x16GB DDR4-3200 G.Skill 32GTZKW TridentZ - 32GB total / PSU: Seasonic Prime Ultra Gold 650W
NAS:
Core i7 2600K 3.4GHz @ 4.3GHz (Scythe Mugen2) / Mobo: Biostar TP67XE / 2x Inland Pro 120GB + HDDs / GPU: ATi Mach64 VT2 / Mem: 4x4GB DDR3-1600 G.Skill 8GBXL RipJawsX - 16GB total / PSU: Seasonic S12II 620W.
Secondary rigs:
Core i3 7130U / MiniPC / SanDisk SDSSDP-128G / GPU: Intel HD 620 / Mem: 1x8GB DDR3L-1600
Xeon X3430 2.40GHz @ 3.06GHz or Core i3 540 3.06GHz @ 4.0GHz (Freezer 7 Pro) / Mobo: MSI H55M-ED55 / PNY CS1111 240GB / GPU: ATI FirePro V3800 / Mem: 4x2GB DDR3-1600 G.Skill 4GBRL RipJaws - 8GB total / PSU: Seasonic S12II 620W
AMD Phenom II X4 B93 / Mobo: ASUS M2A-VM / GPU: ATI Radeon Xpress X1250 / Crucial M4 120GB / Mem: 2x2GB DDR2-800 - 4GB total / PSU: Antec 380W.
Core Temp - Accurate temperature monitor for Intel's Core/Core 2 and AMD64 processors
Re: Excessive CPU usage with "CT Gadget"
UPDATE:
After removing Core Temp and "Gadget" and their respective folders, then downloading the software again, all seems to be OK. I have no idea what "Gadget" was doing to use up to ~20% of CPU resources. If it develops the same issue again, I will post here. For now it's good.
After removing Core Temp and "Gadget" and their respective folders, then downloading the software again, all seems to be OK. I have no idea what "Gadget" was doing to use up to ~20% of CPU resources. If it develops the same issue again, I will post here. For now it's good.