Connecting Quest to PC stops second NVME drive from working

[Morro82]

Every time I connect my Oculus Quest 2 to my PC using the official Link cable, my second NVME drive in slot m.2_2 stops working (you can read the file structure but not write to the drive or open any files in it) 

Once I reboot the drive is accessible again, but the fault will repeat if I plug in the Quest.

 

There are no other fault symptoms or error messages of any kind.

I did try the newest beta BIOS but it didn't fix the fault and introduced other issues while gaming, so I used the flashback to return to the stable version.

• Windows 10 Home 64 bit
• Asus Crosshair VIII Hero (BIOS version 3003, latest non beta)
• Ryzen 5600X
• 4x8GB Trident Z NEO (3600MhZ CL16)
• MSI RTX 3080 Ventus 3X OC (stock)
• M.2_1 Samsung 970 EVO (1TB) boot drive
• M.2_2 Sabrent Rocket 4.0 (2TB) Storage drive
• Fractal Design Ion (850W 80+ Platinum)

[Morro82]

Other things tested:

 

Chipset drivers re-installed

GPU drivers removed using DDU and re-installed latest version

Sabrent Rocket 4.0 tested using Sabrent control panel

USB storage devices connected using the USB-C connector do not replicate the fault

I have tried multiple USB-C and USB-A on my motherboard, the fault persists on all

 

EDIT* Looking through the event log I have noticed this right around the time of Quest connection:

 

"The driver detected a controller error on \Device\RaidPort3."

 

[Morro82]

This appears to be linked to the AMD 500 series chipset issue. 

 

I have contacted AMD and will update if/when they respond.

[A.Hruskach]

On 1/29/2021 at 3:47 AM, Morro82 said:

Other things tested:

 

Chipset drivers re-installed

GPU drivers removed using DDU and re-installed latest version

Sabrent Rocket 4.0 tested using Sabrent control panel

USB storage devices connected using the USB-C connector do not replicate the fault

I have tried multiple USB-C and USB-A on my motherboard, the fault persists on all

 

EDIT* Looking through the event log I have noticed this right around the time of Quest connection:

 

"The driver detected a controller error on \Device\RaidPort3."

 

I was thinking it could be PCIe Lane allocation to your processor. Read this article, they explain it better.

https://www.guru3d.com/articles-pages/amd-ryzen-5-5600x-review,3.html

[Morro82]

On 2/23/2021 at 2:39 PM, A.Hruskach said:

I was thinking it could be PCIe Lane allocation to your processor. Read this article, they explain it better.

https://www.guru3d.com/articles-pages/amd-ryzen-5-5600x-review,3.html

I've tried running both M.2 Drives and the GPU at Gen3 speed, the issue persists.

[A.Hruskach]

On 3/11/2021 at 9:18 AM, Morro82 said:

I've tried running both M.2 Drives and the GPU at Gen3 speed, the issue persists.

Its not the generation that matters, its the PCIe lane allocation. If you have intergrated graphics, use that, then remove your GPU. Your GPU is likely to be taking up most of the PCIe lanes, not leaving enough for the two NVMe drives. Refer to the "best solution" in this link. It explains it better. https://forums.tomshardware.com/threads/pci-e-lanes-issue-ryzen-5-3600-msi-b450m-pro-vdh.3548278/