1 2 Previous Next 16 Replies Latest reply: Jan 19, 2014 12:57 PM by jstateson RSS

    Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.

    ailwen

      AHCI works fine with the Intel SATA controller.  However, if AHCI is enabled on the Marvel SATA controller in the bios, Windows hangs during startup.  Windows will boot if the Marvell SATA ports are set to IDE.  Has anyone been successful in getting AHCI mode to boot with the Marvel SATA controller?

       

      OS: Windows 7 64-bit SP1

      CPU: i7-2700k

      Motherboard: DZ68BC

      Bios version: 0028 (latest)

       

      Intel controller:

      SATA0: Intel 520 180GB SSD

      SATA1: OCZ Agilty 3 60 GB SSD

       

      Marvell controller:

      SATA2: Seagate Barracuda Green 2TB SATA

      SATA3: OCZ Agility 3 60 GB SSD

       

      Marvell 91xx SATA Controller driver version: 1.2.0.1019 (latest)

       

      A couple of notes that might be useful.  Windows will boot when the Marvel controller is set to AHCI if the drives attached to it are unpartioned and unformatted.   Further, I have tried different combinations of drives between the Intel and Marvell controller and all drives work on the Intel controller.

       

      Any help is appreciated!

        • 1. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
          Dan_Intel

          Hello,

          As far as we understand you have installed the Operating System (OS) on the Intel SATA controller.

          If this is the case our recommendation is making sure you have the latest firmware update for these hardrives connected on the Marvell* controller and test by partitioning the hard drives from the OS.

          • 2. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
            mechbob

            You May have to reinstall the under RAID O .    Note the SSDs under will not get TRIM. The other ones not part of the RAIN should Be fine.

            • 3. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
              ailwen

              Yes, the OS is installd on the Intel SSD on the Intel SATA controller.  I have updated to the latest firmware for the drives connected to the Marvell controller.

               

              Can you elaborate on "test by partitioning the hard drives from the OS?"  Thanks.

              • 4. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
                inanc

                Hi,

                I am having the same problem I thing. Approximately same RAID controller  card and SSDs. You said when AHCI enabled on Marvell SATA controller! Do we another alternative except AHCI? If so, how can you set it rather than AHCI? Can you tell me a little bit please? Thank you.

                 

                Warm regards.

                Inanc


                • 5. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
                  mechbob

                  From what I have read it sounds like you are tring to run AHCI and Raid at the same time , no can do , you have to chose one or the other .

                  • 6. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
                    Egor V. Zhilin

                    I have exactly the same problem.

                    no SSDs, just 4 HDD SATA-III drives connected to all SATA-III connectors on Intel and Marvel controllers.

                    I have the same issue on both installed OSs, Windows XP SP3 and Windows 7 Ultimate x64 SP1.

                    Firstly, after changing Marvel to AHCI mode, very long OS start, about 5-7 min, and than, after desktop is already opened, I get "Found new hardware" message and BSOD during installing driver.

                    If it's required i can send more details and mini dump.

                     

                    In IDE mode all functions great.

                    • 7. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
                      Flying_Kiwi

                      Have you installed AHCI drivers for the controller(s) using the F6 Floppy (or slipstream) method for the Win XP installation? If not, go to the Intel downloads page for your board and have a read about how to install these.

                      • 8. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
                        Egor V. Zhilin

                        System (WinXP) was already installed. F6 drivers in all modes were slipstreamed into working OS through the registry, so, after the changing Marvel controller into AHCI mode in BIOS, system goes to BSOD during automatic drivers installation while copying mv91xx.sys instead the same one already installed in the system.

                        • 9. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
                          Flying_Kiwi

                          Are both operating systems on different drives/volumes? The problem you describe (halting during boot with and error after switching to AHCI from IDE) is typical of the OS not being able to find the correct AHCI driver.

                           

                          I'm unsure what you mean by:

                          Egor V. Zhilin wrote:

                           

                          System (WinXP) was already installed. F6 drivers in all modes were slipstreamed into working OS through the registry

                          Slipstreaming means making a customised installation package (typically burning a new DVD) which has additional drivers or hotfixes/service packs contained within. It does not involve working with the registry.

                           

                          Was Win XP installed on this hardware (using the Marvell controller) using the F6 Floppy or slipstreaming method (at the time the OS was being installed)?

                          • 10. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
                            Egor V. Zhilin

                            No. Both OSs were installed on another motherboard (D975XBX2) and Marvell controller was not used, and of course on different drives (logical and physical). But this means nothing, cuz all hardware was found correctly and the latest versions of drivers were installed.

                             

                            Bootable controller is not Marvell, Intel is used, so there is no need to slipstream F6 Marvell driver into installation media even using clean OS install, Intel drivers are quite enough.

                             

                            One thing I have not tried - to update BIOS to the current  035 latest version, currently installed is 028, just cuz it cannot be downgraded. But it was tried on the another PC with the same motherboard and under Windows 7 x64 Pro, clean install - result was exactly the same. Bootable controller was also Intel, and Marvell was used as an additional one, and also were used 4 HDD SATA-III drives connected to 6GB ports.

                             

                            Just interesting - was it checked by manufacturer or not, when both controllers are in AHCI mode? Should it work? And in what OS it was checked if so?

                            Combination of Intel AHCI + Marvell IDE works great, but i dont like this by very well known reason.

                             

                            Some details on BSOD in Windows XP:

                             

                            Error text: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

                            Error code: 0x1000007e (0x80000003, 0xb84a0a07, 0xf79126e4, 0xf79123e0)

                            Driver name: mv91xx.sys

                            Driver description: Marvell magni Windows Driver    Marvell magni

                            Driver version: 1.2.0.1019  built by: WinDDK

                            Case address: mv91xx.sys+34a08

                            From address: 0xb846c000

                            To address: 0xb84f2000

                            Size: 0x00086000

                            Time stamp: 0x4eb79da0

                             

                            Other participants of the event:

                             

                            Module name: ntoskrnl.exe

                            Module version: 5.1.2600.6223 (xpsp_sp3_qfe.120504-1617)

                            Module description: NT Kernel & System

                            Address in stack: ntoskrnl.exe+48ca

                            From address: 0x804d7000

                            To address: 0x80700000

                            Size: 0x00229000

                            Time stamp: 0x4fa3d892

                             

                            Module name: SCSIPORT.SYS

                            Module version: 5.1.2600.6073 (xpsp_sp3_qfe.110127-1729)

                            Module description: SCSI Port Driver

                            Address in stack: SCSIPORT.SYS+1213

                            From address: 0xb84f2000

                            To address: 0xb8509880

                            Size: 0x00017880

                            Time stamp: 0x4d417972

                            • 11. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
                              Flying_Kiwi

                              Egor V. Zhilin wrote:

                               

                              No. Both OSs were installed on another motherboard (D975XBX2) and Marvell controller was not used, and of course on different drives (logical and physical). But this means nothing, cuz all hardware was found correctly and the latest versions of drivers were installed.

                              Some may say that means alot. I'll repeat that the fact you are getting these messages implies the faulting OS has NOT correctly installed the correct driver for the controller (or a driver which it depends on was not correctly installed before it was installed). Intel have a precise installation order for their board drivers and if PnP is left to do its thing like you've relied on (rather than starting from a clean slate and following the correct steps in the correct order)... well, you've seen what happens. You may be able to install drivers in the wrong order and hack the installation to get things limping along with some time and effort though I wouldn't trust such an installation to always behave as expected.

                              • 12. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
                                Egor V. Zhilin

                                Sorry, but as system builder I've built a lot of PCs on Intel boards since 1989 and very well know driver installation order. No need in the clean OS install to do that, especially in this case. Marvell controller is not bootable and can be turned off even during clean install, and only than can be turned on with drivers installation. So we have just the same situation.

                                I know a lot of cases on the different motherboards, when two built in controllers cannot be used in the same mode or just simultaneously. And now I just need to know - should it work on this board or no. It was tested, wasnt it?

                                • 13. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
                                  Flying_Kiwi

                                  As an experienced system builder then you would understand that both Win XP and Win 7 contain the required drivers for IDE configured drives but of those two, only Win 7 has Intel AHCI drivers built in. During my time working as a computer technician for a school with close to 200 PCs at the end  - almost all of which were Intel based and working around Intel servers, switches and print servers (yes this was going back a few years) I can tell you we still had to be carefull about creating images that were precisely system specific.

                                   

                                  It doesn't matter whether the Marvell controller was switched on or off at the time you connected the HDD from the old motherboard based system to the Intel SATA port on this motherboard and booted it up. Once the OS started loading and PnP started to do its thing with all the new hardware (even excluding the Marvell Controller if it was switched off at the time) in whatever order of driver installation it pleases - the damage was then done. THAT is not following the correct driver installation order as I linked to earlier and subsequent driver installations (eg the Marvell controller) may encounter problems as a result. Just because its a part that can be turned on and off in the BIOS and it's HDDs are non-bootable does not mean it operates entirely independantly from the rest of the system. If you've ever tried installing Graphics drivers before motherboard chipset drivers, you may encounter a problem which will highlight my point - thats the typical thing that suffer from the wrong installation order but it's not limited to just that.

                                   

                                  Sometimes it's possible to get away with swapping boards to different brands/models and Win 7 is reputedly pretty good at coping with that (unlike XP) but when it doesn't, even if you do manage to get the system working again, there are still to many unknowns and potential problems waiting in the wings with such a system to be able to count on it 100%.

                                  • 14. Re: Windows 7 hangs at startup DZ68BC when AHCI is enabled on Marvell SATA controller.
                                    Egor V. Zhilin

                                    Of course, when you need to make  the clean OS install on the loads of similar PCs, the best way to do it is to slipstream drivers into installation media, and it's easy

                                    If you need to get working OS which was already installed whithout support of Intel AHCI, the only one way is to implement it into the registry and place the required *.sys, *.cat and *.inf files into the right places, and it's easy also. Ready example for Windows XP for DZ68BC is below:

                                     

                                    ----begin----

                                    Windows Registry Editor Version 5.00

                                     

                                    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1C02&cc_0106]

                                    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"

                                    "Service"="iaStor"

                                     

                                    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\iaStor]

                                    "Type"=dword:00000001

                                    "Start"=dword:00000000

                                    "Group"="SCSI miniport"

                                    "ErrorControl"=dword:00000001

                                    "ImagePath"="system32\\drivers\\iaStor.sys"

                                    "tag"=dword:00000019

                                    "DisplayName"="Intel(R) Desktop/Workstation/Server Express Chipset SATA AHCI Controller"

                                     

                                    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\iaStor\Parameters]

                                    "AtapiOnPrimary"=dword:ffffffff

                                    "AtapiOnSecondary"=dword:ffffffff

                                    "queuePriorityEnable"=dword:00000000

                                    "BusType"=dword:00000008

                                     

                                    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\iaStor\Parameters\Port0]

                                    "AN"=dword:00000000

                                    "LPM"=dword:00000000

                                    "LPMSTATE"=dword:00000000

                                    "LPMDSTATE"=dword:00000001

                                    "GTF"=dword:00000000

                                    "DIPM"=dword:00000000

                                     

                                    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\iaStor\Parameters\Port1]

                                    "AN"=dword:00000000

                                    "LPM"=dword:00000000

                                    "LPMSTATE"=dword:00000000

                                    "LPMDSTATE"=dword:00000001

                                    "GTF"=dword:00000000

                                    "DIPM"=dword:00000000

                                     

                                    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\iaStor\Parameters\Port2]

                                    "AN"=dword:00000000

                                    "LPM"=dword:00000000

                                    "LPMSTATE"=dword:00000000

                                    "LPMDSTATE"=dword:00000001

                                    "GTF"=dword:00000000

                                    "DIPM"=dword:00000000

                                     

                                    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\iaStor\Parameters\Port3]

                                    "AN"=dword:00000000

                                    "LPM"=dword:00000000

                                    "LPMSTATE"=dword:00000000

                                    "LPMDSTATE"=dword:00000001

                                    "GTF"=dword:00000000

                                    "DIPM"=dword:00000000

                                     

                                    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\iaStor\Parameters\Port4]

                                    "AN"=dword:00000000

                                    "LPM"=dword:00000000

                                    "LPMSTATE"=dword:00000000

                                    "LPMDSTATE"=dword:00000001

                                    "GTF"=dword:00000000

                                    "DIPM"=dword:00000000

                                     

                                    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\iaStor\Parameters\Port5]

                                    "AN"=dword:00000000

                                    "LPM"=dword:00000000

                                    "LPMSTATE"=dword:00000000

                                    "LPMDSTATE"=dword:00000001

                                    "GTF"=dword:00000000

                                    "DIPM"=dword:00000000

                                     

                                    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\iaStor\Parameters\oromVersion]

                                    "MajorVersion"=dword:00000007

                                    "MinorVersion"=dword:00000005

                                    "HotfixNumber"=dword:00000000

                                    "BuildNumber"=dword:000003f9

                                     

                                    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\iaStor\Enum]

                                    "0"="PCI\\VEN_8086&DEV_1C02&SUBSYS_B0051458&REV_02\\3&13c0b0c5&0&FA"

                                    "Count"=dword:00000001

                                    "NextInstance"=dword:00000001

                                    ----end-----


                                    But I still dont have an answer on my question - Intel AHCI + Marvell AHCI - should it work or no?

                                    1 2 Previous Next