The1 - whenever there are problems with fileden, know that we also host th latest RealTemp here. ;)
Printable View
The1 - whenever there are problems with fileden, know that we also host th latest RealTemp here. ;)
Hi, you're going to hate me, but i would like to ask for some assistance with calibrating RealTemp.
I have a Q9550 (E0) running at 3.33GHz at 1.144V. With the Noctua NH-D14 it idles at 39-40C (ambient of 22C), which is quite disappointing. Though, I am aware that 45nm Wolfdale/Yorkfield chips often have stuck sensors.
Idle:
http://dl.dropbox.com/u/95820/Real%20Temp%203.40.jpg
Sensor Test:
http://dl.dropbox.com/u/95820/Window...%20%282%29.jpg
I'm not sure what to make of it, but i'd like to use the idle temps of the cooler running cores. Although I think i've seen you state that Core0 is generally more accurate, logically thinking it seems to be the wrong one.
I plotted the data in Excel, and came up with this:
http://dl.dropbox.com/u/95820/Untitled.png
Judging from that ^, it actually seems that Core1 doesn't move linearly, and that Core0 may have a different tjmax.
Any help would be greatly appreciated, thanks :)
Wondering if anyone can help on this issue. RMA'd my Eclipse+ in mid Decmber and opted to wait for a new one instead of a refurb. It arrived two weeks ago and I just rebuilt the machine last night.
The PCIex bus died on the first one but I had it at 4GHz (20x200) 1.416v CPU, 1.44v QPI, realtemp read usually in the mid 60s C. This new one's been happy at 3.9 (21x187), 1.3v CPU, 1.46 QPI, but RealTemp is now reading 77C! WTF?!? Can that be right?
I installed speedfan and it was reading 12 to 15 C lower on each core, so one of them is lying. I do realize they interpret the sensors differently but that is a HUGE margin. This all made me very paranoid, but P95 has been running with no errors for a couple hours now so it seems pretty stable. It's a Corsair H50 (exhausting) that I attached with AS5, with it's stock fan usually running at appr 1700 rpm under 100% load. The idle temp on the original Eclipse+ was around 32 with Realtemp, but this one idles at around 38 to 40. Is it just because it's a different board? Any ideas?
EDIT: Scratch that! It just crashed, aaaargh!
Also just noticed that it's throttling my multiplier back to 20x from 21x dropping me to 3.75gHz. So the system is noticing the excessive temps I guess.
unclewebb, I noticed that Real Temp 3.50 RC6 does work with my X3440 and Windows XP.
When I double-click it, it does not open. If I click on RealTempGT.exe it shows 3 cores.
I then downloaded version 3.40 off of TechPowerUp! and it works fine.
Just thought I'd let you know. :shrug:
Quote:
Originally Posted by SimpleTECH
I've encountered this issue. You launch RT and it does not open yet the process appears in the task manager. What you need to do is to end the process, reboot, delete the program, extract it again and run it. It will run fine afterwards.
http://i49.tinypic.com/2z9addc.png
yes they do like to have stuck sensores for some reason. i have 2 of them 0core and 2core. both wont go lower than 39c. and 3core wont go under 36c but once under stress they are just fine. core 1 is the only one that isnt stuck for me.hence the nice low of 26c. i love that..lol im getting the new HAF922 in the next day or 2 waiting on it to be shipped. hope that will drop a few degrees..
cjbrown80: RealTemp and Core Temp both follow the Intel directions for reading TJMax directly from the Core i7 CPUs. If SpeedFan does not do this correctly then it won't be able to report your temperatures correctly.
SimpleTECH: Thanks for that. That's not the first I've heard of that issue. RealTemp 3.50 always opened up fine for me so I'm not sure if there is a borked version running around in the wild or what's gong on. I'll plug my XP drive in and see if I can figure out any problems. I mostly use Vista or Windows 7 these days and haven't had any problems.
Wishmaker: Your testing might help me find the RealTemp hangs at start up issue.
cincyrob: Your version of RealTemp is so damn bright it's hurting my eyes. :D
M4rk: Intel's sensors on the 45nm Core 2 Quad chips don't start to become consistent until beyond 70C which is where Intel calibrates at least one of them. TJMax can vary significantly from one core to the next on these CPUs but you can't determine or take a wild guess at that until the CPU is at a much higher temperature than what you are running at.
There is so much error in the Core 2 45nm sensors caused by a variety of issues that accurate temperatures is mostly a guessing game. I tend to trust core 0 the most. Run your CPU as cool as possible and you'll be able to overclock it reliably as high as possible. Don't put too much effort into trying to get an exact temperature out of these crappy sensors. That's not what Intel designed them for and it shows.
Quote:
Originally Posted by unclewebb
No worries. Let me know what I have to do. Sorry for my absence, I've had a month of exams and I used my main desktop like a netbook : editing documents , slideshows and printing projects. Talk about having and overkill system for stuff like that :rofl::rofl:.
I have the RT problem again after fixing it two days ago :(. It seems that it randomly stops working. The process is shown in the taskmanager, 2nd process top to bottom but the program does not load. I have to end task, reboot, etc.
After you reboot does RealTemp appear normally?
This might be caused by the ATI code I added. You can try adding this to your RealTemp.ini file next time you have a problem.
NoATIGPU=1
I plan to make the ATI code optional in the near future. It samples my 5770 with no problems but for other combinations it's hit and miss. It might work OK when not in CrossFire but might choke when you are in CrossFire. I was hoping ATI would release a driver by now that would magically fix a few things. Did you update to 10.1 recently or are you using an older driver?
Uncle,I saw Real Temp 3.50 and i5-660,didn't match CPU speed and multi.
1.http://www.xtremesystems.org/forums/...&postcount=101
2.http://www.xtremesystems.org/forums/...2&postcount=21
Any particular reason?Thanks.
Quote:
Originally Posted by unclewebb
Thanks, that fixed this PIA issue I had. :up:
I would end up with multiple RealTemp.exe's in the Task Manager but not see it running (I clicked it multiple times).
I am on Vista 64 SP2 and have a Nvidia GPU and RT 3.50.
EDIT : Just to let you know as it was totally random, I did not need reboot to run it after adding that line to the " .ini file ", I simply edited then saved and ran it and it opened 1st time.
:)
Thanks uncle. Given that the 45nm C2Q sensors are crap, I decided to just calibrate my idle temps, regardless if it's the right thing to do.
Also, I just noticed this:
http://dl.dropbox.com/u/95820/realtemp_fsb_bug.jpg
My FSB is at 390MHz, as reported my CPU-z. New bug? :D
Most of the screen shots are taken at idle. The actual multiplier at idle can be influenced by how the Power Options -> Minimum processor state is set as well as C1E and SpeedStep. I don't know how his computer is set up so it's hard to comment.Quote:
Originally Posted by stasio
In the second post with 4 pictures, CPU-Z and RealTemp are in agreement on 3 out of the 4 pictures. For the first picture, RealTemp is reading a lower multiplier at idle which might be a sign that he has C1E enabled.
In the first post with RealTemp reporting a 25 multiplier, I'm not too sure. RealTemp uses internal timers which can accurately determine the multiplier but unfortunately they are not a protected resource so any monitoring program can change or reset them. I haven't kept track of what program is using or abusing these timers so I'm not sure if maybe one of the other monitoring programs he was using might be using these timers inappropriately.
When RealTemp is running by itself, I haven't seen it get the multiplier wrong on too many Core i7/i5/i3 CPUs.
As for Core 2 CPUs like M4rk, that's another story. :)
I was helping JohnZS with his QX CPU a couple of months ago and accidentally released a "test" version designed for him into the main beta download area. That one off version got hosted everywhere so I said F it. I got side tracked with other projects at that time so left it and since there have been very few complaints, I haven't been motivated enough to fix it. Between that bug and the ATI code blowing up randomly on some computers while working fine on others, I just kind of lost interest in project RealTemp.
M4rk: Try downloading the last official version, RealTemp 3.40, and see if that gets your multiplier right. If so I'll send you an updated version tomorrow.
Not only on I5 Stasio on my Xeon X3380 the same...also Realtemp, Coretemp shows 5C more than Everest, Speedfan, HWinfo and so others :shrug:Quote:
Originally Posted by stasio
you can see the temp issue here
http://img215.imageshack.us/img215/5...951125cust.jpg
Here's the formula that all software uses:
Reported Temperature = TJMax - Digital Thermal Sensor reading
All software reads the same data from the same on chip digital thermal sensors. The disagreement is in TJMax. RealTemp and Core Temp assume that value is 100C and other software assumes that value is 95C so RT and CT will always report a temperature 5C higher than the other programs.
Which value is correct? The truth is that there is no documented correct value. All software is guessing.
The only documentation ever published by Intel calls this value TJ target and they've said that this is not a fixed value. It can and does vary from one CPU to the next with the same model number and in my testing it also varies from core to core on the same CPU. Your core 1 reading much lower than the other 3 is a good indication of that.
These sensors are designed for thermal throttling and thermal shut down control and are accurate enough for those purposes. For any other purpose like accurate temperature reporting, the 45nm Core 2 Duo/Quad sensors are crap with a long list of known issues. 100% accurate temperatures from these undocumented sensors from idle to TJMax is simply not possible.
If you want RealTemp and Core Temp to low ball your temperature readings like the other programs are doing then set TJMax to 95 instead of 100.
Thanks Uncle :up:Quote:
Originally Posted by unclewebb
Yep, that works. Thanks :)Quote:
Originally Posted by unclewebb
Eh, I pref the cleanliness of CoreTemp as I get the exact same temp readings from both utils. The extra info in RealTemp is nice but I just don't care for the extra info for my under-volted E7600.
unclewebb, just for your info, Real Temp 3.50 won't run if I don't put the NoATIGPU=1 into the RealTemp.ini like you suggested. I have a Sapphire Radeon 4850X2 on Win7 64-bit with the 10.1 drivers, and I am running in CrossFire. Let me know if you need more info.
Uncle Webb,
FYI... I came across this bug in RealTemp 3.50. This is on my wife's older 975X chipset mobo running Windows XP Pro. It does not report the fsb/multi like the other two versions.
quick question, is 105c the correct tjmax for the 32nm i3-530?
It's written in MSR (no more guess) so it should be correct. :)
ok thanks.
Hi Uncle, ive been using Realtemp for over a year now. Ive upgraded to the latest beta and am getting this issue:
Realtemp crash on open
Event ID 1000
Faulting application name: RealTemp.exe, version: 3.5.0.0, time stamp: 0x4b25596b
Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdb3b
Exception code: 0xc0000005
Fault offset: 0x0002de64
Faulting process id: 0x12c0
Faulting application start time: 0x01caab602ffe1283
Faulting application path: D:\Jasjeet\Downloads\OC\RealTemp_350\RealTemp.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 6dc56147-1753-11df-8efd-00221517d003
Windows 7 x64, Q6600 3.2ghz, 4gb Ram, ATi 4850 (maybe issue getting the GPU temp)
Prime95 for 2hrs passed today to confirm CPU stable
Memtest 200% pass today
Older versions run fine. Though i cant rule out an OS file system problem, but its only Realtemp causing an issue. If i log off, then log on, it works OK. But if i reboot/shutdown then on boot up it will not launch even with Run as Admin. I have to log off, log on for it to work. Some kind of Ram writing/permission issue i think.
If this is a problem i hope you can fix it =)
Thanks
I have been getting crashes lately too with 3.50 RC6. It worked fine for months and all of a sudden I'm getting this:
http://i176.photobucket.com/albums/w...temp_crash.png
It works fine if I run any compatibility mode. Oddly enough it started crashing about the same time as my .NET runtime started going crazy and crashing any .NET program that tries to use Windows Forms (even in compatibility mode). But RT doesn't use .NET...