New
#11
Have you checked the boot order in your bios? If the system is looking on every drive for boot files that would cause your delay.
Have you checked the boot order in your bios? If the system is looking on every drive for boot files that would cause your delay.
I hope the OP didn't get offended ? But if he comes back, I have a similar setup on my rig and also have a similar enclosure and have no issues in booting the system. I believe his BIOS must be searching all of the disks, and at BIOS time, no driver has been loaded yet. I didn't check his MB, it may not have support for the E-Sata card he has installed. There maybe a BIOS update and I would have him check into that.
There are two log collectors: DM and BETA
At some time the BETA log collector will replace the DM log collector.
The BETA log collector will collect more useful logs.
Please run the BETA log collector near the bottom half of this web page and post a zip into this thread.
BSOD - Posting Instructions - Windows 10 Forums
(extract all > open)
1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
Go into bios and disable the oprom for asmedia 1061.
It is under advanced menu asm1061 oprom ---> disabled.
The oprom reacquired when u boot from this controller and the bios try to scan the drive to find out if u have an os installation there.
So for an esata data drive it must be disabled.
Also for the hot-swap and windows fast boot to work reliably u need the driver 3.2.3.0 that already installed.