locked
Intel Matrix Storage driver Windows XP and STOP: 0x0000007B RRS feed

  • Question

  • Hello

     

    I'm trying to deploy Windows XP using SCCM OSD to a laptop with SATA driver, HP 8510p. However I get the BSOD screen 0x0000007B and it doesn't seem that the correct mass storage driver is being applied.

     

    If I do a manual installation of Windows XP and press F6, the driver is called "Intel 82801HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M)".

     

    If I boot on WinPE after the BSOD and then copy out all contents from system drive, I notice that the winnt.sif file in $WIN_NT$~BT folder contain the line:

    "Intel (R) 82801HEM SATA RAID Controller (Mobile ICH8M-E)"=OEM

     

    The various txtsetup.oem files also reference "Intel (R) 82801HEM SATA RAID Controller (Mobile ICH8M-E)".

     

     

    I downloaded the latest Intel Matrix Storage Manager driver from Intel, version 7.8 and extracted the files. Imported the drivers into SCCM driver repository, created a driver package and added the drivers.

     

    Then I edited my Windows XP task sequence (that have already been tested on another computer) and added the Apply Driver Package TS just after the Apply Operating System TS. Selected the driver package I created, selected the option "select the mass storage driver...".

     

    The only option I get for the Driver dropdown box is "Intel (R) 631xESB/632xESB SATA RAID Controller". I get 4 options for the Model dropdown box:

    Intel(R) 82801HEM SATA RAID Controller (Mobile ICH8M-E)

    Intel(R) ICH8R/ICH9R SATA RAID Controller (Desktop/Server(Workstation)

    Intel(R) 631xESB/632xESB SATA RAID Controller (Desktop/Server(Workstation)

    Intel(R) 82801GHM SATA RAID Controller (Mobile ICH7MDH)

    Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)

     

    If I just import drivers from iaahci.inf, I don't even get the option to select a driver from that driver package in the TS.

     

    So it seems to me that I'm unable to import the Intel Matrix Storage dirver correctly. Am I missing something vital here?

     

     

    /Ragnar

    Tuesday, November 27, 2007 8:57 PM

Answers

  • It looks like that drop down box on the Apply Driver Package TS action only allows you to select drivers where Class=SCSIAdapter. The AHCI drivers you're talking about in this thread have Class=hdc by default.

     

    I was able to get the AHCI drivers to work by following these steps:

     

    1. Delete the nonfunctional Intel AHCI & RAID Controller drivers from my Drivers list in SCCM

    2. Extract the downloaded mass storage drivers to a temp directory

    3. Edit the iaahci.inf file by changing the line that says Class=hdc to instead say Class=SCSIAdapter

    4. Import the driver into SCCM, add to the appropriate driver package and update my DP

    5. Edit my Apply Driver Package TS to select the appropriate AHCI driver

     

    Messy, but it works.

     

    Wednesday, November 28, 2007 5:21 PM
  • Hi, thanks

     

    Yes it worked perfectly

     

    The final respone from ms:

     

    Sorry for the delay in response.

     

    It looks like we being too restrictive with what types of devices we show as boot critical drivers.  We restricted the list to only SCSIAdapter drivers and it looks like we should be showing HDC drivers as well.  You can fix by performing the below workaround, but we have considered fixing this in SCCM SP1.

     

    To get the AHCI drivers in TS please do the following steps:

     

    1.       Edit the iaahci.inf file and change the line Class=hdc instead Class=SCSIAdapter.

    2.       Import the driver into SCCM driver node and add to the appropriate driver package and update the DP.

    3.       Edit my Apply Driver Package TS to select the appropriate AHCI driver under model

     

    Here is a post on the Forums with a similar issue (http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2469344&SiteID=17). 

     

    Please try the above steps and let me know the result.

     

    ******************

    End

     

     

    Br

    erik

    Thursday, November 29, 2007 1:23 PM

All replies

  • Hi Ragnar,

     

    You will need 2 steps in your Task Sequence.

     

    1st step) Apply Driver Package - Select Mass Storage

    Based on what you've said above, select the "Intel(R) 82801HEM SATA RAID Controller (Mobile ICH8M-E)" Model from the drop down

    This will provide the correct Mass Storage driver for text mode setup.

     

    2nd step) Auto Apply Drivers

    In my case, I have 'limited' the driver matching to only select from a category of suitable mass storage devices.

    This will provide the drivers to Windows GUI mode setup.

     

    You will be please to know that this is far easier when deploying Vista

    Tuesday, November 27, 2007 10:11 PM
  • Hi

     

    I have tried this and it doesn't make any difference. The wrong mass storage driver is still installed - as I described I checked the driver actually referenced on the BSOD computer.

     

    I need to know why I can't select the driver (that works during manual installation) in the TS apply driver package dropdown box.

     

    Yeah - I love the deployment improvements in Windows Vista as well, but alas at this time the customer I'm working for are not ready for "next gen".

     

    Thanks.

     

     

    /Ragnar

    Wednesday, November 28, 2007 6:31 AM
  • Hi

     

    Facing the exact same problem.

     

    Unable to choose the SATA ACHI driver from the Apply Driver Package and BSOD error.

     

    I have opended a case with MS (10 days ago).

     

    Will report back with more info.

     

    erik

    Wednesday, November 28, 2007 6:51 AM
  • Excellent. Really looking forward to your results! Smile

     

    Ragnar

     

    Wednesday, November 28, 2007 7:08 AM
  • It looks like that drop down box on the Apply Driver Package TS action only allows you to select drivers where Class=SCSIAdapter. The AHCI drivers you're talking about in this thread have Class=hdc by default.

     

    I was able to get the AHCI drivers to work by following these steps:

     

    1. Delete the nonfunctional Intel AHCI & RAID Controller drivers from my Drivers list in SCCM

    2. Extract the downloaded mass storage drivers to a temp directory

    3. Edit the iaahci.inf file by changing the line that says Class=hdc to instead say Class=SCSIAdapter

    4. Import the driver into SCCM, add to the appropriate driver package and update my DP

    5. Edit my Apply Driver Package TS to select the appropriate AHCI driver

     

    Messy, but it works.

     

    Wednesday, November 28, 2007 5:21 PM
  • Thanks - it worked fine!

     

    However I'm really looking forward to the MS support results - could be that the SCCM driver import doesn't work as good as it should.

     

    /Ragnar

    Wednesday, November 28, 2007 6:31 PM
  • Hi, thanks

     

    Yes it worked perfectly

     

    The final respone from ms:

     

    Sorry for the delay in response.

     

    It looks like we being too restrictive with what types of devices we show as boot critical drivers.  We restricted the list to only SCSIAdapter drivers and it looks like we should be showing HDC drivers as well.  You can fix by performing the below workaround, but we have considered fixing this in SCCM SP1.

     

    To get the AHCI drivers in TS please do the following steps:

     

    1.       Edit the iaahci.inf file and change the line Class=hdc instead Class=SCSIAdapter.

    2.       Import the driver into SCCM driver node and add to the appropriate driver package and update the DP.

    3.       Edit my Apply Driver Package TS to select the appropriate AHCI driver under model

     

    Here is a post on the Forums with a similar issue (http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2469344&SiteID=17). 

     

    Please try the above steps and let me know the result.

     

    ******************

    End

     

     

    Br

    erik

    Thursday, November 29, 2007 1:23 PM
  • This worked for me, thanks guys
    MCSE
    Thursday, November 18, 2010 4:20 PM