F5F Stay Refreshed Hardware Desktop It occasionally halts unexpectedly, but functions properly when used as the main boot drive after a reboot.

It occasionally halts unexpectedly, but functions properly when used as the main boot drive after a reboot.

It occasionally halts unexpectedly, but functions properly when used as the main boot drive after a reboot.

J
Jetfact14
Member
Find
193
07-28-2020, 04:13 PM
#1
I recently acquired a new PC with a motherboard named ROG STRIX B550-A GAMING. It features two M.2 ports—one for PCIe 4.0 x4 and another for PCIe 3.0 x4, which seems to share the bandwidth with the GPU. My previous SSD was a GIGABYTE NVMe 256GB drive identified as gp-gsm2ne3256gntd. The new one is a WD Black SN850 1TB M.2 PCIe NVMe (WDS100T1X0E). According to the manufacturer, the first model is PCI-Express 3.0 x4, while the second supports PCIe 4.0 x4, so they should function together. This appears to be the case—they do work... until they stop. After putting the PC together, I booted with the old SSD and everything operated smoothly. All devices were recognized, and everything was fine. I planned to install a fresh Windows 10 copy on the new drive, but the process proved challenging. Many installation attempts failed, possibly due to using a USB drive for the setup. After disconnecting other drives and installing half of Windows via command prompts, the system booted correctly onto the new SSD. I transferred files from the old drive, left the machine idle overnight, and then tried copying more data. It eventually told me "A device which does not exist was specified." Restarting didn’t help, nor did any online guides. The CHKDSK utility couldn’t be used, and formatting the drive was impossible. It displayed errors repeatedly but wouldn’t respond. My SSD had already written about 30 TB, exceeding its advertised 300 TBW rating. Swapping the M.2 slots didn’t alter anything. Disconnecting and reconnecting the drive offered no relief. I tried booting from the old SSD again—it worked before installing Windows on the new one, possibly because it was functional earlier. After a few attempts, it finally booted normally using the old drive. I then used it for an entire day, left it overnight to train neural networks, and everything functioned perfectly. Both drives operated without issues when connected to the old one. However, after a crash menu appeared, selecting another OS forced a restart, which then successfully booted from the old SSD. This process confirmed its reliability. I formatted the old drive thoroughly and ran CHKDSK, but it remained unresponsive. The drive eventually stopped working two days ago. I used it for several hours before encountering a black screen during a Windows update. I had to force shutdown, then restart multiple times, but each attempt failed. Eventually, after a crash menu, booting from the old SSD succeeded again. Once restored, the old drive displayed correctly. I copied essential files and performed a full format afterward. The drive still exhibited the "device not found" error when accessed through Explorer, even if I navigated quickly. This issue remains puzzling—no clear solution has emerged despite extensive troubleshooting. Online searches yielded few relevant results, suggesting this might be an uncommon or complex problem. It’s frustrating because having extra storage is beneficial, but the drive continues to malfunction.
Reply
Reply
J
Jetfact14
07-28-2020, 04:13 PM #1

I recently acquired a new PC with a motherboard named ROG STRIX B550-A GAMING. It features two M.2 ports—one for PCIe 4.0 x4 and another for PCIe 3.0 x4, which seems to share the bandwidth with the GPU. My previous SSD was a GIGABYTE NVMe 256GB drive identified as gp-gsm2ne3256gntd. The new one is a WD Black SN850 1TB M.2 PCIe NVMe (WDS100T1X0E). According to the manufacturer, the first model is PCI-Express 3.0 x4, while the second supports PCIe 4.0 x4, so they should function together. This appears to be the case—they do work... until they stop. After putting the PC together, I booted with the old SSD and everything operated smoothly. All devices were recognized, and everything was fine. I planned to install a fresh Windows 10 copy on the new drive, but the process proved challenging. Many installation attempts failed, possibly due to using a USB drive for the setup. After disconnecting other drives and installing half of Windows via command prompts, the system booted correctly onto the new SSD. I transferred files from the old drive, left the machine idle overnight, and then tried copying more data. It eventually told me "A device which does not exist was specified." Restarting didn’t help, nor did any online guides. The CHKDSK utility couldn’t be used, and formatting the drive was impossible. It displayed errors repeatedly but wouldn’t respond. My SSD had already written about 30 TB, exceeding its advertised 300 TBW rating. Swapping the M.2 slots didn’t alter anything. Disconnecting and reconnecting the drive offered no relief. I tried booting from the old SSD again—it worked before installing Windows on the new one, possibly because it was functional earlier. After a few attempts, it finally booted normally using the old drive. I then used it for an entire day, left it overnight to train neural networks, and everything functioned perfectly. Both drives operated without issues when connected to the old one. However, after a crash menu appeared, selecting another OS forced a restart, which then successfully booted from the old SSD. This process confirmed its reliability. I formatted the old drive thoroughly and ran CHKDSK, but it remained unresponsive. The drive eventually stopped working two days ago. I used it for several hours before encountering a black screen during a Windows update. I had to force shutdown, then restart multiple times, but each attempt failed. Eventually, after a crash menu, booting from the old SSD succeeded again. Once restored, the old drive displayed correctly. I copied essential files and performed a full format afterward. The drive still exhibited the "device not found" error when accessed through Explorer, even if I navigated quickly. This issue remains puzzling—no clear solution has emerged despite extensive troubleshooting. Online searches yielded few relevant results, suggesting this might be an uncommon or complex problem. It’s frustrating because having extra storage is beneficial, but the drive continues to malfunction.

Reply
Reply