Thanks for your reply, i have posted on Reddit and other tech sites and yours is the first response I've had.
Did you perform a fresh installation of windows to the sabrent 1TB m.2. Can I assume this is your boot drive? How is this disk formatted? MBR, GPT?
How are the other disks formatted? Do they include multiple partitions, etc?
FYI the problems I have encountered only began once I plugged in the new 3080 GPU a few weeks ago. I had been running this same build with a 1070 for about 3 months without an instance of this happening?
I did perform a fresh install, although I had a few issues with the installation (think I set it as MBR initially and had issues with partitions on the drive, I was helped by someone on Win10 forums).
This is my boot drive, it is formatted GPT and has 3 partitions - 100mb EFI System / 930.90GB Boot, Page File etc / 513mb Recovery Partition.
All my other drives are formatted GPT and NTFS with only a single volume on each one.
You are running a windows 10 insider preview build. This is not recommended for a production system. Results might vary.
I was not aware I was running an Insider Build? I got W10 free when it first launched back in the day, and just transferred the licence across so not sure how I've ended up on an Insider Build??!
BIOS rev is? ... F22 or lower might be the best option for your 3700X
Around September when I did the build, I updated to what was the latest (R2?). Then when I started getting these issues early January I upgraded to what was latest available thru the Gigabyte @BIOS app which is R30. This issue began on R2 and has carried on thru R30.
What operate mode for the storage controller are you using?
I'm not sure what you mean by this - sorry my tech knowledge is limited to plugging things in and crossing my fingers.
EDIT: I looked in BIOS and all i could see was a reference to Sata mode which was AHCI?
From an installation standpoint your configuration looks correct, but you have quite a mix of hard drive technologies.
Its always best to use items on the QVL for your system. This includes memory, storage, etc.
Some are drives from the very old build I had (SSDs) and a couple are more reason large drives i wanted for video capturing and games etc.
The drives are all either Seagate Barracudas or Samsung EVOs which are well established drives.
One thing I never recommend is initializing a disk that is formatted and contains data that I might have moved from another system. As you indicated, that ship has sailed.
Yup, sadface.
![Sad :(](http://forum.giga-byte.co.uk/Smileys/default/sad.gif)
Next steps, Answer the questions above.
Then remove the disks which continue to drop off or become unformatted. Verify your BIOS settings and confirm the system is stable. 24 hrs.
Add a disk, just 1. Use diskpart to select, clean and format. I prefer GPT, but you can use MBR if you wish. Run for 24 hrs, performing normal restarts.
Continue this process adding 1 new disk each time. This will require time and some patience.
Note, other options might be indicated should your answers bring other unknown information to light.
I'll try that. I'm not sure what settings to check in the BIOS though with this regard -
one other thing I have noticed since the GPU was installed is that I used to see the Aorus eagle symbol on the black screen (POST screen) prior to the windows screen with my 1070. With the 3080 plugged in my monitor doesn't detect a signal until I get to the Windows login screen.
If I stab the delete button nothing loads and I get an A6 error message on the mobo light which apparently relates to SCSI device, whatever that is.
Again, only happened once I plugged in new GPU.EDIT: Have just noticed after posting the message, when I restarted PC, I had my second monitor switched on for the first time in ages and the POST Aorus logo appeared on monitor 2 before Windows appeared on Monitor 1 (my main monitor). The old 1070 used to just output both to the main window.
When I hit delete at the logo, I went into BIOS and saw the A6 code on the mobo light up so I guess that just comes up when you go into BIOS?
Ok, I'll do what you suggested and remove all the drives that are affected and run it for a few days without them plugged in.
Thanks again for taking the time to respond.