Are You Having RIIIE Post Issues? (Possible Reason Inside)

Second EDIT: We may have found the issue. It seems to be an incompatibility with certain Intel chips. My batch is 3911A, Brettjv's batch is 3912B, and we've found a member on the Asus forum who's having this same issue with no other batch than 3911A!

So do I RMA the processor?

EDIT: I've linked Asus Tech Support to this thread to show that this is not just my issue. It's happening to others as well. Hopefully they can use the information contained within to fix it!

With my 920 I was having an issue where after restarting the board for any reason, it would no longer boot. Using the RC Poster, the board would hang on "CPU Initial" every time. The only way to get it to boot was to turn off the board, turn off the PSU, wait a second for the board to power down, then turn the PSU and board back on.

Incidentally, the "CPU Initial" hang also occurs when there is no processor installed at all. I know it's not my 920 as it works flawlessly in my Gigabyte board.

I received my RMA board from Asus and it has this issue as well.


I just wanted to see if anyone over here had this issue as well. Brettjv over at OCN had it and I wanted to see if it was common. His issues can be seen in this thread.




Note: I've tried BIOSes 0402, 0602, 0704, different memory, different video cards... everything. It's the board.

or a PSU incompatability ?

I have a Corsair HX1000 and Brett has an Enermax Revolution. Both are good power supplies are both are quite common.

I don't think that makes sense with the fact using my W3520 fixed the problem. It's like some BIOS error with my 920...

This was happening to me after the board was cold for 2-3 hours. When switching disks, (going from XP to Vista, etc.) It got to a point where I couldn't get rid of it and that was it for the night. Come back next day or night...board would fire up no probs, only to have it start all over again... Tried all kinds of things...checked mounting pressure, etc. kept checking for moisture, etc. but board was dry as a bone. AND tried various PSU's...Enermax 1250, Silverstone Strider 1500,etc. Finally got rid of Turbo V and problem seemed to go away. Now I just use the extra OC module. I know, pretty inconclusive results but it works for me.

Thanks GriZ. I thought this issue would turn up to be more common. Mine did this before it ever hit any extreme cooling.

I have similar issue with i7 920 and R3E on a ocz 600w psu. The board will power up for 1 or 2 seconds and and then power up before the monitor gets any signal. Forgot how I solved the problem. It happened once so far.

only during cold boot bug...

sorry i don't run air

Quote:

---

Originally Posted by Hondacity

only during cold boot bug...

sorry i don't run air

---

While the only time I can't boot was like this:

After a S3 sleep wake up, I found that my bclk dropped to 100mhz, so I decided to restart the computer. That's when I can't boot the mobo happened.

Happened to me twice IIRC. I think it was after to much messing with the BIOS, then loading stable profile with very different settings.
First time cutting of power and clearing CMOS solved it, but second time I found out it will power on if I hold power button for 2-3 seconds. Then I went in the BIOS just saved the same settings again and issue was gone.

Time to make some sort of logging lads :

Bios used :
RAM used (type : Speeds : timings : )
CPU : @ ( Bclock x ) & cooling used
GPU :
PSU :

Problem desciption : ( if possible also how to replicate the issue )

If possible screenshots of the bios settings or to fill in the Donmarkoni template :

Quote:

---

Target CPU Frequency 2666MHz
Target DRAM Frequency 1603MHz

LN2 Mode: Disabled***
QPI Loadline Calibration: Enabled***

Sync Mode [Enabled]
AI Overclock Tuner [Manual]
OC From CPU level Up [Auto]
CPU Ratio Setting [20.0]
CPU Turbo Power Limit [Disabled]

>CPU Configuration----------------------------
CPU Ratio Setting [20.0]
C1E Support [Enabled]
Hardware Prefetcher [Enabled]
Adjacent Cache Line Prefetcher [Enabled]
Intel(R) Virtualiyation Tech [Enabled]
CPU TM Function [Disabled]
Execute Disable Bit [Enabled]
Intel(R) HT Technology [Enabled]
Active Processor Cores [All]
A20M [Disabled]
Intel(R) SpeedStep(TM) Tech [Enabled]
Intel(R) C-STATE Tech [Enabled]
C State package limit setting [Auto]
----------------------------------------------

BCLK Frequency [133]
PCIE Frequency [100]
DRAM Frequency [1603]
UCLK Frequency [3209]
QPI Link Data Rate [AUTO]

Memory Configuration Protect [Disabled]

>DRAM Timing Control--------------------------
CAS# Latency 9 [9]
RAS# to CAS# Delay 9 [9]
RAS# PRE Time 9 [9]
RAS# ACT Time 24 [24]
RAS# to RAS# Delay 6 [AUTO]
REF Cycle Time 110 [110]
WRITE Recovery Time 15 [15]
READ to PRE Time 9 [9]
FOUR ACT WIN Time 31 [31]
Back-To-BackCAS# Delay 0 [Auto]

Timing Mode 1N [1N]
Round Trip Latency on CHA [AUTO]
Round Trip Latency on CHB [AUTO]
Round Trip Latency on CHC [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) 8 [Auto]
WRITE To WRITE Delay(DR) 8 [Auto]
WRITE To WRITE Delay(SR) 18 [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 [Full]
CPU Voltege OCP [Enabled]
CPU PWM Frequency [1000kHz]

Extreme OV [Disabled]
Extreme OC [Auto]

CPU Voltage 1.250 [1.25000]
CPU PLL Voltage 1.812 [Auto]
QPI/DRAM Core Voltage 1.350 [1.35000]
DRAM Bus Voltage 1.654 [Auto]

>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.244 [Auto]
IOH PCIE Voltage 1.508 [Auto]

ICH Voltage 1.111 [Auto]
ICH PCIE Voltage [Auto]

---------- Spread Spectrum Control -----------
CPU Spread Spectrum [Disabled]
DRAM Spread Spectrum [Disabled]

***on-board jumper dependant

---

Quote:

---

Originally Posted by donmarkoni

Happened to me twice IIRC. I think it was after to much messing with the BIOS, then loading stable profile with very different settings.
First time cutting of power and clearing CMOS solved it, but second time I found out it will power on if I hold power button for 2-3 seconds. Then I went in the BIOS just saved the same settings again and issue was gone.

---

I had exactly the same issue on the R2E. This was also the ONLY way I could fix it. It seemed to me to be an issue with changing straps, setting it once crashed the board, setting it a second time, after a 'failed OC boot', finished the strap change and it worked.

Nice to see the bug is still there. lol :down:

As this happens when I change anything in the BIOS, I don't think I need to fill out the template. Loading all stock settings and setting the fan warning not to come on would cause it not to post.

However, here's this stuff:

Bios used : 0402, 0602, 0704 Beta, 0704 Final
RAM used : OCZ Platinum DDR3 1600MHz 7-7-7 20 1T (any speed)
CPU : Intel Core i7 920 (any speed)
GPU : Sapphire Toxic 4890, Gigabyte 5450
PSU : Corsair HX1000

Quote:

---

Originally Posted by kup

I had exactly the same issue on the R2E. This was also the ONLY way I could fix it. It seemed to me to be an issue with changing straps (*1), setting it once crashed the board, setting it a second time, after a 'failed OC boot', finished the strap change and it worked.

Nice to see the bug is still there. (*2) lol :down:

---

(*1)Could be now connected to changing UnCore multi.

(*2)Yeah, it's like seeing an old friend.:rofl:

I am having trouble with my R3E. Other day I setup my hardware. BIOS 0402, Intel i7 930, Corsair Dominator GT 2000C7, nVidia GTX 285 and Enermax Revolution 1250. My cooling setup is Noctua NH-D14. Everything is on stock settings. When I had first boot everything was fine. I started installing Win XP to my hard drive when installation was on %29, motherboard restarted itself. Now it won't post, no screen, no sound. It hangs on "CPU Initial" state as shown on ROG Poster. Doesn't shutdown or reset. ROG Tweakit shows that 'Remote computer is locked".
CPU is working fine, I tested on other motherboard. I reseated CPU, RAMs and VGA. Nothing changed. The only thing that weird is HDD led light is steady on while no HDD is connected to motherboard. I am using mb on cardbox with anti-static bag underneath. To shutdown I have to unplug my PSU.

Bios used : 0402, 0704 Final
RAM used : Corsair Dominator GT 2000 C7
CPU : Intel Core i7 930
GPU : Leadtek GT6600, Zotac GTX 285
PSU : Enermax Revolution+ 1250W

GTi-6, you can get the board to boot by turning off the board, turning off your power supply, then waiting a bit and turning them both back on. You'll have to do this every time, though. I had trouble getting XP installed as the OS install needs to restart a few times and the board won't POST after the first time without going through the process I explained above, so I installed it with my Gigabyte board instead.

When power up my MB, it hangs and can't shutdown it with its own power button. HDD led light is on while no HDD is connected. It's a bit annoying.

Quote:

---

Originally Posted by GTi-6

When power up my MB, it hangs and can't shutdown it with its own power button. HDD led light is on while no HDD is connected. It's a bit annoying.

---

Even if you hold the power button?

Does your power supply have a master switch on it?

Even I hold power button, it doesn't shut off. Now I tried without CPU, it shutdown while holding power button.

Not a good idea : motherboard on anti static bag :(

Quote:

---

Originally Posted by Leeghoofd

Not a good idea : motherboard on anti static bag :(

---

Really?! I am not that experienced on building systems but my friend advised me to that way. Hopefully my new case will arrive on Thursday. I will give it a shot one more time.

the goal of the antistatic bag is to keep static outside the bag. Just go straight up motherboard box is fine.

BrettJV from OCN asked me to post this since since he's still waiting for his XS account to be activated:

Quote:

---

It would be great if people who stumble on this thread who are having a similar sounding problem could help us determine if we're all having the same issue, so we have ammunition to present to Asus, and can try to get something done about this.

Here's how you can check, and please report back your results:

1) With everything hooked up and ready, do either of the following:
a) Hold down the reset CMOS button (on the I/O panel near the top, it glows green I think) for about 10 seconds, or
b) Unplug or turn off (if there is a master switch) your psu, hold down the power button on your motherboard or case for 10 seconds, then replug/switch on your psu

2) Try to start up your machine. Does it POST now?

3) Now shut your PC down by holding down the power button or shutting down Windows, and

4) Try to restart.

Are you now right back where you started, with no Post, no video, fans spinning, and ROG Poster saying "CPU Initial"? If so, return to step one. Does it work this way every time?

If this is the case, then we have the same problem.

---

Not a good thing to be beta testers, guys. Hope a fix comes out soon.

Quote:

---

Originally Posted by jcniest5

Not a good thing to be beta testers, guys. Hope a fix comes out soon.

---

I signed up to get the R3E, set to tear down WRs! :up:




And then they made me a beta tester :(

every overclocker is a beta tester :p there's no perfect board, each one has issues...

But your board's behaviour is weird... I have a no post sometimes, but this only happens when I push things to hard or volts are not correctly set... all I have to do is press the reset button on the ase and she fires straight up again... I adjust the setings and she spins happily again...

Have had cpu init many times after changing mems/hdd/gfx etc. Now when i hook up something new i start with cmos clear, choose profile again and then boot. Helps a lot here.

Quote:

---

Originally Posted by Viss

Have had cpu init many times after changing mems/hdd/gfx etc. Now when i hook up something new i start with cmos clear, choose profile again and then boot. Helps a lot here.

---

But you don't have to do it every time you go into the BIOS, do you?

Bump for an edit to the OP!

Quote:

---

Originally Posted by bassplayer

Second EDIT: We may have found the issue. It seems to be an incompatibility with certain Intel chips. My batch is 3911A, Brettjv's batch is 3912B, and we've found a member on the Asus forum who's having this same issue with no other batch than 3911A!

So do I RMA the processor?

EDIT: I've linked Asus Tech Support to this thread to show that this is not just my issue. It's happening to others as well. Hopefully they can use the information contained within to fix it!

With my 920 I was having an issue where after restarting the board for any reason, it would no longer boot. Using the RC Poster, the board would hang on "CPU Initial" every time. The only way to get it to boot was to turn off the board, turn off the PSU, wait a second for the board to power down, then turn the PSU and board back on.

Incidentally, the "CPU Initial" hang also occurs when there is no processor installed at all. I know it's not my 920 as it works flawlessly in my Gigabyte board.

I received my RMA board from Asus and it has this issue as well.


I just wanted to see if anyone over here had this issue as well. Brettjv over at OCN had it and I wanted to see if it was common. His issues can be seen in this thread.




Note: I've tried BIOSes 0402, 0602, 0704, different memory, different video cards... everything. It's the board.

---

Which Gigabyte board do you have that the chip works fine in? If I recall correctly, some early Gigabyte X58 boards apply a high voltage to VTT power good (VTTPWRGOOD) and this deteriorates CPUs to the extent where they will no longer POST properly when returned to a board that applies VTT power good at Intel specification (I believe this has been fixed on later boards). This happened to a few people last year - I wonder if you are experiencing the same thing.


Later
Raja

It is a Gigabyte GA-EX58-UD4P.

Brettjv got his second, brand new RIIIE today and it did not work. However, it seems he ran his old processor on a UD4P as well...


Here's Brettjv's post on OCN (can a mod please approve him here?!):

Quote:

---

I wouldn't kid you.

Not to beat my own drum, but ... my deductive skills are pretty well honed when it comes to PC's

And so my 2nd, brand-new RIIIE is in place ...

And ...



Oh, BTW ... I didn't end up grabbing the 930 chip at Fry's, cuz I wanted to get home and try this baby.

And ...



As I strongly suspected ...

Same Problem.

So, let's recount the situation:

brettjv: Has tried 2 brand-new RIIIE boards with his batch#3912 processor, which works fine in two other motherboards, but not in EITHER RIIIE he's received.

xxBassPlayerxx: Has tried 2 open-box RIIIE boards with his batch#3911 processor, which works fine in one other motherboard, but not in either RIIIE board he's received. However, switching to a different batch Xeon-equivalent processor, works perfectly in the 2nd board (did it also work in the first board, BP, or did you not have it yet then)?

Note: it's confirmed that the same temporary fix to the problem (i.e. draining the mobo of all power) works identically in both the above cases.

MGS (on Asus forums): Has tried 1 new RIIIE board with his batch 3911 processor, which works fine in another motherboard, but not in the RIIIE board. However, switching to a 930 processor works perfectly in his RIIIE board.

Note: it's not yet confirmed that the same temporary fix to the problem (i.e. draining the mobo of all power) works identically in the above case.

I'd have to say this shapes up as an extremely compelling case that the RIIIE mobo is not properly compatible with batch #3911 and #3912 processors (and perhaps others).

It sure would be great if Redwoodz would add to our survey. I PM'ed him last night.

---

And his reply to Raju:

Quote:

---

BTW ... addressing the question from Raju:
1) I dunno what your previous GB board was, but mine was a UD4P,
2) My proc works fine in my Classified,
3) This supposition of his, while certainly interesting, esp. if we find out that MGS also ran his on a Gigabyte board ... certainly doesn't explain the odd coincidence that we all three have batch number chips so close to one another. The odds of us 'finding each other' in this way, if this problem was in fact due to us 3 previously running our chips on GB boards, and discovering that we all three have chips of batches 3911 and 3912 ... are statistically pretty low.

I'm leaning against this being the issue, but ... I'll inquire with MGS whether he's run this chip on a GB board. If he has, it becomes interesting.

---

Just an FYI ... I replaced my processor with a new 930, and the issue went away.

Thanks to Raju for the heads-up, I believe his suggested cause was correct, and that the old GB boards we ran our chips on prior to the RIIIE damaged them in such a way that they do not work on the new board. That was KEY advice, because I'd have NEVER thought to check something like that as a possible cause. But as it turned out, sure enough, all 3 people I found (counting myself and bp) with these symptoms had in fact used our chips on old GB boards (circa X58 release) like the UD4P :clap:

Thanks also to BP for his help on this issue. It's always a lot less frustrating when you are not the only one trying to solve a bug like this :clap:

mmm wonder what damage was done then, the bad CPU still works fine on the UD4P ?

Quote:

---

Originally Posted by Leeghoofd

mmm wonder what damage was done then, the bad CPU still works fine on the UD4P ?

---

VTTPWRGOOD needs to be excessively high for the chips to POST.

I've RMA'd my 920. The new one should be arriving soon.

So... the guilty was the old Gigabyte mobo?

Question : does the CPU always boot with higher QPI volts then on the REX III ?

Quote:

---

Originally Posted by Leeghoofd

Question : does the CPU always boot with higher QPI volts then on the REX III ?

---

Yes. In my previous life this problem was reported and fixed in later BIOS and board revisions from the other guys. Certain chip manufacturers were not too happy about it either. ;) There was a reason why we were constantly harping on the "High VTT is bad" bandwagon and this was one of the many reasons why based on internal testing.

Quote:

---

Originally Posted by bingo13

Yes. In my previous life this problem was reported and fixed in later BIOS and board revisions from the other guys. Certain chip manufacturers were not too happy about it either. ;) There was a reason why we were constantly harping on the "High VTT is bad" bandwagon and this was one of the many reasons why based on internal testing.

---

I wish I didn't have to RMA my RIIIE first to figure this out!

You guys need to get this through to the telephone tech support people! I even told him the chip worked fine on my UD4P!

Oh well. New chip from Intel should be shipping today or tomorrow.

man io just found this post after 72 hours of suffering, i tryed everything except the cpu
cant fricking believe this :banana::banana::banana::banana:

I hope it helped you solve the issue. Did you use and EX58 series Gigabyte board before the new board?

i used ud3r,rampage 2 gene and p6t6 ws without any problems, just got this board and hell began, tomorow i try 920 batch 385xxxx so i let you know

I had this issue and it was driving me crazy!

I found that enabling the LN2 mode (jumper - see diagram below where this is located) fixed this problem for me once and for all!

I don't know what it is doing on the board and it does not affect my stability in any way. It's nice that it works now and I don't have to turn off the power supply and/or clear CMOS on a restart!

http://i157.photobucket.com/albums/t...g?t=1284092819

Quote:

---

Originally Posted by dejanbinladen

i used ud3r,rampage 2 gene and p6t6 ws without any problems, just got this board and hell began, tomorow i try 920 batch 385xxxx so i let you know

---

its CONFIRMED rampage 3 extreme doesnt work with 920 batch 391xxxxx just tryed batch 385 and it works like a charm

ASUS EPIC FAIL :cord:

they will never see a cent from me


i also thank bassplayer for great research :up:

Quote:

---

Originally Posted by dejanbinladen

its CONFIRMED rampage 3 extreme doesnt work with 920 batch 391xxxxx just tryed batch 385 and it works like a charm

ASUS EPIC FAIL :cord:

they will never see a cent from me


i also thank bassplayer for great research :up:

---

How long did you use the UD3R for? As I said earlier, the Gigabyte board basically destroys processors. I think the batch thing is just a coincidence while the Gigabyte boards are the problem.

few months but after that i used rampage 2 gene and p6t6 revolution for ery long time without a single problem

any news on bios fix for this stupid bug ???

Quote:

---

Originally Posted by dejanbinladen

any news on bios fix for this stupid bug ???

---

you use bios 1004
- RTL 53-54-55 or 62-64-67
enable jumps QPI onboard
good luck :)

i odesnt work with any bios just antoher processor

So the CPU is the issue ? not ? If another similar type CPU works on the board, then there's nothing wrong with the board... sounds logic to me... doesn't booting with higher QPI voltage not help ? The newer generation got some stuff altered compared to the first generation X58 boards...

So none of the above works for you ?

Quote:

---

Originally Posted by Leeghoofd

So the CPU is the issue ? not ? If another similar type CPU works on the board, then there's nothing wrong with the board... sounds logic to me... doesn't booting with higher QPI voltage not help ? The newer generation got some stuff altered compared to the first generation X58 boards...

So none of the above works for you ?

---

procesor is rock stable even highly overclocked, just when you shut down the pc you cant turn it on again if psu wasnt turned off first (same with altering something in bios when board does hard restart then no post again)... processor works great on other boards

I already made a thread about my problems with an i7 950 chip and computer not starting up. But I noticed there's problems with these boards. I have tried my new i7 950 with both Rampage 3 Gene & Rampage 3 Extreme both won't come to life with my curent setup. Not even managing to spin up fans on the boxed cooler...nothing.

Could I have a "bad" batch CPU that just doesn't want to work with the Asus boards ? I know it's not the CPU since it's been ckecked ok, my PSU runs my old 775 system with no problems, and I don't think my Corsair memory could cause a total lock down like this, board should power up even without RAM installed right ?

*end of threadjack*

I am really beginning to fade into desperation, and don't want to pour more money into fixing the issue ie another board or CPU. :(

ok to bump this thread again, after two 920, i got 950 (bacth starting 390xxxxx) and the same problem as with my first 920 qled shines and nothing until i switch off the psu...

and to see asus didnt respond to this thread in any sense makes me puke :censored:

asus slaping me :cord: