Win 8.1 Update 1 --> LSI Driver = Code 10

Question

Prior to the Update 1 for Win 8.1 there is was no issue with the "LSI Adatper, SAS2 2008 Falcon" driver.  The device is a IBM M1015 cross flashed using the "IT Firmware" as LSI 9211-8i.  Post the update the drive "Code 10"'s.  You can Disable / Enable the driver in Windows Device Manager and it is then fine but on the next reboot it will "Code 10" again.  

I've tried:

• Updated the MB BIOS to the latest version
• Updated the card to the latest LSI IT FW/BIOS & Driver
• Uninstalled / Reinstalled in Safe mode
• ...even purchased a new PSU incase it was flaky 

If I rollback to prior to Update 1 then it is fine.

If I reboot the PC it will Code 10, but many times it will load correctly if I do a Cold boot (power down, power up).

Thanks

Nathan

Answer 1

Hi,

Uninstall the driver with "Delete driver" option, restart and then install the latest driver.

Reference:

http://support.microsoft.com/kb/943104/en-us

Thanks - already tried this and the result is the same.  I've tried:

• Uninstall & Delete driver: then rescan (installs an earlier driver and is fine till the next reboot then Code 10)
• Uninstall & Delete driver: then reboot (Win 8.1 installs the driver during the install and it is Code 10)

Nathan

Answer 2

I've not even got the update to work.

will the folk at Redmond issue a patch.  I've done the DISM things, tried the downloaded patches, prayed!, But to no avail/

so much frustration.

Answer 3

Hi,

Uninstall the driver with "Delete driver" option, restart and then install the latest driver.

Reference:

http://support.microsoft.com/kb/943104/en-us

Answer 4

I thought I was going crazy but I am having the exact same problem. Good thing I only upgraded one of my servers.

Answer 5

It's not the fault of your device, it's Windows 8.1 update. It is not compatible with not only this device but many devices have failed after installing the latest update.

My advice would be to not install this update but wait for any confirmation from the manufacturer for any updated drivers which support this latest Windows misery.