Ongoing BSODs, Marvell driver (reports attchd)

[rcanino]

Thank you very much for your assistance. I appreciate it so much. BSODs =

I built this system 7 months ago in Oct. 2010. Since then I've experienced 25 BSODs, all coming shortly after boot. BlueScreenView lists mv91xx.sys as responsible for 20 of them.

I am using one of the Marvell SATA III ports for my boot drive, which is a SATA III SSD, on the MSI Big Bang XPower X58.

I am running the current BIOS (AMI 1.6) and the current Marvell driver, both downloaded from MSI's website.

Also, I cannot update to SP 1. Tried twice, "sqmapi.dll missing" - ran sfc / scannow and it either finds no corrupt files or it fixes them. Update still won't complete.

I have run memtest86 twice - last month and back in Dec. '10. Both times for ~15 hours, no errors reported either time.

I am willing to change ports to one of the Intel and forget about Marvell's wonderful (!) SATA III. I am not sure how risky that is though; does that mean reloading my entire C:\ drive?

Thank you for your kind attention.
-Richard

Win7 Pro 64-bit (retail); one install in Oct. 2010, updated regularly. All hardware new in Oct. 2010 except:
1 160GB internal HDD (not boot)
2 USB HDDs
CD/DVD burner (Sony DRX-840U)

 

[usasma]

There are basically 4 reasons for BSOD's:
- 3rd party drivers
- hardware issues
- incompatibilities
- Windows

You've taken steps to fix the storage drivers and Windows - this leaves hardware issues and incompatibilities.
Now, add to this the fact that most issues with updating to SP1 are caused by malware or outdated drivers.

SSD is a Crucial RealSSD 128GB? Have you checked for firmware upgrades here: Crucial.com Product Downloads - Firmware Updates

CAVEAT - I have no experience with this website or the drivers offered there:

Marvell drivers

Near the bottom of the page you'll see:

Marvell MV-91xx (88SE91xx) Ahci/Raid Controller

(PCI\VEN_1B4B&DEV_90xx&CC_ & PCI\VEN_1B4B&DEV_91xx&CC_)
Driver Package dated 07/03/11 - mv91xx.sys DATED 02/14/2011

Have you installed/used the utilities for the Marvell controller available on the MSI website?
http://www.msi.com/product/mb/Big-Bang-XPower.html#?div=Driver

I wouldn't think that changing to the Intel ports would require a complete reinstall (but Startup Repair may be necessary if the Intel SATA/RAID drivers aren't loading (I think they are loading as they are evident in MSINFO32 and aren't marked as having problems).

Good luck!

Also, please do the following:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

[font=lucida console]
mv91xx.sys           Wed Jun 30 21:55:14 2010 (4C2BF582)
mvxxmm.sys           Wed Jun 30 21:54:57 2010 (4C2BF571)
amdxata.sys          Tue May 19 13:56:59 2009 (4A12F2EB)
[Color=Red]PxHlpa64.sys         Mon Dec 10 18:49:01 2007 (475DD06D)[/Color]
dump_mvxxmm.sys      Wed Jun 30 21:54:57 2010 (4C2BF571)
nvoclk64.sys         Tue Sep 15 17:59:25 2009 (4AB00E3D)
[Color=Red]wacommousefilter.sys Fri Feb 16 13:12:17 2007 (45D5F401)[/Color]
nvhda64v.sys         Thu Mar 03 10:59:02 2011 (4D6FBAC6)
RTKVHD64.sys         Tue Jul 06 06:05:16 2010 (4C32FFDC)
MBfilt64.sys         Thu Jul 30 23:40:32 2009 (4A7267B0)
dump_scsiport.sys    Mon Jul 12 23:32:05 2010 (4C3BDE35)
dump_mv91xx.sys      Wed Jun 30 21:55:14 2010 (4C2BF582)
wacmoumonitor.sys    Tue Sep 07 18:38:45 2010 (4C86BEF5)
LHidFilt.Sys         Tue Aug 24 13:21:36 2010 (4C73FFA0)
LMouFilt.Sys         Tue Aug 24 13:21:43 2010 (4C73FFA7)
adfs.SYS             Mon Nov 03 11:48:14 2008 (490F2B4E)
UltraMonUtility.sys  Thu Nov 13 20:10:30 2008 (491CD006)
nusb3hub.sys         Thu Dec 09 23:50:35 2010 (4D01B19B)
cpuz135_x64.sys      Tue Nov 09 08:33:36 2010 (4CD94DB0)
Rt64win7.sys         Wed Dec 29 06:44:36 2010 (4D1B1F24)
nusb3xhc.sys         Thu Dec 09 23:50:35 2010 (4D01B19B)
wacomvhid.sys        Mon Sep 21 19:29:14 2009 (4AB80C4A)
aswRdr.SYS           Wed Feb 23 09:55:11 2011 (4D651FCF)
aswFsBlk.SYS         Wed Feb 23 09:54:56 2011 (4D651FC0)
aswSnx.SYS           Wed Feb 23 09:56:59 2011 (4D65203B)
nvhda64v.sys         Thu Nov 11 18:10:36 2010 (4CDC77EC)
WinRing0x64.sys      Sat Jul 26 09:29:37 2008 (488B26C1)
aswMonFlt.sys        Thu Jan 13 03:37:21 2011 (4D2EB9C1)
aswTdi.SYS           Thu Jan 13 03:40:19 2011 (4D2EBA73)
aswSP.SYS            Thu Jan 13 03:41:42 2011 (4D2EBAC6)
nvBridge.kmd         Fri Jan 07 20:57:22 2011 (4D27C482)
[/font]

http://www.carrona.org/dvrref.html#mv91xx.sys
http://www.carrona.org/dvrref.html#mvxxmm.sys
http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#PxHlpa64.sys
http://www.carrona.org/dvrref.html#nvoclk64.sys
http://www.carrona.org/dvrref.html#wacommousefilter.sys
http://www.carrona.org/dvrref.html#nvhda64v.sys
http://www.carrona.org/dvrref.html#RTKVHD64.sys
http://www.carrona.org/dvrref.html#LHidFilt.Sys
http://www.carrona.org/dvrref.html#LMouFilt.Sys
http://www.carrona.org/dvrref.html#adfs.SYS
http://www.carrona.org/dvrref.html#UltraMonUtility.sys
http://www.carrona.org/dvrref.html#nusb3hub.sys
http://www.carrona.org/dvrref.html#cpuz135_x64.sys
http://www.carrona.org/dvrref.html#Rt64win7.sys
http://www.carrona.org/dvrref.html#nusb3xhc.sys
http://www.carrona.org/dvrref.html#wacomvhid.sys
http://www.carrona.org/dvrref.html#aswRdr.SYS
http://www.carrona.org/dvrref.html#aswFsBlk.SYS
http://www.carrona.org/dvrref.html#aswSnx.SYS
http://www.carrona.org/dvrref.html#nvhda64v.sys
http://www.carrona.org/dvrref.html#WinRing0x64.sys
http://www.carrona.org/dvrref.html#aswMonFlt.sys
http://www.carrona.org/dvrref.html#aswTdi.SYS
http://www.carrona.org/dvrref.html#aswSP.SYS
http://www.carrona.org/dvrref.html#nvBridge.kmd

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Apr 23 07:52:57.251 2011 (UTC - 4:00)
System Uptime: 3 days 7:05:35.048
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+2f3e7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+2f3e7
Bugcheck code 0000003D
Arguments fffff880`030b0090 00000000`00000000 00000000`00000000 fffff880`010433e7
BiosVersion = V1.6
BiosReleaseDate = 03/29/2011
CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3329
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Apr 19 22:38:22.891 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:42.388
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+30cc1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+30cc1
Bugcheck code 0000003D
Arguments fffff880`032e80f0 00000000`00000000 00000000`00000000 fffff880`01100cc1
BiosVersion = V1.3
BiosReleaseDate = 08/20/2010
CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3329
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Apr 19 22:34:20.379 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:27.488
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+30cc1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+30cc1
Bugcheck code 0000003D
Arguments fffff880`032e80f0 00000000`00000000 00000000`00000000 fffff880`01038cc1
BiosVersion = V1.3
BiosReleaseDate = 08/20/2010
CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3329
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Apr 19 10:32:18.791 2011 (UTC - 4:00)
System Uptime: 0 days 16:33:11.855
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+2f3e7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+2f3e7
Bugcheck code 0000003D
Arguments fffff880`032e8090 00000000`00000000 00000000`00000000 fffff880`010933e7
BiosVersion = V1.3
BiosReleaseDate = 08/20/2010
CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3329
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Apr 14 14:23:38.997 2011 (UTC - 4:00)
System Uptime: 0 days 0:19:38.509
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+30cc1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+30cc1
Bugcheck code 0000003D
Arguments fffff880`032e80f0 00000000`00000000 00000000`00000000 fffff880`01129cc1
BiosVersion = V1.3
BiosReleaseDate = 08/20/2010
CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3329
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Apr 14 09:49:25.837 2011 (UTC - 4:00)
System Uptime: 0 days 0:04:42.945
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+30cc1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+30cc1
Bugcheck code 0000003D
Arguments fffff880`032e80f0 00000000`00000000 00000000`00000000 fffff880`01100cc1
BiosVersion = V1.3
BiosReleaseDate = 08/20/2010
CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3329
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Apr 14 09:41:28.026 2011 (UTC - 4:00)
System Uptime: 0 days 20:26:36.135
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+2f3e7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+2f3e7
Bugcheck code 0000003D
Arguments fffff880`032e8090 00000000`00000000 00000000`00000000 fffff880`0110f3e7
BiosVersion = V1.3
BiosReleaseDate = 08/20/2010
CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3329
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Apr  4 09:06:19.163 2011 (UTC - 4:00)
System Uptime: 0 days 20:26:51.256
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+2f3e7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+2f3e7
Bugcheck code 0000003D
Arguments fffff880`032e8090 00000000`00000000 00000000`00000000 fffff880`0106f3e7
BiosVersion = V1.3
BiosReleaseDate = 08/20/2010
CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3329
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr  3 12:36:54.769 2011 (UTC - 4:00)
System Uptime: 13 days 17:26:14.862
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+2f3e7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+2f3e7
Bugcheck code 0000003D
Arguments fffff880`032e8090 00000000`00000000 00000000`00000000 fffff880`010813e7
BiosVersion = V1.3
BiosReleaseDate = 08/20/2010
CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
MaxSpeed:     3330
CurrentSpeed: 3329
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[rcanino]

Thank you for your reply U-

I've resisted updating the FW on the RealSSD because it (as I understand it) requires a complete reformat - or at the least it clears all the data. So no, I haven't updated the FW.

I have installed everything from the MSI download site for my board. All my drivers and updates have come from there except the NVIDIA stuff, which I get from their site.

I'm not sure if this answers the question of "if the Intel SATA/RAID drivers aren't loading" but if you're referring to the Intel ports, I do run 2 other HDDs on the SATA II ports and they work fine.

I'm not sure I have a sense of which way to go now. From your post it doesn't sound good for the Marvell port. I either take my chance with the updates on that "station-drivers" site, which is all in French, or I switch to a SATA 3Gb/s port and take a (pretty big) performance hit...

I've posted on the MSI forums and perhaps will receive some help there as well, but so far the answer has been nearly identical to yours - "never heard of station-drivers; try the Intel ports you *probably* won't lose your data."

Yipes, not very reassuring!

Can you tell me - is there a risk in just leaving it alone, dealing with BSOD every so often? I think I've figured something out, which is - if I don't start any resource-hungry apps until after the background services are loaded the machine doesn't crash. It could just be coincidence but...that's the best I've got right now.

Thanks again for your reply, I do appreciate it!

 

[rcanino]

Whoops - sorry, didn't see the scrollable window at first.

So okay, let me get to work on updating those drivers and then I'll post back.

unfortunately the Marvell site doesn't even list the 88SExx in its parts list. There is a "sell sheet" .pdf about the controller but nothing else I could find....

 

[usasma]

You're gonna have to dig down deep and take a chance (IMO):

Plug the drive into the Intel ports and see if it boots.
Don't change anything when booting.
If it doesn't boot, then plug it back into the Marvell ports to see if it still boots there.

FWIW - I haven't used the Marvell ports on any of my mobo's over the years. No solid reason for this other than "I like Intel". BUT, I've noted problems in another thread with an Intel SSD and a mobo w/Intel chipset.

No risk AFAIK in leaving it as is - but once again, the SSD technology is too new for me to say for certain.
Worst case would be an issue with the SSD - all other parts should be OK.
Make sure that you keep a good backup on hand - because each BSOD will increase the chance that you will lose your data (if the SSD is hosed).

Good luck!

 

[rcanino]

Yeah I hear ya, take a chance and see what happens.

I may go about things this way - if you would tell me what you think:

1) Update whatever drivers I can - the Wacom tablet, whatever else

2) Update the Firmware to the Crucial RealSSD. They've got a .ISO procedure mapped out on their site, seems easy enough.

#3 is tricky because I have a choice, both are risky. Either I try the newer Marvell driver on Station-Drivers: le site de drivers, bios, firmwares avec un forum d'aide without totally trusting that site (and as you see it's in French only too ) - or I change ports and try to certify that it is the Marvell port causing the problem.

I really don't want to run SATA 3Gbs on a SATA 6Gbs SSD - sort of seems to defeat the purpose a bit. I realize it'll still be faster than a mechanical drive but I'm used to the 6Gbs (actually 5Gbs) speed the past 7 months.

Anyway - if you have a thought on my tentative plans let me know. In any case thank you very much for your replies!

 

[rcanino]

I've been reading more and more about the Marvell 6Gbs port and all the trouble with it on various boards.

A few places mentioned "rolling back the driver in Device Manager to the Microsoft driver" but never really spelled out how to do it. One guy said "just click 'roll back driver' and it will automatically go back to the default MS driver."

Can that be right? Does MS provide a driver for the Marvell storage controller? How do I know if it's installed and (presumably) waiting for me to try it?

Thanks!

 

[Dave76]

You can switch the SSD to the Intel ports for testing, and you won't loose any data. Only thing is it's 3Gbs but may run better, which Intel RST drivers are you using?
Go to the Intel site and get the latest RST drivers if your not sure.

Just put the SSD on port0, make sure the SSD is in the top of the BIOS boot priority list.

I have used drivers from the Station Driver site and never had any problems, there are other members here that do as well.

Edit: Yes you can use the MS driver for the Marvell controller.
It should be in your roll back driver, it's installed by MS when you install Win7.

Check in Device Manager, in your 'System devices' look for Marvell.

 

[rcanino]

Beautiful - Thanks Dave - very much appreciate your help (and your answers!)

couple questions if you don't mind...

1) I downloaded the RST from MSI's download page for the XPower (Matrix Storage Manager, correct? it's ver 10.1.0.1008). I haven't installed it yet. It was released last month so I assume I'm running the prior version. Not sure how to tell...

Anyway I'll check Intel's site, see if they have an even later version.

2) I have one of my other HDDs on SATA 0 and another one on SATA 1. I've got my optical drive on SATA 3. Ports 4, 5 and 6 (and 8) are empty. Is it necessary to move them all to get the SSD on SATA 0? I've read "yes" and "it doesn't matter." Is there a definitive answer that I've missed or is it more a personal preference?

3) I want (need?) to update the FW on the SSD. The process involves moving the drive to a SATA 3Gbs port. Should I do the update first? Nothing in the release notes suggest it will help with problems on the Marvell ports but...probably good to update to the latest FW on an SSD I think.

4) Lastly - is rolling back to the MS driver a "last resort" kind of move? If it is indeed the Marvell driver causing all these BSOD should I expect them to disappear after rolling back? And if so, should I try this first before anything else?

Thank you very much indeed. I'm nearly ready to give up and just live with the BSODs but your post gave me new life!

[edit: sorry, forgot to also ask about the "Marvell SATAIII Management Utility" that's listed on the XPower download (utilities) page. Any idea if that could help me? Not much info about it when I google it - mostly just d/l sites.]

 

[usasma]

Backup, backup, backup!!!
If you roll back drivers, back up the current drivers first.
If you install later drivers, backup the current drivers first.

Use the heck out of System Restore. It's much more reliable in Win7 than it was in XP. I don't use System Restore in XP, but I do use it regularly in Win7 (I work as a PC tech at a local shop).

Do one thing at a time and test the heck out of it before moving onto the next thing. That way if something breaks you'll have a better idea of what caused it.

I've recently read articles about the 3 vs 6 gBs ports - and the opinion was that you wouldn't notice the difference because the current hardware doesn't push up to those limits (haven't tested it myself). You may want to run a throughput test of some sort to see if it will matter for you.

 

[usasma]

For the SATA 0 thing - just use the BIOS boot order selection to see if it'll boot for you.
If it does, then you can change the boot order in the BIOS.

The RST was recently renamed from Matrix Storage Manager - so you'll find references to both. Just select the most current and you'll have the correct one.

I'm not a big fan of rolling back drivers - and only suggest it if it's a brand spanking new driver that hasn't been thoroughly tested yet. But, it can't hurt to try - worst case is that you'll have to reinstall the current drivers.

 

[rcanino]

Okay thanks - makes sense - try one thing at once, all of it.

Hopefully I'll know something over the next 48 hours or so...

 

[Dave76]

You should do the driver updates and testing as usasma is recommending, this is very important.

Will answer your questions below.

Beautiful - Thanks Dave - very much appreciate your help (and your answers!)

couple questions if you don't mind...

1) I downloaded the RST from MSI's download page for the XPower (Matrix Storage Manager, correct? it's ver 10.1.0.1008). I haven't installed it yet. It was released last month so I assume I'm running the prior version. Not sure how to tell...

Anyway I'll check Intel's site, see if they have an even later version.

You're welcome, that RST driver is pretty current so go ahead and use it.
The Intel 9.6.0.1014 RAID driver was the first one to pass the Trim command which is very important for SSDs, any driver later than that one will work for you.

To check your current driver, at the start button right click 'Computer' and click 'Manage', then when the window opens click 'Device Manager', select the 'IDE ATA/ATPI controllers' in the list should be something like 'Intel 5 Series/3400 Series SATA AHCI Controller' right click this and select 'Properties', then the 'Driver' tab. This will tell you the driver you have currently installed.

2) I have one of my other HDDs on SATA 0 and another one on SATA 1. I've got my optical drive on SATA 3. Ports 4, 5 and 6 (and 8) are empty. Is it necessary to move them all to get the SSD on SATA 0? I've read "yes" and "it doesn't matter." Is there a definitive answer that I've missed or is it more a personal preference?

Are you dual booting another OS?
The answer is, as usual, they are all partially correct.
I put the main OS drive on SATA0, due to the fact that sometimes during OS installation and re-installation this will eliminate issues with the boot files ending up on the wrong drive. You can reduce the chance of this happening if you make sure the data/storage HDDS are not marked 'Active'.
If this is going to be temporary then it doesn't matter, if permenant then I would put the SSD in SATA0 and the HDDs in SATA1&2, optical drive in SATA6 just to leave room for more HDDs if want to add later.
Check your BIOS boot order, you might have to adjust it.

3) I want (need?) to update the FW on the SSD. The process involves moving the drive to a SATA 3Gbs port. Should I do the update first? Nothing in the release notes suggest it will help with problems on the Marvell ports but...probably good to update to the latest FW on an SSD I think.

Is it a destructive FW update?
Did they give you a warning that all the data will be lost?
Even if it is a non-destructive FW update, get an image backup of the SSD before proceeding, better safe than sorry.

I would take care of all these other issues first before doing the FW update, will give you less possible causes for faults.
After your system is running stable for 3+ weeks, then proceed with the FW update.

4) Lastly - is rolling back to the MS driver a "last resort" kind of move? If it is indeed the Marvell driver causing all these BSOD should I expect them to disappear after rolling back? And if so, should I try this first before anything else?

Rolling back drivers is done to troubleshoot driver issues, it's usually easier than installing a newer or older driver that you don't know for sure are stable on your system. A previous driver that was running on your system is more likely to be stable.

Yes, if the Marvell driver is causing your BSoDs, then rolling back the driver should stop them.
As usasma mentioned it does work but, not always your first option.

Thank you very much indeed. I'm nearly ready to give up and just live with the BSODs but your post gave me new life!

[edit: sorry, forgot to also ask about the "Marvell SATAIII Management Utility" that's listed on the XPower download (utilities) page. Any idea if that could help me? Not much info about it when I google it - mostly just d/l sites.]

That is the million dollar question, some people claim good results from the Marvell drivers, most recommend to use the MS driver.
The "Marvell SATAIII Management Utility" might be best to try after everything is stable, no BSoDs.

For SSDs below 300 MB/s read/write speeds it is recommended to use the Intel SATAII 3Gb/s ports which are good for under 300 MB/s.
The newer SSDs are rated above 300 MB/s and will usually perform better on the SATAIII 5/6 Gb/s ports. Marvell drivers do have performance issues, this has to be taken into consideration.

Some people are using SATAIII PCI cards and getting good performance, some of these have Marvell controllers so you need to research this before going this route.

 

[rcanino]

Thank you Dave - I've updated the drivers that were in the first reply to my bug report, with the exception of PxHLpa64.sys (DVD driver) since I can't find a newer driver. I've had no issues with either optical drive that I'm running.

I checked the RST after updating it and it now reads (under Intel ICH10R SATA AHCI Controller Properties) driver version: 10.1.0.1008. The name of the driver is iaStor.sys and that's what the instructions said I should find if the update was successful.

re: the SATA ports - No, I'm not dual-booting, only running one OS (win7 pro 64). In Disk Management I've got 2 HDDs marked "Active," my boot drive (the SSD) and a small notebook HDD I installed when I put the system together. Not sure how or why it's "Active" but I've never had problems with it.

re: the Firmware update to the SSD -According to Crucial if the process is done correctly there is no data loss. It requires moving the drive. From the instructions: "ensure your SSD is plugged into one of the first four ports" and "...process will not work with some drop-in HBAs or 6.0 Gb/s ports."

I will follow your advice and postpone the FW update until I'm reasonably sure my system is stable. However it seems to me I've done nothing that affects the offending driver - the mv91xx.sys. I realize I'm in a predicament: the official mv91xx.sys driver is causing problems, but the unofficial driver updates (from station-drivers) are just that - unofficial.

I'm still confused about this "Marvell SATAIII Management Utility." You said "The "Marvell SATAIII Management Utility" might be best to try after everything is stable, no BSoDs."

I understand you to mean it is some type of extraneous program (?) that has no bearing on the mv91xx.sys driver. Is that right? I can't seem to find any information about it on the web.

I should like to ask your advice, seeing as how I'm basically finished (only the SSD firmware remains). The way I see it I have 2 choices, either roll back the mv91xx.sys driver or update it using an unofficial release from station-drivers. I'd like to try something.

I haven't moved the SSD boot drive off the Marvell port because I'm convinced there's no need to diagnose what BlueScreenView and the Dump files/Bug Reports already confirm - that it is indeed the Marvell driver causing the BSODs. But I suppose that's a 3rd choice, just forget about using the SATA 6Gbs ports and use the Intel ports. I hate to give up on it though - half the reason I bought this particular SSD and board were for the SATA III. I've read some benches that suggest there's no appreciable difference in SSD performance on SATAII or SATAIII, or only sequential reads are affected. I'm not sure about any of that, all I know is this SSD hits or exceeds the advertised speeds on the Mavell port. I'd like to keep it that way if I could.

In any case I thank you for time and help Dave and USAMA. I very much appreciate it.

 

[Dave76]

Thank you Dave - I've updated the drivers that were in the first reply to my bug report, with the exception of PxHLpa64.sys (DVD driver) since I can't find a newer driver. I've had no issues with either optical drive that I'm running.

I checked the RST after updating it and it now reads (under Intel ICH10R SATA AHCI Controller Properties) driver version: 10.1.0.1008. The name of the driver is iaStor.sys and that's what the instructions said I should find if the update was successful.

That is the latest official Intel RST driver.

re: the SATA ports - No, I'm not dual-booting, only running one OS (win7 pro 64). In Disk Management I've got 2 HDDs marked "Active," my boot drive (the SSD) and a small notebook HDD I installed when I put the system together. Not sure how or why it's "Active" but I've never had problems with it.

Did the notebook HDD previously have an OS installed on it? Or plugged into SATA port0?
Was this small HDD installed when you installed the OS on your SSD?
If yes, then the small HDD will probably have the boot files on it, your system won't boot without that small HDD. This can be checked and the boot files moved to the SSD, but is best left for later.

re: the Firmware update to the SSD -According to Crucial if the process is done correctly there is no data loss. It requires moving the drive. From the instructions: "ensure your SSD is plugged into one of the first four ports" and "...process will not work with some drop-in HBAs or 6.0 Gb/s ports."

Then you can move the SSD to the Intel SATAII port, before changing anything on the Marvell controller. This will confirm if the issues are coming from that driver/controller.

I will follow your advice and postpone the FW update until I'm reasonably sure my system is stable. However it seems to me I've done nothing that affects the offending driver - the mv91xx.sys. I realize I'm in a predicament: the official mv91xx.sys driver is causing problems, but the unofficial driver updates (from station-drivers) are just that - unofficial.

Only use un-official or beta drivers if you are comfortable with doing it and know how to remove them and install another driver.

I'm still confused about this "Marvell SATAIII Management Utility." You said "The "Marvell SATAIII Management Utility" might be best to try after everything is stable, no BSoDs."
I understand you to mean it is some type of extraneous program (?) that has no bearing on the mv91xx.sys driver. Is that right? I can't seem to find any information about it on the web.

Bringing too many new things into the system now will only make troubleshooting the existing crashes harder.
I'm not familiar with the Marvell Management app, it might be similar to the Intel RAID management app.
Is this a separate app or it comes with the driver?

I should like to ask your advice, seeing as how I'm basically finished (only the SSD firmware remains). The way I see it I have 2 choices, either roll back the mv91xx.sys driver or update it using an unofficial release from station-drivers. I'd like to try something.

I would roll back the driver first, if that doesn't solve the problem then install the new driver from Station Drivers.

I haven't moved the SSD boot drive off the Marvell port because I'm convinced there's no need to diagnose what BlueScreenView and the Dump files/Bug Reports already confirm - that it is indeed the Marvell driver causing the BSODs. But I suppose that's a 3rd choice, just forget about using the SATA 6Gbs ports and use the Intel ports. I hate to give up on it though - half the reason I bought this particular SSD and board were for the SATA III. I've read some benches that suggest there's no appreciable difference in SSD performance on SATAII or SATAIII, or only sequential reads are affected. I'm not sure about any of that, all I know is this SSD hits or exceeds the advertised speeds on the Marvell port. I'd like to keep it that way if I could.

Moving the SSD to the Intel SATA port is just for testing/troubleshooting purposes. This will do two things, 1) tell you if the Marvell driver/port is causing your crashes, and 2)you will have a way to enable your system to run stable, even if it is not the best as far as performance goes.
You might not be able to tell the difference, except in benchmarks.
This is all part of buying/trying cutting edge new hardware, there are usually some bugs to work out.

In any case I thank you for time and help Dave and USAMA. I very much appreciate it.

You're welcome.

 

[Pixel Panic]

Was having a similar problem with intel Mobo

Some of my system specs:

Intel Motherboard:

DX58502 (with 6 RAM Chip Slots)
BIOS version: S0X5820J.86A.0603.2010.1117.1506 (Marvell?)

CPU:

intel i7 930 @ 2.80GHz

RAM Chips:

Corsair - Vengeance (4 GB x 4) 1600 Mhz 1.5 volts CMZ8GX3M2A1800C9 timing = 9-9-9-24
Note: Out of the box, this MoBo can only handle 4 of these chips in Channels A&C , A BIOS update might allow 2 more slots of use in channel B. intel recommends using 1066Mhz Chips instead to fill all slots.

I too was having the BSOD plague ruin a few of my days. I was forced to re-install Windows 7 Ultimate - 3 times. An error about the Marvell 91xx SATA 6G driver & the Marvell 61xx RAID Controller kept popping up. Later, when I tried to burn files to my Blu-Ray burner, my system would crash. It would also, spontainiously crash when ever it felt like it - even when I wasn't using it.

The cure turned out to be to change the sequence of installing drivers.


If you're having this problem with this intel Mobo; follow this install sequence:

1, If you don't already have it, find a free Low Level Format Utility .ISO image online that's CD bootable on start-up. You'll need to re-format your boot up drive because (while installing) Windows splits it into 2 partitions and you'll want to return it to being just one partition. Or else, Windows 7 will keep eating up disc space by creating .old file versions of your previous Windows installations and it may want to create more partitions too.

2. Disconnect any other hard drives except your target boot up drive and re-install Windows. Connect them back after the Windows Desktop is up and running.

Note: Critically important - Once the Windows Desktop is up and running, (a) DO NOT USE the included intel motherboard driver disc (it's most likely very outdated by now anyway) and (b) DO NOT immediately go online and start downloading Windows OS updates

3. If you have a new DVD or Blu-Ray Burner/Writer in your system, go to that manufacturers website, download and install that drive's most recent firmware update now.

4. Now go to intels website and download and install just the Marvell 91xx SATA 6G driver & the Marvell 61xx RAID Controller drivers to begin with, then re-boot your system.

5. After it's re-booted, go back to intel's website, download and install the rest of the Mobo's drivers. Reboot your system as much as requested by the software prompts.

6. Only at this point, should you go to your "Control Panel" and request Windows 7 OS updates, then let Windows re-boot your system as many times as it needs to.

7. Now, Install all the application software you want on your system (from disc or from downloads).

8: Only after steps 1-7, should you get into installing your anti-virus, anti-malware and firewall software.

9. Once your satisfied that (a) nothing is outstanding in "Device Manager" and that all your apps boot up right, have Windows make a few system image back ups to a few other drives. Don't rely on "restore points" - most of the time they don't fix anything.

 

[rcanino]

thanks for your info Pix - I'm glad you found a way to get this Marvell controller working for you. I partitioned my SSD (and aligned it) using diskpart during the initial install, forcing Win to avoided creating that 100MB partition. I only had the one HDD plugged in during the install.

I'll have to think about reinstalling Windows. I always figured I would have to at some point but ... it'll be my last resort if nothing else works.

Thanks again for taking the time to post. At some point I'm sure I'll be following your method. But honestly I hope I don't have to!

 

[rcanino]

Was this small HDD installed when you installed the OS on your SSD?

No only the SSD - before installing Win7 I made sure only one HDD was plugged in.

Then you can move the SSD to the Intel SATAII port, before changing anything on the Marvell controller. This will confirm if the issues are coming from that driver/controller.

I don't mean to sound argumentative but I thought this was already confirmed by the bug report, that mv91xx.sys is causing all the BSOD. Also BlueScreenView reports that driver as the culprit.

Moving the SSD to the Intel SATA port is just for testing/troubleshooting purposes. This will do two things, 1) tell you if the Marvell driver/port is causing your crashes, and 2)you will have a way to enable your system to run stable, even if it is not the best as far as performance goes.
You might not be able to tell the difference, except in benchmarks.
This is all part of buying/trying cutting edge new hardware, there are usually some bugs to work out.

Thank you for putting it that way and reminding me.

I will change ports and see what happens to the BSOD. At some point if it's stable I will update the firmware, since it needs to be on a SATA 3Gbs port anyway. If I can't see a difference I'll probably just leave it there. Otherwise I will use one of the non-official mv91xx.sys drivers. I can always roll it back if it won't boot I guess.

Oh - re: the Marvell SATA III Management Utility - the actual file, when you download it from MSI is MRUsetup.exe, which is the RAID utility. What I think - it's the GUI you see when you press CTL+M during boot. I'm guessing - but I can't find any more info about it other than what's on Marvell's site and a few references to it on the web (besides d/l links).

Thanks again for your help and your reply!

 

[Dave76]

Sounds like a good plan.

Let us know how the steps are going.


If your other HDD was connected when you installed Win7 on the SSD, it might have the boot files on it.
Win7 looks for a HDD marked 'Active' or sometimes will use the drive in port0, to install the boot files.
Just a heads up if you ever take out that HDD and your OS won't boot.

 

[rcanino]

Can I simply remove the "Active" status of that HDD - using diskpart I guess, or maybe in the OS through Disk Management?

I'm positive I only had the SSD plugged in when I installed Windows. I took great pains to align it and avoid that 100MB partition. I researched the process carefully before I did it and I am confident the system would boot just fine with only the SSD.

But I've never tried "de-activating" (if that's the right term) a HDD. That little HDD did have an OS on it - it was in a Lenovo laptop that died.

If I were to "lose" that HDD it's no big deal - only thing on it is my cache files, which change all the time. In fact I'm pretty sure I formatted it after I installed it in this new system...can't imagine why it's marked "Active" but I'll read up on it more.

Thanks again Dave!