New
#41
Yeah, I was wrong there. Still the reasoning to use ports 0 and 1 is still valid to get the benefit of the native chipset controller. Until the new Intel Z87 chipset there was native support for just 2 SATAIII ports, the rest coming from 3rd party once, Z87 can run up to 6. I'm unsure how AMD works.The BIOS may or may not enumerate disks in a specific order. There is no direct relationship between the BIOS order, and the order in which Windows numbers the disks. During startup, Windows switches from using the BIOS INT13 support to native Windows drivers to access disks. Windows waits for several seconds for the system disk to enumerate through Plug and Play. When there is a match within the time-out period, normal startup will proceed. Otherwise, the system will trigger a bug check with Stop error code of 0x7B. Windows uses other mechanisms to differentiate disks, as Windows has no control over the disk-numbering process before startup. Windows has no information about any changes to hardware when the computer is turned off. Therefore, Windows initiates its own query for device enumeration.
I have done my own tests and using anything other than the native controller results in very noticeable performance drops, in the time it takes apps to open, rendering an image, transcoding video, to reboot times.
Still all this doesn't explain why the OP's drive drops out.
(jumanji, that thread is so old it's grown a long beard. That was when I had been here just a few months.)