Aaaaahhhhhh!!!!!!!!!!!!

[335th_GRAthos]

As it has already beeing said, you never defrag an SSD!
From one side, it does not improve anything on the reading speed as there are no mechanical parts involved in the reading data process.
From the other side, SSDs have they own internal system to write data onto different sectors every time, in order to avoid overusing the same area.
As the memory chips have a limited number of "write" times, writing continously on the same area will eventually lead to a failure (that particular area can not be used any more).
This is normaly no problem as the internal SSD system knows how to cope with it and stops using that specific area and reallocates any data elsewhere (this process happens in the background and the user notices nothing of it). For exactly this reason, at least in the past (I have no idea about newer SSDs) we used to never allocate the full size of the SSD but instead leave some 5% unallocated which could be used by the SSD system to replace any overused areas.

How old was your SSD hard disk? It is still rather strange that it happened.
The disk does not boot because one of the boot files for Win7 is damaged. OK with that.
But, if you connect the disk as a second hard disk on another PC, can you read te contents of the disk? Normally you should...
It can also be that a file was damaged and that replacing it would solve the problem.
Anyway, it is not worth experimenting if it is only $120 for the replacement.
But I believe you would probably be able to use your old SSD still. Just in case, this time, do not particition the whole SSD but leave 5%-10% unallocated.

~S~

[Skoshi Tiger]

Originally Posted by Jatta Raso

did you made any changes in BIOS? were you using it as IDE or SATA (AHCI)?

Using SATA - couldn't find any AHCI settings in my motherboard BIOS (NV 790i ultra board).

Originally Posted by 335th_GRAthos

As it has already beeing said, you never defrag an SSD!
From one side, it does not improve anything on the reading speed as there are no mechanical parts involved in the reading data process.
From the other side, SSDs have they own internal system to write data onto different sectors every time, in order to avoid overusing the same area.
As the memory chips have a limited number of "write" times, writing continously on the same area will eventually lead to a failure (that particular area can not be used any more).
This is normaly no problem as the internal SSD system knows how to cope with it and stops using that specific area and reallocates any data elsewhere (this process happens in the background and the user notices nothing of it). For exactly this reason, at least in the past (I have no idea about newer SSDs) we used to never allocate the full size of the SSD but instead leave some 5% unallocated which could be used by the SSD system to replace any overused areas.

How old was your SSD hard disk? It is still rather strange that it happened.
The disk does not boot because one of the boot files for Win7 is damaged. OK with that.
But, if you connect the disk as a second hard disk on another PC, can you read te contents of the disk? Normally you should...
It can also be that a file was damaged and that replacing it would solve the problem.
Anyway, it is not worth experimenting if it is only $120 for the replacement.
But I believe you would probably be able to use your old SSD still. Just in case, this time, do not particition the whole SSD but leave 5%-10% unallocated.

~S~

I checked it out at the shop I bought the original drive from, and it was a year and a half old and unfortunately out of warranty. Looks like the controller board died.

Anyhoo I ended up buying a 120 GB SSD to replace it (with a three year warranty!!!) and spent last night getting my PC up and running again.

I had a Windows 7 upgrade disk that is a complete 'B' and required me to install windows Vista on the new drive before doing a clean install. Unfortuantely Windows Vista kept on blue screening during the install.

Eventually I got to a point where Vista accepted my authentification code before crapping out. From that point the Windows 7 upgrade allowed me to do a clean install!

What a waste of time just to save a few dollars for an upgrade disk!

Hopefully I will learn for the next version of windows that comes out!

Any way now I've got a completely fresh system with Windows 7, Anti virus, various drivers and COD!

What else could a man want!

Cheers!

[KG26_Alpha]

Originally Posted by Skoshi Tiger

Using SATA - couldn't find any AHCI settings in my motherboard BIOS (NV 790i ultra board).



I checked it out at the shop I bought the original drive from, and it was a year and a half old and unfortunately out of warranty. Looks like the controller board died.

Anyhoo I ended up buying a 120 GB SSD to replace it (with a three year warranty!!!) and spent last night getting my PC up and running again.

I had a Windows 7 upgrade disk that is a complete 'B' and required me to install windows Vista on the new drive before doing a clean install. Unfortuantely Windows Vista kept on blue screening during the install.

Eventually I got to a point where Vista accepted my authentification code before crapping out. From that point the Windows 7 upgrade allowed me to do a clean install!

What a waste of time just to save a few dollars for an upgrade disk!

Hopefully I will learn for the next version of windows that comes out!

Any way now I've got a completely fresh system with Windows 7, Anti virus, various drivers and COD!

What else could a man want!

Cheers!

Ermm



And

http://windows.microsoft.com/en-GB/windows-8/preview