[SOLVED] My SSD and HDD keeps resetting to 'unallocated'. Please help.

Nov 23, 2020
19
0
10
0
So i built myself a new Ryzen 5800x PC and things went pretty well except for few hiccups such as unable to boot in UEFI mode which i fixed recently thanks to this forum. But now i have run into this new problem where my two storage devices. My 1tb Samsung evo SSD and WD blue 2 tb HDD keeps resetting to unallocated. It wiped my data three times now and i don't know what to do.

Hard disk sentinel and crystal disk info show both my SSD and HDD are healthy. No bad sectors. I have changed the wires too but the result is the same. My NVME and Seagate 1 tb is fine though. The problem is repeating itself with only these two storage devices over and over again. Someone suggested to use DMDE but i have no idea how to read it. Any help would be appreciated. Here are the screenshots of my two storage devices right after it got unallocated.





Any way to fix this annoying problem?
 
I have seen exactly the same problem in numerous threads. I'm convinced that there is a bug of some kind. AMD Ryzen CPUs, Gigabyte motherboards, and Windows 10 appear to be the common factors. Do you have a Gigabyte motherboard?

Notice the data pattern in sector 0. That's bogus data which has probably been written by the OS. I don't know why this happens, and I don't know where it originates, but the same pattern appears in other threads.

It appears that you have reinitialised your drives after the latest event. Please don't do that. That said, there is a simple recovery process involving a few clicks.

For your SSD, double-click the "SSD" volume and expand the $Root. Do you see your file/folder tree? If so, then r-click each of the "Microsoft reserved" and "Basic data" partitions and select "Remove the partition". Then r-click the "SSD" partition and select "Insert the partition (undelete)". Then select Drive -> Apply Changes.

For your WD HDD, r-click each of the "BCF" volumes and expand the $Root. Verify that these are your original partitions. If so, then remove each of the black GUID partitions (Microsoft reserved, etc) as before. Insert the "WD 1" and "WD 2" BCF volumes and Apply Changes.

Reboot and allow Windows to redetect your drives. This won't address the root cause of your problem, but will provide a painless recovery.
 
I have seen exactly the same problem in numerous threads. I'm convinced that there is a bug of some kind. AMD Ryzen CPUs, Gigabyte motherboards, and Windows 10 appear to be the common factors. Do you have a Gigabyte motherboard?

Notice the data pattern in sector 0. That's bogus data which has probably been written by the OS. I don't know why this happens, and I don't know where it originates, but the same pattern appears in other threads.

It appears that you have reinitialised your drives after the latest event. Please don't do that. That said, there is a simple recovery process involving a few clicks.

For your SSD, double-click the "SSD" volume and expand the $Root. Do you see your file/folder tree? If so, then r-click each of the "Microsoft reserved" and "Basic data" partitions and select "Remove the partition". Then r-click the "SSD" partition and select "Insert the partition (undelete)". Then select Drive -> Apply Changes.

For your WD HDD, r-click each of the "BCF" volumes and expand the $Root. Verify that these are your original partitions. If so, then remove each of the black GUID partitions (Microsoft reserved, etc) as before. Insert the "WD 1" and "WD 2" BCF volumes and Apply Changes.

Reboot and allow Windows to redetect your drives. This won't address the root cause of your problem, but will provide a painless recovery.
 
Nov 23, 2020
19
0
10
0
I have seen exactly the same problem in numerous threads. I'm convinced that there is a bug of some kind. AMD Ryzen CPUs, Gigabyte motherboards, and Windows 10 appear to be the common factors. Do you have a Gigabyte motherboard?

Notice the data pattern in sector 0. That's bogus data which has probably been written by the OS. I don't know why this happens, and I don't know where it originates, but the same pattern appears in other threads.

It appears that you have reinitialised your drives after the latest event. Please don't do that. That said, there is a simple recovery process involving a few clicks.

For your SSD, double-click the "SSD" volume and expand the $Root. Do you see your file/folder tree? If so, then r-click each of the "Microsoft reserved" and "Basic data" partitions and select "Remove the partition". Then r-click the "SSD" partition and select "Insert the partition (undelete)". Then select Drive -> Apply Changes.

For your WD HDD, r-click each of the "BCF" volumes and expand the $Root. Verify that these are your original partitions. If so, then remove each of the black GUID partitions (Microsoft reserved, etc) as before. Insert the "WD 1" and "WD 2" BCF volumes and Apply Changes.

Reboot and allow Windows to redetect your drives. This won't address the root cause of your problem, but will provide a painless recovery.
I have an Asus rog Strix x570. I will do as you suggested next time it resets. These steps will only help with recovery but HDD can reset to unallocated again?
 
Nov 23, 2020
19
0
10
0
So an update. I ordered new sata cables online. Deleted the sata drivers in device manager. Rebooted in safe mode so that system can reinstall the device and drivers. Paritioned the SSD in safe mode.

Its been a week and so far SSD didn't allocate itself. Keeping fingers crossed. So if you have similar problem. You can try the above methods to see if it fix your problem.
 

ASK THE COMMUNITY

TRENDING THREADS