The versions of Speccy and Core temp are the same, although on Windows 10 they are 64 bit and on Windows XP they are 32 bit.ĪMD 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Ĭore 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.Ĭore i3 7130U / MiniPC / SanDisk SDSSDP-128G / GPU: Intel HD 620 / Mem: 1x8GB DDR3L-1600 The processors are X5460 Quad Core Xeons, and the motherboard is a Supermicro X7DAL-E+ server board.Īnyone any idea why the Core Temp readings would be different on the two operating systems? This is mirrored on Windows XP on Speccy, but not on Core Temp, where the processors appear to be running at pretty much the same temperature. On Windows 10 in fact Speccy and Core temp pretty much agree, and they both agree that Processor 0 runs about 10☌ hotter than Processor 1.
However, I've now become aware that the discrepancies I'm seeing on my dual processor dual boot system are not consistent. Now I'm well aware that Speccy is notorious for giving hugely inaccurate temperature readings with some processors, in fact there is a huge thread on their forum dedicated to this! Hi, I've been using Core Temp for ages to monitor my CPU temperatures in my system tray, but since I installed Piriform's Speccy system monitor, I've been aware of a discrepancy between them on the temperature readings.
0 kommentar(er)
