SSD screw is turned off after 5 minutes of operation Or inconceivable SSD controller logic

Prehistory

I have a computer. And there is on it a SSD hard drive Silicon Power SSD 60GB.

WINDOWS 8 is installed on this SSD. Everything is done according to your mind: TRIM is enabled, all cache files, registry, user profiles, etc. transferred to 2Tb "mechanical winch". He lived for a year he didn’t have a “tugil. The system was loaded quickly, the programs did not reflect ...



To live on such a configuration for him for a long time.

')



Beauty.

Start

The day before yesterday I bought another SSD-drive: Samsung SSD 840 Pro 128Gb. I decided to pump slightly - that way in two.





Here are both handsome.



To update. I decided to use a proprietary program from Samsung - Data Migration. I downloaded the latest version, installed it. The new SSD did not connect, and "drove" the computer into Sleep ...



And he went to sleep.

Death

In the morning, I turned on the computer, checked my mail and Skype. For everything about all 2 minutes. And went to work. Comp stayed to live their lives ...





I arrived in the evening. I watch the computer hangs immediately after the BIOS initializes the devices in the system boot state. I went into the BIOS. It turned out the system tried to boot from a photo flash drive, on which, naturally, it was not installed. Changed the boot order ... The computer has booted. Everything seems to be good. But after 5 minutes, Windows 8 hung, crashed into BSOD and restarted the computer.



Silicon Power SSD is not defined "bios".

Funeral

After a complete power outage and juggling loops, SSD came to life. The system has booted. But she lived exactly 5 minutes, and BSOD ...



The whole evening was dancing with a tambourine:

• The screw was connected to another computer;
• Tried to make a copy of the sections on the new screw;
• Tried to create an image of partitions;
• Stitched screw with different firmware;
• Even nothing done.

But as soon as 5 minutes passed, the SSD fell off. Just disappeared from the device or disconnected if it was under DOS.

Bury can not pump out

I call to friends on the service. I want to put a comma in the title. They say: "We are killing such SSDs and changing them under warranty."

So all the same, he died. Bury!



Moving files manually. 5 minute sessions.



At the move stage, a strange file was found, deep in the subfolders of the Users folder. One thing was strange in this file - the name is too long, very similar to the script code. Neither deleted nor copied, he did not want. Skipping this file, I moved the rest. Through the console, deleted the Users folder with the rd /s/q Users Users command, along with a strange file. Just like that - just in case. ... And it took 10 minutes.



Then I have 8 minutes of “Vipal with zeros” free space ... 20 minutes have passed , the SSD is working.



STRANGE!

He is dead YES or NO . Or the information recorded on the SSD affects the SSD itself. But nobody addressed this unfortunate file, especially under DOS. What side can it affect the work of the drive, just being on it. Impossible! But the indisputable fact is that:

A file with a strange long name like a script code that is simply located on an SSD can disable its controller. No need to even contact him.

Unthinkable logic. Most likely it is enough that the data from the name of this file passed through the controller when updating the disk partitioning control records. I think this process takes 5 minutes and leaves.

URA comrades ... Now the information in the stone affects the stone itself.

Resurrection

I uploaded the moved files back. I connected the SSD to my native computer. The system lives on.



5 minutes.



10 minutes.



5 o'clock.

And I am writing my first article on Habrahabr ...

Exposing

But where did this file come from? Is there a virus or backdoor?



But when did this happen? As soon as Data Migration was established ... Or is this a coincidence?

Maybe the manufacturer of drives knows about this possibility?



I really want to read the opinion of the Habr community.

I would like to see the full name of the unfortunate file that was so suddenly removed by me. It began with a "0" (zero).