Ongoing BSODs, Marvell driver (reports attchd)

rcanino · 23 Apr 2011

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 · 24 Apr 2011

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-Ba...ml#?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:

Code:


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)
PxHlpa64.sys         Mon Dec 10 18:49:01 2007 (475DD06D)
dump_mvxxmm.sys      Wed Jun 30 21:54:57 2010 (4C2BF571)
nvoclk64.sys         Tue Sep 15 17:59:25 2009 (4AB00E3D)
wacommousefilter.sys Fri Feb 16 13:12:17 2007 (45D5F401)
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)

BSOD BUGCHECK SUMMARY

Code:


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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

rcanino · 24 Apr 2011

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 · 24 Apr 2011

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 · 24 Apr 2011

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 · 24 Apr 2011

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 · 24 Apr 2011

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 · 24 Apr 2011

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 · 24 Apr 2011

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 · 24 Apr 2011

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.