UnOfficial Asus Rampage II Extreme Thread

[auchkoenig]

did it not do this pre-1104?

I cant say for sure since I didnt have access to a DMM before the 1104 bios but I also noticed that I can get higher OC with the same vcore with 1104.

I wasnt able to get it to run LinX at all regardless of the vcore but now I can run for 30 mins just like the pic that I showed. I can even run LinX for a few minutes at 4.2 with even higher vcore.

With the fact that I can oc at speed that wasnt possible at all before 1104 and the evidence that now 1104 overvolting like crazy, I guess it safe to say that the previous bios was not overvolting, and if it was, it surely wasnt as bad as this.

[dejanh]

I cant say for sure since I didnt have access to a DMM before the 1104 bios but I also noticed that I can get higher OC with the same vcore with 1104.

I wasnt able to get it to run LinX at all regardless of the vcore but now I can run for 30 mins just like the pic that I showed. I can even run LinX for a few minutes at 4.2 with even higher vcore.

With the fact that I can oc at speed that wasnt possible at all before 1104 and the evidence that now 1104 overvolting like crazy, I guess it safe to say that the previous bios was not overvolting, and if it was, it surely wasnt as bad as this.

The board always used to overvolt. Generally, the actual voltage is equal to whatever you set in the BIOS plus another 0.02V to 0.03V. CPUZ is not accurate in that way.

[Z3R0-CooL]

For some reason, I have to have the CPU Turbo Power Limit set to DISABLED for the override to work as well as all C1 and TDP otherwise my multi drops to 20x when priming. Am I missing something?

Settings should be?

CPU Turbo Power Limit = Enabled or Disabled?
C1 = Disabled (given)
TDP = Disabled or Enabled?

the only change i see is the CPU turbo Power Limit on the new BIOS... under extreme tweaker... where is the TDP option you guys are talking about?

Side note: Doing 4.22Ghz with turbo on on 920.

Also how do u go about increasing the ULK speed? i cant seem to be able to get it higher than 3.45..... IOH/ICH voltages? any indication as to what voltages to use?

[auchkoenig]

The board always used to overvolt. Generally, the actual voltage is equal to whatever you set in the BIOS plus another 0.02V to 0.03V. CPUZ is not accurate in that way.

Yeah thats why I said if it was overvolting, it was surely not as bad as this. I set it in bios for 1.5v iirc and it went as high as 1.556v. Thats some serious overvolting and cpuz was only showing 1.488. To someone that doesnt have an access to a DMM, it is a vcore delta of 0.068v, quite dangerous discrepancy imho.

[dejanh]

Yeah thats why I said if it was overvolting, it was surely not as bad as this. I set it in bios for 1.5v iirc and it went as high as 1.556v. Thats some serious overvolting.

Just checked with my DMM...

Idle 1.358V (rougly the same as CPUZ), Load 1.387V - 1.393V so roughly 0.03V higher. This is with LLC on Auto.

Seems the same to me...

Thanks. I'm on air and the multi under load is changing once I hit 80C...way too early. Real Temp and Core Temp temps. If I disable those options, I keep my multi at 21 and cpu stays at 4200 mhz which is the opposite as you???

Ok, the CPU Turbo Power Limit for me is Disabled, TM is Enabled. Is this what you have as well or?

[T_Flight]

OK, I'll be checking this when I get back home. If that thing is OV'ing like that an e-mail is gonna be sent immediately about it. I'll also do some testing with Loadline enabled and disabled. It might be that they are trying to get the loadline working and failed. heh I'll definitely do some testing. I have a DMM that is really accurate.

I'm glad you caught that. I got careless and should've checked that myself and didn't. I tell you, you can't trust anything anymore. I do NOT want anything over 1.45 going through my CPU and really that is too dang high.

[dejanh]

OK, I'll be checking this when I get back home. If that thing is OV'ing like that an e-mail is gonna be sent immediately about it. I'll also do some testing with Loadline enabled and disabled. It might be that they are trying to get the loadline working and failed. heh I'll definitely do some testing. I have a DMM that is really accurate.

I'm glad you caught that. I got careless and should've checked that myself and didn't. I tell you, you can't trust anything anymore. I do NOT want anything over 1.45 going through my CPU and really that is too dang high.

If you read my post above, I measured it using my DMM under load. The amount of overvolting is the same as before for me...0.02V to 0.03V.

I guess you can test if things are coming up different for you, but on my board everything still seems to be fine. If you explicitly set LLC to Disabled then there is no overvolting but the droop is stupidly high.

[auchkoenig]

If you read my post above, I measured it using my DMM under load. The amount of overvolting is the same as before for me...0.02V to 0.03V.

I guess you can test if things are coming up different for you, but on my board everything still seems to be fine. If you explicitly set LLC to Disabled then there is no overvolting but the droop is stupidly high.

I set the LLC to enabled. I have also tested with a few other vcore value and it seems to always overvolt under load 0.5V to 0.6V which double yours. Dont know if it is a problem with my board, my settings or my cpu?

And i do have a question, the high speed RAM recently introduced by Corsair requires absurdly high vtt, around 1.5v iirc, thats way higher than the Intel limit of 1.35v. So is it okay for manufacturer to sell an item that operates way above Intel spec? Wont it damage the cpu and what is safe max vtt that wont burn out your cpu in a week?

[BustaH]

Auchkoenig, is it possible your mm is not calibrated correctly? Just a thought.

I will also test this tommorow with my mm and see how we all compare.

[theonlybabyface]

Just checked with my DMM...

Idle 1.358V (rougly the same as CPUZ), Load 1.387V - 1.393V so roughly 0.03V higher. This is with LLC on Auto.

Seems the same to me...



Ok, the CPU Turbo Power Limit for me is Disabled, TM is Enabled. Is this what you have as well or?

I have both disabled and then the limit is removed. When I get home, I'll just enable TM and see what happens.

[crazyea]

has anyone else had a problem loading oc profiles? I know it erased them when I flashed, but I have a few for different stages of oc, and sometimes when I select profile 3, for ex, it loads 2 or 4, or even 1 instead.....very irritating as it did not do this with 1001.

[auchkoenig]

Auchkoenig, is it possible your mm is not calibrated correctly? Just a thought.

I will also test this tommorow with my mm and see how we all compare.

Well that's probably true.

[crazyea]

I have both disabled and then the limit is removed. When I get home, I'll just enable TM and see what happens.

the only options that matter for the extra multi is that your multi is set on auto, speedstep/turbo is enabled, and the new cpu turbo power limit setting is disabled. all else doesnt matter in this regard.

[scaramonga]

I've still got it. I've been to busy to mess with it yet, but it will be going. I can't get that RAM to OC worth a . Anything over 1604 and it just won;t run. If I take the ram out it'll OC up to 4.3GHz. Put the RAM back in even at 1704 or even 1654 and it is not stable. I've tried just about every combination of multi's and BCLCK I can and even loosed the timings down to 9-9-9-24-1T and it won't run worth a damn. It Dominates allright...it dominates at sucking really bad.

Strange? I'm still on BIOS 0805, and my Domms happily run at 1700+ with 8-8-8-20-1T timings (1.64v), not had time to try new BIOS as yet

[T_Flight]

Yeah, on top of that to add insult to injury, they pulled a nasty stunt with me on their forums over there. Even if this stuff OC'd to 2000 I'd still get rid of it. After it's gone I will never run another Corsair product again. That's why it's been removed from my sig. They had a longtime customer that would've been a lifelong one, and blew it.

Not once, not twice, but 3 times they pulled some BS with me, and the third time one of their Admins tried to post under my username like it was me. I got that rectified real quick, and their Server Admin told them never to do that again. I had my user account removed from that place along with my posts pronto. Two of them there better be damned glad that Server Admin had more sense than they did...I'll put it that way.

Straight up though. This RAM will not clock worth a damn. That has nothing to do with what I wrote about above. It's the worst clocking RAM I've ever had. I could've got value RAM that would've clocked better than these sticks...for about 200 dollars less too. It's going on Ebay soon though.

[BustaH]

Even if this stuff OC'd to 2000 I'd still get rid of it.

Pride is a killer..... just kidding.

I have the 1866 corsair dominator triple channel stuff, its fine but not clocking great I have to say.

I also have 4x1gb dual channel stuff, kingston hyperx 1866mhz. I run 3 of those, they will go much tighter with low voltage too! and get this, I got them for £41 gbp on ebay auction!

The doms are good imo, they cost me £165 proper low voltage triple channel ram but the hyperx are better and dual channel [I use three] work that one out!

[theonlybabyface]

the only options that matter for the extra multi is that your multi is set on auto, speedstep/turbo is enabled, and the new cpu turbo power limit setting is disabled. all else doesnt matter in this regard.

Thank you very much. Off topic, I hope the Canucks kick some Dallas @ss tonight.

[T_Flight]

OK, my board is overvolting too. I did the testing and these are the numbers I got.

Set In Bios - 1.44375 volts
Actual Voltage at Idle - 1.442 volts measured with DMM
CPU-Z Voltage in Vista64 - 1.432 volts
Voltage Under Load - 1.479-1.481 volts fluctuates slightly. Chess Benchmark was used to load all 8 threads.

CPU-Z showed no change during load at all, but the DMM don't lie. I used ProbeIt straight through the CPU ProbeIt point to measure.

This is a little higher than I'd like to see. I'm kinda disapointed not just with the BIOS, but with myself. I made a promise to myself I was not gonna make mistakes like this. I Screwed Up is what I did. I did not test my voltages, and because of that I exceeded my hard limit I placed on myself for vCore. I was not gonna go over 1.45 volts under any circumstances. 1.4 was really my max, but I made a mental note to allow 0.05 if I needed that extra bit to maintain stability. Now I broke my own rule I placed upon myself, and if it degrades over time it's because I screwed up.

I feel like a damned idiot for not watching my voltages. I know better. The thing could've OV'd to 2.0 friggen volts and I would've never known it. That's got to be the dumbest mistake I've made in a long time.

T_Flight loads a beta BIOS and doesn;t check his voltages. Arrrrghhh! With a Rampage II Extreme with ProbeIt points and everything.

OK, I'm done venting...

[cstkl1]

guys
overvolting on load its what loadline is all about

loadline started working correctly starting from m2f/re/r2e

previous loadlines on other mobo's was set bios say at 1.4v droop 1.375... loadline 1.4v

on the 16 phase setup set bios at 1.4v dropp 1.396v loadline around 1.453v

so its just different but still way better than gigabyte on their implementation of loadline


the latest dfi also seems to be similar to asus loadline.

btw it was like this since bios 080x
also loadline is to have a higher load voltage than idle.. so it is correctly implemented

[crazyea]

Thank you very much. Off topic, I hope the Canucks kick some Dallas @ss tonight.

no such luck.......

[cstkl1]

well hmm not sure but found a issue

with the tdc limit disabled

theres this one proc at multi 21x200

if it hits 80C on all the cores.. it will bsod

no throttling however.

anyone with a similar issue??
cause it looks like the tdc/tdp limit one of them is not implemented prop for mycase
it stops the throttling but theres the issue of the 80C limit.

[T_Flight]

guys
overvolting on load its what loadline is all about

loadline started working correctly starting from m2f/re/r2e

previous loadlines on other mobo's was set bios say at 1.4v droop 1.375... loadline 1.4v

on the 16 phase setup set bios at 1.4v dropp 1.396v loadline around 1.453v

so its just different but still way better than gigabyte on their implementation of loadline


the latest dfi also seems to be similar to asus loadline.

btw it was like this since bios 080x
also loadline is to have a higher load voltage than idle.. so it is correctly implemented

That wouldn;t be loadline calibration though. It would be negative loadline. I have a VDroop and Loadline mod on my old IC7-G vmodded onto the board via a pot. The first pot calibrates the voltage droop so it matches the BIOS. The second pot calibrates the hysterisis so that it doesn't create negative or postive loadine which is droop or negative droop under load. You can actually set negative loadl into it, but I never did. I was never sure what it would do long term, and the guy that designed the mod wasn;t either, and recomended not trying it.

I'm gonna go back and turn off loadline and see what happens. If it's overshooting that isn't calibrating. Now I have to figure out what the worst of two evils is. I'm still disgusted, becasue I di not want that thing going over 1.45 ever. It was going to be a longevity test. Now all that just went out the window. If it degrades I'll never know if it was caused by the overshoot or not. If it does degrade I'll always blame myself for that one.

[Falkentyne]

guys
overvolting on load its what loadline is all about

loadline started working correctly starting from m2f/re/r2e

previous loadlines on other mobo's was set bios say at 1.4v droop 1.375... loadline 1.4v

on the 16 phase setup set bios at 1.4v dropp 1.396v loadline around 1.453v

so its just different but still way better than gigabyte on their implementation of loadline


the latest dfi also seems to be similar to asus loadline.

btw it was like this since bios 080x
also loadline is to have a higher load voltage than idle.. so it is correctly implemented

Links for proof of this?
Loadline is supposed to ELIMINATE droop, not cause negative droop (or as you are describing it a voltage BULGE). Loadline is supposed to keep idle and load voltages very close to the same. Just like the pre-P4 cpu boards worked (e.g. Pentium 3/coppermine/etc, P2...)

Why do you think vdroop resistor and pencil mods were out for so long?

[theonlybabyface]

well hmm not sure but found a issue

with the tdc limit disabled

theres this one proc at multi 21x200

if it hits 80C on all the cores.. it will bsod

no throttling however.

anyone with a similar issue??
cause it looks like the tdc/tdp limit one of them is not implemented prop for mycase
it stops the throttling but theres the issue of the 80C limit.

The exact same thing is happening to me.

[T_Flight]

Links for proof of this?
Loadline is supposed to ELIMINATE droop, not cause negative droop (or as you are describing it a voltage BULGE). Loadline is supposed to keep idle and load voltages very close to the same. Just like the pre-P4 cpu boards worked (e.g. Pentium 3/coppermine/etc, P2...)

Why do you think vdroop resistor and pencil mods were out for so long?

I know this. I do NOT wanna have to hard mod a 400 dollar motherboard. They need to caliobrate the calibration on their loadline trick in that BIOS.

Let's see a show of hands for who's on board with this. We got them to fix the TDP override. Let's see if we can get this one fixed too. I can start hunting for specs on every chip on that dang board and find the pins but it would take forever, and I really don't wanna go "old scool" on a board that costs this much. I don;t want that kind of negative loadline either though.

I'm getting rwady to do some testing now. If I can fix it, I'm gonna ahve to turn it off or downclock and neither of those are good choices, but I can't have that. My rig has some serious bucks tied up in it. It's not just the money, but the time spent testing and tweaking. I don't want it dead.

Just to clarify that. I don;t want a BIOS putting high juice to my 1000 dollar CPU! heh

Be back after awhile after I try to see what I can do about this as a workaround for the time being.