I am also having the same problem on a 120gb 520 drive. I am running RST 188.8.131.523 drivers on windows 8 64 bit.
I have been having this problem for several weeks if not longer.
Same problem here with an Intel SSD 520 240GB.
Intel SSD Optimizer stucked at 85%. (Toolbox 3.1.2)
After reboot, i had a blackscreen after Windows Logo disappeared.
The next reboot, all was fine.
Checkdisk didn't find problems.
We are looking into the issue you are reporting.
Are any of you using your drives in a RAID?
Are any of you using your drives in systems with non-Intel chipsets?
I am using my 120GB Intel 520 SSD on a Dell Latitude e6400 (PM45 northbridge, 82801IEM ICH9M-E southbridge),
Dell BIOS A32.
Driver version is: RST 184.108.40.2063
OS: Windows 8, 64bit. Fully updated up to February 15, 2013.
The drive is not in a RAID.
I should note that the Bluescreen does not happen during the optimization process, but occurs within 1-2 minutes after completion.
This may be a related issue, but I am having difficulty hibernating the system with the 520 drive. Entering into hibernation fails 100% of attempts while the 520 drive is present in the system. This is regardless of RST driver versions, and also occurs under Windows 7. I have the exact same experience with two separate 520 drives. "Fast startup" on windows 8 also fails when shutting the computer down.
Mirroring and swapping the 520 drive to another non-intel HD alleviates the issues with hibernation and fast start-up.
Any ideas Ken?
The system is set to RAID in the BIOS. However the two SSDs in the system are not part of a RAID array. Four HDDs are in two RAID0 arrays.
Here are some additional details of the system:
Motherboard: Rampage IV Extreme (BIOS Rev. 3404)
Processor: Intel i7 3930K
Memory: 16GB Corsair Vengeance Dual/Quad Channel DDR3-1866MHz (CMZ16GX3M4X1866C9)
SSD1: Intel SSD 520 (240GB) on SATA Port 0 (6Gb/s, Intel) (Boot)
SSD2: Intel X25-M (160GB) on SATA Port 1 (6Gb/s, Intel)
HDD Raid 0 Array 1: 2 Seagate 1.5TB Barracudas on SATA Ports 2 and 3 (3Gb/s, Intel)
HDD Raid 0 Array 2: 2 Seagate 2.0TB Barracudas on SATA Ports 4 and 5 (3Gb/s, Intel)
Optical Disk 1: LG BD-RE BH08LS20 on SATA Port 6 (3Gb/s, Asmedia)
Optical Disk 2: LG BD-RE BH12LS38 on SATA Port 7 (3Gb/s, Asmedia)
Graphics Card: ASUS Nvidia GTX 680 (4GB model)
Sound Card: Creative X-Fi Titanium
Power Supply: Antec 1000W HCP-1000
OS: Windows 8 Pro with Media Center
If I can provide any other information, let me know.
I also get BSOD's in RAID mode when trying to TRIM an SSD drive.
I have the DX79SI motherboard and two Intel 520 SSD's.
I have given up on getting any answers to this problem after 6 months of waiting. The x79 chipset will apparently be obsolete before this SNAFU will be solved - if ever. And by the way - forget about Smart Response for the x79. It was promised last year. Apparently socket 2011 support isn't high on Intels agenda.
I have the same problem with the 520 240GB. Stuck ar 86% - then a system failure - but in Windows 8 which is not a BSOD, but a system failure page. Same thing.
I have lots of Intel SSD's. The 520 is the only model with this problem.
Any advice would be appreciated.
I just tried installing the new RST drivers: 220.127.116.111, and the computer BSOD as it was restarting as soon as the install completed.
Windows 8 error message:
EDIT: To follow up, after restarting, I tried running SSD optimize and it reached 100% but then the computer locked up but did not BSOD. Had to manually power off after 5 minutes of being non-responsive.
IMO, this issue is related to the SandForce controller used in the 520. Given the way the SandForce controller works, which is very different from other SSD controllers, it is difficult for the Optimizer to perform its work relative to other SSD controllers. Note that other Intel SSDs that don't use the SF controller do not have this problem.
I doubt there is much if anything users can do to fix this issue, it will require an update to the Toolbox so it will work correctly with Windows 8.
Until then, the Windows 8 Optimize feature for SSDs works fine in my experience, even with SSDs in RAID 0 volumes.
A bit of an update. I just installed the Intel RSTe ver.18.104.22.1683 drivers that were released on February 21. After doing so, Toolbox optimize only made it to 35-percent before throwing up an error saying optimization had failed and a reboot was required. Although I did not get a BSOD this time, the system performance was "sluggish" after I closed the Toolbox program. As I was navigating to the shutdown option, multiple memory access violation errors occurred for other running processes before the system locked up entirely. I had to do a hard shutdown of the computer at that point.
This problem effects the 180 GB SSD 520 models.
Intel SSD Toolbox: 3.1.2
Intel 520 180 GB Firmware: LCSi
Intel RST: 22.214.171.1243
SSD is connected to the SATA III as my only internal drive. No RAID. Two external hard drives via USB 3 ports.
OS: Windows 7 Pro 64-bit SP1 with current patches
System: HP Pavilion dv7t-7000 Quad
CPU: Intel i7-3720QM four cores.
BIOS: Insyde F.24
I have own the PC for five months. Today after the scheduled SSD Optimizer ran, the PC did not respond to opening applications. The mouse moved, however when I clicked on an icon on the desktop about 1 or 2 minutes after the SSD Optimizer finished running, nothing happened.
Then all of my desktop icons disappeared along with the system taskbar at the bottom of the screen. Basically, I was staring at my wallpaper image. Then I started getting memory access violation errors and about another minute later BSOD which was unable to create a crash dump file. I had to hold the power button down and crash the PC.
No errors reported when I ran full diagnostics in the Intel SSD Toolbox.
I have not been able to recreate this issue yet.
Do any of you that are experiencing the problem have an HDD password set in the BIOS? If so, please try removing the password and then run the optimizer.
For my 520 180 GB SSD, I am not using BIOS password when the incident occur per my original post.
PS: In case it matters, I have never had a BIOS password set on the machine or a password set on the SSD.
Also, I was unable to recreate the problem when the schedule task initiated the SSD Optimizer. However, from this thread, it appears that the SSD will stop responding after the Optimizer completes causing the BSOD and in my case the BSOD could not create a crash dump.
In your attempts to recreate the problem, have you tried making a lot of deletes to the SSD drive that would cause the SSD Optimizer to have cells that needed to be clean-up when the SSD Optimizer job is run from the scheduler?
Maybe clone the SSD and restore the image to the SSD. With wear leveling, this should cause cells that are unused that contain data that need to be cleaned-up after the image restore correct?