Hi! I have been experiencing this weird issue lately, where my M.2 SSD seems to temporarily bug out. Windows will start giving out "A device which doesn't exist was specified" for actions with files on the drive. However this usually does not affect the whole drive, just certain dirs, and I can work normally with the rest. If I restart, the drive vanishes completely even from BIOS, and I have only been able to return it by unplugging the power cable and holding the power button for a few seconds. After this it returns and continues to work normally.
So far it has only happened occasionaly, when I am running a specific heavy AI tool which can stress the system to near freezes, and sometimes causes this drive error.
Things I have tried so far:
- sfc /scannow - no errors
- chkdsk - no errors
- updating and reinstalling drivers on anything and everything
- re-seating the SSD
- moving the SSD to a different slot
So far none of this has had any result. This isn't a crippling problem, but seems kinda weird and I am very curious to know if someone has encountered something similar?
System spec:
- Ryzen 3700X
- RTX 3070 TI
- Asus TufGaming B550 Plus
- 4 x 8 Gb 3200MHz HyperX Fury DDR4
- Samsung 990 Pro 2Tb PCIE SSD (the one in question)
- Windows 10 Home os
So far it has only happened occasionaly, when I am running a specific heavy AI tool which can stress the system to near freezes, and sometimes causes this drive error.
Things I have tried so far:
- sfc /scannow - no errors
- chkdsk - no errors
- updating and reinstalling drivers on anything and everything
- re-seating the SSD
- moving the SSD to a different slot
So far none of this has had any result. This isn't a crippling problem, but seems kinda weird and I am very curious to know if someone has encountered something similar?
System spec:
- Ryzen 3700X
- RTX 3070 TI
- Asus TufGaming B550 Plus
- 4 x 8 Gb 3200MHz HyperX Fury DDR4
- Samsung 990 Pro 2Tb PCIE SSD (the one in question)
- Windows 10 Home os
Last edited: