Hi there
 
I updated my Marvell Controller BIOS. To the latest version. I think right from the beginning or just after installing Windows.
Everything did run fine and the performance in CrystalDiskMark was good (just did 1 or 2 mark runs i think).
But then (not doing anything special) i got the following Bluescreen in Windows:

INTERRUPT_EXCEPTION_NOT_HANDLED
0x0000003d
fffff880`03192000 00000000`00000000 00000000`00000000 fffff880`01093cc1 mv91xx.sys mv91xx.sys+30cc1         x64  

But after the reboot it continued to run without problems.
Then i began some CrystalDiskMark benches again and it crashed with the same BSOD about every second time.
So i think the problem was there from the beginning.
It just doesn't occur that often in windows, but about every second or third CDM run.
 
I tried the following things:
-Change SATA cable
-Change SATAIII Port (btw. the upper port has far worse performance lol, did you know that? at least on my board...)
 
But still the same.
I now flashed the BIOS back (of course with the two common errors: the one in the beginning and the header error, but nevertheless it flashed correctly).
Im now benching again with CDM and testing if i get the BSOD again.
Strange that the performance seems to be better on the old Firmware (on the lower Port again ofc).
 
Anyone had the similar issues with the Marvell Controller or the new BIOS?
 
Spec:
Classified 3
i7 950
CrucialRealSSD 128 (Firmware 2)
 
regards
 

It was mentioned in another thread, that EVGA is working on a BIOS aimed at improving Raid, The actual quote was they are working on a Raid rom, ( I know sounds like something from the shining , ) Not sure if it will address the Marvell defecinces, or not, I decided to just stick with the Black ports. But I dont like system crashes.

Here is what I ended up with on the Intel ports : 3(80G, X25M-G)

 

thanks for your reply.
like 4-5 CDM runs now with the old firmware without crashing.
i even tried to be annoying and opening other tools and surfing while the benchmark was running.
hoping i got i stable now with the old firmware...
sigh... i should just have bought an intel SSD and run on the intel port... but no i had to be cool and get a Marcell Sata 3 disk on the marvell port :/
 
anyway... any further infos or expiriences of other users contributing to the topic will be appreciated!

ok new infos..
the last few CDM runs which where stable where in a somewhat inconsistent state:
i had the old firmware but still the new driver, but in the device manager the Marvell thing had an exclemation mark, so it was not recogniced corretly anymore.
 
this is even more a hint that the marvell controller firmware is the problem and not the driver...
 
now i have the old driver installed, device is recogniced (in another category !?) and i am running some more CMD's.
 
hope it stays stable.
maybe this thread will be usefull to someone who has the same problem...

lol dude how many ssd's do you have in raid to get such a performance.
btw. i have my problems with just one crucial real ssd so no raid thing just normal ACHI one disk

looks like with the old firmware the latest driver did not recognice the drive anymore.
so it worked with the MS AHCI Driver.
 
But because i did not get rid of the Event Log Error
"The following boot-start or system-start driver(s) failed to load:
mv91xx"
 
I messed around with driver quite abit and ended up calling some ConsoleDrv.exe on CD which removed the eventlog error and once again installed a marvell driver (probably the old one which belongs to the original firmware).
 
after 3 CDM's run with this combo still no BSOD's.
Or to say it in other words: With the Old Firmware I m not able to crash it again. Maybe its the new firmware itself which causes the problem, or the new driver which seems to recognize the drive with the new firmware.
So it may be any of these or both :)
 

have had no issues with the new crucial FW, love it in fact, working awesome,
it was my understanding that the work evga is doing with the bios is an attempt to get their bios working with third party raid cards...ie  the raid rom