if i had change log it would be published in english. :) ex-gf is hungarian?
Printable View
I updated the Front page with the bios from the hungarien link. I will personally try it to confirm it works ok. i will post back with results.
Up to 226 bclk Dram @ 1.64 , QPI @ 1.41 here is Vantage run @ 226. Only other voltage I changed with was the CPU amplitude setting which is at 700v. Asus TurboV software gave out at 226 bclk:) CPU-Z
Any word on the new bios?
Yeah, what does this bios fix??
Coud someone with coldboot/ram issues try this on their other bios chip? Would like to know if those dumb asus techs have accidentally fixed something. :/
EDIT: Guys i may have found something! Try disabling Quick Boot from BIOS before you test that beta version and see if the coldboot problem still exists.
I'm on the new bios. No news on whats new. I've looked through the Asus forums and have'nt found anything on it. I'm not experiencing the cold boot but so i'm not for sure if it fixed it or not. I am now flashing back to 0704 as that's my fav bios so far. When Asus makes this one official or puts up a change log I will post it. But until then i'm flashing back. I just wanted to confirm that the bios was ok to use. Which it is. No new features that i notice. Probably some memory compatibility fix's.
What? So disabling quick boot eliminated the cold boot problem? Or are you just mistyping something...
So I know this is all a bit preliminary but I installed this 0901 BIOS and while I see no visible changes I noticed that my temps in real temp dropped significantly (about 5C-10C) compared to before and as I am typing this I am running a 100% load stress test on 4 cores/8 threads at 4.0GHz with 20x200MHz. All settings Auto except for memory profile X.M.P. Temps are maxing out at 76C on cores 1 and 2, 75C on cores 3 and 4. 12 minutes in right now...
:shocked:
Scratch everything I said. No difference going from 0804 to 0901. It was a fluke run.
http://www3.mediafire.com/imgbnc.php...986cf66a5g.jpg
Seems like a slow super pi, does it not
so is the 0901 BETA worth a try?
I can't say that I have any cold boot issues myself... Save, of course, the whole not booting at all incident. I have a feeling that was somehow my fault though.
It looks like you have the 9-9-9-24 latency Corsair kit, while people with the problem have the Dominator 8-8-8-24 latency kit. I have the Dominator kit running 8-8-8-24 1t and I never have this coldboot issue....I am thinking faulty boards maybe?? Has anyone just reduced the timings to 9-9-9-24 2t like the cheaper Corsair kit and seen if it stops the coldboot??
Tested with SS.., still having issues when I want more v-core above 1.5.., will not boot.., (boots on air though) have to raise v-core in vTurbo insted..
This superpi is overvolted just to c if it holds... rams are Corsair Dominator 1866.., bios 0705.., will test 0901
http://i44.tinypic.com/hv71qh.jpg
HMMM...... It boots with air? Sounds like the chips temp is too low when starting it on watercooling or more extreme cooling.....Are the aircooled people having the coldboot issue, or just those people watercooling??
Thanks for the response. Exactly the same as everyone else with the cold boot problem. Have to power cycle the PSU to get a boot. Did troubleshooting for a month (got the board when if first came out). Tried everything, and I've been messing with PCs since the IBM PC XT. The board is bundled up and on its way back to Newegg. No question. Defective.
Strange. i'm not sure what is causing this. Evidently Asus made a bad batch of some soft. I know i have the Corsair RAM kit and have had not sorts of problems with the cold boot issue. But we need to get a petition togather to send to asus if this is happenening more and more.
If there is a batch number associated with this board than we can get everyone's batch numbers togather.
Right now i'm looking at my box, and the Label has:
Serial Number-XXXXXXXXXXXX
Part No- 90-MIB6L0-G0AAY00Z
Check Number- 4436
EAN-4719543166185
UPC-610839166183 (should be the same for everyone)
Compare these number i have posted with the numbers on your box. The part No, may be the batch number associated with this board. If your Part No or any other number listed above besides the SN, is different, post on here your number and if you have the cold boot problem.
P/N EAN UPC all the same Check number is 4800
I do not have the boot problem.
I flashed the bios to 0804, and now I'm having a mild boot problem. The board cycles twice before it finally posts, and it takes forever. I think my old 680i board would already be loading windows by the time the r2e posts. Does it regardless of whether it is stock or ocd.
I'll let you guys know if my problem is gone after I receive the RMA board from Asus. It is supposed to arrive by Wednesday. It won't be easy to test it though as I only have the coold boot on maybe 15% of my overall boot attemps. For instance, my computer was off since 17:00 yesterday and I booted it fine this morning. Overclocking or stock makes no difference.
Part number is different than yours...it is 90-MIB6L0-G0AAY10Z
I got the board early too. One of the first boards to hit retail.
Serial Number-XXXXXXXXXXXX
Part No- 90-MIB6L0-G0AAY00Z
Check Number- 0745
EAN-4719543166185
UPC-610839166183
Again, I can't say that I have the cold boot issue. I've have had to power cycle, but I think it had to do with unstable OC settings.
Also, I have been running the newest BIOS as they are released. Currently on 0901.
Five days without the cold boot problem, and on the sixth day there it was again :shocked:. And i thought it was solved by turning the "DRAM Back-To-Back CAS# Delay" value to 4, apparently NOT!!! :shrug:
Only difference is now i'm on BIOS 0901 and running with HT on @ 3.6GHz, 4 hours Prime95 blend stable :up: Before was 3.8GHz with HT off, couldn't get it Prime95 stable with HT on! Constantly BSOD :down:
Serial Number- XXXXXXXXXXXX
Part No- 90-MIB6L0-G0EAY00Z
Check Number- 5700
EAN- 4719543166185
UPC- 610839166183
Made in China :clap:
i'm thinking the Check number may be the batch number. Like i said. I do not have the cold boot. But i'm on the 07 bios. In reality, The check number could be anything. It could be the Quality control Line the board went through to get certified as a good board. I'm emailing asus about this one.
Asus just release a new official 0805 Bios. Added support for DDR3 2000. It's up on the front page if any of you want it. Straight from Asus's FTP
It may be worth it to some of you who are experiencing the cold boot to give it a try.
I am having some slow boot and S3 sleep problems with my Gigabyte EX58 Extreme and was considering switching to this board . . . but until this cold boot issue gets addressed/resolved, looks like I'll stay put. Hope there's some good news sometime soon!
0805 (or for that matter 0901) do not fix the cold boot issue. Also, I cannot believe that they would release such a useless BIOS that is 0805. Added support for DDR3 2000? Yeah, that's exactly what we freaking need, more incompatible DRAM. Who gives a $#!^.
Bah :shakes:
My replacement board better work flawlessly.
How do you know so fast if the cold boot issue is still happening? With my board it takes 5 or 6 days (random) before i know :eek:
Test this one please, found on this thread from saaya http://www.xtremesystems.org/forums/....php?p=3387593
No LED all fans spinning,
If the Board powers on with all fans spinning and all LEDs running but the DEBUG display doesnt display any POST codes and nothing else happens, then the PWM probably cant get enough juice. Check if the 8Pin 12V plug and the 24Pin ATX PSU power plugs are plugged in properly, make sure they dont bend too much or haven a lose cable. Check another PSU if possible. If nothing helps, power off the mainboard, remove both BIOS chips and wait a few minutes, then put them back in and power the mainboard on again. Make sure the BIOS chips are seated the right way around, the marks on the chips should face downwards. Let us know if :up: or :down: THX
After updating the BOIS and while the computer is booting (shows cpu speed, sata drives etc) all I do it shut it down before windows starts to boot. Then I'll try to turn it back on, and poof... nothing. Then I verify this letting the computer boot up, once it's up I simply shut it down via the start menu. I have to admit though the rampage II extreme is consistent with not booting after it's shut down. Maybe it's an advanced feature. :ROTF: :clap:
I'm not sure what you want me to test. Please explain. Thanks.
After the computer is shut down and I try to turn it on, there is a brief flash, and the fans come on for <1 second. Then nothing........ If I hit the power button again, nothing happens, nada, if I turn the PSU off for 10 seconds and back on all is well.
Yes and yes. Checked, re-checked, only used the 4 pin power connector (because the other 4 were covered up), then I used the 8 pin connector, then I got my old 1000W PC Power & Cooling out of the attic, hooked it up, same thing......
Are the BOIS chips still removable? It's been a while since I removed one. Ok, let find my "tool" and I'm post the results. Thanks for trying to help. :)
This is the BOIS removal tool that I have. Can someone please verify if it will work with the new BOIS chips? Thanks.
http://img293.imageshack.us/img293/6115/biostooleu7.jpg
Um.. What kind of bios socket is there on R2E? That should work as long as it's a PLCC chip.
I'm thinking about RMA'ing my board because of the problem I had a few days/week ago. I am also thinking about selling it off because of the RMA process of my 4870x2. I sent it on the 8th, 2-day air, yet they are claiming the didnt receive it until the 16th. So, with 5-10 business days to RMA it, I won't have it until probably the 5th of January. that's almost a MONTH to replace a GPU. I'm really angry with them right now.
Heya all.
after I read the whole tread a couple of times trying to solve my own cold boot problem I suddenly realised that maybe my 12 GB Dominator 1600 Mhz got to much juice. I then sat the voltage to 1.55 and now im running strong on 0805 Bios with 12 GB 1603 mhz Dominator.
Just wanted to share my findings.
Hope it helps =)
I might be silly saying this but could the Cold Boot problem be an issue with grounding? I had a Foxconn board that would boot on carpet but not in a case.
Well, I got the RMA board today and...I am extremely disappointed. The RMA board has the QPI/DRAM voltage stuck at 1.46V, the little joystick is broken (goes right, but not always left), and the board seems to be older than my current board even though it was a retail replacement. Sending it back to Asus, they said they will send me another one instead. At least they are picking it up tomorrow and shipping it back at their own cost.
The RMA board was part 90-MIB6L0-G0AAY00Z and my original (now better working board) was part 90-MIB6L0-G0AAY10Z
I'm kind of losing hope for this board working good overall...
Well, unfortunately my window for replacement with the place I bought it from expired two weeks ago. I have no choice but to go with Asus now. However, if their next board turns out to be a POS I will have to keep the current board and send them back the replacement...
Same situation here. I am worried about RMA'ing the board and having them give me what's laying around too. I'm worried about my 4870x2 too.
This should not be how the process works. They *should* send you out the newest product comparable to what you purchased. It really doesn't affect their bottom line, and would keep customers coming back. But alas.
I still have a feeling that the overclocking limit has something to do with the memory. Im really thinking about going to the Dominator GT when they are released... Im curious to see if underclocking strong sticks would help.
That's a lot of money to pay for underclocking, but I guess it is worth a shot :)
In terms of the RMA, if they send me a dud again I will just ship it back to them and keep what I have. I do not have particularly serious problems with my board other than I have that cold boot issue, in some combinations DRAM channels disappear, and IOH voltage cannot be adjusted + a bunch of minor issues. I do hope my SLI works as I did not have an opportunity to try it yet cause that would be the game killer for me. If I run into SLI trouble on the X58 I'm going back to AMD.
I have run SLI in all 3 slots with no problems! I have 2 9800gx2's in quad sli and at first I had one in the top blue slot and one in the bottom white slot. I later put the second card in the second blue slot and it also worked just fine. What I am trying to figure out is why with TURBO on and HT on, my cpu will instantly back down to 4ghz from 4.2 ghz when I start prime95. With HT off this does not happen and the temps look fine. Is it related to the voltage? Does anyone else have this problem, as this is the only problem I am having....:(
Same thing here. Running 23 multiplier on the 940 with turbo on, turbo goes off as soon as I fire up Prime. There seem to be two states where the CPU clocks down, and this is what is being tripped. Unfortunately, I did not find a way to prevent this. Turning all throttling options does nothing.
Does it throttle down when you have HT off? Mine only happens when HT is on.....
Omg this is really a nightmare! Cant believe asus is doing this to you dejanh :(:(:( and skypx have you tried removing bios chips?
Since last week i'm playing around with a R2E setup. No cold boot issues whatsoever. The only strange thing is that with my setup i cant go over 14 gb/s bandwith by using Everest Ultimate. Sisoft gives my 27 gb/s mem bandwith. Seems my i7 920 does like to get to 200 bclk. The CPU is a 3837A507......
Attachment 91335
So far this setup seems allright:
20 * 201 bclk in bios
Turbo on
HTT off
All other CPU settings off
vcore 1.35 in bios
Vqpi 1.35 in bios
The rest on auto
Mem DDR1600 @ 8-8-8-24-1
LLC enabled
Full phase
All the other settings on auto
I think the R2E is overvolting the vcore and undervolting the vqpi. See the screenshot. I have set 1.35 vcore in the bios, i'm getting 1.39v. As for vqpi i have set 1.35 in bios and i'm getting 1.31v.........
Hmmmm, I will have to try your settings since I have similar components.....I did notice the board overvolts. 1.5v gives me 1.54v. I didn't check the dram/qpi voltage though, Everest is wrong on the voltages then....
Those of you who are experiencing there turbo mode turning off with prime.. well it's supposed to do that. Prime is putting all core's to 100%. Turbo mode only works on single threaded applications. It overclocks one core and shuts the other 3 down. Your board is performing just perfectly because this is the way intel designed turbo mode. If you run a single threaded app like SuperPi, You'll see that your Turbo mode will work every time because it's a single threaded app. (Unless you have manually set affinity to all cores in the process manager).
And as for the RMA. This is a standard practice with all motherboard manufacturer's. If you RMA your board, you most likely will get a refurbished one back as a replacement. Thats why if your within 30 days of buying the product, you should always RMA to the reseller such as newegg or tigerdirect. Biostar, Asus, EVGA, Gigabyte, all do the same thing. Send refurbs back.
@Bringerofdeath- When you switched your second GX2 from the bottom white slot to the second blue slot, Did you see a performance increase at all? The bottom white slot only runs at a max of 8X so I'm just wondering what kind of difference you saw.
Thanks
Oh, ok, but it only happens when HT is on....I noticed that one core completes tests faster than the other though. About the bottom slot, I saw almost no difference in 3dmark06 scores or my games. Maybe it's because it pci-e2.0 slot it isn't affected much, though I did see fitseries saying it was bottlenecking his 3 gtx260's compared to his 790i thats 3x16x pcie.
I can assure you that this is wrong. Turbo will run when using the CPU at 100% with all 8 threads. I will show it to you later with a screenshot. For me it is the temps that trigger turbo shut-off. Hit 85C and bam.
Also, the board I got was brand new, retail, but obviously something wrong with it. If you look closely you can tell nothing was ever screwed or plugged into it. It was new, but faulty.
Disable CPU TM in the bios and it will quite shutting your turbo down. Turbo is only on one core tho. Not all 4.
CPU-Z may tell you it is all four but it's just not reading it right.
Can't download bios 0805 :(
It's not CPU-Z, it's RealTemp reading it. It reads it correctly, believe me. I have double checked this with the creator of RealTemp. We even used a small test tool to check the multiplier and it stays in turbo. Disabling CPU TM does nothing to stop the Turbo from turning off, but you can try this yourself (or I can post another screenshot for you)
Anyway, here is a screenshot that is showing system load at 100% on all 8 threads with turbo still on. I can also do a test for you where I lock the multiplier at 22x and you will see the performance difference in Arena. What you are saying I heard as well, but in practice this is not the case. I do not know whether there is an incorrect implementation on this board, or in general, or the original information about turbo is wrong. Either way, turbo is sure running...
Good to know. i've seen a few people at the gigabyte forum have turbo stuck on, on all four cores. ME GONNA TRY haha
Sorry for two posts in a row, but this is important as I think I may have found a serious problem on the R2E. I will need your guys help to test this as well (I confirmed it on two R2E boards, different part numbers that are currently here with me). I'm using the same Corsair Dominator 1600MHz 1.65V DRAM on both boards.
Basically, here is the problem. QPI/DRAM voltage is incorrectly set in the BIOS leading to a whole host of problems that exhibit randomly such as missing memory channels (e.g., 2/4GB detected instead of 6GB), cold boots, stuck at LOCKED/DET DRAM, general system instability, etc.
1. If the CMOS defaults are set the system will boot fine and QPI/DRAM voltage will be set at roughly 1.12V.
2. If the X.M.P. profile is set, the QPI/DRAM voltage gets set in the BIOS at 1.35V. However, after saving settings the system will reboot and the voltage will measure 1.37V for a couple of seconds (normal, within spec) but a few seconds later it will get bumped to 1.46V (not normal, and out of spec completly). This may not happen on every reboot/system start. However, if the system is overclocked it happens on every boot basically. As I am typing this I am running 23x180MHz OC with memory at 1800MHz with 3.6GHz Uncore and 3.96GHz QPI. Below screenshot shows the settings however (done through BIOS, not this utility...I'm just showing TurboV so that I can show the settings). DMM is physically measuring 1.462V QPI/DRAM on the board (1.454V under load).
Edit: I guess I forgot to mention why I believe that this is related to the whole host of problems people are seeing...I have been measuring voltages every time when I experience instability and/or missing memory channels, and/or no boot/cold boots and I noticed that every time this happens QPI/DRAM voltage is out of spec completly and is stuck high at 1.46V even if it is manually set lower in the BIOS (1.35V in my case). This cannot be a coincidence. Also, I have confirmed this behavior with most of the problems (except cold boot, cannot run other R2E stable at all) with the two R2E boards that I have here. Again, the two boards are different part numbers.
We need to get people on both sides to confirm this please. If I am right those that are having issues will have QPI/DRAM running high and those that are not should have their QPI/DRAM running close to what it is set in the BIOS.
You have a multimeter dont you? hook up the Probe it leads to the board. Dont trust the bios or the software.
Are you noticing this only with the Memory set to XMP?
I have the Corsair 1600mhz Cas 8 Kit but i'm running custome settings. No particular profile. VTT is 1.36 on the multimeter.
I measured everything with a DMM. I mentioned it in the post above. So far all of my test have been with X.M.P. first and then OC, but I cannot see this making a difference. All X.M.P. does is set some timings and voltages. I will test without X.M.P. and post back as well. My current memory settings are as follows...
X.M.P. Profile #1 (only profile), OC to 1804MHz, 8-8-8-24-2T, 1.65V DRAM, 1.35V QPI/DRAM (measured high at 1.46V, boots okay for the first 5-10 seconds at 1.37V measured). Same thing happens at 1600MHz as well (default for X.M.P. profile). Error free in all memory stress tests.
In the meantime, you say you are measuring 1.36V, so I have a couple of questions.
1. What are you running your memory at (speed, voltages including QPI/DRAM)?
2. Are you using X.M.P. profile?
3. Do you experience missing memory channels?
4. Do you experience cold boot issues?
Well im running on manual settings, 1603 mhz and sat the timings at 8-8-8-24.
When i boot my system i get into windows and the system is rock solid! but when I shut the system down my fans would just spin a 1 sekund. Then i'll have to shut the psu off totally for about 10 sekunds. After that i boot just fine again.
Right now with my moderate overclock i'm at 4.2 with turbo and HT. CPU is set to 1.43v with the rest of the voltages set to auto except RAM.
1. Running my Ram Speeds at 1603mhz, 1.65v, 1.36v VTT, 8-8-8-20-1N
2. No, Overclock is set to Manuel
3. No, I have Triple Channel according to CPU-Z.
4. No I do not have the cold boot issue.
Why would you even want to load up the XMP Profile, What about the ROG profile? Does it do the same thing?
I've heard on the Asus forums people have been having luck lowering there Vdimm voltage to 1.55 instead of 1.65. Lay off of your OC'd RAM settings to test this theory out.
Run it all manuel. with 8-8-8-24-2N with 1.55v and see if the problem persist.
I've also heard of people reseating there VTT Card.
jason,
Since you don't have any issues can you tell me did you buy your board from the release batch or a later batch?
release batch. Got it from Tiger Direct. There first shipment. About 7 days after launch of the i7. I was waiting for someone to stock the corsair ram haha.. finally NCIXUS.com had about 5 kits back then and i scooped one of them up quickly. They even have that new 1866 Corsair stuff right now.
You got lucky then. It just seems that those who got these boards like last week or so don't have any issues.
The only time I've had a problem like you guys are explaining is when i have grounding issues with something. Something was Tripping my PSU over voltage protection like a short or something. My fans would spin up for half a sec and shut down. Most of the time that's indicative of a short somewhere. And maybe by you guys Power cycling your computer your resetting the PSU's Over-voltage protection. Thats the reason it's working when you power cycle your PSU. Have you guys tried switching your ram around to different slots. How about taking the motherboard out of the case completely and putting it on a anti static bag? I know it's a lot of trouble but it might be just what it takes to figure this thing out.
I know it's highley unlikley that all of you have a short but there's got to be something more going on here. What about Quick Boot? Disable it if you have'nt already
I've upped the 0805 BIOS to Rapidshare for anyone having trouble getting it from ftp.
:)Code:http://rapidshare.com/files/176181266/RampageII-ASUS-Extreme-0805.ROM
I believe that skypx already tried that quick boot disabling but didnt work.
And jason, do you think that this could still be related to ram? I'm beginning to believe that we are dealing with individuals. It's just probably bad luck that there are so many defective boards. I may be wrong tho. It could be immature bios. Who knows.
no cold boot problem, here is my batch number 90-MIB6L0-G0AAYOOZ
Well im still trying to figure out the right settings in Bios so the cold boot would go away.
90-MIB6L0-G0EAY00Z
are you sure about your part numbers? I have seen stores only selling the ones with -G0EAY00Z number
Well, I guess you were right. After I turned off the X.M.P. profile and did all of the OC settings manually the VTT does not crap out on me, or it has not done it yet. This is very (no wait, extremely) strange as X.M.P. sets the exact same settings as what I have entered in manually. It must not be doing the exact same thing then...it must be doing something else. I will keep you posted on the results as time goes a bit too. I am still running tests.
Now, after I did this I changed my OC settings to 20x200MHz flat, 1600MHz DRAM with 8-8-8-24-2T timings (default), 1.424V core voltage (high voltage chip unfortunately), but get this, I was able to lower the VTT to 1.3V (I can go lower, down to 1.25V - 1.27V but I do not want to), and DRAM voltage down to 1.5V (lowest available setting) :shocked:
So far 30mins stable with 4-cores/8-threads at 100% constant load...
Oh and temps, peak out at 75C on all cores on air. WTF? Must be the lower VTT (QPI/DRAM).
Something is majorly screwed up on this board. The more I use it the more confused I am. I'm thinking that it has major issues with DRAM now...not sure any more...maybe it is the low voltage DRAM parts that are problematic? It is the first time around these are being done...hmm :confused:
I've also noticed that all of you guys have the 90-MIB6L0-G0EAY00Z part. Asus sent me this part as an RMA as well and I found it way worse than my current board. However, my part is (get this) newer it seems and it is 90-MIB6L0-G0EAY10Z. I'm thinking maybe to stop my 2nd RMA now. I don't think there is a point. Maybe everything is working as intended and memory is the culprit for it all? I almost want to go pick up some Mushkin sticks (I never had problems with Mushkin in any board for 12 years) and see whether that changes anything...
Edit: Test crashed about 50 minutes in. I upped the voltage now to 1.432V on the core. This should be sufficient for 24/7.
Just messed up. That's all I have to say. I think I will get Asus to pick up the board now and tell them to send me an RMA only if they have a part number different than the two we listed here. Otherwise, I do not care to replace it now. Maybe when it's close to 1 year from now and all of the initial batches have gone through the system.
....anybody else having problems with xmp profiles etc......?