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

[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.

[bassplayer]

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?

[bassplayer]

Bump for an edit to the OP!

[Raja@ASUS]

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

[bassplayer]

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?!):

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:

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.

[brettjv]

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

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

[Leeghoofd]

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

[Raja@ASUS]

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.

[bassplayer]

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

[kpablo]

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

[Leeghoofd]

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

[bingo13]

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.

[bassplayer]

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.

[dejanbinladen]

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

[bassplayer]

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

[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

[Rubycon]

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!

[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

they will never see a cent from me


i also thank bassplayer for great research

[bassplayer]

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

ASUS EPIC FAIL

they will never see a cent from me


i also thank bassplayer for great research

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.

[dejanbinladen]

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

[dejanbinladen]

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

[havu2000]

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

[dejanbinladen]

i odesnt work with any bios just antoher processor

[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 ?

[dejanbinladen]

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