Speed may not be the issue with AHCI, but at least in earlier Windows versions, AHCI was reportedly needed (or not) to use Windows TRIM. If that is true of Win 10, then you should enable AHCI. My Prime 370-A came out of the box with AHCI set, so unless you have changed it, your host controller should be able to use it. To see if Windows has loaded an AHCI driver, look in device manager under ATA/ATAPI controllers for an AHCI controller. If none is there, you will need to set it in uefi, with the caveat mentioned in my post above.
To see if TRIM is enabled you need to open an elevated command prompt (CMD in search box to bring up Command Prompt icon, right click on that and choose run as administrator from the drop down) and type:
fsutil behavior query DisableDeleteNotify
hit return and if it returns:
DisableDeleteNotify = 0
then TRIM is enabled.
Google should have brought you to a number of reports from people who have your drive who have had similar problems and seem to have resolved it by using a mysterious ritual as follows:
set an open Windows session to boot at the next boot so that it boots into safe mode
restart
enter uefi prior to the loading of Windows safe mode and set your controller to AHCI
close UEFI and allow to fully boot into safe mode
restart
I have no explanation for why that might work, except that there may be an installed driver that is hijacking Windows recognition of your drive and plugging it into the AHCI controller driver. Safe mode may bypass that and let Windows do its thing.