NVMe Drive disconnecting with sustained load

I have a: ADATA SX8100NP 4000.7 GB connected to x570 Taichi AsRock Mobo in the 3rd slot.

It throws this error and becomes unreadable/unwritable:
“An error was detected on device \Device\Harddisk5\DR5 during a paging operation.”

After some minor testing it seems to do this when Dropbox hits it with insane IOPS when indexing because dropbox sucks and has to reindex for no reason…
I disabled dropbox and can copy files off (~800GB) in sustained operation to a spinning platter no prob.

Any thoughts?

I think next step is to try a separate NVMe slot, perhaps the chipset is being overloaded and it is causing the drive to disconnect?

The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume6.

       Failure status: A device which does not exist was specified.

       Device GUID: {071af6fe-86ac-cedd-4a7a-9d4bae19c0bc}
       Device manufacturer: 
       Device model: ADATA SX8100NP
       Device revision: VB411D51
       Device serial number: 0000_0000_0100_0000_4CE0_0018_DD8C_9084.
       Bus type: NVMe

       Adapter serial number: 2K23291H9D2F        _0001

Checked thermals? Disable pcie4 aer with kernel param or bios option?

Thermals seem fine when it’s running. 38c which is lower than my other drives. It has the mobo heat spreader on it too FWIW.

I’ll try disabling 4.0, though I’d love to keep it for boot/game drive.

Had no issues until Dropbox needed to reindex.

I forced Gen3 speeds on x16, x8, and Chipset.

CrystalDiskInfo still reports Gen4.0 speeds on my G4 NVMe drives.
Drive in question is running at 3.0 speeds.

I updated bios firmware to P4.40

Drive works fine (3k MB/s R/W, 60/140 MB/s 4k Q1D1) after reboot prior to letting Dropbox talk to it. Once I let Dropbox ‘index’ even for a sec, the drive becomes unwritable and unreadable except for file structure.

Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 - Unexpected parameters

{Delayed Write Failed} Windows was unable to save all the data for the file E:\$Mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

This topic was automatically closed 273 days after the last reply. New replies are no longer allowed.