Does same happen with only 6GB memory or non-raid SATA disk array ? Does it happen at lower cpu clocks i.e. 4Ghz or 4.2Ghz ?Quote:
Originally Posted by Peen
Printable View
Does same happen with only 6GB memory or non-raid SATA disk array ? Does it happen at lower cpu clocks i.e. 4Ghz or 4.2Ghz ?Quote:
Originally Posted by Peen
Only problem I can think about is getting the x21 multiplier working with Windows 7. You might need to download Real Temp 3.30 or an application called ready boost to get it going right.
Otherwise, the board works fine for me :)
Win7 multi issue is fixed with new beta BIOS 0724. I've checked with Win7 RTM.
so no dfi old diseases like ... "will not power up" , suddenly crushes , etc ... ?
Nope, no "will not power up" , suddenly crushes , etc , here. My setup has been running rock solid in several weeks now, but I'm keeping it at summer-OC @4GHZ(211x19) 1.15v 24/7 for now.
Even tho i didn't need/use x21 for now, but my only concern has been x21 multi, and it is working just fine with the new BIOS, now :)
http://img199.imageshack.us/img199/30/superpi32m.th.jpg
The next fun will start at the autumn, with keeping this hot babe cool enough @4.4GHZ 24/7 on air-cooling ;)
ok thank you :)
i just recently burned evga classified e760 and had no warrnty :(
so i looking for a solid mobo with great overclock potencial , features and tweakable bios ... so far DFI UT X58-T3EH8 answers to all of those.
i have great cpu ... I7 920 (batch 3849B203) that doing 4.7 on air and 5.2 on dry ice , great memory sticks ... mushkin redline 1600mhz cl6-7-6-18 and great air cooling ...Prolimatech Megahalem + panaflo 120X38 medium.
all is left is an awesome mobo :D
Did somebody try the new bios? i'm havin' problems. they're the same as the 6/19 bios, but more evident. Can't get the cpu stable >3.6ghz and uncore >3000mhz
I keep getting this thing where prime95 LargeFFT just turns off, like it restarts the computer with no BSOD, yet when I do the testing for core voltage, it doesnt reboot?
Any ideas guys?
ChaosMinionX
Vcore?
Temp PWM?
1.4375v on Vcore.... PWM temp is almost always under 60C
From my experiance this board is very sensitive especially the area where the volterra voltage regulator chip is located. I've tried once my finger accidentally touched the chip / resistors and it turn off immediately and turn back on like rebooting.Quote:
Originally Posted by ChaosMinionX
I could try it only 6gb to see what happens, only get about 1hr a day to play with it. It didn't do it at 4ghz but I will try 4.2ghz now...Quote:
Originally Posted by eva2000
I don't see why the raid would matter.
This is the first computer I have that will stress test stable but idle it BSOD's :ROTF:
Bha, i'm gonna hate this mobo
I don't have the UT but the DK version... finally got the 21x MP working under load :D
A real DFI board lol... you have to get to know it to let it work for you :D
I can't find any test on these, but I'm hearing ver. 2.2 can make a big difference. Can you give some feedback on performance and OCing headroom of these sticks?Quote:
Originally Posted by ci2kla
any one else experience this kind of problems?Quote:
Originally Posted by ChaosMinionX
also , any one experience overclock crushes that couldn't be fixed by taking of the battery or restrating bios by jumper?
and the only solution was takin the powering of the PSU and disconecting the 24pin cable ... like in the old dfi boards ...
So i'm the only one that can't get the pc stable with uncore >3000mhz?
When an OC fails real bad, you can now reset the bios to default settings with your reset and power buttons (or the ones on the board).Quote:
Originally Posted by Juiced_IL
I've tried some crazy OC's but haven't resorted to pulling out the battery or using the jumper method..... yet.... ;)
Ah, one question. Is there any option to save energy (C1E-Cstate) without losing stability?
Yup, I have C1E enabled all the time, even when stressing to find a 24/7 OC :) Get the latest bios 07/24/2009 and the turbo multiplier (x21) issue has been resolved in Windows 7.Quote:
Originally Posted by Razer(x)
do not use C1E - it's 100% crashing for idle. may be it dropped Vcore and x22 multiplier for a core
my settings 200*21 for save energy:
and Get:Code:Genie BIOS Setting
CPU Feature
Set VR Current Limit Max: Enabled
Thermal Management Control: Disabled
EIST Function: Enabled
CxE Function: Disabled
Execute Disable Bit: Disabled
Virtualization Technology: Disabled
***** Logical Processor Setting *****
Intel HT Technology: Enabled
Active Processor Cores: All
DRAM Timing
Channel Interleave Setting: AUTO
Rank Interleave Setting: AUTO
Memory LowGap: 1536M
DRAM Command Rate: 1N
CAS Latency Time (tCL): 7
RAS# to CAS# Delay (tRCD): 7
RAS# Precharge (tRP): 7
Precharge Delay (tRAS): 19
REF to ACT Delay (tRFC): 60
Write to PRE Delay (tWR): 10
Rank Write to Read (tWTR): 6
ACT to ACT Delay (tRRD): 6
Row Cycle Time (tRC): 30
Read CAS# Precharge (tRTP): 6
Four ACT WIN Time (tFAW): AUTO
Voltage Setting
O.C. Shut Down Free: Enable O.C.S.D.F
CPU VID Control: Auto
CPU VID Special Add Limit: Enabled
CPU VID Special Add: 109.92%
Vcore Droop Control: Enabled
DRAM Bus Voltage: 1.620v
DRAM PWM Switch Frequency: Nominal
DRAM PWM Phase Control: 2 Phase Operation
CPU VTT Special Add: AUTO
CPU VTT Voltage: 1.31
VTT PWM Switch Frequency: Nominal
VTT PWM Phase Control: 2 Phase Operation
CPU PLL Voltage: 1.80v
IOH/ICH 1.1V Voltage: 1.11v
IOH Analog Voltage: 1.10v
ICH 1.5 Voltage: 1.5v
ICH 1.05V Voltage: 1.05v
DIMM 1/2 DQ/DQSTB Bus VREF: -00.0%
DIMM 3/4 DQ/DQSTB Bus VREF: -00.0%
DIMM 5/6 DQ/DQSTB Bus VREF: -00.0%
ADDR/CMD VREF Control: Disabled
x DIMM 1/2 ADDR/CMD Bus VREF: 110
x DIMM 3/4 ADDR/CMD Bus VREF: 110
x DIMM 5/6 ADDR/CMD Bus VREF: 110
CPU QPI Drive Strength: Normal
IOH QPI Drive Strength: Normal
Exit Setup Shut down: Mode 2
O.C. Fail Retry Counter: Enabled
O.C. Fail CMOS Reload: Disabled
PPM Function: Enabled
Turbo Mode Function: Enabled
1 core Max Turbo Ratio: 22x
2 core Max Turbo Ratio: 21x
3 core Max Turbo Ratio: 21x
4 core Max Turbo Ratio: 21x
CPU Non-Turbo Clock Ratio: 20x
* BCLK/UCLK/QPI Controller Settings *
QPI Control Settings: Enabled
QPI Link Fast Mode: Enabled
QPI Frequency: 4.8GT/s
CPU Base Clock (BCLK): 200 Mhz
Boot Up CPU Base Clock: AUTO
PCIE Clock: 100 Mhz
DRAM Frequency: 8x
UnCore Frequency: 16x
CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled
IDLE - 200*12=2400MHz Vcore=1.056V, CPUvtt=1.28V
and full load:
http://img145.imageshack.us/img145/5...hrprime.th.png
Thanks guys :)
@Factotum, 110% gaves me a too high vcore, what can i do? can i decrease it?
play with CPU VID Special Add:Quote:
Originally Posted by Razer(x)
but if set Vcore Droop Control: Disabled - receive Vcore without dropped
Ok i'm gonna try, just increasing the vcore and those 2 cpu settings from 3.8 to 4.2ghz the pc BSODs within 20 secs of Linx. I think i gotta change the vttQuote:
Originally Posted by Factotum
I'm going to try the latest beta BIOS today but I do have a question about my setup. Specs are in my sig. I'm having a hard time getting 4.0GHz to be stable. I'm running 20x200, RAM at 1600, etc., basic 20x200 settings. For my setup to run Prime at all it requires 1.32vid and 1.32vtt. PLL I have at 1.85, everything else is default or auto. 4.0GHz shouldn't be difficult to get stable, suggestions?
Most users find it a lot easier to get 4GHz by using an odd multiplier like 19 or 21 compared to using an even multiplier like 20.
If you have trouble getting 20x200 stable then try 21x191 instead.
I'll give it a shot today. :up:Quote:
Originally Posted by unclewebb
For me, 200 bclck gives me a nice round figure of 800mhz for my RAM (which is rated at 1600mhz).
Factotum: I'll try and play with the CPU VID special add to see if it makes a difference to my OC (I'm currently using CPU VID control).
Almost stable for 8 hours of prime at 210x21 for 4410mhz (with HT on). 1 thread decided to die at 1hr 40m. The other 7 made it.......... GRRRRRRRRRRRRR
Might be ram, atleast my cpu never errors, it just bsods but my ram tends to error prime outQuote:
Originally Posted by JustCallMeFrank
Still crashing with 6gb ram 4.4ghz and 4.2ghz on idle...WTH something isn't right
800MHZ was the norm at the start av i7 C0, but i7 has evolved and most D0's will do @4.2-4.4GHZ 24/7, and this is the BCLK210 territory. 840MHZ has become the "not so nice an round" number that creates a big RAM-dilemma (many sticks can't run at this speed even with higher voltages). I guess many of these "strange" stability problems starts when people try to push the RAM over it's limits.Quote:
Originally Posted by JustCallMeFrank
imho is not only RAM issues, I think these problems are related to CPU Integrated Memory Controller and QPI bus frequency.Quote:
Originally Posted by Sam_oslo
Not all the CPU are abe to run with uncore > 3.6 GHz and/or QPI bus strongly overclocked: BCLK>190 MHz and then QPI bus >190x18=3420 MHz.
C1E=Disabled?Quote:
Originally Posted by Peen
I agree, depending of the CPU-batch, the QPI bus can be the problem too, but that's relatively easy to diagnose/fix. On the other hand, many RAM-sticks can limit a good CPU-batch to run at BCLK210 (1680MHZ RAM). This is not so easy to diagnose and people are reporting some "strange" instability problems (it can pass the Memtest, LinX and PrimeBlend, but fails in SuperPI, or other "strange and unheard" problems).Quote:
Originally Posted by v_parrello
It is not easy to generalize, but I believe many of these "strange" instability problems are rather related to "too high BCLK for the RAM" than for CPU/QPI/Uncroe (but I agree that this problem exists too). After "the dead of the hyper", there not many sticks in the marked that can run stable @1680MHZ (even with unsafe Vdimm).
An easy way to diagnose the QPI-problem can be to run LinX/PrimeBlend with QPI fast mode, disabled.
My problem is, for example, that i can't get the pc stable with uncore >3000Quote:
Originally Posted by Sam_oslo
If Uncore is your "only" problem, then you can solve it easily. You haven't post any detail screen-shot yet, and it is not easy to guess the rest from your short posts either.Quote:
Originally Posted by Razer(x)
I'm afraid your problems are a bit more than that, but if that's the only problem, then you can use x6 multi on RAM, and have 12x or 14x Uncore, and still be under 3000 even at BCLK210. 14x210=2940 < 3000. We ended up with RAM-settings again? :rolleyes:
What about this one? :DQuote:
Originally Posted by Sam_oslo
http://forum.nexthardware.com/galler..._screen186.jpg
I think the main problem to run high RAM frequency is strictly related to uncore frequency and quality of IMC of CPU. There are a lot of RAM in the market that are able to run at high frequencies with really low voltages (all the kits equipped with elpida BBSE).
In fact now i'm stable at 200x18 with uncore 2800mhz with 1.24v (the lowest vtt, my mobo has a positive drop of 0,03v)Quote:
Originally Posted by Sam_oslo
Ok, i don't really care about the uncore, but 'cause of this mobo i can't get my pc stable with ram >1400 mhz
I won't trust this one for 24/7 use, either the stability (because you have tested the RAM all the way, at least on this screen shot) or the reliability/durability (because your are using VVT>1.35v). But yes you are right, when you get to high speeds (around 2000MHZ) then IMC plays much bigger role than it plays around 1700MZ. You need good CPU-batch to run Uncore >4200MHZ.Quote:
Originally Posted by v_parrello
I know some sticks can run >1600MHZ, but most of these who are reporting about problems here, are running those "god old first generation 1600MHZ" RAM.
Maybe your RAM (or CPU or other settings which i don't know much about) are limiting your MB? Uncore is sitting in your CPU, and is more dependent on your CPU-batch than your MB. In these speeds will the MB has almost nothing to say about your Uncore speed.Quote:
Originally Posted by Razer(x)
I don't think so. This kit can easily do 2000mhz CAS8 with 1.65v (2h of memtest passed)Quote:
Originally Posted by Sam_oslo
Sorry what does mean your sentence "because you have only the tested GPU-RAM"? I have tested CPU and RAM not GPU and RAM (OCCT was CPU test with large data set for RAM, and prime was blend test for CPU and RAM).Quote:
Originally Posted by Sam_oslo
The test demonstrates RAM could easily run at 2100 MHz with low vdimm voltage, obviously is not for 24/7 use because of high VTT voltage.
Then do you agree with the fact that the problem are not RAM but CPU uncore and IMC?
RAM are able to go over 2100 MHz easily and to be stable, the problem is CPU that are not able to manage so high RAM frequencies because of high uncore and Integrated Memory Controller (IMC) quality that need high VTT voltage to be stable.
The IMC always plays bigger role: there are CPU that are not stable (with prime, linx and similar application), with 3200 Mhz uncore and need a lot of VTT to be stable. Is not a RAM question. The same kit of RAM could be not stable with low VDIMM and low VTT with a CPU at 1600 Mhz and 3200 Mhz uncore, with another CPU the same kit is stable with same settings.
Sorry I misunrestood/exchanged your OCCT-shot, but edited my sentence now. I sow your high VVT and and got disturbed. :shocked:Quote:
Originally Posted by v_parrello
This is impressive speed, and is always fun to bench/test at high speeds, but I would run at leasts 100% of 8 instance memetest (or something similar) to make sure it is stable for 24/7 use. And I'm glad that you are not pushing that much VVT to your "expansive" sticks for 24/7.
As I have already said, The IMC will play a bigger role at high DDR3-speeds. Are you suggesting that most instability are most likely related to IMC?
For sure!Quote:
Originally Posted by Sam_oslo
RAM are able to run at specified frequency and timings declared, the problem is that IMC CPU is not able to make the same.
You shouldn't believe all specifications and PR-stuff on those sticks. It is a good idea to run some memtest to make sure it is running stable (even withing the spec.). Many think like you, and then it is easy to jump over testing the RAM throughly.Quote:
Originally Posted by v_parrello
Believe me, I have had a few memtest frailer good within the ability of my IMC. In these cases, the system seams to be stable, and will pass many stress-tests too, but suddenly you can get some "strange".
You have to notice that most people are trying to push/OC the RAM to it's limits (and even over it), and then I believe the most likely source of the instability is memory itself (RAM timing/divider), not the IMC, unless we are talking about very high DDR3-speeds (Uncore>4200).
But every setup is different and your scenario may apply to some cases too, I'm just suggesting that one should test the memory throughly before concluding MB or CPU/IMC as the source of instability.
I agree with you, but if memtest fails is not 100% RAM issues. It could be also IMC issues.Quote:
Originally Posted by Sam_oslo
In this architecture is not possible to separate RAM from IMC, they work togheter, if one of them fail then memtest fail.
So survey says?
Is it this board, or are these problems experienced wide spread in the i7 world? I have to do some more reading, but from what I can tell I think its a combination of the platform and the BIOS. I think RAM is a big factor, as soon as I go over 1600mhz these sticks are like hell no.
memtest86+ v2.11 DOS or windows HCI memtest on DFI UT X58 is weak and not entirely accurate for stress testing memory and stability real tests for stability are hyper pi v0.99b 8x 32M for 64bit systems, 8x 16M for 32bit systems and Prime95 custom large FFTs or blend set at 5400MB for 6GB cofigs. But memtest86+ v2.11 is useful still for figuring out what voltages and settings are lacking or need tuning, depending on which test the errors are showing up at - http://i4memory.com/f79/memtest86-v2-11-a-6/Quote:
Originally Posted by Razer(x)
Also when talking about IMC/ram dependence don't discount the bios itself and how it interacts with different types of cpu and memory type/brand pairings.
Personally, I find once you figure out the memory side of things, cpu side falls into place much more smoothly. I'm able to repeat almost all my memory and cpu clocks I managed on DFI UT X58 on a completely new motherboard, Asus P6T6 WS Revolution once I figured out the memory site and bios settings/voltages needed for that board. Still early days on new board. But believe me when I say memory is the key to cpu clocks/stability as well.
I find HyperPi 32M to be the most "picky" on RAM/IMC too.
I have been trying today (based on my @4GHZ(19x211) 1.15v, 11 & 8 hours Primestable setup), and event tho I have had many successful Superpi 32M and Prime-smallFFT runs up to BCLK220, but Hyperpi 32 will eventually fail over BCLK212, no matter what i could do so far.
At BCLK212 it will run about 8-10 passes, and then 1 core drops out. At > BCLK213, the core drops out after 1-2 passes. Raising the VVT or loosing the RAM-timings didn't help . Even tho this setup has passed several hours Prime smaFFT at 4.1GHZ(216x19) 1.168v, but BCLK212 seams to be the BCLK-wall for RAM/IMC-stability at x19 multi on my setup.
I have been experimenting with QPI:Uncore 1:1 at x18 lately, and it was good to see it passing Hyperpi 32M.
@4GHZ (211x19) 1.15v , Hyperpi 32M:
http://img73.imageshack.us/img73/409...pi4ghz2.th.jpg
Yep eva, i know :D
I have read the manual and checked out most of the threads but I am still not 100% clear on the issue.
When crossfiring with double slot video cards... the only other slots available would be the yellow pcie and the green pci in the middle.
As I understand...if I install a pcie x1 sound card in the yellow pcie slot, that will downgrade the bottom pcie slot to x8. is that true?
The layout just doesn't make sense to me: being left with only a single pci slot while crossfiring. Most motherboards have seperate x1 slots or speed detection to avoid any ill effects.
New beta bios 07/24/2009 :clap:
"The BIOS fixed Windows 7 CPU ratio issue."
http://forum.crazypc.ro/attachment.p...9&d=1249065572
I cant even get HyperPI with Bclk 191mhz to run anymore, even though it used to!Quote:
Originally Posted by Sam_oslo
Try to bump the Vocre a few notches up, and see who it works for you.
I found HyperPi 32M to be very "picky" on Vcore too. The setup will run stable and pass several tests (including at least 1 hour Prime-smalFFT, and SuperPi 32M) with whole 3 notches less Vcore than HyperPi 32M. Maybe this is happening only my setup, but give it a shot.
dont worryQuote:
Originally Posted by Peen
hyper pi is actaully same as super pi
i can't pass it under vista 64-bit even on my laptop ibm lenovo r61i, same as on othjer 2 desktops
so it is not problem of overclock, but just incompatibility vista and hyper pi
use ither tests
i'll try it again but it used to pass 32m with 1.24ish V now its even failing still at 1.3vQuote:
Originally Posted by Sam_oslo
Ya i know just the fact that it used to and now that it's crashing while idle but not underload is kinda pissin me offQuote:
Originally Posted by rioja
Must be under idle some clock signal isn't stable...
It usually freezes, or BSOD's with the no clock signal on secondary cpu in allocated time. Tryed turning off CIE, upping IOH Voltage and upping the PLL volts. Well those 3 seperatly it still would crash within 15min idle (even though prime 2hrs) but with all 3 (1.15v IOH, 1.9v PLL and CIE disabled its been idling for 6hrs at 4.4ghz 4.2ghz Uncore. HyperPi 32m still fails mid test usually
With the Vista audio service disabled there is no reason why either should not pass.Quote:
Originally Posted by rioja
nope
not only audio but other 2 checkbox (aero and smth else) wont help
also it is depends of some background work (if i live 32m running along it may pass) but if i run it woth internet browsing in parallell or some other work it will crash
i have cheked it on x38 e6420, x58 w3520 with no o/c, and laptop c2d with no o/c
everywhere hyperpi crashed
vista x64 sp2
Don't know what to tell you. With the exception of the UT X58 board SuperPi has run with no problem on any board I have tried by disabling audio services. On my UT board multiple instance will run fine just not a single instance but that is because the board is screwed.Quote:
Originally Posted by rioja
The easiest thing is move to Win7 then nothing has to be disabled.
Same here, HyperPi crashes in Vista, but I have WPrime and it works just fine. I have to change it to use 8 threads for HT, that's all. It's also based on SuperPi, right?
You could also use LinX, OCCT (built-in LinX also) or IBT (Intel Burn Test) and set it up to use over 5GB of memory for testing your 6GB kit.
Do you still use ure OCZ Gold sticks? I've ditched them though they worked great on my Rampage II Extreme, DFI hates OCZ Gold :shrug:Quote:
Originally Posted by Peen
Now running on Corsair Dominator 1866MHz 9-9-9-24-1T @ 1600MHz 7-8-7-20-1T. Passes HyperPI 32M 4 threads, 8 threads and 16 threads without problems on Vista 64-bit.
Check disable audio and everything works fine here :up:
Put on Windows 7 RTM, 7/24 bios now its not crashing, multi stays at 21x, and HyperPi works! :)
Great...just Great. One of my Hyper has decided to die and cannot be detected anymore. However the funny thing is it can boot up with my Rampage Extreme...Sign I hate RMA:mad:
Not too bad for just $135 isn't it?
http://i317.photobucket.com/albums/m...Untitled-1.png
Not bad at all. This is "Corsair XMS3 DDR3 1600MHz 6GB CL7", right? Can you see if it can run stable @1600MHZ (or 1700MHZ) CL6 1.65v?
Yes that's the new toy but too bad my Kingston is just went dead...:(Quote:
Originally Posted by Sam_oslo
Will test 6-7-6-18 1600 right away.
http://i317.photobucket.com/albums/m.../676181600.png
Check it out. If this can run 1600MHZ CL6 1.65, then Who needs the dead hyper and Kingston?
I have been waiting for new GT', but with these good results you are getting, it is not going to get easier.
Currently testing.Quote:
Originally Posted by Sam_oslo
From the information I've got Ver 2.2 should be Elpida BBSE ICs and I heard they don't like tight timings and not very responsive to voltages for this...this kit cannot do 8-8-8-24 but 8-9-8-24 is fully stable.:shrug:
300% seems an piece of cake~
http://i317.photobucket.com/albums/m...C71600/300.png
DON'T USE THE NEW 7/24 BETA BIOS! I thought it was stable, until I put a load on it. My comp just shuts off after 30s of load and killed my OS wasn't even repairable. Putting the 6/19 back on and Voila no longer just turns off
This looks really good, and 1600MHZ CL6 can be a great 24/7 setup. I knew this wouldn't be simple, but now I'm really in doubt about waiting for GT or getting one of these.Quote:
Originally Posted by ci2kla
Yes if you're looking for a really good C/P value you can't miss this!Quote:
Originally Posted by Sam_oslo
http://i317.photobucket.com/albums/m...71600/4000.png
I'm in 0724 BIOS now, so far so good and no problems...Quote:
Originally Posted by Peen
In order to get x21 multiplier, do you have EIST enabled?Quote:
Originally Posted by Peen
Because Im on win7 professional and I need to have it on to reach x21.
And... I have 7/24 bios.
Also, I would like to know which are the safe voltages for VTT and PLL.
And is it true that you only need to add more vtt when you have 2000mhz memory modules?
Thanks
Weird, my PC was just shutting off randomly, now its not again with 6/19Quote:
Originally Posted by ci2kla
Ya you have to have EIST onQuote:
Originally Posted by Osterman
I run 1.45v vtt because my uncore is 4.2ghz. If it dies, it dies. Somehow I doubt it will though. People were afraid to go over what was it 1.35v with Penryn and I ran 1.55 for a year with no problems :ROTF:
They say higher VTT helps stablize ram at higher speeds, couldn't tell ya though since my board hates my ram and have to run it at 1260mhz. Pretty sure intel says 1.35v max but so far so good with 1.45v
pll couldn't tell ya, I run stock because it doesn't seem to make a difference with anything. I think Intel says 1.89v max
Thanks!!!
And... according to the first quote you did. Im also on 7/24 and no problems I think.
Well maybe I think "different board have it's own personality" isn't it? :ROTF:Quote:
Originally Posted by Peen
In my case my baby doesn't like higher IOH or IOH Analog (aka QPI PLL?) voltage. Anything more than 1.25v will be worse
Corsair XMS3 DDR3 1600MHz 6GB CL7 in the house. I have to test more, but the first stability tests looks promising.
BCLK 211
Core/Multi X19
QPI/Unccore 1:1 x18
RAM x8
@1688MHZ 7-8-7-20 1.65v HyperPi 32M:
http://img44.imageshack.us/img44/240...yperpi2.th.jpg
Strange.. with my T3eH8, I can enjoy 1600MHz memory @ 7-7-7-24 timings, with 1.65v. CPU VTT only needs to be increased to 1.24v and Vcore at 1.28v. I just leave all other voltages @ stock, including IOH @ 1.10v.
Been folding @ 4GHz ever since... stable in everything. It was a breeze overclocking the DFI board.
What's the strange thing?Quote:
Originally Posted by Bo_Fox
PS: one thing, any advice to easily find the correct vtt?
Ya but if you have any ram it doesn't like or a Xeon or try to max it out, it starts getting pissy :up:Quote:
Originally Posted by Bo_Fox
I know it is kind of hard to believe but...
http://i317.photobucket.com/albums/m...600/stable.png
Well I really dont know if its the CPU or me.
Im trying to get 4.2 stable for 24/7, I was able to reach 4ghz very easily but now 4.2 seems to be impossible with a safe vcore (safe= less or equal to 1.3652, I think that was the last option called safe by intel).
Now Im trying with 1.31VTT, 1.3652 Vcore, 1.65Vdimm, everything else is stock or auto.
And the rest of the options are BCLK 200x21 (TURBO Enabled with EIST also Enabled in order to get 21 multiplier), the Ram is 200x8= 1600mhz, UNCORE 200x18= 3600mhz, HT Enabled.
The batch of cpu is 3911A, I read that 39 are not that great as the 38 ones.
Maybe you need more CPU VTT...have you got BSODed?Quote:
Originally Posted by Osterman
Yes it gave me BSOD.
But 1.31VTT isnt enough for a 24/7?
I have had zero problems so far running my 920 @ 1.4125v for 4ghz 201x20 (its been above 1.4v for about 6 months now and I have yet to see any need to increase voltage or a loss of stability from degradation).... Its a C0 and water cooled, if your temperatures are fine, there is no reason that extra voltage up to 1.44v (beyond 1.44v I believe was stated as a mileage may vary zone for life expectancy).Quote:
Originally Posted by Osterman
But I would imagine same holds true with as long as your voltages for VTT/VDIMM are kept within .05v of eachother, that if your temperatures are fine, then most vcore wont kill the processor.
Im having some success with this new BIOS and retesting all the settings.
The problem is you're running 3600Mhz uncore and if you don't get a good IMC embeded CPU you will need more VTT juice :DQuote:
Originally Posted by Osterman
Updated 1st post in this thread for Initial notes, findings and tips DFI UT X58-T3EH8 thread as i moved it to it's own dedicated thread for easier access. I see alot of the issues asked in this thread still can be answered by info in all the links in first post http://www.xtremesystems.org/forums/...69&postcount=1 ;)
Looks good. Are you changing subtimings (or other RAM/IMC settings too)? In case do tell, I want to try them too.Quote:
Originally Posted by ci2kla
I'm experimenting with some "high-BCLK, low-Volt"-actions :cool: and getting some very proposing results by letting the RAM on "relax" timings for now. I couldn't get it stable at over BCLK212 on my previews setup (with 1333MHZ CL7 RAM), but it seams to be running stable at BCLK216 now (and I have seen indications for even higher). @4.1GHZ(216x19) seams to be stable for 24/7 use :).
4.1GHZ(216x19), 1.18v :cool:
HyperPi 32M:
http://img19.imageshack.us/img19/642/hyperpi32m2.th.jpg
45 min OCCT:
http://img19.imageshack.us/img19/9859/occt7.th.jpg
I have to test more, but it seams to be running stable at higher BCLK with the new RAM :)
It's good to hear you got good results with these babies :up:Quote:
Originally Posted by Sam_oslo
From my own experiance, CPU VTT is also important when going for higher bclk overclocking. Also if you have time you can play with IOH / IOH Analog voltage as well as they seems have effect when getting to ultra high base clocks. If you hit a wall, try up the PCI-E to 105+~
Yes I'm having some fun and good results with these sticks :).Quote:
Originally Posted by ci2kla
VVT-volt seams to be very CPU-pendent. So far, my w3520 hasn't care much about VVT, and I can't see it having any effect on stability, yet. So far (up to 216x19) it is running stable with anything from 1.21v to 1.28v VVT. But it doesn't like high VVT-volts at all, and it can't even get into windows with VVT>1.32v :rolleyes:.
On the other hand, my i7 920 C0 wouldn't run stable at it's highest 24/7 OC, @4GHZ(211x19) 1.34v with anything else than VVT=1.34v. But it didn't care much about VVT at lower speeds and would run stable with almost anything at < @3.8GHZ.
I have to test more to make sure, but so far, the new RAM haven't had any affect on VVT, either.
I belive VVT is very CPU-batch dependent and seams to get important when you get closer to your max-stable 24/7 OC, but not before that.
Anyways, does this mean that you haven't changed subtimings or other RAM/IMC settings
Subtimings = no.Quote:
Originally Posted by Sam_oslo
Some BIOS settings = yes, PWM frequency Reduce 15%, all data vref -0.5%
VTT is very useful when overclocking uncore frequency. Try it out!~
Well I still having problems to get 4.2ghz also with 1.34VTT.
But I will leave this cpu and I will try with one with a better batch to see if here the problem is the cpu or me :p
Secondly, I would like to hear from people with this board and Windows 7, how can I do to make a RAID if I cant installa ICH10R drivers, I downladed the ones on the Intel site properly for Windows 7, but when I try to install them a notification shows up explaning that the system doenst meet the minimun requirements.
So, what can I do?
Thanks as always
Windows 7 comes with ALL the ICH10R drivers, and installs them during setup. This includes the Raid drivers.
So just set your Raid array in the bios, and let Windows do the rest.
4.2GHZ would depend on your CPU-batch, but sometimes you need to find the right/sweet spot for your setup, so don't give up too fast.Quote:
Originally Posted by Osterman
I installed w7 on my OCZ Vertex 30GB (single disk RAID-mode), without loading/installing any raid-driver and it worked just fine. I got some error when i tried to load the driver too, but it wasn't requited anyways. Did you try just to installing w7 on it?.
I installed Intel Matrix Storage Manager on w7 later.
BCLK216 is not final yet), but the Core sames to be stable too. :)
w3520 @4.1GHZ(19x216) 1.18v :cool: , 1 hour primestable
http://img35.imageshack.us/img35/361/prime21.th.jpg
Thanks for the support, but maybe tomorrow Ill get a new 920 D0 with a good batch seems they are hand picked, so I will try them.Quote:
Originally Posted by Sam_oslo
I also thought about the sweet spot, maybe 200BCLK wasnt a nice spot, but I tried higher and nothing happens, and to be honest, trying less is not the idea.
And If I try high BCLK with a lowe multiplier on cpu, ram will be affected by the high bclk and I will have to lower the multiplier. I dont think is the best idea.
Yes I tried to install this on W7: http://downloadcenter.intel.com/Deta...-bit*&lang=engQuote:
Originally Posted by Sam_oslo
But it makes appear a warning like I told you.
Also I didnt have RAID to do now, but I was thining in an upgrade and I wanted to know how was the stuff with W7.
Now I will try to install the one on your link.
Thanks for your answers
I personally don't mind loosing RAM-performance, because X58 has introduced such a huge RAM-performance that it is an overkill for most 24/7 scenarios anyways, unless you are using very rare RAM-demanding applications.
If I have to choose, i would rather choose high BCLK, than good RAM-timings/performance. High BCLK will give more options for CPU-OC (and in some cases better performance too). Right now I'm running with loose timing (for these sticks) and it seams to be making it easier to run stable at BLCK216.
Right now I'm trying to get @4.1GHZ(19x216) stable, and if I can find right voltages/parameters to run RAM, IMC, Uncore, QPI ,.. "really stable" at BCLK216, then @4.3GHZ(20x215) would just be the matter of proper cooling.
Did you could install that one?Quote:
Originally Posted by Sam_oslo
Because I also tried it and It didnt work:shakes:
Hi Osterman, I need 1.375V on my W3520 for 4.2ghz (8 hrs prime stable). But I do have a double and tripple radiator keeping CPU my temps down. I don't think going over 1.35V is that bad, so long as you keep the temps in check.Quote:
Originally Posted by Osterman
I have installed Intel Matrix Storage Manager 8.9.0.1023 on w7 RC1 64bit.Quote:
Originally Posted by Osterman
Moving up to @4.2GHZ(210x20) 1.248v, SuperPI 32M went like a dream with VVT=1.25v :) VVT is set to 1.23v in BIOS, but flips between 1.24-1.26v under stress on SG, and Everest is reporting it to be like 1.25v.
Both Vcore and VVT is dependent on the CPU-batch, but my CPU is showing the VVT=Vcore trend gets more visible at higher speeds.
BCLK 210
Core/Multi x20
Unccore x16
QPI x18
RAM x8
@1680MHZ 7-8-7-20 1.65v HyperPi 32M:
http://img30.imageshack.us/img30/1998/hyperpi32m.th.jpg
May be I cant install it because I didnt register my w7.
Like also I cant validate with cpuz.
i just got a replacement board (one lan port not working on the old board). after a quick few tests of new board with all the old hardware i noticed that the chipset on the motherboard can affect quite a bit for VTT and IOH, my new board requires quite less VTT and IOH than the old one.
anyone experience this?
CPU VTT 1.21 (bios),
on the old board i needed to use at least 1.34-1.36 for 12GB RAM, uncore 18x and 1T...
http://img141.imageshack.us/img141/6...0807221728.jpg
http://img141.imageshack.us/img141/7...0807222628.jpg
http://img141.imageshack.us/img141/6...0807222612.png
IOH 1.13,
i would need to use 1.25+ for the old board or it would cause hang up at bios...
http://img524.imageshack.us/img524/2...0807193038.jpg
http://img524.imageshack.us/img524/7...0807193045.jpg
http://img524.imageshack.us/img524/7...0806003243.png