I have purchased and installed internally to my Desktop free SATA port a new 1 TB SSD, which correctly shows capacity in Win 10 file explorer but can only write 128GB? However when I start copying data to it (mainly Steam Apps moved across using the Steam Move facility, once it gets to around 128Gb of data it then fails with write errror and he disk is no longer seen in Explorer. I have to recover the SSD using Chkdsk /r which takes about 12 hours !! Then when I try again the same thing happens.
I consider myself a reasonably competent power user for PCs and Windows and go right back to even 386 computers !! I have never had any problems similar to this with installing a new extra SATA SSD drive. I have checked the BIOS and ensured there is no pagefile problem (windows manages this on the main M2 C Drive) . I am at a loss as to why and a good friend of mine, also an IT guy, is also baffled. I have checked my Windows installation with sfc /scannow and that did correct a small error but that was corrected and now reports good integrity yet this new drive still fails.
I have searched for an answer but all problems others report seem to be with File Explorer only reporting a smaller size which is usually an easy to solve problem. But this drive is correctly reported as a full about 960 GB but will only write up to 128GB when it slows right down and then crashes no longer visible in File Explorer or Disk Management. I do eventually get to see it and run chkdsk /r so the drive can be recognised and reformatted into NTFS but then fails again when i write more than 128GB of data to it.
Any help most appreciated. Oh and yes I sent two new SSD drives back and then brought a different make (Sandisk Ultra) from a different supplier and the same thing happens in all cases so it is clearly not a faulty SSD drive ???? Oh and I have also updated the BIOS on my Gigabyte H410M H V2 motherboard to the latest F4 version but same problem remains ??????
I have never before been so baffled as to why thus is happening and my Kaspersky AV shows no viruses either. Without this new drive installed my system is working normally and pretty fast (i3 10400f cpu, 16GB RAM, Aorus GTX1080Ti 11GB graphics card).
I consider myself a reasonably competent power user for PCs and Windows and go right back to even 386 computers !! I have never had any problems similar to this with installing a new extra SATA SSD drive. I have checked the BIOS and ensured there is no pagefile problem (windows manages this on the main M2 C Drive) . I am at a loss as to why and a good friend of mine, also an IT guy, is also baffled. I have checked my Windows installation with sfc /scannow and that did correct a small error but that was corrected and now reports good integrity yet this new drive still fails.
I have searched for an answer but all problems others report seem to be with File Explorer only reporting a smaller size which is usually an easy to solve problem. But this drive is correctly reported as a full about 960 GB but will only write up to 128GB when it slows right down and then crashes no longer visible in File Explorer or Disk Management. I do eventually get to see it and run chkdsk /r so the drive can be recognised and reformatted into NTFS but then fails again when i write more than 128GB of data to it.
Any help most appreciated. Oh and yes I sent two new SSD drives back and then brought a different make (Sandisk Ultra) from a different supplier and the same thing happens in all cases so it is clearly not a faulty SSD drive ???? Oh and I have also updated the BIOS on my Gigabyte H410M H V2 motherboard to the latest F4 version but same problem remains ??????
I have never before been so baffled as to why thus is happening and my Kaspersky AV shows no viruses either. Without this new drive installed my system is working normally and pretty fast (i3 10400f cpu, 16GB RAM, Aorus GTX1080Ti 11GB graphics card).