Interesting question here about bricking older hdd's :/  

BillyBob said:

jimbo45 said:

Hi there.

Hardware defects DO happen and I'm sure it's NOT due to ANY build of Windows -- Ms has 100'000's of employees / contractors world wide -- if a defect in Ms's software causes HDD bricking I'm sure the courts would be flooding with compensation claims as well as info coming out of Ms itself. They aren't the CIA / FSA (Old KGB rebranded) etc so couldn't possibly keep that type of event under wraps.

People love conspiracy theories but this just isn't the case here. As a sideline into what Humans actually believe vs reality take an example from current day politics --in the UK a few months away from a General Election MORE people apparently believe in the "Loch Ness Monster" than in one of the Politcal Leaders (I think the opposition leader - but not sure). At least whether you like him or loathe him the existence of that person is a FACT which cannot be said of the Loch Ness Monster -- but that still doesn't stop people believing in it.

From across the pond (in the USA) I believe that a significant number of National Inquirer readers still believe that they were once abducted by Aliens in flying saucers. !!! So again people believe in what they believe regardless of evidence or lack of it in their theories.

So Factually it's about 100% impossible for a standard OS like Windows to BRICK an HDD -- it could eventually BREAK one - excessive read writes for example but you'd get indications of failure soon enough.

People will believe in what they will believe - in spite of evidence disproving their theories -- so if you want to blame build 9879 go ahead -- I think though you are wasting your time and just got defective hardware.

Cheers
jimbo

I don't know what you Icelanders drink but it must be pretty powerful, I've got no idea what you're talking about or who you're talking to.

Urban myth | Define Urban myth at Dictionary.com

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.

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.

That certainly may be, it was a large update and changed almost if not all system files judging by it's size and time and way it updated, looked almost like a new or installation or at least like regular installation repair. I'm resigned to it being a beta OS and that all kinds of problems can be expected, that's why it's only my secondary OS. Can't really put all my eggs in that basket, might develop a hole !!!!

Just keep a drive for it alone when installing Windows and while updating, both, 9860 and 9879 screwed up (temporally) my dual boot so I had to fix it. Next time I'll disconnect other dives while doing that.

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.