The reason behind this is because it made my life simple. I told you I was new to using INI files. In the next major release I'll make some changes so RealTemp is more logical and doesn't create an all new INI file on each exit.
The factors I've chosen were based on what I've observed to date. I can certainly add a 3 to the list. I thought that if a user had to go beyond 2 then it was possible that RealTemp had guessed wrong at TjMax.2. Calibration can be either +- 0, 1 or 2. This is not enough.
Are you air or water cooled? My observed idle temperatures during my low MHz / low voltage test were with a Tuniq Tower with the fan at its highest speed. More data from other users running this test with a variety of processors would be helpful.
I'm 100% confident that TjMax=95C is correct for my 45nm E8400 but I have not had my hands on a 45nm Quad for testing. This choice looks appropriate for core0 and core1 of your Quad but not so appropriate for core2 and core3. I'm still trying to sort this behaviour out on my Q6600 and what is the real cause of it. Can you PM me a RealTempLog.txt file for your Quad with the calibration factors all set to 0 and run it from idle to full load to idle using Prime small FFTs on each core? Do all 4 cores report more or less the same at full load?
Neither does CPU-Z! I'll see if I can save some X,Y co-ordinates in the INI file.3. On my box, RT does not remember its last position on a screen.
BTW, The GUI is now very clear![]()
Even SpongeBob is happy now!




Reply With Quote

Bookmarks