Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Ongoing BSODs, Marvell driver (reports attchd)

24 Apr 2011   #11
usasma
Microsoft MVP

 
 

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.


My System SpecsSystem Spec
.
24 Apr 2011   #12
rcanino

Win7 Pro 64-bit sp1
 
 

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

Hopefully I'll know something over the next 48 hours or so...
My System SpecsSystem Spec
25 Apr 2011   #13
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

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

Will answer your questions below.

Quote   Quote: Originally Posted by rcanino View Post
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.

Quote   Quote: Originally Posted by rcanino View Post
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.

Quote   Quote: Originally Posted by rcanino View Post
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.

Quote   Quote: Originally Posted by rcanino View Post
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.

Quote   Quote: Originally Posted by rcanino View Post
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.
My System SpecsSystem Spec
.

25 Apr 2011   #14
rcanino

Win7 Pro 64-bit sp1
 
 

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.
My System SpecsSystem Spec
26 Apr 2011   #15
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Quote   Quote: Originally Posted by rcanino View Post
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.
Quote   Quote: Originally Posted by rcanino View Post
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.
Quote   Quote: Originally Posted by rcanino View Post
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.
Quote   Quote: Originally Posted by rcanino View Post
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.
Quote   Quote: Originally Posted by rcanino View Post
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?
Quote   Quote: Originally Posted by rcanino View Post
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.
Quote   Quote: Originally Posted by rcanino View Post
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.
Quote   Quote: Originally Posted by rcanino View Post
In any case I thank you for time and help Dave and USAMA. I very much appreciate it.
You're welcome.
My System SpecsSystem Spec
26 Apr 2011   #16
Pixel Panic

Windows 7 64Bit
 
 
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.
My System SpecsSystem Spec
26 Apr 2011   #17
rcanino

Win7 Pro 64-bit sp1
 
 

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!
My System SpecsSystem Spec
26 Apr 2011   #18
rcanino

Win7 Pro 64-bit sp1
 
 

Quote   Quote: Originally Posted by Dave76 View Post
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.

Quote   Quote: Originally Posted by Dave76 View Post
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.

Quote   Quote: Originally Posted by Dave76 View Post
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!
My System SpecsSystem Spec
26 Apr 2011   #19
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

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.
My System SpecsSystem Spec
26 Apr 2011   #20
rcanino

Win7 Pro 64-bit sp1
 
 

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!
My System SpecsSystem Spec
Reply

 Ongoing BSODs, Marvell driver (reports attchd)




Thread Tools




Similar help and support threads
Thread Forum
Ongoing BSODs at random times
Hi all, I made a post regarding this issue back in December but never received any replies, and that thread seems to have been deleted. Please let me know if there is any issue with this post so I can rectify it. As in the title, I am suffering from recurrent BSODs with my laptop. I can't tie...
BSOD Help and Support
BSODs while playing games, browsing (ongoing 6 month problem)
I've been having problems with random BSOD's, mostly while playing games. They started around march, this year (as far as I remember). Thing I have done so far: -formated hard drives twice and reinstalled Windows (zeroed once) -ran memtest (couple of times with every stick tested solo, around...
BSOD Help and Support
Random BSODs, ntoskrnl, driver power state failure reports on minidump
Win7 laptop running fine, suddenly 2 BSODs today, within an hour. First occurred while surfing (firefox), second occurred without any keyboard/mouse activity. No new hardware installed since new hard drive about a month ago. SF attached. TIA
BSOD Help and Support
!! HELP PLS. !!! RANDOM BSODs - have documented 4- attchd all details
Gurus...pls. help. and I'm a newbie I had a new system built 5 months ago- COre I5 2500K, GIgabyte Z68xUD3H MOBO, 8GB corsair RAM, Win 7- it was running off the vertex OCX SSD - 64GB. The guy didnt do the intel RST properly as he loaded Win 7 directly onto SSD. System was giving unusual app...
BSOD Help and Support
Marvell Yukon Driver
Hi, Just wondering who else has a Marvell Yukon network controller and are you happy with the new driver changes? Thanks,
Drivers
Ongoing BSODs
Hi there I've been dealing with an ongoing computer problem for the past month with no hope. I seem to be getting BSOD's in spurts and different ones with no pattern. Here is the following of what I've tested to resolve the problem: PSU HDD RAM Motherboard appears fine with no bulging...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 09:40.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App