:(Answer one that no !!! i cant flash back to 1403 :down:damn bios 1406Quote:
Originally Posted by emertX
Printable View
:(Answer one that no !!! i cant flash back to 1403 :down:damn bios 1406Quote:
Originally Posted by emertX
I read somewhere there's an older flasher program that will allow you to down-flash Asus BIOS. IIRC, it was version 1.6 something, but can't be sure anymore.
U have to use afudos via DOS.
U can download afudos from the ASUS-FTP.
ftp://ftp.asus.com.tw/pub/ASUS/mb/flash/Afudos238.zip
Anyone with BIOS 1406 and Asus TurboV working?
Mine allways say "Function is disable! To enable this function, please set CPU ratio to Auto in BIOS.", even with CPU ratio option set to "AUTO" in BIOS.
If i checked with CPU-Z 1.51, Latest Everest or in CoreTemp, i could see Turbo is working, but not in Asus TurboV! :mad: Asus....:slapass:
I'm using Asus TurboV 10016.
Hmmmm, I am still using 1306 with it working well. 3.64 at 100%load W/HT enabled w/good temps. I think I will skip 1406 for now.
No one had this "problem"? :confused:Quote:
Originally Posted by MFM
anyone has notice a discrepance on v-core rilevation during the load?
with llc enabled...
You have a very old version of TurboV.Quote:
Originally Posted by MFM
The last version is 10041 and it works even under Win7 64x.
You can find it on Asus ftp site (now it is down)
With LLC enabled my Vcore under load is some tenth of mV more than on idle.Quote:
Originally Posted by Andrea deluxe
I saw on the Rampage II Extreme support page, and there's only version v1.00.16! :(Quote:
Originally Posted by Brama
I've to find, and try that version!
Thx! :up:
I give up! :shrug::mad:
Anyone with this board and BIOS 1406, could please try Asus TurboV and see in "CPU Ratio" tab, if it's working?
Even with Asus TurboV 1.00.41, doesn't work! In the BIOS i've "CPU Ratio" on "AUTO", "Speedstep" "Enable", "Turbo mode" "Enable"...
Here's a pic with the error...
http://img38.imageshack.us/img38/890...10041error.jpg
ok, but everest show a very different v-core compared to cpu-z......Quote:
Originally Posted by Brama
try to reset the bios and re-tryQuote:
Originally Posted by MFM
Thx....but doesn't work! Maybe is better to forget this utility!Quote:
Originally Posted by Andrea deluxe
I can see on everest, cpu-z and coretemp that turbo is working... Might be a problem with this Asus TurboV and this new BIOS 1406! :shakes:
Hi, guys.
I've just put together my first gaming rig with an asus board, I had MSIs with nForce chipsets in past and that was just one big headache as for overclocking. I was aiming for 4ghz 24/7 overclock on my new I7 with the RIIE. When I tried my first overclock I couldn't believe what happened, I just set the core voltage to 1,25 dram to 1,65 and up the bclk to get just over 4ghz, everything else untouched and the very first oc seems to be rock solid...I ran Prime95 overnight, Intel burn test, played around with some games(crysis, cod4...), did some compressing, movies decoding, 3dmark benching...just about everything, just to be sure and it realy is 100% stable... Now, what's my problem? It's just to good and easy to be true.....I ask you - way more experienced guys to check my settings(temps,volts) and tell me if I have everything on the safe side, I don't want to burn the chip or board.... Also, would anyone help me how to get higher, should I just keep upping Vcore or is there some other important setting/feature I should enable/disable to have it right? One last question, why is my chips revision not showed in cpuz and realtemps, I was hopping to get the DO revision as after quick research i found out it's supposed to be the best for oc, the Intel processor identification utility says my chip is rev. F, but that didn't help me at all since I couldn't find any info about F revision at all...anyone, please? Btw this is a great thread and the RIIE is in my eyes the best man can get, I fell in love with it already....
first, update your cpu-z it's kinda outdated
for 4.2Ghz
bump vcore to 1.35v
set the qpi ( try 1.35v first)
it worked in mine, might as well yours, try it.
Thanks. I'm gonna try it right now. What about my temps. Are they ok to go higher?
Ok, Cpuz and coretemps updated now show D0 rev. but the intel processor ident. utility still shows F, any idea which is correct? Tried those volts @4,4, it looked fine but bluescreened after about 10 mins of prime95 and the temps were 75-78C. I'm gonna do some research and reading of this thread tommorow as I don't want to fry anything after only about 20hrs of playing with it. Anyways, would the settings, volts and temps on the above screenshots be ok for 24/7?
just stick to cpu-z, that's what every one using, or you could use everest.Quote:
Originally Posted by ifi444
for 4.4 it need more volts about 1.4xv from the looks of your chip.
what cooling you're using ?
i have find a new problem.....
i oc my cpu at 4ghz, and i am stable with 12 hours of linx with all the voltage manually set.
but if i plug off the current and i replug it, my pc is not more stable (only 15minutes of linx)....
it is super strange-......:-(
I'm on water. Tried 1,4v but the temps seemed too high (80-82)under load so I backed off to 4,2 @ 1,275Vcore, which I'll be happy with for now....running prime for about 3 hrs now and the temps are still below 70C.
Hi everyone. It looks like a new BIOS 1501 is about to come out, along with this OCing gadget.
Take a look http://www.theinquirer.net/inquirer/...rog-oc-station
Looks cool...Quote:
Originally Posted by Baer
WTF happened to my PC. I upgraded to the latest bios 1406 had it working all day the computer. Powered of at night in the morning booted gave me overclocking failed message so I entered bios and did a reset to auto setting, reset computer, now want boot at all. No screen what so ever no writing on screen just want start to display anything on monitor? Reset CMOS jumper nothing..I don't know what to do is it a dead CPU? The lights inside flash as normal I don't hear any beeps either really confused?
LCD Poster says LOCKED!!
I had issues with mine setting the wrong uncore multiplier if I left it on Auto. Setting it manually helped me regain 24/7 stability between reboots.