MaximusIV-Extreme Thread

[Leeghoofd]

my board is bricked anyway , will test tonite against UD7

[jcniest5]

here it is ... 3DMark'01 Bios for Asus Maximus IV Extreme, Maximus IV Extreme-Z and Maximus IV Gene-Z
let's get back to 3D01 guys
http://theoverclocker.it/ASUS3D01/3D01-BIOS.rar

Perhaps I missed something, but are these BIOSes specialized for 3DMark'01 only or something?

On this BIOS, my -Z displays the date very arkward...it consistently changes the day and year.

[Leeghoofd]

testing right now... keep you lads posted

SLI 01 1409 bios : 93483

SLI 01 1596 bios : 96847


wOOOOOOOOOOOOOOOOOOOOOOOOOOt

Plus subscores tab works now, no more workarounds !!!!

other runs were in the 96K range too.. 03 seems faster too

3D011596bios.png

3D031596bios.png

3D061596bios.png

[Sauron_Vie]

new beta bios 1850 for the MIVE

http://hwbot.org/forum/showthread.php?t=15952

[[XC] Synthetickiller]

I'm still on 1303, I'm behind the times.

Should I just skip to 1850 or just 1409?

I just ran 3dmark11 benches today! Damn, I'll have to update and try again!

[l0ud_sil3nc3]

I'm still on 1303, I'm behind the times.

Should I just skip to 1850 or just 1409?

I just ran 3dmark11 benches today! Damn, I'll have to update and try again!

if you want to bench 01 check out 1596 the bios that andreyang just posted, or else give 1850 a spin

[[XC] Synthetickiller]

Will do tomorrow.

[Leeghoofd]

Perhaps I missed something, but are these BIOSes specialized for 3DMark'01 only or something?

On this BIOS, my -Z displays the date very arkward...it consistently changes the day and year.

Benching only mate, try to login on MSN with 1st of january 2005 on MSN... it will not work

[GaBBa-Gandalf]

Does somebody know if you have also the boost in 3DM2k1 with the 1850 bios?

[Stelios]

No . You should use only 1596 and newer 1598 for 3d01 .

[kagula323]

New 3DMark2001 BIOS

Asus Maximus IV Extreme 1598
Asus Maximus IV-Extreme-Z 0498
Asus Maximus IV-Gene-Z 0498

Changelog:
Fix some bugs

Link: http://theoverclocker.it/ASUS3D01/3D01-1.rar

[[XC] Synthetickiller]

Tiny update.

Installed 1850 Beta. Scary! Updated the bios fine, but restarted 3 or 4 times there after talking about ROG connect update. It works though, so don't panic!

I went back, tried my original settings (basically everything on auto), 1.4v 49x100. Fine. Just attempted 50x100. I could barely get into windows. I was able this time to complete at least one round of Prime95 FFT before BSOD. I think I can tweak it now to get 5ghz actually stable (I hope).

There is an improvement over 1303, clearly!

[bro20000]

Will give 1850 a try!

[jcniest5]

Benching only mate, try to login on MSN with 1st of january 2005 on MSN... it will not work

Does the newest one have this date glitch fixed?

[kagula323]

Does the newest one have this date glitch fixed?

yes it has the date bug fixed .. install it and try it! enjoy!

[zeist]

Anybody had problems with raid on intel controller with bios 1409 and 1850?
With 1303 and previous everything works fine and smoothly.
With 1409 and 1850 if i enable raid on intel controller i'm unable to boot. If i try to install win7 i can create and format partitions but i can't install getting:"Windows cannot be installed on this disk. This computer's hardware may not supporting booting from this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu."
Switching back to ahci function restore complete disks functionality and theoretically i can install and boot OS.
I'm the only one that experienced this problem with the last two bios?

[Raja@ASUS]

Have you created that RAID array on the newer BIOSes?

-Raja

[GaBBa-Gandalf]

I also use a raid system (raid-0) and have no issues at all with the newer bioses...

[zeist]

Have you created that RAID array on the newer BIOSes?

-Raja

yes and no
The first volume (ssd raid0) has been recreated with new bios after secure erase
The second volume (HDs raid1) has been kept as is from previous bios.

Both result not bootable if i try to install win7, and by the way, i slammed in a fifth 1tb hard disk not in raid, win7 installation see it and allow me to partition and format, but again "not bootable".
If i switch back intel controller to ahci, every disk is seen and can be used to install win7.
Pretty much odd....

[Raja@ASUS]

yes and no
The first volume (ssd raid0) has been recreated with new bios after secure erase
The second volume (HDs raid1) has been kept as is from previous bios.

Both result not bootable if i try to install win7, and by the way, i slammed in a fifth 1tb hard disk not in raid, win7 installation see it and allow me to partition and format, but again "not bootable".
If i switch back intel controller to ahci, every disk is seen and can be used to install win7.
Pretty much odd....

Try removing the second RAID volume when you install Windows (if not done already). What BIOSes do you have flashed to both chips?

-Raja

[zeist]

Try removing the second RAID volume when you install Windows (if not done already). What BIOSes do you have flashed to both chips?

-Raja

Hi Raja
Already tried, i also tried to unplug both arrays and run the system with a single 1Tb disk alone, with controller configured as ahic i can install win. If controller is configured as raid i still see the disk, can partition and format it but i still get the "not bootable" error message.
Now i have 1850 on one rom and 1303 on the other one (1303 allowed me to install win7 and boot the system).

[Raja@ASUS]

Hi Raja
Already tried, i also tried to unplug both arrays and run the system with a single 1Tb disk alone, with controller configured as ahic i can install win. If controller is configured as raid i still see the disk, can partition and format it but i still get the "not bootable" error message.
Now i have 1850 on one rom and 1303 on the other one (1303 allowed me to install win7 and boot the system).

I am wondering if the ROM update between those two BIOSes is causing issues. When you change from one BIOS to the other do you get a few reboots with a ROM update message?


Only other thing is some of the RAID array meta data is still on the drives (which it should not be if you "broke" the array via the RAID ROM and also secure erased the drives).



-Raja

[zeist]

I am wondering if the ROM update between those two BIOSes is causing issues. When you change from one BIOS to the other do you get a few reboots with a ROM update message?


Only other thing is some of the RAID array meta data is still on the drives (which it should not be if you "broke" the array via the RAID ROM and also secure erased the drives).



-Raja

Yes, every time i switch i get a couple of reboot with asus rog connector updating himself "do not shutdown etc etc".
About to array metadata dunno... told you, even with both arrays unplugged, and i really mean plugged out from the case, even a single new disk get the "not bootable" error if controller is enabled as raid.

[deachus]

I am running a RAID 0 config with two SSD's and a single 2TB WD Cavier Black as a storage drive and everything is running great on 1850. All I did was flash bios, configured bios and rebooted.

[zeist]

I am running a RAID 0 config with two SSD's and a single 2TB WD Cavier Black as a storage drive and everything is running great on 1850. All I did was flash bios, configured bios and rebooted.

Well, though i found another couple of guys on asus forum with the same problem i figured out it's something pretty uncommon, otherwise this tread would have exploded a long time ago