F5F Stay Refreshed Hardware Desktop Resolving connection problems with two fresh M.2 SSDs on my Lenovo LOQ 16

Resolving connection problems with two fresh M.2 SSDs on my Lenovo LOQ 16

Resolving connection problems with two fresh M.2 SSDs on my Lenovo LOQ 16

R
Roccoboy8
Member
162
07-09-2016, 12:52 AM
#1
Hi there! You've had some trouble with your new storage setup. After installing the Kingston and Lexar drives, everything seemed to work at first. However, during stress tests, the data read back as zeros, and even after checking the partition manager, the SSDs displayed as "RAW" and vanished. You tried a few fixes—swapping the OS drive, checking BIOS support, cleaning the drives, and scanning for errors—but nothing resolved the issue. What might be causing this? It could be a hardware problem or a driver conflict. Consider testing with another operating system to rule out OS-specific issues. If it persists, contact Kingston or Lexar support for further assistance.
R
Roccoboy8
07-09-2016, 12:52 AM #1

Hi there! You've had some trouble with your new storage setup. After installing the Kingston and Lexar drives, everything seemed to work at first. However, during stress tests, the data read back as zeros, and even after checking the partition manager, the SSDs displayed as "RAW" and vanished. You tried a few fixes—swapping the OS drive, checking BIOS support, cleaning the drives, and scanning for errors—but nothing resolved the issue. What might be causing this? It could be a hardware problem or a driver conflict. Consider testing with another operating system to rule out OS-specific issues. If it persists, contact Kingston or Lexar support for further assistance.

F
Fernan_Gamer
Junior Member
40
07-16-2016, 07:51 AM
#2
Crystal disk mark hits SSDs pretty hard when doing the tests. So, unless you have a good reason, try not to abuse this feature. I think that your SSDs did overheat during testing and the controllers shut down at some point. If it was while writing on the partition table, it is possible that your SSDs went back to RAW because the partition got corrupted and was lost. What I'd try to if there was no important data on the SSDs is try to partition and format them again. Then try using them the old fashion way to copy some files. As for SSDs, I recommend using Crystal Disk Info instead of Crystal Disk Mark. Stress testing a NVMe SSD is not the best idea since they have a limited writing lifespan and can overheat, especially in laptops where cooling solutions are at a premium. Hope that helps
F
Fernan_Gamer
07-16-2016, 07:51 AM #2

Crystal disk mark hits SSDs pretty hard when doing the tests. So, unless you have a good reason, try not to abuse this feature. I think that your SSDs did overheat during testing and the controllers shut down at some point. If it was while writing on the partition table, it is possible that your SSDs went back to RAW because the partition got corrupted and was lost. What I'd try to if there was no important data on the SSDs is try to partition and format them again. Then try using them the old fashion way to copy some files. As for SSDs, I recommend using Crystal Disk Info instead of Crystal Disk Mark. Stress testing a NVMe SSD is not the best idea since they have a limited writing lifespan and can overheat, especially in laptops where cooling solutions are at a premium. Hope that helps

Y
YoukaiRuler
Junior Member
20
07-20-2016, 10:25 PM
#3
Hello! The temperatures appeared normal, tracked via Crystaldiskinfo (about 50°C during testing). This suggests the C: OS SSD controller might have failed, but it handled the workload correctly and gave accurate results. After allowing time for cooling, copying files still failed—only a few succeeded, then disks became unreachable. It seems there could be an issue with the slot or a BIOS problem. The system is running the latest version.
Y
YoukaiRuler
07-20-2016, 10:25 PM #3

Hello! The temperatures appeared normal, tracked via Crystaldiskinfo (about 50°C during testing). This suggests the C: OS SSD controller might have failed, but it handled the workload correctly and gave accurate results. After allowing time for cooling, copying files still failed—only a few succeeded, then disks became unreachable. It seems there could be an issue with the slot or a BIOS problem. The system is running the latest version.

Z
ZazaPanda
Member
151
07-21-2016, 04:26 AM
#4
Controllers differ in quality and can vary even between identical models from different manufacturers. You might have received a less efficient unit or the product may not have maintained its original durability. The slot and BIOS should function properly. The part nearing its capacity was likely the SSD, which probably caused the failure.
Z
ZazaPanda
07-21-2016, 04:26 AM #4

Controllers differ in quality and can vary even between identical models from different manufacturers. You might have received a less efficient unit or the product may not have maintained its original durability. The slot and BIOS should function properly. The part nearing its capacity was likely the SSD, which probably caused the failure.

V
Vinula
Junior Member
4
07-21-2016, 06:13 AM
#5
You're experiencing issues with your LENOVO LOQ 16APH8 after installing the Kingston KC3000 2TB drive. A new BIOS was released recently (LYCN39WW), which seems to have introduced problems mainly related to writing data to the disc. From Steam, you can download up to 1GB or 10GB, but then suddenly you encounter a "disc write error," causing the drive to lock up and preventing further writes. After a reboot, it recovers partially, but the issue persists when trying to write more data. A few reboots restore full functionality, though the drive still gets stuck during writes.
V
Vinula
07-21-2016, 06:13 AM #5

You're experiencing issues with your LENOVO LOQ 16APH8 after installing the Kingston KC3000 2TB drive. A new BIOS was released recently (LYCN39WW), which seems to have introduced problems mainly related to writing data to the disc. From Steam, you can download up to 1GB or 10GB, but then suddenly you encounter a "disc write error," causing the drive to lock up and preventing further writes. After a reboot, it recovers partially, but the issue persists when trying to write more data. A few reboots restore full functionality, though the drive still gets stuck during writes.