Windows 10: Interesting question here about bricking older hdd's :/

The drive originally had 2 MBR Partitions, but I added another partition to install Windows 8.1 to see if it was the drive that was the problem. Anyway there were that many crashes I ended up completely repartitioning the whole drive, it was the only way it would let me install Windows in the end.
I deleted all the partitions and let Windows setup the drive itself which was the only way it would work. I'd say some kind of overlapping is highly possible as Windows wouldn't even install onto drive until I deleted all the partitions.

Anyway I'm not going to put TP back on this drive until there's a new release, this has caused me a lot of headaches and time. I've still got 9860 on another PC so I'll just tinker around with that.

 

That's no myth, urban or otherwise lol. But it takes a lot of effort to trash HDD by using OS alone, it takes a lot of specialized SW to change firmware in a HDD and apart from electronic or mechanical breakdowns it's very unlikely it could be done by accident. I remember trying to salvage data from some half dead HDDs by changing controller boards on them and flashing same FW on it to match serial numbers so it would work and I can tel you, it was a lot of work. I would say continual BSODs and freezing etc can put a bit of strain on an SSD and do quite a bit of damage.

I had a few spare hours this afternoon and tried repairs with TP and Windows 8.1, didn't work. Tried installing Windows 8.1 straight over the top as a new install, didn't work, formatted one partition and tried again, didn't work. Formatted all 3 partitions and installing, didn't work.

Fully removed all partitions and installed again, this time it worked, Windows 8.1 and fully updated. Have rebooted a few times and run some apps, no BSODs.

No matter what anyone thinks, this was caused by 9879 and nothing else, end of story. File system yes, physically bricking, trashing HDD not likely. I've never said it was bricked, I said it was very close, trashed absolutely, close to being bricked absolutely, was it 9879, absolutely.
What SSD brand and model are we talking about here? I have no problem with Samsung Evo 120GB. It's a Kingston HyperX 120GB, I've got two of these, the reason I bought the 2nd one was because the 1st never gave me any problems.
The 2nd never gave me problems until 9879 and so far since completely repartitioning and installing Windows 8.1 no problems. I didn't do anything wrong, just did what Microsoft said to do, upgrade to 9879, that's when the problems started.
I suppose people could say why didn't you do a clean install with 9879, that's not what Microsoft wanted, it's an in place upgrade.
I know I'm not the only one there are quite a few people who have had similar problems, and I suppose in a way that's what Microsft wants, problems being reported. My first SSD is a Kingston HyperX 120GB on my Win 7 main PC. I transferred it to my Win 8.1 PC and it's been 2 years and that SSD never had a single hiccup.

I also have 3 Samsung (2-120GB and 1-250GB) and 1 Crucial 128GB SSDs installed on my Win 7 PC now. I am running Win 10 separately on a Samsung Evo 120GB SSD. I guess the issue with your Kingston SSD is caused by dual-booting and having multiple partitions on it.

 

My first SSD is a Kingston HyperX 120GB on my Win 7 main PC. I transferred it to my Win 8.1 PC and it's been 2 years and that SSD never had a single hiccup.

I also have 3 Samsung (2-120GB and 1-250GB) and 1 Crucial 128GB SSDs installed on my Win 7 PC now. I am running Win 10 separately on a Samsung Evo 120GB SSD. I guess the issue with your Kingston SSD is caused by dual-booting and having multiple partitions on it.[/QUOTE]

No, the drive was new, I only put WINDOWS 10 Preview on it from the 1st to 9860 to 9879. So two partitions, System Reserved and TP, the problems only started with 9879.

Because of of all the BSODs and the drive not showing up in the BIOS I thought I'd put another partition on it with Windows 8.1 to see if that had any problems. The whole thing didn't go to well so I put the drive in a USB caddy and formatted one partition with Ten on it and did a repair to see if Windows 8.1 would boot, it booted up once but it was limping, so I formatted all the partitions and tried to install Windows 8.1, wouldn't work.

So then I deleted all the partitions and let Windows do the partitions, that worked and now the drive is running like a kitten with Windows 8.1.

 

OMG last night My build got updated and now my HDD disappeared. All my data and my windows 8.1 is on that HDD (which was main HDD) how do i get it back without losing any of my data ? It doesnt show up in disk management. (windows TP is on separate SSD drive)

 

could spinrite find or fix this problem?

 

could spinrite find or fix this problem? Find maybe but if there's a HW failure not likely.

 

could spinrite find or fix this problem? Find maybe but if there's a HW failure not likely. It was just a thought. In the past while repairing a laptop i had a dead drive. as a last resort i installed in my own machine to see if i could recover any DATA i ran spinrite and it picked up the drive and found and blocked the errors. I have had this on two seperate ocasions it was about two years ago so i cannot quite remeber the proceadure with the spinrite software but i think it was easy enough to use ,it just takes a long time to examine and repair any damage.

 

Software errors maybe but if mechanical parts or controller electronics are a problem, no SW can repair that.

 

With conventional drives, suffering this issue due to the latest TP version, there are a lot of people stating that accessing the drive is possible via a Linux Live CD, and indeed some have stated that the mere action of accessing this way can reset the drive to a working state.

This may be something to try if all other methods fail

 

Yes understood, i used to sell HDD in there thousands when i worked for Mitsubishi years ago failuares were very rare But there were a few.I must of misunderstood the origianl thread.
regards Topper.

 

Yes understood, i used to sell HDD in there thousands when i worked for Mitsubishi years ago failuares were very rare But there were a few.I must of misunderstood the origianl thread.
regards Topper. Ha ha, problems with too long threads, almost always they end up with something else.

 

As I said here on or in another thread. I think the cause is the partition overlapping whether the partition is mbr or gpt. I think this is what causing boot issues. It would be interesting to know if it does this when windows 7 is installed on a partition without the system reserve partition or with windows having a system reserve partition. This may explain why it doesn't work on some Vm's setup as well. Does the system reserve partition need to be bigger or is the build overlapping partition when it shouldn't.

Another possible thing, is the active partition got set wrong during install this will also cause boot errors and can be set back using diskpart from the installation disk.

 

Yea 10 made shambles of the 7 boot manager Twice nothing fixed but a clean install so there might be a difference in installs without the system reserved partition ?
Cheers.

 

On another note,
Accidently I noticed 10 can access 7's system but 7 can not access 10's system,
I got a you do not have permissions to access :/

 

If you use a third party file manager, open as administrator or a UAC pauses the access but you get access. I use Total Commander and have been since W98 maybe. I pass my MS Outlook PST files back/forth using it.