You can try flashing both BIOSes to 1850 and see if that helps. If not submit an RMA request.Quote:
Originally Posted by zeist
-Raja
Printable View
You can try flashing both BIOSes to 1850 and see if that helps. If not submit an RMA request.Quote:
Originally Posted by zeist
-Raja
Gah... though it works perfectly with bioses previous 1409 it could be an hardware issue?Quote:
Originally Posted by Raja@ASUS
Ok, i'll try this evening, otherwise i'll have to submit an RMA and rip apart my just finished new water cooled rig :/
You got me thinking when you said you just finished your new watercooled rig. What case are you using? Does it have Hot Swap bays and backplane like the Corsair 800D? I had a problem with my Corsair 800D when I first installed my MIVE where it would not recognize my RAID 0 config. I ended up getting RMA'd a NEW version of the backplane and it then worked great. Just a suggestion.Quote:
Originally Posted by zeist
Oh, actually Corsair 800D is what i have. But thinking about it, both vertex 3 ssd are installed in the lower compartment and connected directly to the sata3 ports, and i've also tested everything with just them removing the other raid1 array that is connected through the backpanel. Thanks for the hint anyway deachus.Quote:
Originally Posted by deachus
Hmm, I guess not the problem then. If I connected both my SSD's directly to SATA ports on Board and bypassed backplane then I was fine which is how I discovered problems with backplane. Corsair sent me the new SATA3 compatible backplane which works great now on the Hot Swap bays with my RAID 0 array. I use the Intel SATA connectors on the Board though.
What leave me wonder is that the very same configuration works absolutely smoothly with bios 1303 and previous ones (also with impressive raid0 performances). With bios 1409, and 1850 and intel controlled configured as raid, without touching a single wire simply my disks are seens as "not bootable".Quote:
Originally Posted by deachus
This evening i'll try to reflash both bios with 1850. I also tried to load the latest IRST drivers during win installation but the issue persist.
Cool, try 1850 on both BIOS chips, and see what happens.Quote:
Originally Posted by zeist
-Raja
Bingo:
Flashing both bios didn't worked.
I disabled everything on "onboard devices" and suddenly win7 booted.
Then i started to enable stuff again and isolated the problem into "oprom" option of marvell controller, if this thing is enabled it completely bypass the intel controller in some freaking way and prevent me to boot or install anything.
Just to let you know the only thing i have on marvell controller is a plextor DVD reader/writer (i kept the other two intel sata2 port for another possible raid1 array in the future).
Still wondering exactly why happened this.
Anyway thanks to Raja and Deachus for the support
Update:
1850 is something unbelievable.
With 1303 i got 5ghz 100x50 with 1,515 or 1,520 vcore, tweaking vccio to 1,175, LLC 75% and VRM fixed 350
With 1850 i get 5ghz 100x50 with vcore (auto) 1,480, vccio auto, LCC 75%, VRM fixed 350, everything else auto, gskill 2133mhz 9 10 9 24 at 1,5v, stable with superpi, prime95 Linx and 3dmark vantage.
Not bad for a bios upgrade, not bad...
That's weird but I am glad you got it figured out. I haven't had a chance to retest LinX and Prime95 with 1850 but I am running 5Ghz right now at 1.48 also with no issues. Will do a Prime95 and LinX overnight and see if I can lower vcore.
Honestly i'm still perplexed. I'll tell you that also new bios resolved some stability issues (shuttering) that i was blaming on Vertex ssd.
Bios 1850 is smooth, stable and awesome, at least from my perspective. I still have to figure out how/why Marvell controller was causing such conflict with Intel one (and i also have to move my dvd recorder on one of the intel ports).
How to enable Offset Mode?
In the Digi+ VRM Section of BIOS, Phase Control needs to be set changed from Extreme to Standard, Optimized or Manual in order for Offset Mode to become available in the CPU Voltage menu.
-Raja
Tnx.
I have a question for Raja@asus,
I have not been able to use PCIex1 sata controllers on one of the PCIeX8/16. Is this a limitation of the board or is there any bios option that I can use to make it work?
I have a problem here, actually a friend of mine.
Every time he gets a time without touching the PC when he returns to play with it a PC is "freezing" (error AE), the M4E seems to not detect the SSD it uses, there to solve the problem he has to turn off the PSU and turn it back on, then the problem is solved. Does anyone have any idea what might be happening? Thank you!
By chance your friend ssd is OCZ?Quote:
Originally Posted by _AntLionBR_
It is. And a Vertex 3 120GB. A problem with that?Quote:
Originally Posted by zeist
Mhm, yes, i suggest you to give a look both and ocz forum as much as a couple of thread on xtremesystems too (if i remember well).Quote:
Originally Posted by _AntLionBR_
Fact is: i had the same problem, OCZ released a 2.09 firmware to fix the issue. For me the fix worked. Mind that to avoid further problems OCZ reccomend to secure erase, format, and reinstall everything on the disk after you upgraded firmware, and for what i can tell it's actually needed.
Thank you for answering. I'll tell him to update the firmware to see if it solves this problem. After I give a feedback here. Thanks again!Quote:
Originally Posted by zeist
Hot-plugging needs to be enable for the port the Vertex is connected to.Quote:
Originally Posted by _AntLionBR_
just flashed new bios into gene-z and blk + memory clocking has improved
voltage control is great:up:
tks shamino for havin a hand in this board:up:
only thing missin is faster boot
VTT in the Maximus IV Extreme is? - vccio?
Yes, VCC I/O voltage and VCCSA is the system agent voltage.Quote:
Originally Posted by lysyn123
Another possibility with AE is if you set the motherboard to have CPU PLL Overvoltage turned on and put it to sleep (which it sounds like it is idling to sleep) when it tried to return it can't give the right voltage apparently and fails to come back. My only solution was to disable pll overvoltage unless I was going for benchmarking OCs, otherwise I keep it at around 4.5 where it isn't needed.Quote:
Originally Posted by _AntLionBR_
Care to elaborate this? ? :) thanks!Quote:
Originally Posted by Raja@ASUS