Used Active-Killdisk. Put the system image back on. Tried trim (it had been five days). OK, worked. Leave it alone for a coupla hours, try trim again. Uhm, nope. Same thing. Disk activity at 100%, no reads or writes, crashed and burned.
So, it's either the installation or the drive. That seem reasonable? Where's the flaw here?
1 of 1 people found this helpful
When you said perform a low level format, were you referring to a SSD Secure Erase? A HDD type format, writing to a drive, is not appropriate for a SSD.
Looked up your board, no Windows 8 support (driver downloads, etc) or certification from ASUS for your P45 chipset board. I have an ASUS X58 board with the same Intel SATA chipset as yours (ICH10R), also without Windows 8 drivers. You may be better off using the standard Windows 8 AHCI driver, storahci. You said you installed the latest INF (188.8.131.526) and IRST driver, what version? Not listed in your system specs.
What SATA mode was used in the OS installation?
The Toolbox 3.1.2 requires .NET Framework 3.0, but your system info shows "not detected". The 520 SSD seems to take a while after a Toolbox Optimize has completed, to complete the manual TRIM of the drive. The drive will seem completely busy, but completes that phase in ~one minute (Samsung's SSD optimize takes several minutes, why Intel did not implement their optimize that way escapes me.) My Windows 8 PC with a Z77 chipset board uses 520's as the OS volume, and I don't have your freezing issue at all, and I have used the Windows 8 SSD optimize feature successfully.
Your board has a secondary SATA controller, the Silicon Image Sil5723, besides the Intel ICH10R. Which SATA controller is the 520 connected to?
Are you using the ASUS Drive Expert Software?
1 of 1 people found this helpful
Hello, on this case I suggest you to move the Solid State Drive to the SATA port 0 or 1 and try to select the AHCI option in your BIOS prior the installation of the operating system.
Another recommendation is to change the SATA and power cables for the Solid State Drive and try again.
The secure erase option is definitively a good idea, after that you can try to install the operating system and test the system again.
If the issue persist please contact the place of purchase if you have less than 30 days if you have more than that, please contact the Intel(R) technical support at the following phone number to replace the unit: 916 377 7000 option 7.
Man, I lost an entire post. Dag, that's irritating. OK, cliff notes version.
IRST version 184.108.40.2063. AHCI mode in BIOS. No ASUS software, except for the E-Green thing for the optical. Swapped cables, tried another SATAIII (blue) cable and a SATAII (red) cable, both crashed on 1st trim.
Yep, Intel gathering tool missed a few key things. Probably didn't have .Net installed at that time. Event logs show I had 6 crashes in the first 3 days. The 520 is on port 0 on the Intel Southbridge.
Used killdisk from:
to zero the drive. Sorry to be short, I just wrote a paper to answer your questions and it got lost.
The system runs great, otherwise. Don't think the: cables, ports, or drive are bad.
OK, more calm and composed and writing this in Word so it doesn’t get lost.
Previously, on this box, I had Win7 Pro, x64 installed on a M4 SSD2. I didn’t have Windows 7 support
on this board then, but it didn’t seem to affect anything as far as I was concerned. The system was rock stable and performed very nicely for a collection of old hardware.
Before I installed the M4 SSD in Win7, I did some research which appeared to imply that the best results would be had from installing the SSD formatted through diskpart, to guarantee the partition offset was correct,
and that there would be no hidden system partition that could wreak havoc with Acronis. So, a while ago, I set the board to AHCI mode and installed the OS. All good.
Then I got Win8, and didn’t have any problems with that, either. I have a third computer that I figured I would upgrade the disk, that’s when I started looking around looking at SSDs to see what might be good. I had read good things about the 520 and was able to purchase a new one cheap.
I hooked it up to this box so I could get it formatted and run some benches on it. I decided to fit the 520 instead of the M4 because the 520 bested the M4 in seq. reads and 4K writes. I had what appeared to be a better disk, why shouldn’t I? After imaging the system drive and swapping drives, Acronis let me down and couldn’t put the system image on the 520. But the M4 was intact and I swapped that back in until I had more time to work on getting the 520 in.
I did a fresh install on the 520. The chipset didn’t go in on the first try,
but it did on the second. I had a lot of trouble getting drivers installed for a PCI USB3 card. And it started randomly crashing. I don’t remember what I was doing to make it crash, but they was a happening. I was ready to RMA the thing when it seemed to get its act together. I did get the toolbox installed and was able
to run a one full disk diagnostic (usually, running any feature other than reading SMART data freaks the disk out, or so it appeared). According to the toolbox, my disk is hunky-dory.
Actually, after the disk wore in, the system worked pretty
well. The toolbox is gone. Apparently, as long as I don’t try trim, everything
is copasetic. This is a desktop, always on, with the power plan set to high performance. I’ve looked over things like LPM, DIPM, and halt states, haven’t had any luck with any of those settings. It seems clear there’s some setting that I’m missing, I just don’t know what it is.
May have found the answer. Raised Southbridge voltage 0.1 V. It's too early to tell, but it seems to be crash proof.