M5 1707 bioses

[Shamino]

http://www.mediafire.com/?28rhmf7drn7zutk

[AsterAstoria]

feniks wrote:
thanks Aster Astoria .... geeez, I hate BIOSes ranging from 1309 to 1604, they keep somehow half of OC settings even after reflash, CMOS reset and loading defaults ... had same problems always (including some settings revert to auto like c-states or digi+), I just haven't used raid0 on this board in past.

Same here. My experience has been that sometimes it locks the OC too. Reports 4.8 in UEFI and 4.6 from my old OC inWindows, but it takes the Volt increase if maual Volts set in BIOS. When I delidded it saw proc as new and wanted F1 so I did (Under 1309) went in and all OC settings were there Loaded defaults but it did not do it so when I saved settings and rebooted well that is when I got one OC in UEFI and old OC in Windows.

As far as OROM don't trust what you see in any of the older BIOSes you have since you have come down to them from higher ver. It could just be a bug. LIke the settings not holding bug. It may report one thing and you have another. This is the first board I have had the MVE that I just don't trust the BIOS and I have owned tons of boards. I see lots of different comps all day since I am in IT and fix everything so this stumps me.

I am very pleased that Asus has kept the updates coming. Some vendors do one or two revs and stop leaving us to find them elsewhere as unofficial versions. So we should praise them and encourage them to keep them coming until we are happy.

[feniks]

all true, same experience here with oc on older BIOSes. i'm an IT pro too, working with workstations and servers (and networks) in daylight and playing around with my own rig at night time, save for weekends like this one.

well, full CMOS reset didn't help. OROM stayed reported as 11.0.0.1339 in 704 (flashed it again, same thing). right now I have 1707 BIOS on both positions and same problem happens - raid0 gets broken and secondary disk thrown out to non-raid disk status whenever I flash BIOS (any).

since I have sort of mismatched firmware on SSDs (shouldn't be a problem according to mushkin tech), I decided to send the new SSD back and buy a pair of something else today, and test it with identical SSDs ... however, I have no idea what to do if that fails too! I don't even want to think about board RMA yet, still hoping there is a cure for that issue (in case it was happening on identical new SSDs too).

[pathfindercod]

I am running two samsung 840 pro's (256gb) in raid 0. Running the last bios release 16xx. Your issue happened after updating the the new 1707? I flashed form the bios my board came with to the the one im on now 16xx and everything went fine. Little nervous to try the 1707 now. Guess Ill go for it 🙂 Ill have to wait till I get back vacation coming up this week. If I flash and my system goes to crap I will not have a fun vacation thinking about my system at home.

[feniks]

well, i'm not convinced the problem is related to 1707, however it did happen on this BIOS first, but simply because i never used raid0 on ths board before.
for some reason raid0 gets broken every time I flash any bios, so it's either related to drives themselves or something about my board...

pathfindercod wrote:
I am running two samsung 840 pro's (256gb) in raid 0. Running the last bios release 16xx. Your issue happened after updating the the new 1707? I flashed form the bios my board came with to the the one im on now 16xx and everything went fine. Little nervous to try the 1707 now. Guess Ill go for it 🙂 Ill have to wait till I get back vacation coming up this week. If I flash and my system goes to crap I will not have a fun vacation thinking about my system at home.

[limitz]

I have had the secondary (port1) SSD not recognized as member in the raid array (BIOS 1604). It somehow broke but after some reboots and shutdowns it would be ok again - temporarily. *error occurred (0)* in red at 11.0.XXXX OROM. Then once back at Desktop, I check IRST Interface and it will show as port1 SSD in my array as "Status: Failed" and gives me the option to select "Normal" and I do, then I get "Status: Normal". Then next reboot/restart OROM shows all green without error. Pretty annoying, haha.
I am on modified 1707 + 12.5.xxxx OROM and so far I haven't had the same error yet as I previously mentioned.
I'm currently sitting on Intel RST driver 12.0.xxx as TRIM is passing through. Intel RST 12.5.xxx will not.

I used Trimcheck.exe and seems to work well.

[feniks]

hey buddy, today at work I encountered "error occured(0)" on one of our HP workstations (model Z210) with 10.5 OROM, it reported a failed RAID1 (mirror) and both drives (WD 1tb black) with this error. it got me really surprised. as I said I have never seen it before and I handled lots of raid arrays in my life.
after removing the drives from broken system, it came up that files were on them no problem (backed up most important stuff), but when I tried taking Acronis image of one of drives it failed with "Read Sector fail" eventually (bad drive). the other drive was good (took image no probs).

My understanding is, after googling a lot, that this error happens only when usually there is at least 1 bad drive in array (raid0) or may appear on both drives in raid1 config (bad sector being mirrored to other). the only other occurrence of this error was happening in past with old Intel Matrix Storage manager 7.6 which was also sometimes conflicting with some early apple itunes (LOL).

so buddy, most likely you have a bad SSD, good call on getting it RMA'd.

also, yeah Fernando (overclock.net) confirmed that IRST 12.5 driver doesn't pass TRIM commands to drives. IRST 12.0 does no problem.

EDIT:
I found a quirky SATA cable on port1 (secondary) ... replaced it and so far HDD RAID0 runs well (was lagging badly), perhaps thsi was my whole problem with SSD RAID0 LOL ... the simplest things can cause the biggest disasters 😉

limitz wrote:
I have had the secondary (port1) SSD not recognized as member in the raid array (BIOS 1604). It somehow broke but after some reboots and shutdowns it would be ok again - temporarily. *error occurred (0)* in red at 11.0.XXXX OROM. Then once back at Desktop, I check IRST Interface and it will show as port1 SSD in my array as "Status: Failed" and gives me the option to select "Normal" and I do, then I get "Status: Normal". Then next reboot/restart OROM shows all green without error. Pretty annoying, haha.
I am on modified 1707 + 12.5.xxxx OROM and so far I haven't had the same error yet as I previously mentioned.
I'm currently sitting on Intel RST driver 12.0.xxx as TRIM is passing through. Intel RST 12.5.xxx will not.

I used Trimcheck.exe and seems to work well.

[Buckster]

whats the best way to save bios setting when upgrading the bios - or is it just not possible ?

in the past on other motherboards its not been such a faff - but with ROG boards and the numerous pages and pages of settings ( a good thing - except when upgrading bios) and possibly a couple of "saved" profiles

to say its a right faff is an understatement

writing it out takes a number of pages of A4 !

you can't save to USB as you can only re-load back into the same bios version

am I missing something please ?

[nikosa43]

Buckster wrote:
whats the best way to save bios setting when upgrading the bios - or is it just not possible ?in the past on other motherboards its not been such a faff - but with ROG boards and the numerous pages and pages of settings ( a good thing - except when upgrading bios) and possibly a couple of "saved" profilesto say its a right faff is an understatementwriting it out takes a number of pages of A4 !you can't save to USB as you can only re-load back into the same bios versionam I missing something please ?

Best way to keep settings is to put a USB flash to the white ROG USB port and press F12 to any page of BIOS you are interested. After a few clicks you will have a nice collection of your BIOS images, stored to your stick 🙂

[feniks]

I have never seen such message like "error occurred in port(0)", when it was running it was running always, just very slow in sequential Read benchmark.
then always after a BIOS flash, it would reset the secondary (port1) disk to non-raid disk status and that was the end of raid0, can't fix it without resetting (and erasing at same time) the whole array and restoring volume from backup. later I tested it even without volume, just raid array configured in OROM (CTRL+I at bootup) and it was always getting broken after BIOS reflash or switch to another BIOS (MVE feature).

god, I'm having a bad day here LOL ... missed good promo on Samsung 840 Pro 256GB ($190/each), deal expired, so for now I am restoring my OS on a single SSD (old one), will be sending the new one back to newegg as defective - EDIT: holy crap! they do not allow return for a refund on SSD!

figured that I will borrow two of same hard drives from work (WD Black 1TB) and try the same trick with them in raid0, if that fails through BIOS reflash as well then my board is f**ked... still hoping it's just a bad SSD not liking ot run in raid0 or something ...

a question. does anybody have a link to some handy tool allowing for a full reflash of ASUS BIOS? it was a special tool, mentioned in some thread which I can't find now... would try that tomorrow ...

also a question, can you guys see OROM number change when you flash older BIOS (or different modded BIOS)? mine seems stuck on OROM 11.0.0.1339 no mater how old BIOS I use.

[Grymmie]

feniks wrote:

a question. does anybody have a link to some handy tool allowing for a full reflash of ASUS BIOS? it was a special tool, mentioned in some thread which I can't find now... would try that tomorrow ...

Its called FTK

http://hardforum.com/showthread.php?t=1726429

Regards,