Bads at the beginning of the disc

Question

Iron

I’ll tell you at the beginning how the bads appeared, and then I’ll move on to the essence of the issue. The laptop has 2 systems: Windows 8.1 and Elementry OS (Ubuntu-based distribution). The disk is divided into 5 partitions (system with Windows, system with Elementary OS, media partition, /home directory partition and swap partition).
During the reboot of Windows, an update began, and some big one, because. I couldn't wait for the end and closed my laptop. The next time I started the laptop, Windows booted up, but everything worked incredibly long and slow, after the second reboot, a blue screen began to pop up.
I thought something with Windows because of the "hot" shutdown of the laptop during the update. I went to Elementary OS, I decided to go to the section with Windows. I went to the section itself, but I could not go into the folders. I booted from under DOS and checked the disk with Victoria for bads. The check showed that approximately the first 10% of the disk is all in bads, and the rest of the disk is "clean" (white, gray).
I want to leave these first 10% of the disk in the unallocated area, and put Windows where there are no bads. How can I more accurately determine where the bads are downloaded? I would also like to hear the reasons why this could happen ...

Answer 1

"I want to leave these first 10% of the disk in the unallocated area, and put Windows where there are no bads." don't do that, shoot this disk.

Answer 2

I think it's worth trying to Remap in Victoria and then checking again for bugs. If the bads remain, then it is better to step back from the end of the bads with a margin, for example, 1-2 GB, since they can grow.
Although, on the other hand, since hard drives have limited space for remapping sectors, it is better not to do it, but immediately step back with a margin and use it. But then in other places of the hard disk, if problems arise, there will still be free space for remapping (including automatic, if any defects occur).
To the question why, probably because these "places" of the hard disk have not been accessed for a long time and everything was fine (although it could already be in the balance, as if worn out), but this time enhanced recording began there, these are the weak points and came to light.

Answer 3

If the screw itself does not remap them, run something like the badblocks utility from the Linux distribution in write-read-destroy mode.
How much does SMART show in attribute value 5, 197 and 198?
If after running multiple "write-read", the value of 197 and 198 does not go to 0, then throw out the screw. Or use it as a non-critical garbage dump, because after a couple of weeks of intensive work, he will die.