leadsgogl.blogg.se - Amd ahci raid controller driver windows 10

#Amd ahci raid controller driver windows 10 drivers
#Amd ahci raid controller driver windows 10 update
#Amd ahci raid controller driver windows 10 Pc
#Amd ahci raid controller driver windows 10 windows 7

If you can find 1E03 in your inf file you know you have the right driver :-) In this example the device ID is DEV_ 1E03 or just 1E03. To list all devices in those classes use these commands: devcon listclass SCSIAdapterĮxample of result: ePCI\VEN_8086&DEV_1E03&SUBSYS_21FB17AA&REV_04\3&21436425&0&FA: Intel(R) 7 Series Chipset Family SATA AHCI Controller If your storage controller is connected to the computer, it will be located in the device class SCSIAdapter or HDC. To find Device ID, which might be needed to find the right driver (the device ID is listed in the inf file), you can use the console util devcon.exe (a tool part of the MS Windows Driver Kit package). Windows now booted with this RAID driver :-)

Start Windows in safe mode with a command prompt (F8 if you can make in time!). Rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 132 %~dp0iaStorA.inf In my case is was:ģ: I create the file install.cmd with this content:

#Amd ahci raid controller driver windows 10 drivers

The device ID of this SATA RAID controller is 2826ġ: Make a USB key, in my case I had GPT partition.Ģ: Copy drivers to the key. When I changed the SATA controller mode to RAID in BIOS Windows booted into a blue-screen: Inaccessible boot deviceĬhipset: Intel C232 (i believe this will work with C236 too and more) The following has been tested on Windows Server 2016, which was installed with SATA in AHCI mode. You can prepare Windows for a new storage driver on next reboot using this command: rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 132 %~dp0NewDrv.inf In linux the lspci command shows this info. The most reliable info is to set the controler to RAID mode, boot some OS (Linux comes in small handy formats) and check the PCI id there. You can also try to look it up on this web site. * the 1002/4392 is the PCI id of the RAID controller when set to RAID mode.

#Amd ahci raid controller driver windows 10 update

(after it worked, I went to Device Manage again and set the driver for IDE controller back to the correct one: Update driver, select automatically.)

restart, in BIOS change mode again to RAID.

start "regedit" and in key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1002&dev_4392 change the value Service to ahcix86s (see note below).

set RAID controller mode back to AHCI in BIOS.

boot Windows, fails again, the same way as before.

Reboot, set RAID controller mode to RAID in BIOS and select the above INF file and then the driver. Then in Device Manager I selected to Update the driver of the IDE controller, "let me select the driver", Have disk.

in the RAID driver INF file (ahcix86s.inf) I added a line with this ID:īefore: %NapaDesc%=Napa_Inst,PCI\VEN_1002&DEV_4392.

in Device Manager I looked up the PCI ID of the IDE controller (it was 439C) (select Properties on the controller, the ids are on the tab Details, under HardwareId in dropdown menu).

I picked the (unused) IDE controller as a scapegoat for the RAID driver.

Try to boot Windows, it fails (it reboots during startup, no error message is visible)

I added 2 more hard drives (connected them to the RAID controller ports), set RAID controller mode to RAID, and set up some RAID arrays on the 2 new HDs (all this in BIOS setup).

#Amd ahci raid controller driver windows 10 windows 7

RAID controller set to AHCI mode, Windows 7 installed on the first (and only) HD.

additional IDE/SATA controller with 2 ports (for eSATA and optical drive, I guess) (from now on "IDE controller").

one hard drive connected to the RAID controller.

#Amd ahci raid controller driver windows 10 Pc

a PC with an AMD SB820M chipset - 4 SATA/RAID ports (I'll refer to this controller as "RAID controller" from now on).

As I did several tries, I can not be sure what steps are necessary and what not, so I'll list everything I did.