Real Temp - New temp program for Intel Core processors

[zoom314]

I tried 3.60 on Vista x64, 3.60 would not show the temps of My video cards(a 6200 and a GTX295), Yet 3.58 does, So I went back to 3.58.

[unclewebb]

zoom314: Did you try checking the Nvidia box in the Settings window? GPU monitoring is optional in the recent versions of RealTemp so maybe that's the problem. Nvidia and ATI temperature monitoring code is not the most efficient stuff so I thought making it optional would be the best solution. If it still doesn't work, let me know what happens.

[zoom314]

zoom314: Did you try checking the Nvidia box in the Settings window? GPU monitoring is optional in the recent versions of RealTemp so maybe that's the problem. Nvidia and ATI temperature monitoring code is not the most efficient stuff so I thought making it optional would be the best solution. If it still doesn't work, let me know what happens.

Huh? settings window, Is that the Nvidia control panel? If It's not, please advise, As that is as clear as mud to Me, As I just installed Vista Business x64 on Monday.

Ok, I think You meant the 3.60 settings window, the gpu button in 3.60 is disabled, So no dice. I'd provide a screen shot, But My normal video software is not installed under Vista x64 yet.

[unclewebb]

What happens when you put a check mark in the Nvidia box?
If the box goes gray and nothing happens that's a problem.

[zoom314]

What happens when you put a check mark in the Nvidia box?
If the box goes gray and nothing happens that's a problem.

Oopsie, I didn't see that, My bad, That Nvidia fixed that, I must be more tired than I thought I was.

[dejanh]

Any updates to RealTempGT as part of the 3.65 bundle?

[unclewebb]

RealTempGT doesn't need Sandy Bridge support at the moment so I won't be working on it quite yet. I learned a few interesting things about monitoring power consumption in Sandy Bridge as well as correctly adjusting the Sandy Bridge power limits so that's going to come first.

[Daddyjaxx]

Both Realtemp and Aida64 both freeze on me running Prime95 after about half an hour although Prime95 keeps chugging along. If I use OCCT large, Realtemp freezes immediately and stops responding. Am I the only one with this issue on a 2600K? I do not run Realtemp and Aida64 at the same time. Any idea why Realtemp stops responding?

I have to use the Asus beta BIOS 1053 to boot into Windows at anything above 4.7 and then I can run 5.0 stable at 1.425, but with all my temp programs freezing, I don't have any idea what the temps are. Before it freezes, my highest temp is about 65c. Another bad thing about the Asus Beta is that I cannot run my memory over 1600 MHz or it won't even boot. I can do 4.7+ with memory at 2133 or 5.0 with memory at 1600.

[ehume]

I have an As.s board. I can't use their software to monitor anything - it screws up the interfaces for everything but itself.

[unclewebb]

I had random freezing problems recently when checking out AIDA64 on an older Core i5-650 CPU. I had no freezes before installing AIDA64 and I've had no freezes since removing both versions that I tried.

Try completely removing AIDA64 including the side bar gadget. I can't think of anything that RealTemp is doing any differently than what it has been doing for a long time without any issues.

Daddyjaxx: Are you running RealTemp 3.65?

[Daddyjaxx]

It is definitely Aida64. I just reinstalled Windows because I was having all kinds of flakiness from switching to the P67 chipset from an X58 backup. On a fresh install at stock, the computer froze on me. When I restarted, the Aida64 side gadget was stuck where it was when it froze. Uninstalled it and no more freezes. I am using 3.65. I'm going to let Prime run now and see if I get the same wierdness. I don't think I will because I used 3.60 on a fresh install with the same CPU and motherboard before I put it in the case and restored the backup.

[unclewebb]

RealTemp 3.67
http://www.mediafire.com/?n99nq4kn95u6i6a



-added Sandy Bridge VID / power consumption monitoring.
-added Sandy Bridge power limit adjustments if they are not locked by the bios.
-added ability to save the log file to a network computer.
-added Disable Turbo (IDA) option for Core 2 mobile CPUs.
-updated i7 Turbo GT program for Sandy Bridge CPUs.
-also updated the RTCore.dll RivaTuner plugin.

Thanks to burebista and somebody for all their help testing.

Daddyjaxx: Thanks for confirming that AIDA64 is also causing you some random lock up problems. Without AIDA64 installed, the computer I was using seemed stable. I've heard this issue might be memory voltage related but I lost interest trying to debug this without doing any thorough testing.

Too busy working on my own projects.

[boogeyman]

Thanks Uncle ! Works good in RT.

[unclewebb]

RivaTuner has been mostly replaced by MSI Afterburner.
It's good to see the updated RealTemp RTCore.dll RivaTuner plugin reporting Sandy Bridge correctly.



The Frequency graph might help some gamers confirm that their CPU really is turbo boosting up to full speed.

[ugotd8]

Perfect !!! Nice job and thank you.

[Sandog]

Real Temp does not work properly with the i7-970 Gulftown. It only shows 3 cores.

Thanks,
Sandog

[BobyTT]

use the GT exe instead.

[roadie]

Thanks for making this mate. Extremely useful utility.

[boogeyman]

Another useful item in this proggy would be Vcore display in Rivatuner. Is this possible?

[burebista]

I guess it's possible, but only for Sandy and TBH we don't know yet if that register is Vcore or a sort of VID request.

[Bullu$]

Realtemp doesn't show the bclck value correct


I oc the bclck with MSI Control Center II

edit;
When I'm set it in the bios it read fine but change it in MSI CCII it doesn't change

[unclewebb]

WinTimerTester
http://www.mediafire.com/?io91a22pa6z8ntv

Bullu$: If you want to help fix this bug, can you run the above program for about 60 seconds when not overclocking and then run the same program when you are overclocking with MSI CCII and post a screen shot of each.

WinTimerTester uses two different methods to measure time in a Windows PC. In theory, these two methods should both run at the same speed so the long term ratio between these timers should be 1.0000:1. If one of these timers is not accurate after you overclock while in Windows, then that is the source of this problem.

I think the bug you've found is a Windows bug with the high precision timers. Windows can measure time very accurately but this "stopwatch" is sometimes based on the total CPU MHz. If you change your base clock speed by using SetFSB or a similar Windows program, the Windows high precision timer can go out to lunch. This bug can screw up a wide variety of programs besides RealTemp.

If you run those tests, I'll put fixing this on the things to do list. If you're willing to waste some CPU cycles, this problem can be fixed but the results might not be as steady as the RealTemp MHz usually are.

There haven't been enough complaints over the years so it hasn't been a high priority to fix this. I thought this problem was mostly fixed in Vista but then it came back in Windows 7. Have you upgraded to SP1 yet? I'm not sure if Microsoft has come up with a fix for this or not. It tends to be motherboard specific so not all boards have this problem. Windows is supposed to measure time based on a fixed timer that doesn't change speed when the FSB or base clock changes speed but that's not always the case.

[some_one]

I think the bug you've found is a Windows bug with the high precision timers. Windows can measure time very accurately but this "stopwatch" is sometimes based on the total CPU MHz.

Try setting BCDedit to use HPET with W7.

bcdedit /set {current} useplatformclock yes

[Bullu$]

WinTimerTester
http://www.mediafire.com/?io91a22pa6z8ntv

Bullu$: If you want to help fix this bug, can you run the above program for about 60 seconds when not overclocking and then run the same program when you are overclocking with MSI CCII and post a screen shot of each.

WinTimerTester uses two different methods to measure time in a Windows PC. In theory, these two methods should both run at the same speed so the long term ratio between these timers should be 1.0000:1. If one of these timers is not accurate after you overclock while in Windows, then that is the source of this problem.

I think the bug you've found is a Windows bug with the high precision timers. Windows can measure time very accurately but this "stopwatch" is sometimes based on the total CPU MHz. If you change your base clock speed by using SetFSB or a similar Windows program, the Windows high precision timer can go out to lunch. This bug can screw up a wide variety of programs besides RealTemp.

If you run those tests, I'll put fixing this on the things to do list. If you're willing to waste some CPU cycles, this problem can be fixed but the results might not be as steady as the RealTemp MHz usually are.

There haven't been enough complaints over the years so it hasn't been a high priority to fix this. I thought this problem was mostly fixed in Vista but then it came back in Windows 7. Have you upgraded to SP1 yet? I'm not sure if Microsoft has come up with a fix for this or not. It tends to be motherboard specific so not all boards have this problem. Windows is supposed to measure time based on a fixed timer that doesn't change speed when the FSB or base clock changes speed but that's not always the case.

first is in idle


Next is changing the blck


Real temp does also change correct, but if i close the wintimer it goes back to 105bclck.

I running W7 with SP1

tnx

[Bullu$]

sorry double post ,because the forum is really slow