Printable View
Quote:
Originally Posted by CryptiK
Yes there is a lot of extra heat load, but it is also true the block is very restrictive. Just the nature of this large W.B.Quote:
Originally Posted by zoson
I had a NB block only and after installing the full coverage EK block I could see the water was now very slow when entering the res.
But hey it works great and my over all temps are great.
No clearance issues with first slot what so ever.
Yeah the chokes at the CPU socket run hot, can't leave you finger on them for more than a second or two. Would like someone with an IR temp gun to get some temps. I wasn't planning to run 1000KHz PWM freq, I saw what that did with the Classifieds in terms of temps, 500KHz seems fine and is giving better results than the full analogue PWM on the R2E.Quote:
Originally Posted by zoson
Idle temps have gone up maybe 2 degrees, load temps have risen 2-3*C. I run a MCP655 and have turned it up from 3 to 4 to compensate for the reduced flow. I also had to re-orient my CPU block vertically which is not optimal, and block order is Pump->Rad->Mobo->CPU->VGA->Res so may revisit tubing path etc to improve it (people say order has little effect though).
No clearance issue with the 1st PCI-E slot lock, it's damn close but doesn't touch it.
4.3GHz @ 1.230v | 26*C Ambient | Quad rad + fans @ 1000rpm
http://i720.photobucket.com/albums/w...1xat43GHz1.jpg
This board has some weird quirks, not sure if its just mine........doesnt like 3710MHz uncore and anything less than 1.35Vtt BIOS (~1.296v real - I only needed 1.257v real for that uncore on the R2E). Less than that is stable in all tests, but wont cold boot, just hangs on DRAM. This is not ram timing/voltage related. Same thing happens with 2 different kits. It also just hates having uncore at 2 x ram, very unstable, if I add a tiny bit more voltage than needed to stabilize 3560MHz uncore I can easy do 3710MHz probably more (yet to try). Also needs more voltage to clock the ram than my R2E did (DDR3-1780MHz 7-7-7-21 1T took 1.495v on my R2E, need 1.56v on the R3E), so that coupled with the Vtt I'm using higher voltages all round except CPU.
Looking a my old review results here, the R3E loses about ~0.1V from the VTT last cap on the high side of the power plane to the under socket MLCCs (the gap widens with increasing current - so higher frequncy = more sag). 1.35VTT set is going to be very close to 1.25V~1.27V under full load. The measurement points on the board are a little off, and report the voltage a little higher than it actually is at the north side of the socket.Quote:
Originally Posted by CryptiK
I never had an R2E here so don't know what the offset between the measurement point and the north side of the socket is. The only way to check is either to flip the board while it's running (tricky) or solder a small wire to one of the MLCCs and check the offset under full load.
Of course, this was don one an earlier BIOS, there is the chance that ASUS have shifted the voltage table to compensate for the delta somewhat.
I don't think this will cure all your quirks but might explain some of the issue. :)
-Raja
Running an 980x at 4.1 Ghz and 1.3v results in cool chokes, that's with the machine crunching 24/7 and all cores fully loaded. Using an IR gun the temps are between 31c and 38c depending on the choke.Quote:
Yeah the chokes at the CPU socket run hot, can't leave you finger on them for more than a second or two. Would like someone with an IR temp gun to get some temps. I wasn't planning to run 1000KHz PWM freq, I saw what that did with the Classifieds in terms of temps, 500KHz seems fine and is giving better results than the full analogue PWM on the R2E.
Thankyou, that's interesting. I have at least preliminarily corrected the issue by increasing Vtt to 1.35625v in BIOS, which according to everest is 1.296v under load, and as per your findings this is higher than the real Vtt. I will have to measure at one of the MLCC's as you suggested to see what my board does. I did that with my R2E (I have a TJ07 so the socket area is cut out making access easy) and made a table of BIOS vs Software vs Real voltages.Quote:
Originally Posted by raju
Thing is I thought I'd sorted it last night by upping it to 1.350Vtt BIOS but this morning it hung on DRAM again on cold boot after PSU power off.
Did you investigate what enabling Vtt LLC did to the voltage? I don't usually run any LLC as I want to avoid transient overshoot conditions. However if it corrected the sag a little but still allowed some droop under load I'd be temped to use it.
31-38*C for the chokes under full load? (Just to make sure we're talking about the same thing - the ferrite blocks with R68 written on them to the IO side of the CPU socket).Quote:
Originally Posted by Johnmark
Mine are way over that. I'd say 45-50*C by guessing and touching. I'm running a W3570 at 4.3GHz @ 1.237v and have my PWM freq set to 500KHz, what do you have yours set to? You on water or air? Is there any airflow over that area in your case?
Ok no go, I can get it to boot into windows and be stable, but the second cold boot will get past the point during POST where it would DRAM hang with lower Vtt, but then it will either BSOD loading windows or just hang requiring reboot, whereupon it will say OC failed blah blah. I can reboot it multiple times after this and it will never make it into windows.
The alternative scenario after raising Vtt is it boots into windows but only with 4GB of ram. Rebooting and changing voltages will not rectify it, but a power off then on cycle will.
This is rather frustrating I must say, everything is set correctly but it goes from stable to can't load windows or detects 4GB of ram in 2 reboots. Never had any issues like this with my R2E.
I have tried reseating CPU and ram, and cleaned all the contacts with iso before putting them back in. I have tried every BIOS and tried using the second BIOS chip. I've tried setting manual ram timings (loose safe ones too), manaully setting QPI lower, different combinations of uncore, enabling Vtt LLC, changing ram ref voltages and vdimm, cpu and IOH skews etc. Nothing makes any difference so far. I'll keep at it, hopefully I find the trick.
cryptic raise the ioh to 1.26 and ioh/ich to 1.6
No difference zsamz, tried that before too. I am actually kinda stumped. Never had an issue this bad (actually with the R2E same thing happened until they released BIOS 1504 then it fixed the cold boot problem).
There's nothing wrong with my components or settings, the board should not be doing this.
what sucks is that I don't think they have had a bios come out for a while:shrug:Quote:
Originally Posted by CryptiK
I know that when I had mine I could run 4.3 stable and with lower volts that my UD7 however, above that there was a complete lack of stability.
try another boisQuote:
Originally Posted by CryptiK
man i cant beleive how high the lemon rate is with the reIII simply ridiculous
i was just too happy to take a 100$ loss after a few weeks with the board
i shoulda just takin the restocking fee lol but had too high hopes
:rofl::rolleyes:asus
Ok testing more, doesn't do it running stock clocks, DDR3-1333 etc. I'm now on 30 x 133 @ 4GHz, ram at DDR3-1866 8-8-8-24 and its ok too...............I'll keep testing and hopefully I'll find what is causing this. I will RMA it if this keeps going, try another R3E, and if it does the same thing then I'll sell it and move try another board. Would probably give a UD7 a go and find a full cover block for it.
you should try a classy:yepp:Quote:
Originally Posted by CryptiK
That's always an option.
I didn't get time to investigate the LLC option, unfortunately.Quote:
Originally Posted by CryptiK
One thing I would do is check what the board is defaulting the RTL settings to, if they are too tight some of the symptoms you mention would manifest. Hunting something like this down can be like shooting in the dark, though.
@raju
Since you mentioned RTLs I wanted to ask you. Did you happen to have a RTL calculator specifically for the R3E that you use? I have been using your rtl2 calc and have noticed the board sets RTLs as if the ' Min Sep Delay ps ' field value was 0.58 instead of 0.67.
I also agree that the right RTL settings are essential in achieving a stable overclock.
No, nothing specific for the R3E. The min sep delay was probably left like that when I saved the file. There's normally some drift in that setting at increased clock speeds and somewhere around 580ps is the least I've ever seen the IMC default too. The reason is that clock skews need to be advanced as you increase bus frequency.Quote:
Originally Posted by spoolindsm127
It's very odd, I can get it to post from cold boot (PSU power off) now at the overclocked settings, but it can't load windows. It seems to be SATA/southbridge related - often says my bootmgr is corrupt. It's not. Sometimes it gets to the 'loading windows' splash screen and freezes.Quote:
Originally Posted by raju
Ive tried new SATA cables, and I did try setting RTL's manually, all ram timings in fact, I know this kit very well from my previous board.
The odd thing is, once I'm in windows from a hot boot, not problems, it will pass any stability test. If I restart mostly it will get back into windows fine. Shut it down and kill the power to the PSU though and its a cold boot nightmare that I can't seem to track down the root cause of.
Could be several things. A corrupt bootmgr message (when it is not really corrupt) obviously signifies instability, and most likely on the memory end.Quote:
Originally Posted by CryptiK
Try playing with the torque of your waterblocks - make sure they aren't warping the board in any way - these boards are very sensitive to that. The problem with these custom blocks is that they sometimes allow you to overtighten, which isn't good for BGAs or the transmission line traces.
Lastly, if you have the option, try another PSU.
-Raja
Found it. Can't believe it took this long. The C1 ram slot or signal path is damaged. It wont boot at all when overclocked with a stick in that slot alone, boots occasionally with 3 sticks in but rarely loads windows, and I get erratic boot errors when running stock speeds with that slot populated (eg: bootmgr is corrupt or missing etc).
Board will be exchanged for another. Hope the next one works!
Thanks for the advice guys, nice to have people to bounce ideas off :up:
EDIT: Picture now added explaining my feelings :D
http://i720.photobucket.com/albums/w...UUUramslot.jpg
So, has the Marvell 9128 controller been fixed now then ?
It cant be as poor as it was at launch as surely Gigabyte would not use it on a £429 M/B
http://www.novatech.co.uk/novatech/p...-assassin.html
Anyone know if a firmware update was included in a recent bios from Asus
?
When you get your return board, run it without the full cover block (use the stock sink) for a few days first. The if everything is a-ok use the block, making sure not to go too tight.Quote:
Originally Posted by CryptiK
Will do, I don't want another saga like this happening. I nearly did that when I got this board, but the red mist descended and I wanted it all done and in the case asap :rolleyes:Quote:
Originally Posted by raju
Thanks for the advice too.
Yes we are talking about the same thing. I'm WCed using the same block and loop arrangement as you. Using an Obsian 800d case (air flow sucks) so I do have a fan that is blowing cold air into the case inside of sucking out as per original design, running PWM at 500 as 1000 didn't seem to buy me anything.Quote:
31-38*C for the chokes under full load? (Just to make sure we're talking about the same thing - the ferrite blocks with R68 written on them to the IO side of the CPU socket).
Mine are way over that. I'd say 45-50*C by guessing and touching. I'm running a W3570 at 4.3GHz @ 1.237v and have my PWM freq set to 500KHz, what do you have yours set to? You on water or air? Is there any airflow over that area in your case?
Water temp in the loop is 30c at its hottest.
Glad you found the source of your boot problem! They sure don't make boards like they used to!! Recently put together five crunchers for WCG and ended up RMAing two boards, both GB's within 2 months of install.
About to get the R3E up and running again after a few months off while planning the upgrade to my upgrade (went back to the backup rig for the time being). Anything that I should know about the R3E as far as improvements over running it at stock? Hardware will be:
ASUS R3E (water cooled, EK full cover)
Corsair AX1200
i7 920 @ 4+ GHz (water cooled, EK Supreme HF w/ plate #1)
6GB DDR3 Cas 6 Mushkin Enhanced Ridgeback
256GB Crucial RealSSD C300
GTX 480s in 3-Way / Tri SLI (water cooled, Koolance blocks)
Windows 7
Main purpose for this rig: Triple monitor gaming via Nvidia Surround @ 5760 x 1200.
Very similar setup to mine,
all you have to decide is weather to run the C300 on the Marvel or the ICH10R !
still not sure if a recent bios update has boosted the Marvell's performance, currently I have 2 C300s on the ICH10R and run 3 x Hanns-G HG 281s in 2D surround 6200 x 1200.
asked the question earlier on this page but no reply as yet.
Quote:
Originally Posted by Johnmark
Well this is a kick in the nuts. Got a replacement board and its doing the exact same thing as the first!
There must be some kind of incompatibility going on between the board and I think my ram kits. The board detects 2/4/6GB depending on the moment. Cleaned all the contacts, socket, ram and ram sockets with contact cleaner. Changed everything I can think of in BIOS and nothing helps. This is insane. My kits (Dominator GT 2000C8 Hypers and GSkill Trident 2000CL9) are common kits. The Tridents in 2x4GB form are on the QVL for this board.
I have a W3570 and it even plays up with my 920! No way is the board incompatible with those CPU's especially the 920. It recognises them both on POST, just have this incessant cold boot issue, and if it does manage to POST it's usually not with 6GB. If it does manage to POST and detect 6GB, it can't load windows!
Think this board will have to go back and I'll go to another brand :rolleyes:
try running the mem with the secondary timing 1 higher than 1st and 3rd IE = 8-9-8-blah blah blah
something to do with it not liking 4.3+ on the CPU and 2000mhz on mem without having to do that with the timing it seems. i tried at getting the 2000 mark with 12gig @ 6x 2gig chips. at first i thought it was just a matter of voltage and IMC on the CPU but as soon as i loosen just that one specific timing it alows me to do 4.5+ with about 1950mhz on the mem (can't seem to get higher than that with the quantity of chips i use).
it's worth a shot if you haven't tried it yet. this board is real damn touchy i've come to find. right now i can't seem to do higher than 4.4 @ 1866 CL7 (7-8-7) mainly due to heat issues (i think i may have too much paste). i can hit 4.5 but i just don't feel like having full loads at 90c across the board on a WC'd 980X with a koolance CPU-360+MCP655+1/2" ID tube+9x120 double thickness rad... which again, leads me to believe it's paste issue or too much / little torque on the block.
Ram timings don't help that was one of if not the first thing I tried. This issue can be slightly altered by not even close to cured by adjusting any of the BIOS settings in 2 boards now.
Are there any known incompatibility issues with:
Dominator GT 2000C8 kit:
CMG6GX3M3A2000C8
GSkill Trident kit:
F3-16000CL9T-6GBTD
CPU's:
Xeon W3570
i7 920 D0
on the Rampage III Extreme?
Quote:
Originally Posted by CryptiK
The board does select a tRL that's too tight at times (this is set behind the scenes and generically i think it's offset with tWR). I have reported this back to ASUS, but I'm not sure if they are working on it.
It's so weird Raju. I have replicated the exact same issue on a totally new board now. Ive verified all the gear works on another board. Ive tried numerous brands/types of all hardware.
Seems the cold boot issue is common, many people posting about it over on the Asus forums.
I am still testing this, but it seems so far (4 times) that I can set up the PC, boot and pass stability tests etc, turn it off but not turn off the PSU or wall socket, then it will just boot up again normally and pass tests again. This board actually seems a bit better than my last as I remember it had issues doing that too but I am now exclusively using my Corsair Dominator CMG6GX3M3A2000C8 (3x2GB) kit.
I'll let you know if I find anything else out.
I Couldn't even get that set to post off stock setting when running it on a d940. Aka 1066 just swapped my processor to a i970 and its defaulted at 1333. Haven't messed with it more due it being my work comp and i need it up and stable atm.
Sent from my X10a using Tapatalk
Thanks, I'll keep the thread updated as I work through this.Quote:
Originally Posted by raju
You have the 2000 8-9-8-X kit though with PSC IC's, I have the 8-8-8-24 kit with Hyper IC's, so slightly different there.Quote:
Originally Posted by MagisD
People have reported this board is just so much better with Gulftowns, which is very unfortunate.
@CryptiK
BTW, which BIOS are you using?
I run the exact same Corsair Dominator GT kit.Quote:
Originally Posted by CryptiK
No problems here.
I say you try an official bios and try setting RTLs manually. The only time I have detection issues is when RTLs are too tight.
Good luck tho :)
Last night I started working on finding out my max blck. got to 220 with qpi at 1.2v and IOH core at 1.25v. increasing the QPI doesnt seem to help guess I need to bump up the IOH a bit more now.
Has anyone messed with the Extreme OV option?
I recently Enabled it and noticed some extra settings appear: QPI, IOH, DRAM Voltage OCP and QPI, IOH, and DRAM PWM Frequency. Does anyone know what the settings for PWM Frequency mean? They are AUTO, 1x, 1.33x. Are the settings in relation to CPU PWM Frequency?
I have recently seen users mentioning they use a lower setting for CPU PWM Frequency so I thought I'd lower PWM Freq. for QPI, IOH, and DRAM also.
@ Cryptik
I have run the exact same kit (Corsair Dominator GT 2000 8-8-8-24) on that board with no problem and the only time I would get memory missing (usually drops a channel to dual instead of triple), it was due to an unstable overclock, but in your case I see that you have tried multiple boards, chips and sticks of ram.
I'm trying to go beyond 220 blck anyone have any pointers for this board? I've tried raising PCIE to 105 and upping my IOHQuote:
Originally Posted by Xel_NaGa
I have tried them all from 0402 to 1102, even some betas. 0402 seems to be the best and is working ok but I cannot cold boot or it hangs, fails to detect all ram etc.Quote:
Originally Posted by donmarkoni
Tried all official BIOS. Tried setting all ram timings manually too. No change, in fact setting ram timings manually can actually make it hang more than leaving them on auto.Quote:
Originally Posted by spoolindsm127
Interesting, I hadn't enabled it. The settings tie in with the setting of higher voltages - the OCP settings give some semblance of protection of the circuit and components. The PWM frequency when raised above stock can reduce transient response and may give some benefit in OC but also produces more heat since the mosfets are switching on and off faster (1KHz = 1 thousand cycles a second) so setting this to a moderate value is a good compromise between heat production and performance.Quote:
Originally Posted by spoolindsm127
Yeah I have seen others with the same kit too, that's one of the reasons I'm so confused. I cannot understand why my kit, which works fine on a UD5 with my W3570 just won't play ball when in the R3E with the same CPU. I think it must be a BIOS issue, as I have tried multiple components (CPU/VGA/PSU/HDD) and the problem is the same. I do only have one other triple channel kit which is the GSkill Tridents 2000C9's and these are even less stable than the Corsair 2000C8 kit, however the Tridents (the 2x2GB kit) is on the Asus QVL for this board! Makes no sense.Quote:
Originally Posted by l0ud_sil3nc3
Seems to be some weird CPU/ram interaction going on with this board, as people have said as soon as they dropped in a 980X they went from no POST to full stability with the same kit of ram. WTF has Asus done with this board. Some people have even reported certain batches of CPU seem to have incompatibility issues ie: my 920 and my W3570 don't work with a kit of ram other people have used and say is fine. Sucks because both my CPU's are week 47 and 49 gem batches.
Increase PCI-E freq to 110-115, increase vIOH to ~1.30v and increase Vtt to ~1.4250 BIOS and see how far you can get.Quote:
Originally Posted by Xel_NaGa
what would be an unsafe voltage for 24/7 on a 980x as far as QPI goes.Quote:
Originally Posted by CryptiK
I would be led to believe it is a board issue as you were having no problems with said hardware before the board upgrade, and when I had my R3E I ran nothing but bloomfield chips with no problems (except for the low bclk issue) and usually the R3E required less voltage than my UD7. Regardless I hope you get this issue figured out as it sucks having new hardware that doesn't work properly.
I would try to keep it a touch below 1.4 if you can, I always ran 1.34 for 1720 6-6-6-18, but if you are going to run the memory at 2000+ you are going to need closer to 1.4-1.45:up:Quote:
Originally Posted by Xel_NaGa
guys, is it safe to run QPI/DramV=1.4125v 24/7..?..
Its real voltage not BIOS set voltage you need to worry about, if you have Vtt LLC enabled, you are a bit over intel spec, but if you dont have it enabled you would be about right on it. Most guys would say that's ok, its a bit high for me personally, but really your call. Anything over intel spec no one can say for sure is safe.
Real load voltage will be in the region of 1.32V without LLC, which most people deem safe.Quote:
Originally Posted by kaka_89
So I was reading up on CPU PLL, I can boot with 4.6 - 5g with anything from 1.45 vcore. now when I run Linx , the Linx process crashes but the os continues.... I've tried raising the vcore all the way to 1.55 and it doesn't seem to help. It only seems to make it worse by raising the temps near 100c on full load and risks a bsod. My CPU PLL is at 1.8 and for the heck of it I've tried setting it to 1.3... My question is... Could cpu PLL Be an issue here? From what I read CPU PLL isn't a lower it for better results kinda thing more like a sweet spot kind of thing... Is there a best way to tune out the CPU PLL?
Thanks for all the pointers guys
******other settings*******
I've set my memory, qpi, and uncore to the lowest speed to rule them out
Qpi is set to 1.42v ( stable @ 1.25v. 1950 mem 3900qpi 15x multi 220 bclk)
Iohc set to 1.25v ( stable @ 1.25v. 1950 mem 3900qpi 15x multi 220 bclk)
Dram set to 1.65v 8-9-8-24 (stable @ 1.25v. 1950 mem 3900qpi 15x multi)
Check this out, and this.Quote:
Originally Posted by Xel_NaGa
Key is high PCI-E freq and high IOH Core V.
Some will say it isn't, but I say it is. ;) I run my at 1.4375V QPI LLC Enabled. :DQuote:
Originally Posted by kaka_89
You could say CPU PLL needs to be on sweet spot and I would agree. I use 1.35V for 980X, but for 970 I was using 1.2V. No way of finding it, but trial and error.Quote:
Originally Posted by Xel_NaGa
BTW, don't drop everything to lowest possible, just use known stable settings, and try to avoid lowest UnCore multi, very unstable for me.
BIOS 0404 released March 14, 2011
http://dlcdnet.asus.com/pub/ASUS/mb/...-ASUS-0404.zip
Found on asus r3be vip forum.
It has updated firmware for intel/marvell controllers!
No idea if it works for r3e tho.
Hi
With i7 970 a 4.25GHz (21x202), you leave C1E Support and Intel (R) SpeedStep (TM) Tech enabled?
thanks ;)
Don what bios you running on yours?
:Dtook your advice on not the lowest uncore and using 1.35 CPU PLLQuote:
Originally Posted by donmarkoni
big help :up: :D
http://i48.photobucket.com/albums/f2...5/progress.jpg
Although the temps seem a bit high to me considering the vcore... would you agree? or is this just normal 980x 6core heat?
Can't flash it using EZ flash, says 'bios boot block is not valid'Quote:
Originally Posted by zoson
You'd have to try force flashing and hope it didn't brick the board.
It would be interesting to get someone who can mod bioses to take a look and try and make a new bios for the R3E with the new firmware and hopefully better ram compatibility.
Asus is lazy and aren't looking like supporting the R3E anymore :shakes:
I have a W3570 same batch as you Cryptix as well as Dominator GT 2000 C8 (Elpida Hyper), I may have to excavate the 980x and slap the Xeon into my R3E. What issues were you having?
Hey mate, page 173 on is basically all me bashing my head against a wall. Have a read, too much to explain in one post. To sum it up the mobo wont cold boot (ie after PSU or wall socket switched off) with my CPU/Ram or a combo of the two. Once into BIOS I can reload my saved profile, load windows and its stable (mind you the first R3E I had would not do this). Does it with my i7 920, W3570, Corsair 2000C8 kit, and GSKill Trident 2000C9 kit.
My CPU's are fine, the rams are fine, 2 different mobos both do the cold boot thing. Tried all BIOS available. Tried multiple VGA cards, PSU's, HDD's and 2 diff CPU's and 2 diff ram kits. All my gear works great on the UD7 and UD5 and R2E. Just not on the R3E.
John - I was thinking about why you had cool chokes and mine were hot. Since I had to pull apart my system to RMA the mobo I had a good look at my block. EK recommend using the 0.5mm thermal pad on the mosfets, and also provide those acetal standoffs we all love to hate to prevent over-tightening. Now in my opinion, EK's machining isn't good enough to use a 0.5mm pad, and after feeling my chokes and seeing my NB/SB temps, I was convinced that the standoffs were too thick and they were preventing good contact, which was supported by the contact mark in the past on the NB after block removal. When I put the block on the new mobo, I used the stock thermal pad (this one was much better than the last one) and its ~1mm thick. I also used a coarse emery board and filed at least 1mm off all 9 standoffs then attached the block as per usual being very careful not to over-torque the screws.
Surprise, now my chokes are cool under load too, and my NB/SB temps have come down ~15*C under load!
Anyone with an EK-FC R3E and bad temps I recommend you do this 'mod'.
Screen cap of temps 5 mins after startup in 20*C ambient temps:
http://i720.photobucket.com/albums/w...mbientnew1.png
I also picked up a GTX580 as an upgrade from my ageing GTX295. At 950c1900s2025m, it only scores ~500 points more in 3DM06 than my highly over-volted and overclocked GTX295! However it does do that effortlessly, and feels awesome to game with, plus DX11 support, and it's so much cooler running. I'm using the Koolance VID-NX580 block with it and its great, and matches the EK-FC R3E perfectly IMO.
3DM06 - GTX295 @ max stable OC
http://i720.photobucket.com/albums/w...tiKone/064.jpg
3DM06 - GTX580 @ 950c1900s2025m
http://i720.photobucket.com/albums/w...1900s2025m.jpg
how are you checking choke temps?
John used an IR temp gun, I just touched them with my fingers. They burned me in <5 seconds before I modded my block and used thicker thermal pad on the CPU mosfets. Now they are totally cool to the touch, feels like skin temp which supports John's measurements of ~38*C.
Thanks, a slight improvement for me, it will now post after full PSU power off but still cannot load windows, just starts to and crashes to black screen and keeps trying then crashing again (will remain stuck in that loop indefinitely). If I then switch it off, then back on again it won't say 'overclocking failed' like BIOS 0402 does forcing me to enter BIOS and reload saved settings, but boots at the OC settings again and this time makes it into windows fine. Just stability testing now but usually if it actually makes it into windows its fine.
This proves to me my issue is BIOS related.
Changelog??Quote:
Originally Posted by Fire4Wire
.."Improve system stability" :rolleyes:
Asus in well known for the thorough bios chanchelogs... :lol:
Yeah, I'm def wondering if I should even bother. Every BIOS I've tried so far has not been better than 1005 for daily use...
Quote:
Originally Posted by CryptiK
enjoyyy da beast my friend :up:
Sadly, they still haven't updated the firmware for the Marvell controller in this new bios 1207:( :mad:Quote:
Originally Posted by Fire4Wire
Not sure about the Intel controller though very unlikely this controller will be updated ether.
[ 1207 ]
----------------------
1. Improved DRAM compatibility
2. Fixed S3 resume fail when USB 3.0 controller was disabled
3. Fix incorrect CPU temperature may display in BIOS setup menu when the temperature is under 0 degree
4. Support GPU tweakit function
Quote:
Originally Posted by Fire4Wire
maybe they added better timings for higher SPD. I know on my modules I have to manually enter just about every timing in order to get all 6 sticks detected at 1950+
i thought id wait for the 1207 bios to see if my issue worked out, but it hasn't so i wonder if someone knew this-
using the blue usb 3.0 connectors in back, and updating the nec chipset to the latest firmware 3027 and driver 2.0.34, i am plugging a few various usb 3.0 devices and cables into them, and yet they are showing up under another usb port and not using 3.0 but 2.0, and i cant figure it out.
notice in my screenshot the nec/renesas controller has nothing showing as attached to it, and yet another intel 2.0 port (the intel ich10 3a3 controller) is showing the usb 3.0 item connected to it.
this is in xp32sp3, and all else works perfectly on the system since the week this board came out. usb 3.0 devices always show under another controller altogether, and i cant get any device to show up uinder the 3.0 controller.
thanks for any advice
Awesome improvement!Quote:
John - I was thinking about why you had cool chokes and mine were hot. Since I had to pull apart my system to RMA the mobo I had a good look at my block. EK recommend using the 0.5mm thermal pad on the mosfets, and also provide those acetal standoffs we all love to hate to prevent over-tightening. Now in my opinion, EK's machining isn't good enough to use a 0.5mm pad, and after feeling my chokes and seeing my NB/SB temps, I was convinced that the standoffs were too thick and they were preventing good contact, which was supported by the contact mark in the past on the NB after block removal. When I put the block on the new mobo, I used the stock thermal pad (this one was much better than the last one) and its ~1mm thick. I also used a coarse emery board and filed at least 1mm off all 9 standoffs then attached the block as per usual being very careful not to over-torque the screws.
Surprise, now my chokes are cool under load too, and my NB/SB temps have come down ~15*C under load!
I must of got lucky on my first install as I was struggling to get everything aligned just right :)
Other than the large restriction this block has (I expected it) performed very well. NB and SB 38C with water loop temp at 31c at 100% load 24/7.
Why not? Drops multi and lowers temps when idle. ;)Quote:
Originally Posted by tistou77
I was using 0095 with Elpida BDBG, but after having issues with Elpida Hyper with it, I switched back to 0096 which plays much better with Hypers. :up:Quote:
Originally Posted by Xel_NaGa
Glad i could help. :)Quote:
Originally Posted by Xel_NaGa
Yeah, maybe a slightly higher temps, but depends on cooling and ambient temps...
and you, you have them enabled or not?Quote:
Originally Posted by donmarkoni
me, I just enabled C1E
thanks ;)
All enabled. Why would I use and call stable CPU with disabled functions I paid for. ;)Quote:
Originally Posted by tistou77
ok I leave enabled ;)
thanks
here is latest test bios with TRL timing for each chanel in dram timings, you can try +1, +2, -1, etc to curb dram disappearing when oc'ed
http://www.freefilehosting.net/rampa...reme-asus-0003
Thanks, I'll give this a try when I get home.Quote:
Originally Posted by LardArse
i still didn't manage to get a stable linx test..
it drops on the 14, 17 and 18th test...
http://i645.photobucket.com/albums/u...ka_189/oc1.png
this is my bios template..(1102)
is there anything that i've overlooked here..?Code:Target CPU Frequency 4000MHz
Target DRAM Frequency 1604MHz
LN2 Mode: Disabled***
QPI Loadline Calibration: Disabled***
Sync Mode [Enabled]
AI Overclock Tuner [Manual]
OC From CPU level Up [Auto]
2D Performance Booster [Disabled]
CPU Ratio Setting [25.0]
CPU Turbo Power Limit [Disabled]
>CPU Configuration----------------------------
CPU Ratio Setting [25.0]
C1E Support [Disabled]
Hardware Prefetcher [Disabled]
Adjacent Cache Line Prefetcher [Disabled]
MPS and ACPI MADT ordering [Modern]
Intel(R) Virtualization Tech [Disabled]
CPU TM Function [Disabled]
Execute Disable Bit [Disabled]
Intel(R) HT Technology [Disabled]
Active Processor Cores [All]
A20M [Disabled]
Intel(R) SpeedStep(TM) Tech [Disabled]
Performance/Watt select [Power]
Intel(R) C-STATE Tech [Disabled]
C State package limit setting [Auto]
C1 Auto Demotion [Enabled]
C3 Auto Demotion [Enabled]
----------------------------------------------
BCLK Frequency [160]
PCIE Frequency [100]
DRAM Frequency [1604]
UCLK Frequency [3528]
QPI Link Data Rate [7057]
Memory Configuration Protect [Disabled]
>DRAM Timing Control--------------------------
CAS# Latency 6 [8]
RAS# to CAS# Delay 7 [8]
RAS# PRE Time 6 [8]
RAS# ACT Time 18 [24]
RAS# to RAS# Delay 4 [auto]
REF Cycle Time 72 [88]
WRITE Recovery Time 10 [auto]
READ to PRE Time 6 [auto]
FOUR ACT WIN Time 24 [Auto]
Back-To-BackCAS# Delay 0 [Auto]
Timing Mode 1N [1N]
Round Trip Latency on CHA 59 [auto]
Round Trip Latency on CHB 61 [auto]
Round Trip Latency on CHC 62 [auto]
WRITE To READ Delay(DD) 8 [Auto]
WRITE To READ Delay(DR) 8 [Auto]
WRITE To READ Delay(SR) 18 [Auto]
READ To WRITE Delay(DD) 7 [Auto]
READ To WRITE Delay(DR) 7 [Auto]
READ To WRITE Delay(SR) 7 [Auto]
READ To READ Delay(DD) 7 [Auto]
READ To READ Delay(DR) 6 [Auto]
READ To READ Delay(SR) 4 [Auto]
WRITE To WRITE Delay(DD) 7 [Auto]
WRITE To WRITE Delay(DR) 7 [Auto]
WRITE To WRITE Delay(SR) 4 [Auto]
----------------------------------------------
CPU Differential Amplitude [Auto]
CPU Clock Skew [Auto]
IOH Clock Skew [Auto]
------------ Extreme Engine Digi+ ------------
Digi+ PWR Mode [T-Balanced]
PWR Volt. Control [Auto]
Load-Line Calibration [auto]
CPU Voltege OCP [Enabled]
CPU PWM Frequency [Auto]
Extreme OV [Disabled]
Extreme OC [Auto]
CPU Voltage 1.343 [1.31250]
CPU PLL Voltage 1.349 [auto]
QPI/DRAM Core Voltage 1.429 [1.43125]
DRAM Bus Voltage 1.654 [1.65625]
>DRAM REF Voltages----------------------------
DRAM DATA REF Voltage on CHA [Auto]
DRAM CTRL REF Voltage on CHA [Auto]
DRAM DATA REF Voltage on CHB [Auto]
DRAM CTRL REF Voltage on CHB [Auto]
DRAM DATA REF Voltage on CHC [Auto]
DRAM CTRL REF Voltage on CHC [Auto]
----------------------------------------------
IOH Voltage 1.111 [Auto]
IOH PCIE Voltage 1.508 [Auto]
ICH Voltage 1.111 [Auto]
ICH PCIE Voltage [Auto]
*QPI Voltage OCP [auto]
*IOH Voltage OCP [auto]
*DRAM Voltage OCP [auto]
*QPI PWM Frequency [Auto]
*IOH PWM Frequency [Auto]
*DRAM PWM Frequency [Auto]
---------- Spread Spectrum Control -----------
CPU Spread Spectrum [Disabled]
DRAM Spread Spectrum [Disabled]
***on-board jumper dependant
That looks good, I wouldn't worry about it dropping fractions of a gflop here and there, could be background process related as is not IMO demonstrative of an issue.
you can see on my cpu-tweak, the uncore clock turns to be 10xxxmhz when it is actually 35xxmhz..!!..Quote:
Originally Posted by CryptiK
is that a bug issue..?
Yeah looks like it, with mine it doesn't detect the core multi/freq properly. I just use CPU-Z
Can somebody direct me to a good overview of oc'ing i7's and/our this board in particular. It's ben quite a while since I oc'd last build ran stable for a long time and didn't have half the features of this board.
Need a refresher.
Running an 970 six core now.
A almost 4400 posts digging through here for relevant info is a pain.
Sent from my X10a using Tapatalk
Not sure Ive seen one. Try and not use lowest uncore speed is the one thing I picked up for gulfies. Other than that specifically what kind of info are you after?
I keep hearing this as well, but when I increase my uncore mult x1 from lowest, I have stability issues... I think there can be a lot of variation as to what's good and what's not for individual cpus. Just like CPU PLL on R3E, different values work better for different cpus.Quote:
Originally Posted by CryptiK
I think the important thing to know is these things *can* help, but you won't know if it will help *you* specifically unless you try it.
If I were you I'd just look through the thread in reverse order, and find a BIOS template someone posted that is ~ the speed you want, and work from there.
i7-970 @ Watercooling
4813 Mhz @ 1,501v. @ Prime95 26.4 :cool:
http://www.abload.de/thumb/4813mhz15...7uncorn7v9.jpg
5187 Mhz @ SuperPI 1M :D
http://www.abload.de/thumb/superpi1m5187mhzq7xg.jpg
this is a new version of bios?Quote:
Originally Posted by LardArse
I'll take an order of that with a side order of ram tweaks.Quote:
Originally Posted by mahaudi
Honestly I'd like a good noob guide to start off with. I have no idea what I've forgotten.
Sent from my X10a using Tapatalk
This isn't a noob forum so you're not going to get any noob guides dude.Quote:
Originally Posted by MagisD
New Bios 1207
1. Improved DRAM compatibility
2. Fixed S3 resume fail when USB 3.0 controller was disabled
3. Fix incorrect CPU temperature may display in BIOS setup menu when the temperature is under 0 degree
4. Support GPU tweakit function
ftp://ftp.asus.com.tw/pub/asus/mb/LG...-ASUS-1207.zip
days behind.Quote:
Originally Posted by mahaudi
is that safe to run on a regular day basis(24/7), especially on the high the cpu/vtt at 1.43125v..Quote:
Originally Posted by CryptiK
Quote:
Originally Posted by mahaudi
03/04/2011
1.43125v BIOS is going to give you around 0.1v less by Raju's measurements. My 1st board was closer from the MLCC's at the back of the CPU socket (with VTT LLC enabled I would set 1.29v and get 1.28v) but you'd have to measure to know for sure on your board. I haven't measured my new one.Quote:
Originally Posted by kaka_89
Anything under intel spec is safe.
!!!!! well i may have found a cure of my frustration. out of all the bios out there, 1207 finally seems to be showing promise.
i've been endlessly trying to be apart of the 4.5 club and it seems i might have gotten it finally with 1207. every time i tried with other bios it would get to about 4.4 and then it refused to go any further. i could push it to 4.5 while in windows, but i couldn't get it to post at startup afterwords.
UPDATE: something i find to be annoying... 1207 seems to have issues on startup or cold starts. it takes several shut downs to finally get it to start booting...
Same here ! >_<Quote:
Originally Posted by skuldarin
No problems here with 1207, but I went for 0003. Those 0xxx were always better for my HW combo then 1xxx since 9124 crossroad.
the 0003 requires less tensions, etc. ... than the 1207?Quote:
Originally Posted by donmarkoni
Tensions to the hardware, or to my brain trying to tweak it? :DQuote:
Originally Posted by tistou77
Anyway, I don't know, cause I didn't test 1207 much, just booted one evening on standard settings and flashed 0003 tomorrow, no tweaking or testing.
So far positive results with 1207 for me. Exact 1005 settings were stable.
Now testing at 21x205. I want the extra 100mhz! ;)
More bclk needs so much more IOH! 200 I only need 1.2 IOH, 205 I need 1.272.
Edit:
I tested CPU PLL 1.2 and it seems better than 1.55v!
Well my ram kit worked perfectly first try with 1207. Xmp profile. Couldn't do more then 1333 stable before.
Now to work off that for oc.
Sent from my X10a using Tapatalk