mv91xx.sys BSOD - Windows 7 64 - Samsung Evo SSD

[nofx1728]

I just installed a new SSD Samsung EVO 250gb (boot drive) and now I'm getting a BSOD - 0x0000003D
mv91xx.sys - address FFFFF88000D8778E base at FFFFF88000D56000

I have an Asus p8 z68-V Pro motherboard
Intel I7-3400 processor
Nvidia Gefore GTX 570 Graphics Care

I have 2 Samsung HD322GJ Hard drives in Raid 0

I have 4 Hitachi HDS Hard drives in Raid 10

+ System 

  - Provider 

   [ Name]  Microsoft-Windows-Kernel-Power 
   [ Guid]  {331C3B3A-2005-44C2-AC5E-77220C37D6B4} 
 
   EventID 41 
 
   Version 2 
 
   Level 1 
 
   Task 63 
 
   Opcode 0 
 
   Keywords 0x8000000000000002 
 
  - TimeCreated 

   [ SystemTime]  2014-08-04T18:19:32.414008600Z 
 
   EventRecordID 6892 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  4 
   [ ThreadID]  8 
 
   Channel System 
 
   Computer Mike-PC 
 
  - Security 

   [ UserID]  S-1-5-18 
 

- EventData 

  BugcheckCode 61 
  BugcheckParameter1 0xfffff80000b9bf60 
  BugcheckParameter2 0x0 
  BugcheckParameter3 0x0 
  BugcheckParameter4 0xfffff8800146378e 
  SleepInProgress false 
  PowerButtonTimestamp 0

Help would be appreciated.

 

[nofx1728]

I can't even get into windows long enough to make changes. Half the time I get the BSOD on boot. The other half I get it within 20 seconds of windows being launched.

 

[trippap]

I have a very similar problem. Samsung 840 Pro 256GB SSD (system drive), two WD 1TB black SATA 3 drives configured as RAID1. MB is Asus P8P67. I have the two WD drives connected to the Intel SATA 3 ports and my SSD is connected to one of the Marvell SATA 3 ports. I've seen BSOD mainly just after a major Microsoft update (Windows 7 Professional 64-bit). My computer will usually reboot without the BSOD, but I get several minutes of frenzied disk activity without any indication of what Windows is doing. Since my SSD doesn't make noises, it's obviously something other than that drive.

When I first encountered the problem early this week, I was running overclocked and suspected I was pushing some timing limit. So I backed out the overclock and things seemed to run OK until after the Windows Update today, when I got another BSOD. I saw something on the Web about not connecting a SSD to a Marvell port, but since I have only four SATA 3 ports and four SATA 3 devices, I did it anyway (the 4th disk is a third WD 1TB black drive I use to archive image backups. The alternative was connect my SSD to one of the Intel SATA 3 ports, but that would have put my RAID1 array on the Marvell ports and would not have used the built-in Intel RAID controller on the MB.

I'll be following the progress of this post, as I've found nothing else useful on the Web about these mv91xx.sys BSOD problems.

 

[nofx1728]

anonymous1 solution above worked for me. I was finally able to get it to boot and not bsod immediately which gave me enough time to update the driver from that link. It's been 3 days now and I haven't received a BSOD. I had to search for the driver because it didn't directly link me to it but it was on that site and worked perfectly once installed. Hopefully you encounter similar success. And gracias anonymous1 for your help.

 

[nofx1728]

Here is the direct link to the driver that worked for me: MV91xx Driver