I believe I found the problem. The drive is not detected correctly, and is showing up as a RAID SCSI device instead. Now....how do I correct that...?
MOBO: Aorus x399 Extreme (F5g BIOS)
CPU: AMD 2950X
RAM: 32 GB Aorus RGB
GPU: EVGA 1080ti in SLI
Storage: 3x Samsung 970 NVME
Power Supply: Corsair AX1200
So what's happening is that I'm trying to install the Aorus RGB AIC NVME SSD card that was recently released. I have my two video cards running in SLI with no problem, latest NVIDIA drivers installed. One card is in PCIe x16 slot 1 and the other is in slot 3, as recommended in the motherboard documentation. I'm installing the new NVME in slot 2, should be x8. Upon doing so and booting the system I get a message in the device manager that there is a problem with the bottom gpu and it has been stopped [Windows has stopped this device because it has reported problems. Code 43], and SLI is disabled at this point as well of course. The NVME SSD is installed and recognized, running with no issue. I've reinstalled both my graphics cards and the SSD several times and it always comes back to detecting a problem.
Things I have tried:
Moved card to very bottom x8 slot on motherboard - this actually will disable the other gpu instead.
Flashed to newest BIOS
Changed PCIe settings in BIOS from Auto to Gen 3
Changed PCIe settings from x8 to x4 + x4
Changed PCIe settings from x16 to x8 + x8
Reinstalled NVIDIA graphics drivers
Installed NVME specific drivers
I consider myself fairly tech savvy and have been building custom PCs for years, but this one has me stumped. It was suggested in a Facebook group that I may have maxed out the number of PCIe lanes, but since this board supports 4x SLI and would use the same number of lanes in that configuration that I am attempting to use, I don't see how that could be possible. Any and all help/advice is greatly appreciated.
I believe I found the problem. The drive is not detected correctly, and is showing up as a RAID SCSI device instead. Now....how do I correct that...?
Not necessarily, which storage controller is it using?
had my PM981 showing as SCSI in windows 7.
Try to see wih CrystalDiskInfo or HWINFO
Looks to me more like conflict between resources.
EDIT: check even log if you can see there anything
Last edited by Chike; 06-15-2019 at 01:35 PM.
CrystalDiskInfo actually doesn't detect the drive at all, see the screenshot below. I have it formatted and setup as A: (Gaming 3) within Windows. Unfortunately I don't really understand what this means, or where to go from here.
![]()
That is the first drive CrystalDiskMark finds, click the "play" button to show the next drive and so on
Also What storage controllers installed? (down in device manager)
BTW how hot those 970 Evo get?
Pressing the play button only cycles through the drives you can see listed, it never moves over to show any additional drives.
List of storage controllers is in the screenshot. Second shot below is from WWiNFO.
Gigabyte sent me a new BIOS version to try, F5i, but it didn't resolve the issue.
I'm not really sure how hot the drives get, never paid any attention, lol. I'll see if I can grab a temp after some gaming.
![]()
Did they try it with 2 grapic cards n the x16 PCIe slots, preferably the same cards?
Make sure they understand the actual problem.
At what configuration the SSD works? Are they any RAID setting in BIOS?
They did, as I reported the problem as the AIC screwing with my SLI configuration that was the first thing they attempted to replicate was just the AIC and SLI.
I'm trying, but honestly I'm not sure what the actual problem is. I know the symptoms and keep reporting back what happens when they have me try different things, but nothing has fixed the issue.
Sorry, I don't understand what you mean by this.
There are RAID settings in the BIOS, although very limited, and they are all disabled.
If it's working, then it will show in HWiNFO and CrystalDiskInfo, what do you see there?
If all RAID options are disabled why is it recognized as AMD-RAID? Try to remove the drver, then remove the the second GPU, reset BOIS laod defaults and reboot see if it finds the right driver.
There are currently 1 users browsing this thread. (0 members and 1 guests)