Printable View
That's what the log file option in i7 Turbo is for. Upload the log file somewhere and I will have a look at it. Excel makes it easy to find the minimum value in a column of numbers and then you can find that minimum value in the log and have a look to see if it was a one second freak occurrence or if the multiplier spent a big percentage of time at 20.5 or whatever.
SendSpace works good.
http://www.sendspace.com/
unclewebb, which log file i have to look at ?? realtemp ?? prime95 ?? or which one
When testing for throttling, you should be logging with i7 Turbo V8. Just check off the Log File option. It's the most accurate tool to report your multiplier so use it. You can save your data as an Excel file but if you don't have Excel then your data will be saved as a text file so you can check it out with Notepad or WordPad. It's easy enough for me to import that data into Excel so I can do some analysis with it no matter what format you save it in.
I ran OCCT test for 2 hrs, I use realtemp, everest , cpuz to monitor the multiplier and it never went down , so is that mean I don't have the throttling issues right ???Quote:
Originally Posted by unclewebb
Where I can download i7 Turbo V8 please ,thanks
http://www.fileden.com/files/2008/3/3/1794507/Turbo.zip
RealTemp 3.00 and CPU-Z round the multiplier off to the nearest 0.5 which isn't much use when checking for turbo throttling. Everest is probably similar.
Would you do neurosurgery with a butcher knife? I hope not. :D
You need to use the right tool for the job.
This thread has a few examples of what this turbo throttling stuff is all about.
http://www.xtremesystems.org/forums/...d.php?t=225450
I just use realtemp version 3.30 to monitor multiplier, and I notice it jumping from 21 to 20.8 occasionally.
If you saw 20.8 at full load, that's the first warning sign of turbo throttling. RealTemp 3.00 used to use steps of 0.5 but I tightened that up to steps of 0.2 for RealTemp 3.30. The best tool is still i7 Turbo V8. That uses steps of 0.001 to report the multiplier. If you are running Prime Small FFTs, it should be locked on 21.000 and should rarely if ever drop below that number while you are at full load. Turn off Everest and try running LinX. If the Calculated multiplier is dropping at full load then that's a problem. If this happens, overclock your CPU less and re-run LinX until your multiplier is steady at 21.000 at full load.Quote:
Originally Posted by icecpu
even at idle or full load realtemp multiplier jumping up and down 21 to 21.8
I will try i7 Turbo V8
EDIT:
I just tried i7 Turbo V8, at idle it also jumpimg from 21.000 to 20.999 to 20.875
When testing, turn off Everest. That and HW Monitor can cause issues on some boards. i7 Turbo V8 should report a steady 21.000 at full load. Your idle multiplier can be effected by your Control Panel -> Power Options -> Minimum processor state setting in Vista or Windows 7. If your CPU is lightly loaded and you have C3/C6 enabled in the bios, it's also possible to see multipliers greater than 21.000 depending on your board.
ok thanks a lot unclewebb
It is locked at 21x in i7 Turbo V8 at full load
so how long does it take to find out if it throttling??, I ran for 10 mins it seems to stick at 21
If your temperature and voltage are consistent at full load then it shouldn't matter whether you test for 10 minutes or 10 hours. If you can run LinX at 4.1 GHz with 1.25 volts and the multiplier is steady at 21.000 then you don't have a problem with turbo throttling. If you decide that you want to push a little further then test again. There's not much point in overclocking to 4.2 GHz if your CPU suddenly starts to turbo throttle at full load, the multi drops to 20.0 and all you're really ending up with is 4.0 GHz. If you do a long Prime or LinX run, it won't hurt to run an i7 Turbo log at the same time so you can go back and make sure everything is OK.
my temp for the highest core is very high at 87C , so I don't think temp is the factor that cause the turbo throttling issue,
the multiplier is really steady at 21.000
Thanks a bunch for all your great program and help
hey guys...
Some one have the config of the high bblock get it on P6T DLX?
Hi, I am a novice in the subject overclock, and if they could not comment on my oc, I also left some questions in order to dispel my doubts:
Okay the oc?
CPU voltage is too high for 24/7?
that could be done to improve the oc?
Now here we leave the description of my pc and photograph
PS: greetings and thank you very much for your answers :D
http://img190.imageshack.us/img190/7894/cpup.th.jpg
Corei7 920(D0)
Noctua NH-U12P
Asus P6T Deluxe V2
6 GB G.Skill DDR3 1600 Mhz (8-8-8-21)
Topower M2 600W v2.2
@March3lo
I'm using 1.26vcpu for 4.0ghz (20x200) and 1.3vqpi / 1.70vram @ 1600mhz 7.7.7.24.
Will try later 21x200 to see the vcpu required to be stable.
I have a dlx v2 crossflashed to v1 with 0006 bios.
thanks for your reply kado-pt, but as I have a question, 1.7 for the memories will not be much?
As long as the difference between vram and vqpi does not exceed 0.5v it's ok to use 1.70v (1.70-1.30=0.4).
Hi,
Just wondering if anyone could say what is the trouble with my BIOS update on the subj.
Any BIOS newer than 1206 won't let initialize my USB keyboard (Logitech G15) during POST so that I cannot enter the BIOS settings...
Thought the newer BIOS versions would save this, but still to the same effect.. Every time I'm trying to update the BIOS, I have to pull out of garbage my old PS/2 keyboard to be able to enter BIOS settings at all... WTF???:(
Thank for any suggestions.
Regards,
R
vDimm - vQpi ≤ 0.5v :)Quote:
Originally Posted by kado-pt
Will the 0006 bios increase overclocking capability (lower voltage or higher frequencies) or will it just fix the turbo issue?
I'm thinking of flashing my v2 with it but if it's just the turbo issue I might skip it. :)
:) :) :) :)
Quote:
Originally Posted by kado-pt
thanks :D, but I have another question, my oc that well? or very high voltages? there any risks for 24/7?
thanks for all :D
My results with bios 0006 installed on P6T DLX V2.
I juts don't understand why the bblock is not locked in 215 like i put in the bios. This is something to do with the 0006 bios?
Core i7 D0 @ 4510mhz - 1.368vcore
watercoooled :)
Teste over 8h Prime95 Stable!
http://img338.imageshack.us/img338/3...ei74500mhz.png
http://img232.imageshack.us/img232/7...105h59cpu1.png
http://img268.imageshack.us/img268/7...105h59cpu2.png
http://img115.imageshack.us/img115/4...105h59cpu3.png
http://img338.imageshack.us/img338/8...105h59cpu4.png
It's important to keep in mind how much your QPI/VDIMM voltage droops on your board though. On some i7 boards the vqpi droops as much as .1v so if yours did you'd be right at 0.5v differential.Quote:
Originally Posted by kado-pt
Okay guys, I was about to flash my v2 to the 0006 bios but I have a little problem.
I made a bootable cd with Nero and put afudos and the .rom file in it, but after it has booted my usb keyboard does not work.
So I cant write anything.
Anyone has a solution?