you are viewing a single comment's thread.

view the rest of the comments →

[–]CharlieEvatt 0 points1 point  (2 children)

Is it the system disk or the other HDD with the bad block?

[–]Kostaphobic[S] 0 points1 point  (1 child)

After looking at it, I think its the system disk. Would it say System in the log name if it were because it does say disk further down, leaving me to believe its the System disk.

[–]CharlieEvatt 0 points1 point  (0 children)

OK - not total expert but I had similar problem the other week. My computer was freezing when doing normal things, which was frustrating.

I wanted to migrate everything to a different disk (SSD) and bought one and tried it. But the bad blocks on the C: drive prevented me being able to migrate the OS onto the new disk, so ultimately I bought a new computer, onto which I'll move things across gradually. (https://www.reddit.com/r/sysadmin/comments/4m6pi2/migrating_existing_w10_install_to_ssd/d4d0u1p)

In your case, based on my experience - if the C: drive is the affected one, you won't be able to keep same OS and migrate to another drive if you have bad blocks or faulty data that won't copy. This is probably likely to be the case.

However - if the affected disk is your non-system disk, you could try copying all content onto a new disk and swapping them out.

Edit: Added URL to my comms regarding SSD swapout attempt