BSOD after updating the Intel(R) C610 series/X99 chipset 6-Port SATA AHCI Controller - 8D02 Driver

Ragahv

Distinguished
Dec 30, 2012
198
0
18,690
I am trying to update the 2 drivers:

Intel(R) C610 series/X99 chipset 6-Port SATA AHCI Controller - 8D02

and

Intel(R) C610 series/X99 chipset sSATA AHCI Controller - 8D62

I currently have an old version installed and i want the new one which was made in 2016. The old one was made in 2013.

I think it may improve performance and increase stability. - Does anyone know what the Intel(R) C610 series/X99 chipset sSATA AHCI Controller - 8D62
updated driver may do? I want to know exactly why the update was released and why people update when you dont even notice any changes while playing games like battlefield 4 and perform disk (SSD) transfers.

I may have less issue when i install the driver.

Also i use this utility : Auslogistics driver update (latest version).

I perform a scan and the software finds the sata controller driver:
Intel(R) C610 series/X99 chipset sSATA AHCI Controller - 8D62

and install succesfully. After install, the computer restarts and upon boot of windows 7 before i see logon screen, i get the blue screen of death indicating there is a fualt with the driver install or there is a boot virus. I scan my pc with best AV and nothing is found. The bsod is not boot virus , its just a corrupt driver and im sure that driver is corrupted install and every driver i install is, corrupt for only Intel(R) C610 series/X99 chipset sSATA AHCI Controller - 8D62
device.


 
Solution
Some sata and usb driver updates may require a bios update as well.
Also some motherboards might require that you use the driver they provide. Chips can have logic bugs that require certain drivers to work around the problem. The motherboard vendor knows what version of chips they used.
Some sata and usb driver updates may require a bios update as well.
Also some motherboards might require that you use the driver they provide. Chips can have logic bugs that require certain drivers to work around the problem. The motherboard vendor knows what version of chips they used.
 
Solution