Real Temp - New temp program for Intel Core processors

I've re-thought this and I know when I've been doing some high temp Prime runs that Core processors randomly re-boot before showing an error. Losing all the temp data that's been gathered before it's been saved isn't much use to see how hot it was running at the time that it crashed. An INI option is simple to implement. I'll also reduce the default setting. Compared to the way Windows is always thrashing away, RealTemp isn't exactly a major load on things. If a user doesn't want RealTemp writing to their hard drive then it's easy enough to turn off the log file option.

Thanks for the suggestion.

I had always assumed it just wrote to log whatever interval was set. I'm still stuck on mbm5 and that's what those logs were like.

Hard drives are slow compared to memory so it's more efficient when writing small amounts of data to cache it in memory for a while first but the risk is loss of data if your computer crashes. It's better to write 2000 bytes of data to the hard drive once than to write 20 bytes of data 100 times. I'll make this fully adjustable for power users but will hide it from the GUI. I've got no room left there for any new features!

I guess I'm showing my age. My first computer ran at 7 MHz and didn't come with a hard drive. I couldn't justify spending another couple of hundred bucks for a 20 MB drive so only had a floppy. :rofl: Writing data to the hard drive back then was not an option!

Any chance of adding a 'run this program when windows starts' option?

Cheers.

Quote:

---

Originally Posted by Xello

Any chance of adding a 'run this program when windows starts' option?

Cheers.

---

I second that idea :D

In XP, drag a link to RealTemp into your All Programs -> Start Up folder and in Vista, let the Task Scheduler handle it.
http://www.xtremesystems.org/forums/...postcount=1816

I prefer not to add anything to a user's registry but I'll consider an option for this in the future.

Quote:

---

Originally Posted by unclewebb

In XP, drag a link to RealTemp into your All Programs -> Start Up folder and in Vista, let the Task Scheduler handle it.
http://www.xtremesystems.org/forums/...postcount=1816

I prefer not to add anything to a user's registry but I'll consider an option for this in the future.

---

Thanks i'll try that out.

I have vista home premium, UAC disabled, I saved the entire RT program in the start up folder. When I had the RT file elsewhere and a shortcut to RT in start up it did not work. Now it will start minimized every time.

Quote:

---

Originally Posted by WoodButcher

I have vista home premium, UAC disabled, I saved the entire RT program in the start up folder. When I had the RT file elsewhere and a shortcut to RT in start up it did not work. Now it will start minimized every time.

---

Use the Task Scheduler, that worked for me. Right click Computer > Manage, and you'll see it.

Thanks Xello, I found a couple of goodies there I didn't want, didn't know were running. Microsoft was looking in my window!:eek:

Did you try that Autoruns program I think I recommended here a while ago. It's almost shocking when you see how much junk is starting up in the background when you start Windows. A Windows OS is definitely not for anyone with paranoia issues! :shocked:

Yes I did, popped that into my toolkit when you mentioned it 2-3 pages ago. I haven't had use for it yet but it looks good. Dinner at the in-laws, watch the game, tune the pcs'.
What I found was one of Microsofts user experience goodies. I don't mind answering a survey from time to time but I don't like the idea of leaving the line open.

...right now RT tried to access internet via PG2, PeerGuardian2, which ZA alerted me and asked if I would let it do that, I chose Deny as it has never happened before...

was that a good decision?


http://osalerts.zonelabs.com/osanaly...4&tab=overview

There is no code within RealTemp that should be contacting anything. The only code that I know nothing about is the WinRing0 driver that RealTemp uses. Putting a processor into Ring0 mode could be seen as suspicious but there is no other way to read the digital thermal sensors on the processor.

The message says that it was RT trying to contact PeerGuardian2. It doesn't say that it was trying to contact the internet.

What version of RealTemp are you using and where did you download it from?

You can tell ZoneAlarm to permanently block RealTemp from trying to send Messages to PeerGuardian2 and see what happens. If RealTemp doesn't report temps anymore then I guess you'd have to change that if you wanted to continue to use RealTemp.

ZoneAlarm and PeerGuardian2 are both firewall programs so maybe they're fighting it out!

Quote:

---

Originally Posted by -X-hellfire

...right now RT tried to access internet via PG2, PeerGuardian2, which ZA alerted me and asked if I would let it do that, I chose Deny as it has never happened before...

was that a good decision?

---

ZA is a trojan on its own...

Kind of slow today so here's some testing that i43 sent my way so hopefully he doesn't mind that I share it:

http://img183.imageshack.us/img183/5...4232pu4.th.png

It shows a few things. You can be overclocked and still be Prime stable at a blazing hot 99C even while thermal throttling is taking place.

i43 needs a large negative calibration factor on core0 to get his idle temps balanced out but at TjMax, where these sensors are calibrated by Intel, the temps start to line up very nicely between core0 and core1.

The last thing this shows is that CoreTemp continues to use TjMax=105C for the 45nm processors and the competition still gets confused when the temps go beyond TjMax.

Another thought, the main temps i keep an eye on during prime runs are my 4 cores and my NB, but i'm having to use Everest for the NB right now. Any chance of putting a NB display in the program? Or is this just for cpu's. Would save having an extra program open :D

RealTemp will likely remain Intel core temps only. I think you can manually set TjMax in Everest now so as long as that is the same as what RealTemp is using then your full load temps should be pretty much the same. I hate recommending the competition. :(

If you double left click on RealTemp at least it won't take up too much screen real estate.

Quote:

---

Originally Posted by unclewebb

Kind of slow today so here's some testing that i43 sent my way so hopefully he doesn't mind that I share it:

http://img183.imageshack.us/img183/5...4232pu4.th.png

It shows a few things. You can be overclocked and still be Prime stable at a blazing hot 99C even while thermal throttling is taking place.

i43 needs a large negative calibration factor on core0 to get his idle temps balanced out but at TjMax, where these sensors are calibrated by Intel, the temps start to line up very nicely between core0 and core1.

The last thing this shows is that CoreTemp continues to use TjMax=105C for the 45nm processors and the competition still gets confused when the temps go beyond TjMax.

---

Hi Unclewebb :)
No problem with any screens what have sent to You .. U can use them what ever you want :)

---
just a note to that (current) screened ''heat-up'' test
(where 99 C * read/logged by RealTemp )
-- this was achieved ONLY! when CPU TM Function was DISABLED ! -- ( in asus P5K3 DLx - bios )

PS ! in my other tests, where this *CPU TM function* [ ENABLED ]
i was never able to get that high ( i mean over 94C )

:)

Your testing was very interesting and thorough i43 so don't be afraid to post some of it here or in the E8400 forum to show people what these processors are capable of.

Many users turn off everything in the bios when overclocking but you've proven that leaving TM enabled is a good idea in case of a CPU fan failure or your heatsink falls off!

Hey again.

I noticed that after a certain amount of time (a few hours maybe), the program becomes see-through or just a black box. Though when minimized the temps continue to display properly, so it's not a complete hang. I'm on Vista 64, is this a known issue?

Never seen that with RT. Are you sure you are 100% stable with stable graphics drivers?

Yeah this is definitely a RT thing, my 9600 is on stock clocks and completely stable with WHQL drivers. If i close the program and run it again it's fine, i'll try to get a pic of the next time it happens. Even though the box goes black / see through, when i move my mouse cursor over the areas where the fields of text are the cursor changes accordingly. Really strange! It's definitely after extended periods of time being minimized.

Xello: I can honestly say that this is the first I've ever heard of this problem and off hand I can't think of anything RealTemp is doing that would cause this. Next time it happens post a screen shot and any details you can think of like if it was Minimized to the system tray or if it was in Mini-Mode or if the RealTemp dialog was just sitting on the desktop and then you had a look at it an hour later and it was black. If you move the mouse back and forth over it will every thing return to normal or do you have to restart? It does sound like a Vista / driver issue. What card are you using and what driver version?

Quote:

---

Originally Posted by Xello

Yeah this is definitely a RT thing, my 9600 is on stock clocks and completely stable with WHQL drivers. If i close the program and run it again it's fine, i'll try to get a pic of the next time it happens. Even though the box goes black / see through, when i move my mouse cursor over the areas where the fields of text are the cursor changes accordingly. Really strange! It's definitely after extended periods of time being minimized.

---

That's a 9600gt issue not realtemp I think. I have occasional weirdness with my 9600's too.