SSD causes slow Windows, IDE controller causes BSOD

Hey,
I am currently running a Toshiba DT01ACA300 SATA 3TB HDD on my computer connected through a SATA 3G port, and the BIOS' SATA controller mode is set to AHCI.
My friend gave me an SSD (120GB 6Gb/s Patriot Blast SATA3) because it had his Windows installation files that became corrupt (he was watching a YouTube video and apparently his PC froze, and when we restarted it, the drive was either not detected as a bootable device, Windows Bootloader popped up claiming some files are missing, or it would go into infinite loading) so I decided to take it, format it and use it myself.
I popped this little thing into my PC, plugged it into another SATA 3G port and power, and booted my PC up.
The boot took way longer than usual. After about 10 minutes I got booted into Windows 10, and the first boot it was so unresponsive that I had to restart the machine. In particular, explorer.exe was freezing and crashing like crazy, and it took about 15 minutes just to open a random app. This is not normal for this PC.
I restarted, and the time was again way longer than usual. This time I was patient, and I waited.
Right-clicking the drive in explorer did nothing (ah, and also having the SSD inserted made a few icons and the input method at the bottom disappear) so I decided to format it with a command.
I explored the files, and even though the drive appeared corrupted at my friend's house, I could browse the files on it - it had the Windows 10 files and some personal programs etc.
I ran the format command on the drive, and after 3 hours it made no progress, staying at 0%.
I stopped the formatting, and the drive stopped being discovered by Windows, and after restarting also by the BIOS.
I changed the SATA slot to which I plugged it in, and ran the PC once more - again, very very long bootup speed. Ta da!
The drive was once again disconnected, although now labelled Local Disk (D:) and had no storage information. Right clicking just crashed explorer.exe.
Then I read online that crashes with explorer.exe when using an SSD can be fixed by enabling IDE instead of AHCI - and so I did. The PC was again very slow when booting up, but this time I got a Blue Screen of Death saying INACCESSIBLE_BOOT_DEVICE.
I unplugged the SSD and changed the drive controller back to AHCI - system booted up very quickly, and there was no BSOD.

What is wrong with the SSD and how can I fix it? I planned on using it for a Linux installation but now it seems useless.

Margister said:

Hey,
I am currently running a Toshiba DT01ACA300 SATA 3TB HDD on my computer connected through a SATA 3G port, and the BIOS' SATA controller mode is set to AHCI.
My friend gave me an SSD (120GB 6Gb/s Patriot Blast SATA3) because it had his Windows installation files that became corrupt (he was watching a YouTube video and apparently his PC froze, and when we restarted it, the drive was either not detected as a bootable device, Windows Bootloader popped up claiming some files are missing, or it would go into infinite loading) so I decided to take it, format it and use it myself.
I popped this little thing into my PC, plugged it into another SATA 3G port and power, and booted my PC up.
The boot took way longer than usual. After about 10 minutes I got booted into Windows 10, and the first boot it was so unresponsive that I had to restart the machine. In particular, explorer.exe was freezing and crashing like crazy, and it took about 15 minutes just to open a random app. This is not normal for this PC.
I restarted, and the time was again way longer than usual. This time I was patient, and I waited.
Right-clicking the drive in explorer did nothing (ah, and also having the SSD inserted made a few icons and the input method at the bottom disappear) so I decided to format it with a command.
I explored the files, and even though the drive appeared corrupted at my friend's house, I could browse the files on it - it had the Windows 10 files and some personal programs etc.
I ran the format command on the drive, and after 3 hours it made no progress, staying at 0%.
I stopped the formatting, and the drive stopped being discovered by Windows, and after restarting also by the BIOS.
I changed the SATA slot to which I plugged it in, and ran the PC once more - again, very very long bootup speed. Ta da!
The drive was once again disconnected, although now labelled Local Disk (D:) and had no storage information. Right clicking just crashed explorer.exe.
Then I read online that crashes with explorer.exe when using an SSD can be fixed by enabling IDE instead of AHCI - and so I did. The PC was again very slow when booting up, but this time I got a Blue Screen of Death saying INACCESSIBLE_BOOT_DEVICE.
I unplugged the SSD and changed the drive controller back to AHCI - system booted up very quickly, and there was no BSOD.

What is wrong with the SSD and how can I fix it? I planned on using it for a Linux installation but now it seems useless.

At a guess, the SSD has suffered a hardware failure. I've only seen that kind of behavior with fried drives.

You may be able to check it further if you can get access to an external USB adapter. At least, that may prevent it from interfering with the basic operation of the PC.

Since this affects the Windows boot operation, reckon Linux would be affected? Perhaps I could format the drive as ext4 in gparted

Bump