Interesting question here about bricking older hdd's :/

groze · 25 Nov 2014

Billybob,

Even though I don't test W10 any more. I still read about it. I came across a post that said 9879 overlaps a partition that causing it to be bricked. It sounds to me it causing the drive to have more than 4 primary partitions unless your drive is GPT. This might fix, if you can boot to 9879, shrink windows 10 partition, reboot install MiniTool Partition Wizard Home Edition free version don't know if work in this build. You can use MiniTool partition wizard to resize it back to without it overlapping. Now, if you can't boot, I would recommend trying Linux gparted. I am unclear if resizing a windows 10 partition using gparted keeps the data.

LittleJay
Is your drive Gpt or MBR partition?

All,
Even if you have GPT partition, your partition could be overlapping as well.

LittleJay · 25 Nov 2014

LittleJay
Is your drive Gpt or MBR partition?

I use MBR partitions for my W10TP installation. As I mentioned before, I haven't had any trouble with my Kingston SSD bricking, but it is good to be forewarned that it might be possible.

BillyBob · 25 Nov 2014

LittleJay said:

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.

I also installed 10 TP build 9879 on a Kingston HyperX 128 GB ssd, but I've had none of the same problems as you. So far anyway. But it's good to know about potential problems.

Who knows what causes these things but Microsoft has admitted to BSODs etc in 9879 and has released a patch. Different computer configurations with different hardware and drivers are bound to cause problems.

BillyBob · 25 Nov 2014

groze said:

Billybob,

Even though I don't test W10 any more. I still read about it. I came across a post that said 9879 overlaps a partition that causing it to be bricked. It sounds to me it causing the drive to have more than 4 primary partitions unless your drive is GPT. This might fix, if you can boot to 9879, shrink windows 10 partition, reboot install MiniTool Partition Wizard Home Edition free version don't know if work in this build. You can use MiniTool partition wizard to resize it back to without it overlapping. Now, if you can't boot, I would recommend trying Linux gparted. I am unclear if resizing a windows 10 partition using gparted keeps the data.

LittleJay
Is your drive Gpt or MBR partition?

All,
Even if you have GPT partition, your partition could be overlapping as well.

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.

badrobot · 25 Nov 2014

BillyBob said:

badrobot said:

BillyBob said:

CountMike said:

BillyBob said:

CountMike said:

BillyBob said:

You must be talking about the Urban Myth that Microsft has 100s of thousands of employees, so they couldn't possibly be responsible for trashing a HDD.

That's like Apple saying, You're holding it wrong.

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.

BillyBob · 25 Nov 2014

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.

netuser · 26 Nov 2014

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)

toppergraph · 26 Nov 2014

CountMike said:

During OS installation and large updates that change a lot in the system, HDD has to work much harder than normally so a marginal one might brake just then.

could spinrite find or fix this problem?

CountMike · 26 Nov 2014

toppergraph said:

CountMike said:

During OS installation and large updates that change a lot in the system, HDD has to work much harder than normally so a marginal one might brake just then.

could spinrite find or fix this problem?

Find maybe but if there's a HW failure not likely.

toppergraph · 26 Nov 2014

CountMike said:

toppergraph said:

CountMike said:

During OS installation and large updates that change a lot in the system, HDD has to work much harder than normally so a marginal one might brake just then.

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.