Humm it sounds weird that you needed to set the IOH higher just like that...
Which BCLK are you running at?
Printable View
Humm it sounds weird that you needed to set the IOH higher just like that...
Which BCLK are you running at?
1.4v is high indeed, so far 1.3v seemed to be enough for everybody i heard of...
reboots huh? hmmmm what are the cpu and chipset temperatures? what psu are you using?
do you use eist? did you try to bump up vcore to see if that helps?
Hi saaya,
my current emps are roughly 37C on the chipset/board and core temps are about 71C in Realtemp or 61C in Speedfan. Stupid unclear Tjmax specs... Running the memory at 1200 doesn't change the temps much, if at all.
Not using EIST. All CPU features except for the prefetchers are disabled.
My PSU is a Coba Nitrox 750W. It is a OEM PSU made by CWT, it has the same 'innards' as the Thermaltake toughpower series with their fake four 12V rails. I was surprised to see a double-sided green PCB inside instead of the normal single-layered ones.
Matter of factly the 12V rails are connected together internally.The MOSFETs and diodes for the 12V circuit are specified for 80 amps. Makes sense if the total current for 720W on the 12V rail alone could be up to 60A. It is one year old and I checked the elcaps when I put the i7 together. All looked fine. Voltages are stable with my multimeter. I can't see ripple tho without an oscilloscope.
As for my core voltage, 1.25V are enough for 3.8 GHz. I am currently at 1.30, but I did not intend to go further than that.
I read a recommendation from TheRAMGuy at the Corsair forums to someone who had an issue that sounded much like mine, but with 6 modules. RAMGuy recommended to set the QPI voltage to 1.5, but that did not change anything for me.
I've tried IOH voltages of 1.20, 1.26 and 1.36-1.4. Anything above 1.26 did not show a change, 1.20 was unstable. So 1.26 seems to be about the sweet spot.
Hmmm....
qpi voltage is vtt, it actually has nothning to do with qpi, its powering the uncore of the cpu, the l3 cache and imc... so yes, if you use a lot of mem at high clocks or tight timings you need to push the uncore voltage up so the imc can run stable... ioh is the northrbidge, the x58 chipset, increasing ioh 1.1v results in higher and higher stable bclocks, its not related to memory directly.
so what exactly is your problem? getting mem clocks up?
Like saaya said, qpi voltage is "only" about everything in the processor, but the cores... So it's pretty important for memory overclocking..
I wish evga x58 bios offered a 9x multiplier for the memory... I can't use 2000MHz with the 200BCLK, but I wish I could use 1800 instead of 1600...
as far as i know there are no uneven memory multipliers :(
even on 1156 there wont be... thats where unlocked cpu multis really come in handy, you have a much wider range of cpu and memory speeds you can run... but getting a 965 just for that doesnt make sense, of course...
i asked intel for half multipliers or at least uneven multipliers a while ago but they said they dont think its necessary...
more multipliers always mean a slight loss in efficiency and can cause annoying bugs, need more time to test as well to make sure they all work...
in the end intel is right, especially seeing how extra mem clocking barely makes a difference... and with ddr3 we are quite flexible with timings and speeds, so just tighten the timings id say...
1600 cas6 is way tight and as fast or faster than 1800 cas7...
I can only repeat myself:Quote:
Originally Posted by saaya
I am running my i7 920 at 19x200 and either DDR3-RAM clock 1200 or 1600. My memory is 4 pcs./2 sets Corsair TW3X2G1600C9DHX modules that I bought in fall 2008 with the perspective of using them on my future Nehalem system. Memory sockets A1, A2, B2, C2 are populated according to Intel's specs.
My modules are working fine at 1200/7-7-7-20, 1.5V.
However, 1600 is a bit of a different story.
1600/9-9-9-24/1.8Vdimm and 1.35-1.5V QPI/uncore leads to random sudden reboots of my system without a bluescreen.
I am not getting any errors in LinX, no errors or failing worker threads in Prime 95 x64, and no errors in Memtest 86 plus V2.11 either. The temperature of the cores and chipsets are the same no matter if I am running 1200 or 1600 memclock.
I can certainly post a filled out template for my P6T Deluxe V2 board if neccesary. :)
PS: A quick thought, isn't it better to rather use the module in socket A1 in C1? I know A1 is the correct configuration, however, poulating C1 instead would make sure to have the on die termination for the black sockets at the end of the board's traces.
sorry, i dont get what you mean with swapping the one stick to another slot...
your mem cant run 1600 999? what kind of rating is that anyways? 1600 999 is teribly slow...
so your running 4 2gb modules, right? how about running 3x2gb, maybe that works? might be a bios problem since the bios remapps the memory address space...
might be worth giving a try, and i doubt you need more than 6gb... but 1600 999? damn thats terrible... isnt 1200 777 faster than 1600 999?
if you shoot me a pm with all your settings ill see if i can help you get it stable at higher speeds :)
I'll PM you shortly as soon as I've fetched all BIOS settings. My modules are 1 GB modules. The TW and 2G in Corsair's article codes refers to a twin kit of a total of 2 GB. So I wouldn't like to run on only 3 GB.Quote:
Originally Posted by saaya
According to Everest 5.01, I am getting a read throughput of roughly 14 GB opn 7-7-7-20/1200 but up to 17 or 18 at 9-9-9-24/1600. The question is indeed if that would reflect in a higher system performance....
1600 9-9-9-24 is the XMP profile's settings stored in the modules, but they run fine at 8-8-8-20/1600 too, except for certainly still having those reboot issues.
What I mean by moving one memory module is that the manual states that for a four module configuration one should use slots A1-A2-B2-C2. '2' are the orange slots, and A1 would be the black one closest to the CPU socket.
When it comes to bus termination, and the RAM modules' on-die termination, wouldn't it make more sense to have the fourth module in the last of the black slots? To terminate the signals at the end of the copper traces.
actually pushing ioh volts does help with mem clocks for linx/prime and super pi 32m stability http://i4memory.com/f80/i7-920-d0-df...ability-16617/ for some :)Quote:
Originally Posted by saaya
2.10v vdimm / 1.82v vtt = ok for 2 days of non stop 3D Mark. (air)
yeah, but only at high bclocks right?Quote:
Originally Posted by eva2000
when the prob is that qpi/bclocks arent fully stable, at least in my experience... and its a bit weird, some people seem to need high ioh, some say it doesnt help and some say it makes things worse if ioh is too high... i suspect it has to do with what bclock your running and possibly on the cpu and chipset.
btw, that zoom feature on large images is very nice... :D
thats high! :DQuote:
Originally Posted by before
did you notice different ocing after this?
do you need more volts for the same clocks or can you reach only slightly lower clocks when maxing everything out?
more bw helps in some apps, lower latency helps in others... the difference is really small in my experience, but games tend to prefer latency since bw on i7 is pretty massive to begin with.Quote:
Originally Posted by Amurtigress
hmmm could be that the memory pwm gets too hot or cant cope with the load... but that doesnt make much sense since your on a p6t and they have 2 or 3 memory pwm phases right? do they get hot? ask asus tech support about it... maybe your on an early pcb rev and theres some prob... who knows...Quote:
Originally Posted by Amurtigress
i remember that the renessance had similar probs early in development, it was some prob with the memory pwm... but it only happened with certain psus for some reason... so kinda a psu mem pwm compatibility... try another psu, maybe its the same thing.
each channel is terminated independantly, so i dont think it matters... channel a has the shortest traces so thats why intel recommends using 2 dimms there if you use 4 afaik.Quote:
Originally Posted by Amurtigress
Saya (and all others),
thanks for the reply.
I might have shed some more light on my issue here. I came up with the idea to dig up the old and IMHO untrusty OCCT 1.1, but it seems like it shows some detail about my system. It might have to do with differential amplitude settings:
I tried the following (so far diiferential amp has always been AUTO):
memlock/ucore clock/D.A. -- stability
1600/3200/auto -- OCCT 1.1 stops after ~3 minutes
1600/3200/700 mV or 800 mV -- stops after 19-21 minutes
1200/3200/700-800 mV -- stops after ~3 minutes
1200/2400/700-800 mV -- stops after ~3 minutes
1200/2400/auto -- stops after 20 minutes.
(Remark: In all cases when OCCT failed after ~3 minutes it would also fail to update it's clock every second, but only every few seconds. It would be absolutely smooth in all cases when it bailed out after 20 minutes. irregular clock performance looks to me like it was a symptom of internal problems of my hardware)
The table above leads to an assumption: At 1200 the differential amplitude must be set to AUTO, and at 1600 most likely to anything around 700-800 mV. In the past OCCT 1.1 has been extremely flakey on my previous Q9550/DDR3 system, so I am tempted to dismiss it's failures after 20 minutes as issues with newer hardware.
Now testing my theory with OCCT 3.0.1 in OCCT mode:
1200/2400/auto -- 1h PASSED!
1600/3200/700-800mV -- in Progress
Saaya:
My board is actually the P6T Deluxe V2. The PCB is identical to the P6T Deluxe, with only a sticker on the original board model print on the board itself. The revision is 1.02G as on all shipped Deluxes...ASUS simply just left out the SAS controller chip and it's SATA connectors. :p:
The P6T series has 16+2 phases, the two extra ones appear to be for the uncore voltage. I just added a fan to my northbridge since the heatsink and heatpipe were getting very hot when running the uncore at 3200 MHz (neccessary for DDR3-1600). However it was significantly colder at 2400/1200.
Cross fingers, I might get to the skinny about the issue!
Oh no, just tried to shot this sucker down :p:Quote:
Originally Posted by saaya
:lol: :up:Quote:
Originally Posted by before
lol and i thought i was pushing a bit with 1.7-1.75 VTT :rofl::DQuote:
Originally Posted by before
dam 1.8+ CPU VTT :eek: Never tried above 1.65v myself for CPU VTT heh
Not solely for high bclk but mem clock too but helps with anything that stresses all cores versus single threaded apps. But yeah each cpu will respond differently.Quote:
Originally Posted by saaya
8x 32M Super Pi instance via HyperPi @DDR3-2080Mhz 7-8-7-20 1T at 1.725v bios set vdimm = 1.730v real DMM vdimm.
http://fileshosts.com/intel/DFI/DFI_..._32m_x8_tn.png
http://fileshosts.com/intel/DFI/DFI_...15/everest.png
I have been running 1.88 vtt for awhile now 24/7 crunching...
can i ask whyQuote:
Originally Posted by road-runner
that seems a bit ridiculous if you dont really have to have it so high :shrug:
Sorry not vtt I meant Pll... :shakes:Quote:
Originally Posted by dinos22
oh i see :up:
i've never had CPU PLL over 1.8v. I can use that all the way up to 4.3 GHz HT on. Wonder if the hard time I have to get over 4.3 GHz is due to not bumping up the PLL higher??Quote:
Originally Posted by dinos22
Hi people, Saaya,
I am pretty certain now that my reboot issue is solved now. I had the idea the other day to look into settings for ASUS boards and certain memory modules they sell, tho not neccessarily the same as mine.
Some Corsair DDR3 modules require 1.9V to run stable at 1600 in two pairs in older systems, so I tried this. For some 1866 modules Corsair recommends to set uncore/QPI to 1.6V, which I did too.
The third factor is that to have 1.6V uncore working it would require a fixed Differential Amplitude setting of 700 or 800 mV.
My system passed seven hours of Prime 95 x64 the other night.
1.9V vdimm and 1.6V uncore seem a bit high and pretty much heat up the processor, but it doesn't reboot on me anymore.
I also came across this older german report on ASUS presumably having found ways to design the P6T boards in a way to allow for high VDIMMs without affecting the IMC. I have no idea if this holds true, also since this report was released on Oct. 8th. However they also refer to similar statements from Fudzilla at that time:
http://www.hardware-aktuell.com/news...m_limitierung/
Any comments on this?
Edit: I just found the Fudzilla article. However Fudzilla says nothing about this workaround NOT having an effect on the IMC.
http://www.fudzilla.com/index.php?op...9824&Itemid=37
Earlier article:
http://www.fudzilla.com/index.php?op...9489&Itemid=37
Let me try to sum it up what might have happened to let this 'myth' grow:
I believe that Intel's reference design for Socket 1366 mainboard was having one voltage rail that provides power to the uncore part of the i7 CPUs, and also to the DIMM sockets.
This would mean, if Intel said that more than 1.65V on the uncore could kill it, it would limit the VDIMM voltage along with it.
However, mainboards that have a separate VDIMM voltage setting in their BIOS, and a separate VDIMM switching regulation, would not have this limitation on the memory modules.
Or, to put it differently:
The UNCORE is limited to 1.65V, NOT the memory voltage. UNCORE above 1.65 can kill your processor, and most likely NOT VDIMM.
Then came this stupid sticker on the ASUS boards that began to feed the legend of high vdimms killing CPUS. And we know now from Saaya that only a small number of excessively high voltages on modules during the board design were actually killing a smaller number of A and B stepping engineering samples at Foxconn.
Per chance noone ever said VDIMM above 1.65V would kill the IMC (save for ASUS' sticker), unless they meant VDIMM and QPI/uncore voltage were THE SAME.
OK, this is just a theory based upon what little I know about reference designs, but it seems to make sense.
Feel free to flame me now. ;)
Has anyone killed a CPU by running 1.45 QPI 24/7?
thats normal, i'm using 1.7v on the qpi :D and it isn't dead yetQuote:
Originally Posted by Bei Fei
Bei Fei, Hondacity,
you might want to have a look at post 223 that I just edited. It might shed some light on the whole matter of VDIMM....
:)
Hello, (continued from post #223)
I just realized that it would have another consequence if Intel really designed their CPUs to have the uncore powered by the same voltage as the DIMM sockets.
It would mean that the uncore/QPI voltage would always be the same as the standard JEDEC compliant voltage for normal DDR3 DIMMs. Namely, 1.5V!
As a consequence of this, we should probably do the following:
1) Start considering 1.5V to be the default voltage for the QPI/uncore part of our i7s. And thus stop wondering if any lower voltage than that could kill our precious chip.
2) Reconsider the voltages we use depending on the actual DDR3 clock rates we are torturing our uncores with.
So I am suggesting the following table for uncore/QPI:
DDR3 clock uncore voltage DIMM Voltage
1066 1.5V (JEDEC compliant) 1.5V
1333 1.5V (JEDEC compliant) 1.5V
1600 1.55V See specs of your modules but keep below 2V
1800 1.6V (suggested by Corsair for some of their products)
2000 1.65V
Certainly this has to be tested on any individual setup. And the fact that for example ASUS is defaulting to 1.2V for QPI doesn't make it correct. I rather see what Intel built the CPUs for and stick to that.
It might as well be possible that stable operation of the IMC below 1.5V is a design precaution by Intel to support future die-shrinked memory chips that will stick to upcoming JEDEC specifications, for example Samsung who announced 1.35V DDR3 chips. 1.35V uncore would be supported right away then.
Any thoughts? I hope I am not ridiculing myself here with such a theory. :rolleyes:
the imc isnt powered by vdimm afaik, but it needs vdimm since the memory bus is using it, and its interfacing with that bus.
so some of the logic obviously is exposed to vdimm, i dont know how exactly it works, but this logic can work fine with a higher signalling voltage on one side compared to the other, ie higher vdimm than vtt or higher vtt than vdimm, but if the difference is too high, the logic will degrade and at some point burn out.
the ideal situation is where vdimm=vtt i guess, but it really doesnt hurt having higher vdimm than vtt, as long as its not too high.
intels default vtt is around 1.1, not sure on the specs, but they accept lower than this, so lets say 1.05 or 1.00 is still acceptable.
and for vdimm they say more than 1.65v is not ok, again probably 1.75 is still acceptable, so that means a voltage diference of up to 750mv is probably acceptable, which means 1.1 vtt is ok to run 1.85v vdimm, and for 2.3v vdimm 1.55v vtt would actually be enough. then again thats pushing the limits, and more importantly, it really doesnt make sense to run that high vdimm with that low vtt... if you run high vdimm its cause your tweaking your mem to get a tiny bit of extra performance, and if your doing that, your more than likely to be tweaking uncore as well to clock it as high as possible, which means youll be running vtt at 1.55v at least.
if you look at the usual combinations of vdimm and vtt people are running youll notice that nobody is running them more than .5v apart, even if they dont care about the voltage diferential. thats probably why we havent seen more than a handful of i7 chips go bust from this, at least that we know of... and even those might just be freak accidents and not really caused by vdimm and vtt being too far off from each other.
BUT, the newer chips requiring less and less vtt to clock high with might be a reason to worry, but actually the newer memory all needs less vdimm to max out as well, so then again things seem fine... combining d0 or future chips with memory that needs 2.3v to max out might be problematic... but even that is unlikely to cause problems as barely anybody would run that high vdimm 24/7
Amurtigress
i just read it, sorry i push my voltages above the values you just wrote. anyways if you want to stay safe and have a good oc on your ram, vtt should be 1.5v-1.65v, intel specs are rather too safe... on the XS overclockers perspective we tend to go beyond the vmax specs. kill the proc or not, it happens :)
hey people i don't know it this is realy offtopic but...
i have to run my qpi @ 1,35 V for 1520 mhz mem and qpi @ 1,45 V for 1866mhz mem (1866mhz rated mem)
howevver i thought my mobo/cpu was faulty (still not sure wich) but according to your theories that kind of voltage is normal?? (still need to learn soooo much about i7 but do wanna learn :) )
I thought Intel says 1.35v VTT/QPI max .
1.6v VTT/QPI is just crazy in my opinion.
I don't think any RAM manufacturer would recommend such crazy voltage:shrug:
Note jcool damaged his cpu with 1.55v QPI in a matter of weeks !!
(this is 24/7, full load)
why did you think your cpu or mobo are faulty dopestuff?
read through this thread and google, there are xmp profiles with 1.7v vtt, and its not programmed by accident...Quote:
Originally Posted by Jaco
i know a few people running up to 1.7v vtt on air, for months, without problems...
how would he know it was vtt that damaged his cpu?Quote:
Originally Posted by Jaco
how is it damaged? what happened?
maybe the newer d0 chips are more sensitive to high vtt...
or maybe his board has some problem with high vtt... you have to know when to increase vtt during the system initialization... and vtt stability during system initialization is very risky, if it fluctuates during the early stages of initializing the cpu, it might get damaged or die pretty quickly.
@ saaya: because everyone gets there whit under 1,3 qpi and 0,1V qpi for only 310 mhz i thought was kinda high... my cpu further is pretty good though it does 4 ghz ht on @ 1,376Vcore prime stable (its a C0)
I can tell you why they do, they rely on the board maker's defaults. But the masses aren't always right...Quote:
Originally Posted by dopestuff
Here's what I found through the link in TheRAMGuy's signature:
http://www.houseofhelp.com/forums/sh...ad.php?t=54052
Quote:
Motherboard make and model : ASUS P6T Premium/Deluxe !
Each set is tested and packaged together using the following settings:
Advanced
Jumper Free
CPU Ratio Control: Depends on CPU
FSB Frequency: AUTO
PCIE Frequency: 100
DRAM Frequency: DDR3-1866 MHz
DRAM Timings Control: Manual
CAS# Latency:___________7
RAS# to CAS# Delay:______8
RAS# Precharge:__________7
RAS# Activate to Precharge:20
DRAM Voltage:_________1.65V
QPI Voltage:___________1.60 V
XMP1.2 settings
All settings not listed should be left at AUTO or BIOS Default
Maximum DDR3 recommended VDIMM: 2.00 Volts
End Quote.
so there is nothing wrong whit my cpu/mobo that's nice and according to everything i have learned so far i can also up the dram volts a bit if i want/have to :)
i have been folowing this thread for some time now and things are getting a bit clearer...
i will keep folowing this thread and do greatly thank you all for sharing your knowledge!!
You're welcome, but I wish we were so sure about it. Frankly, all I can do is looking for official things like this on Corsair's support forums, and hope they are right. They're supposed to know it better than I do....Quote:
Originally Posted by dopestuff
I do have 17 years of experience in making my own computers out of parts and an education in electronics, but I am certainly not an insider who works at Intel...
I can tell that much, my system is stable now at 1.55/1.6V VTT/Uncore, and 1.9V VDIMM.
I hope this means my rig 'feels' good and won't blow. My only basis to judge from.
hmmm yeah ive seen some people run 2000 with 1.3v vtt...Quote:
Originally Posted by dopestuff
well some imcs are better than others i guess... and maybe it also has to do with what mem and timings and vdimm you use, plus what bclock and mem multiplier and uncore multiplier...
so in other words part of it is hardware and the other part a LOT of playing around whit settings (or in other words the dude behind it) :)Quote:
Originally Posted by saaya
now running stable whit 1900 9-9-9-24 t2 mem whit 1,654V mem and 1,47V qpi (maybe in near future some Vdimm overvolting and see if theese corsairs are worth the money :p: )
Hello,
I don't know if this document has been referred to here before. Intel gives some clear numbers on voltages there...
http://download.intel.com/design/pro...hts/320834.pdf
See page 22 and 23.
Page 22 has a table of absolute maximum voltages, and page 23 gives us a number of nominal voltages on the single power panes.
Typical for VDDQ (VDIMM) would be 1.425-1.575/1.5V, and an absolute maximum of 1.875V on page 22.
The maximum for QPI/VTTA/VTTD should be 1.35V according to this. (there goes my theory! Oh well... :p: )
Maximum core voltage is listed as 1.55V.
Intel's state ment of app. 1.875V on VDIMM fits well to ASUS' BIOS, which allows 1.9V. The extra voltages are only acessible through an overvolt jumper.
Maybe this helps a bit?
To my experiences, these limitations do not mean "More than that kills your processor", but normally "These are the limit that we, Intel, are guaranteeing nominal operation for as stated in this document."
For benching it's ok to use the old ram that needs high volts with a D0 I7.Quote:
Originally Posted by saaya
1.6VTT and 2.1Vdimm here and everything is fine, however, I would not try it for 24/7.
i think its 60% hw if not more... good mem plus good cpu = high mem clocks, without much tweaking or high voltages...Quote:
Originally Posted by dopestuff
check out anandtechs classified review, they were limited by samsung based mem i think, went to elpida based mem and wham, 20mhz higher bclock and higher mem clocks with tighter timings iirc...
you obviously didnt read this thread... the doc you mention is referred to in the first page of this thread, and the absolute max values are posted there :PQuote:
Originally Posted by Amurtigress
those values are the absolute max values a mainboard should not exceed at any moment. so voltages can vary and fluctuate but should never exceed those values or the chip MIGHT get damaged after some time or even die.
there were cases when cpus really did die if the max voltages were exceeded, but thats rather rare...
those numbers are more of a last line of slight guarantees on intels side as what they guarantee to work... beyond that, if anything goes wrong, your on your own and cant say its intels fault.
naokaji, thx :)
whats the sweet spot for vtt on your d0?
1.6? or rather below? i heard d0 has rather low sweet spots for vtt while c0 seems to have its sweet spot around 1.7v more or less
1.6 is the sweetspot for my D0 if I want to tighten the latencies, especially Tras and roundtrip, if I leave those on loose settings though the sweetspot moves down to 1.5 - 1.55.Quote:
Originally Posted by saaya
ok... same as c0, but c0 usually scales until higher than 1.6v from what i heard...
Quote:
Originally Posted by saaya
Hi Saaya
if my i7 set dimm 1.8V and vtt at 1.55V
how long will be dead (approx.) under air cooling
hello
for my Corsair Dominator GT 2000MHz, you need to vQPI 1.49v in bios (Rampage II Extreme) in idle 1.46v and ~1.43v in load
and 1.65v for vDIMM
for a 920D0, is that these voltages are safe for the h24 or is it dangerous (watercooling)?
thank you very much ;)
I think, and I hope (because I am also running 1.45 VTT), that 1.45vtt is fine for 24/7 use. As long as temps are kept under check.Quote:
Originally Posted by tistou77
vdimm 2.25
vtt 1.75
ok for 3 days at air :D
Depends if your mobo undervolts VTT or not, if you have some chance to test it with multimeter, try it. But even with 0.05V undervolt.. it should be 100% safe like forever..Quote:
Originally Posted by erickwok
Btw. what's your mobo?
im using 200*21 on my 920 D0, using multi 10x for the rams, gskill trident pc3-16000 6GB, but it requires 1.63125v qpiv. it this safe for 24/7? my mobo is P6T "vanilla". i have good ventilation, noctua nh-u12p push pull + antec 1200 (7x120,1x200)
thanks,
infected_
ps: btw, running with that qpiv for 10 days now, without probs.
Why do they put in their XMP profile then 1.65QPI volts for 2000mhz speeds ? some CPU's like rams etc will die,degrade when being overclocked. Remember though the numbers are very very small compared to the others that run fab... it's a risk you take when you push stuff.Quote:
Originally Posted by Jaco
FYI I smoked on of them Kingston PC16000C8 rams, even when it was at only 1900mhz 1.63Vdimm (not even at stock speeds/voltages) These things just happen sadly
Hi all,
Any reports if this Elpida kits are dieing to?
A DATA Triple channel 2133X "ELPIDA"
Thanks
Check the other graveyardQuote:
Originally Posted by darthvedor
ThanksQuote:
Originally Posted by Astri
Hi guys!
I have an i7 920 D0 (3908A419 batch)
GA-EX58-Extreme
6Gb 1866 Mushkin 998687 (Elpida chips)
I am running it at 4.2 Ghz HT on (200x21)
memory@ 2000 mhz
Vcore = 1.4 (1.376 in windows)
VTT = 1.575 !!! (would not be stable with less!)
VDIMM = 1.68V (8-9-8-24)
PLL = 1.9V
... and i pretty much increased all other voltages by 0.22V :)
Clock skew is 150ps
Is 1.575V for VTT too high for 24/7 usage? I run it on air with Prolimatech Megahalems. Max temp is 65*C under full load.
I see most users can run 4.2 Ghz with much much less VTT voltage than me. What the hell is wrong with my cpu? :) I guess the latest D0 batches aren't that great overclockers ...
nope looks good
I would like to OC it even further, let's say 4.4 Ghz (210x21). How far do you think i could safely go with the VTT voltage for 24/7 use?
I wouldn't think much higher. But you can try in small increments. Sometimes the amount of voltage needed on a certain component is not worth the extra MHz.Quote:
Originally Posted by EQUANT
What are you using to monitor temps?Quote:
Originally Posted by EQUANT
If you are using RealTemp have you set the TjMax to 100c?
Those temps look wrong to me, everyone else I know with the Megahalems are getting temps in the mid 70's and they are only running their chips at 4GHz..
I think your TjMax is only set to 90c hence these low temps...
With those voltages I would imagine you were pushing closer to mid 80's with the Megahalems.. like I said though, it depends on what you are using to monitor temps, when I checked my temps with EasyTune6 it said that I was idling at 26c, but RealTemp shows that I am idling at 39c...
@BLunTSmoKeR - i use EasyTune6 to monitor temperature (other temp monitoring show much higher temps). The temp with reading with ET6 i think is accurate. If i set a low temp warning in BIOS, when it will start beeping the temp in ET6 = temp limit set in BIOS, while RealTemp shows a much higher temp before the system even starts beeping.
im using my gskill tridents with qpiv @ 1.63v on my p6t and 920 d0
is it safe to use for 24/7? using noctua nh-u12p in push pull with another nf-p12 and mx2.
thanks,
infected_
in ET6 on my UD3P/R p45 board the temps are no where near accurate.you need to use realtemp for accurate temps.et6 is like a 10c less in my experience.you might be killing your cpu.be carefulQuote:
Originally Posted by EQUANT
Anyone?Quote:
Originally Posted by infected_
@infected_ - just out of curiosity - what is your CPU's FPO/BATCH and what's the speed that your memory is running? BCLK=?
batch #3851A220Quote:
Originally Posted by EQUANT
200*21
vcore: 1.33v ht off | 1.35v ht on
qpiv/dram: 1600mhz = 1.34v | 2000mhz = 1.63v
is it dangerous to run qpiv at 1.63v for 24/7? most of the time its on idle or browsing. some games at night.
thanks,
infected_
No one can tell for sure. I keep it 24/7 at 1.575V qpi/vtt, 2000mhz memory@1.68V VDIMM. If it dies ... the hell with it, i will RMA it :)
1.63V is the lowest stable voltage you can get? What is your RAM voltage?
I hope someone can help me out
Got my modules replaced.. these are alot better.
I disabled HT and am running it at 20x200 @ 1.30 volts
QPI @ 1.6
Vdimm @ 1.68
Now i want to run my uncore higher then 20x.. to do this do I only need to raise my qpi volts from 1.60 to higher? or must i also raise vdimm?
These are my stats
http://img412.imageshack.us/img412/9323/stable.jpg
Quote:
Originally Posted by EQUANT
ET6 is really inaccurate, the temps it reports are the temps of the socket iirc, and not the CPU's core temps.
RealTemp is what you should use for temp monitoring, or CoreTemp as well.
I am currently trying to get my chip stable at 4.2GHz under air, I can get it stable with LinX (20 passes using all available RAM), with my Vcore set to 1.3375v, (1.312v in CPUZ when idle, and 1.291v under load) and uncore set to 1.355v, but when I try running Prime95 Blend Test overnight, when I come to check it in the morning I have a message on my screen saying my system has recovered from an error.
What is considered the highest amount of Vtt that would be safe for 24/7 usage?
I don't really know which one to raise again tbh, whether it be more Vtt, or more Vcore.
Can someone please tell me the highest I can take both of these settings for 24/7 usage?
I am currently running 1.575V VTT 24/7 so i guess you can easily increase yours from 1.355 ;)
So I've got a D0 i7 920. I could not get it to run stable at DDR3 1600 using any settings so I RAM'd the OCZ 1600 7-7-7 that I bought with it and replaced it with Mushkin 1600 6-7-6 and now I am stable but only if I use 1.435 volts on the QPI. I am only overclocking to 3.36 GHz (blk 160) and my Vcore voltage is at the motherboard's default of 1.25 volts.
So my question is... do you think I will reduce the life span of my i7 by running the QPI at 1.435 volts? I've been doing so for 5 weeks now with no problems. Ironically, 1.435v is my motherboard's default QPI voltage when the memory multiplier is set to 1600 MHz. However, most have been able to run DDR3 1600 with as little as 1.3v on the QPI and usually no more than 1.375v. From what I've read it appears that the i7's memory controller is quite inconsistent when overclocking the RAM (> the default 1066). So I'm feeling like I got an i7 with a "weak" memory controller / QPI. But is 1.435v safe for 24/7? I could always RMA it and probably receive one that will run the same at 1.35v QPI or less.
What do you think?
Thanks,
Devin
BTW, here are my specs:
Intel Core i7 920 - D0
Gigabyte EX58-UD3R
Mushkin 998691 DDR3 1600 6-7-6-18 - 3x2GB
I'm @ 3.36GHz (160 blk), DDR3 1600, 2.8GHz QPI, 3.2GHz Uncore
At Vcore 1.250v, QPI 1.435v, QPI PLL 1.20v, IOH Core 1.22v, ICH Core 1.14v, DRAM 1.65v and everything else default
hey devin, welcome to XtremeSystems :toast:
nothing to worry about... will you reduce the lifetime of your processor running higher voltages? most certainly!
but the lifetime of modern processors is unknown, and estimated to be anywhere between 30 and a few hundred years :)
so if increasing the voltage cuts that down to 20 years or even 10... thats nothing to worry about really, as its very unlikely youll be using the same system in even 3 years from now :D
i think even with higher vtt than 1.5v and vcore above 1.5v as well, i7 chips can work for a decade or more without any problems... so dont worry about it :toast:
saaya,
Thanks for taking the time to respond and for the welcome! I was assuming, and hoping, that that was the case, but I needed an expert opinion. We'll see how long it lasts :). I was thinking the same thing-- if I get 3 years of overclocked performance out of this thing I will be happy and ready to move on to the latest and greatest :D.
Love the sig-- LMFAO.
Devin
Yesterday i got my first crash in this configuration (blue screen). Today i got another, system in idle mode, just surfing the net ... it just crashed.Quote:
Originally Posted by EQUANT
Could this mean that something's cracking up? :rolleyes:
Oh, and one more thing: lately i noticed that when powering the pc from S3 occasionally it starts freezing randomly: works a few seconds, then it freezes a few seconds, then it works fine for about a minute and it freezes and so on. It won't stop until i reboot, then it works fine.
This doesn't happen each time i restore from S3, it's just random.
Any ideas?
EQUANT,
That is definitely pretty high for QPI voltage but it supports my suspicion that the memory controller on the i7 is terribly inconsistent with some users needing very little extra QPI voltage to get "overclocked" memory speeds and timings while others like ourselves are stuck having to juice up the QPI to rediculous lengths. As I mentioned, I have to use 1.435 volts QPI to be stable at DDR3 1600 6-7-6 while everyone else in the Mushkin forums need no more than 1.375v max to run the same settings. I read one story, and I forget where it was or I would try to post a link, of a guy who went through 4 i7's before he got one that would do DDR3 2000 at a reasonable QPI voltage. It would appear that we got a couple of i7 920's that are "weak" in the memory controller. Possibly would-be 940's or extreme's that got branded as 920's because of their weak bus? I don't know.
It would be very interesting to see what happens with your setup. I think the general belief is that the i7 can run at 1.5 vcore/ 1.5 QPI w/o problems but your case is a perfect experiment for that and I am very eager to see how things go for you.
Good luck and keep us posted.
Devin
http://pic.ipicture.ru/uploads/09100...BK2X6Np1vP.jpg
1.7 QPI
4560 QPI - 1.72v
Alex,
Impressive! :D How long has it been running at 1.72v ?
lol for those settings you can run it at 1.4 i'm sure :p:
1.368 CPU
1.4 QPI
1.70 DRAM 7-7-7-21 @ 1640
1.80 PLL
Should be acceptable for 24:7 use? ;]
May, 1st 2009Quote:
Originally Posted by devhen
Works in day of hours 12, 24/7 :D
equant, might be mem failing and degrading as well...
I usually use these info below on EVGA Classifield 760 :D
vQPI 1,45V
VTT 1,65V for Uncore 4,5GHz on Water :up:
VDimm 1,85V for 2200MHz cas 8 Kingston HyperX (2000cas9)
I thing VTT 1,65V and VDimm 2.0V are safety :D
Now I'm running 24/7:
vQPI 1,35V
VTT 1,55V
VDimm 1,75V
I'm wondering if this will work for i7 920, as I notice that the voltage seems to be much higher than recommend for EVGA SLI LE X58, or any X58 for that matter:
Muskin DDR3 1600 MHZ
http://www.newegg.com/Product/Produc...82E16820146871
They run at 1.7-1.9v. Running these at 1.8 shouldn't be a problem, should it? I have this in my current build of X48 and I want to carry it over to i7 to reduce cost.
(off topic question - on the EVGA cards, can you run Crossfire on them?)
Hi Jarret,Quote:
Originally Posted by JarrettM
any kind of memory specified for 1.8V will work on an i7 system but them running at 1.8 at 1600 indicates that they are oldish. Normal DDR3 RAM is running at 1.5V and more than that means higher clock speeds achieved through that increase in voltage. 1.8V modules should be considered to be technology of late 2008.
Just choose RAM that's running at 1.65V at 1600-a pretty safe hint that it is designed with a special eye on i7s and i5/i3. The less voltage the better, the more headspace for overvolting and overclocking. Either to go easy on the clock and use tighter timings instead, or for higher clock speeds.
The official JEDEC specification for DDR3 RAM up to 1333 is 1.5V.
However, in GENERAL, almost any kind of DDR3 memory should work on i7s...I bought Corsair XMS3 1600 CL9/1.8V sticks before I got my i7, no problems. Aside from not hitting 1600 stably because I used 4 of them...but 1200 was just fine with just about the same performance with only 1.5~1.6V
Hope that helps...
Yoh guys,
I read the last four pages of this thread and I am still a little confused about the safe qpi/vtt voltage.
Setting the qpi/vtt on "auto" I will receive a qpi/vtt of 1,54v. As I told that fact on this page : http://www.xtremesystems.org/forums/...60#post4298760 some guy told me (post#933) a qpi/vtt is not a good idea so I reduced it to 1,36v (the system is still stable, vdimm is 1.62v real).
But is a high qpi/vtt the early grave for a i7 like it is for an 45nm build QX9650
http://www.anandtech.com/show/3381 :confused:
I understood this thread here so far that:
- the vdimm and the qpi/vtt should not be more apart like 0.5v
- a high qpi/vtt (high is <1,54v) wouldn´t cause a degradation of an i7
Here are my bios settings:
Advanced CPU Features:
CPU Clock Ratio ................................ [21 ]
Intel(R) Turbo Boost Tech ...................... [enabled]
CPU Cores Enabled .............................. [All]
CPU Multi Threading .............................[enabled]
CPU Enhanced Halt (C1E) ........................ [disabled]
C3/C6/C7 State Support ......................... [enabled]
CPU Thermal Monitor ............................ [enabled]
CPU EIST Function .............................. [enabled]
Virtualization Technology ...................... [disabled]
Bi-Directional PROCHOT ......................... [enabled]
Uncore & QPI Features:
QPI-Multi………………………..[36]
QPI Link Speed ..............................[6,91]
Uncore Frequency ............................[3840]
Isonchronous Frequency ......................[enabled]
Standard Clock Control:
Base Clock (BCLK) Control .......................... [192]
BCLK Frequency (MHz) ................................[enabled]
PCI Express Frequency (MHz) ........................ [Auto]
C.I.A.2........................................... .. [Auto]
Advanced Clock Control:
CPU Clock Drive ..............................[800mV]
PCI Express Clock Drive ................... [900mV]
CPU Clock Skew ............................. [0 ps]
IOH Clock Skew ............................. 0 ps]
Advanced DRAM Features:
Performance Enhance ...................... [Turbo]
Extreme Memory Profile (X.M.P) ........... [disabled]
System Memory Multiplier (SPD) ........... [10x ]
DRAM Timing Selectable (SPD) ............. [Quick]
Channel A + B + C
Channel A Timing Settings:
##Channel A Standard Timing Control##
CAS Latency Time ......................[9]
tRCD ..................................[9]
tRP ...................................[9]
tRAS ..................................[24]
CR.....................................[Auto]
B2B.....................................[Auto]
Advanced Voltage Control:
CPU Intel Xeon W3565 D0 Stepping
Load Line Calibration ................. [Level 1]
CPU Vcore ..............................[1,26875V]
QPI/VTT Voltage 1.150v .................[1,36V]
CPU PLL 1.800v .........................[1,6V]
PCIE 1.500v ...........................[Auto]
QPI PLL 1.100v ........................[Auto]
IOH Core 1.100v .......................[1,2]
ICH I/O 1.500v ........................[Auto]
ICH Core 1.1v .........................[Auto]
DRAM
DRAM Voltage 1.500v .............. [1,64]
DRAM Termination 0.750v.......... [AUTO]
Ch-A Data VRef. 0.750v ...........[AUTO]
Ch-B Data VRef. 0.750v ...........[AUTO]
Ch-C Data VRef. 0.750v ...........[AUTO]
Ch-A Address VRef. 0.750v ........[AUTO]
Ch-B Address VRef. 0.750v ........[AUTO]
Ch-C Address VRef. 0.750v ........[AUTO]
The temps. are under load 69° C.
Asus P6T SE crossflashed to P6T, overvolt jumper for QPI used,
Currently running 1.725v VTT/ 1.72v DRAM to get 4000 mhz uncore stable for about 4 weeks now, i'd like to run the maxmimum 1.9 to reach higher uncore if someone else dare to try before me =P
Everest showing some nice numbers: 20k read, 21k write , 24k copy
Attempted 1.9v QPI to get 4400 Uncore but failed(hard reboot), instead took a shoot for 4200 Unc @ 1.825v. Intended for 24/7 but hey lets see how that works out.
Edit: had to do 1.875v to attain stability
24/7 Overclock, OK for 4 weeks now. Prime and LinX stable. I went ahead and raised the vDIMM after the Corsair Dominator decided not to play nice at 2000 (v3.2 Micron). I managed to tighten up the timings, seem to get flaky below 1.73 so I left it at 1.74. I am going to politely ignore the 1.65v warnings for now.
i7 930 @ 4.2 Ghz (200 x 21)
vCore: 1.3375 BIOS
QPI 3600mhz: 1.350 BIOS
PLL: 1.8
Corsair Dominator C8 @1.74 DRAM 7-7-7-17 @ 1603
you still gotta have qpi vtt .05 close to vdimm;)Quote:
Originally Posted by Xanth
so bump qpi to 1.7v
:D no, you need to have it in 0.5v range...
I got bored, figured I would tighten up the timings, so far:
i7 930 @ 4.2 Ghz (200 x 21)
vCore: 1.3500 BIOS
QPI 3600mhz: 1.400 BIOS
PLL: 1.9
Corsair Dominator C8 @1.8 DRAM 7-7-6-16-60 @ 1603
Chip seems to hate the 22X multi. Also, the ram hates running any faster. I might be stuck here for a while.
fyi, ive been running my 920 D0 at
1.15v vtt and 1.65v vdimm, which is a .5v gap, for around 6 months
and
1.40v vtt and 1.8v vdimm, which is a .4v gap, for around 10 months...
its has always been a bad clocker, but i didnt notice any degradation...
After benching for hours with i7 980 on 1.6v vtt, 1.9v vcore i left the system for cooling down. An editor on a gaming site saw the system cooled down and strip the system for air cooling, didnt reset the bios, opened the system with Ln2 bios config... Instant death. :shocked:
Cpu was ES so "Bye bye happiness..."
I wouldn't say so.Quote:
Originally Posted by AbsoluteZero
You can't kill an Intel processor of our era like that.
Just put the CPU on another mobo and it'll work ;)
I wouldn't say so.Quote:
Originally Posted by AbsoluteZero
You can't kill an Intel processor of our era like that.
Just put the CPU on another mobo and it'll work ;)
Hey guys, i'm running a 860, what's the general consensus on the max VTT and degregation for these CPUs? I've run all my CPUs mercilessly into the 80s and 90s with decent voltages and never seen any degradation, I've seen 1.21v, 1.4v, and within .5v of the Vdimm. Can anyone clear this up? Why do ram XMP profiles set VTT to something like 1.65v?
Tried 3 different mobos. It was killed on MSI X58 Pro. I tried on Giga X58A UD7 / MSI X58 Eclipse / Giga X58A UD5.. Nothing is changed. I also tried on Giga X58A UD7 after one month passed but it is still dead. Late autopsy. :)Quote:
Originally Posted by BenchZowner
That's weird.
There's a protection "mechanism" on-die or on the mobos for sure though.
Try giving 1.9Vcore 1.9Vtt on a Rampage III Extreme or any Classified ( E759/E760/E761/E762 ) on air and you'll find out that while it doesn't post ( gets stuck @ FF ), clear CMOS = CPU is alive and not damaged at all ( no degradation, etc )
I've been running my 920 c0 at 200x19 for awhile now.
Ram is Corsair 1600 3x2GB Kit CAS 8 timing.
The Vcore is 1.39, VTT at 1.475, VDIMM at 1.65.
Is this safe in the long run with only air cooling? I find the VTT to be quite high for only 1600mhz memory.
Wish there was some way to lower the Vcore but that's about as low as I can go without screwing up in P95 and Linpack.
I'm in the process of rma'ing the ram... I think it's not 100% fully working.
hi
Vtt 1.66/1.70v
Vcore 1.50/1.55v
Vddr: 1.65v
(water)
Since too months 24/24 (boinc) on i5 750 with sucks maximus III (poor mb,no possible to desynchronize ram on high ,pi 17600..) and at this instant no problem :D
wait and see :up:
Since it is massively overvolted out of every spec, please report when something changes due to prolonged usage in such conditions.
Hope it doesn't, but 1.7 Vtt is damn a lot for 24/7.
I predict a dead cpu... that way too much vtt... not likely needed...