topic Re: SSD 510 Series Drive Access Lockup in Archive

SSD 510 Series Drive Access Lockup

idata — Wed, 21 Sep 2011 11:07:21 GMT

I am seeing some odd behavior with my SSDSC2MH250A2 drives. I have two of these connected to my DX58SO2 motherboard. What was happening was that access to my second SSD drive would cause Windows to freeze. The OS itself would hang while trying to access to drive. I was not sure what was causing this, and I thought I had defective hardware at first.

I had to hold down the power button due to some of these freezes. After doing this, I ran a chkdsk /f for both drives followed by rebooting to ensure the file system was intact. My second SSD drive was even freezeing or extremely slow during the chkdsk. I had to hold down the power button during one chkdsk after it reported unexpected errors.

I ran Intel's SSD Toolbox followed by running the SSD Optimizer for both drives. After doing this, the freezing issues seemed to have stopped. Here is where I am confused though-- I am running Windows 7 Professional, and the Intel PDFs I have read stated that the functionality of the SSD Optimizer is built into Windows 7. This leads me to believe I should not need to run the optimizer.

I do not understand why the SSD drives would cause the OS to hang after about three weeks of use. I can find no firmware updates for the 510 series at all.

Re: SSD 510 Series Drive Access Lockup

idata — Thu, 22 Sep 2011 17:46:39 GMT

I just wanted to add to this thread that I am seeing the same Windows 7 behavior freezeing behaviour after installing the same SSDSC2MH250A2 drive as the user Dryne.

My Windows is periodically locking/freezing up. My mouse works but I cannot click on anything. It seems that all I can do is hit ctrl-alt-delete and bring up the task manager. As soon as the task manager is running, Windows unfreezes. I did leave my locked up Windows for a while and it looks like the freeze out eventually fixes itself.

I ran across this support thread after a coworkers computer completely crashed. It turns out his Intel SSD (around 120gb) crashed and no longer functions (this is apparently a known issue with his model and a firmware update is needed to fix the issue - unforyunately for him now that his SSD crashed, it will no longer accept the firmware update and his PC has been rendered useless along with a loss of all of his data).

I was looking for a firmware update for my SSDSC2MH250A2 drive (which apparently there is none) when I came across this thread. I was suprised to see the exact same issue for another user (I had not even determined that it was the SSD drive causing the freeze although I was suspicious because the problem only began after installing the SSD - a year of use of the same computer without the SSD never froze up once).

Re: SSD 510 Series Drive Access Lockup

idata — Sun, 25 Sep 2011 01:22:44 GMT

Windows locked up again moments ago when reading the second SSD drive. Running the optimizer is not the fix. The issue happens under certain circumstances that I am not sure how to reproduce.

I ran the fast diagnostic scan for the second drive that is having issue:

Read Scan Failed Contact your reseller or local Intel representative for assistance

Data Integrity Scan Passed Ready for use

If I power the computer off then back on, the one SSD drive works okay for awhile until this read issue happens for whatever reason.

Re: SSD 510 Series Drive Access Lockup

idata — Sun, 25 Sep 2011 01:38:07 GMT

I just powered my desktop off then back on, logged into Windows, and ran the Fast Diagnostic Scan once again for the second SSD drive. Now it passeses both the Read Scan and the Data Integrity Scan.

I really have no idea what is going on, but I've never had this many issues with a storage device before.

Re: SSD 510 Series Drive Access Lockup

idata — Sun, 25 Sep 2011 04:45:18 GMT

Did you see this post? http://communities.intel.com/message/139439# 139439 http://communities.intel.com/message/139439# 139439

Re: SSD 510 Series Drive Access Lockup

idata — Sun, 25 Sep 2011 05:18:50 GMT

Both drives are running the PWG4 firmware and are only a few weeks old. I do not see that either drive is being switched from SATA600. SiSoft Sandra is showing SATA600 for both drives.

I am wondering if it is due to the buggy Motorolla Bluetooth drivers that Intel has on the download center for my mobo. I have uninstalled it and rebooted. The issue of Windows 7 freezeing I just described above was during an attempt to copy 22 MP3 files I had downloaded from Stream. Windows would lockup everytime I attempted to copy the files, which is why I suspect the Bluetooth drivers. Motorolla's drivers are poor and cause Microsoft Word to crash.

You know what -- I think it was the buggy Motorolla drivers in this case. I am now able to browse the folder containing the 22 MP3 files with zero delay. Before I had uninstalled it, I could only see id3 tag info for like 2 out of 22 files when explorer would hang followed by Windows freezing.

Re: SSD 510 Series Drive Access Lockup

idata — Sun, 25 Sep 2011 05:21:51 GMT

These are the drivers I downloaded from Intel's download center for my DX58SO2: Bluetooth_allOS_3.0.2.285_PV_MSI.exe

These drivers are buggy and cause all kinds of issues.

Re: SSD 510 Series Drive Access Lockup

idata — Sun, 25 Sep 2011 14:44:36 GMT

The SSD drive is still locking Windows up even without the Motorolla drivers installed. It is fine for awhile after the system is booted, but after about two hours, accessing the drive results in Windows hanging. The caps lock key causes the keyboard to light, but control-alt-delete is very slow to respond (like about three minutes until I see the blue screen with options). I tried control-alt-delete, waited three minutes for the menu to appear, then clicked task manager. I am now back at a loading screen not seeing the task manager at all. Control-alt-delete is no longer working, and my computer is stuck. The caps lock key is still working though, but nothing else in Windows does.

This is really poor. I really cannot use my computer to run anything else for diagnostics. It's stuck.

Addition: okay -- after a longer wait, I finally got the blue screen with menu choices from pressing control-alt-delete. I selected task manager once again, and now I am back at the desktop. The desktop is frozen though and not responding to mouse clicks. At this point, I usually have to hold down the power button to shut off the machine. There is nothing else I can do. I think I will wait it out and let it sit this time. It seems to do things very slowly while the drive is inaccessible.

Re: SSD 510 Series Drive Access Lockup

idata — Sun, 25 Sep 2011 16:19:37 GMT

After an extremely long time (over an hour), I was able to logoff Windows 7 then shutdown the computer. Powering the computer back on, I am now posting info from the Event Viewer:

Windows Logs:

System:

Level: Error; Date and Time: 9/25/2011 10:37:48 AM; Source: atapi; Event ID: 11; Task Category: NoneGeneral: The driver detected a controller error on \Device\Ide\IdePort4.(there are six of these messages with the same info as above)

Level: Error; Date and Time: 9/25/2011 10:46:53 AM; Source: atapi; Event ID: 11; Task Category: None

The driver detected a controller error on \Device\Ide\IdePort5.(there are three of these messages with the same info as above)

Level: Error; Date and Time: 9/25/2011 11:08:34 AM; Source: Service Control Manager; Event ID: 7011; Task Category: None

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the syncagentsrv service.

Level: Warning; Date and Time: 9/25/2011 11:10:04 AM; Source: Ntfs; Event ID: 57; Task Category: (2)

The system failed to flush data to the transaction log. Corruption may occur.(there are two of these messages with almost all the same info as above; the date and time is off by seconds)

Level: Error; Date and Time: 9/25/2011 11:46:22 AM; Source: atapi; Event ID: 9; Task Category: None

The device, \Device\Ide\IdePort5, did not respond within the timeout period.(there are four of these messages with the same info as above)

Level: Error; Date and Time: 9/25/2011 11:46:22 AM; Source: Kernel-General; Event ID: 6; Task Category: None

An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '\SystemRoot\System32\Config\SOFTWARE'.

Level: Warning; Date and Time: 9/25/2011 11:46:22 AM; Source: Disk; Event ID: 51; Task Category: None

An error was detected on device \Device\Harddisk1\DR1 during a paging operation.(there are four of these messages with the same info as above)

Level: Warning; Date and Time: 9/25/2011 11:46:22 AM; Source: Ntfs; Event ID: 57; Task Category: (2)

The system failed to flush data to the transaction log. Corruption may occur.

Level: Warning; Date and Time: 9/25/2011 11:46:22 AM; Source: Disk; Event ID: 51; Task Category: None

An error was detected on device \Device\Harddisk1\DR1 during a paging operation.(there are five of these messages with the same info as above)

Level: Information; Date and Time: 9/25/2011 11:46:23 AM; Source: Application Popup; Event ID: 26; Task Category: None

Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x000007FEFDB6718C 0x000007FEFDB6718C 0x000007FEFDB6718C 0x000007FEFDB6718C

Level: Warning; Date and Time: 9/25/2011 11:46:23 AM; Source: Ntfs; Event ID: 57; Task Category: (2)

The system failed to flush data to the transaction log. Corruption may occur.

Level: Warning; Date and Time: 9/25/2011 11:46:23 AM; Source: Ntfs; Event ID: 50; Task Category: None

The description for Event ID 50 from source Ntfs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.If the event originated on another computer, the display information had to be saved with the event.The following information was included with the event: \Device\HarddiskVolume3\Games\Steam\GameOverlayRenderer.logthe message resource is present but the message is not found in the string/message table

Level: Information; Date and Time: 9/25/2011 11:49:23 AM; Source: USER32; Event ID: 1074; Task Category: None

The process C:\Windows\system32\winlogon.exe (DESKTOP) has initiated the power off of computer DESKTOP on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be foundReason Code: 0x500ffShutdown Type: power offComment:

Re: SSD 510 Series Drive Access Lockup

idata — Sun, 25 Sep 2011 16:32:05 GMT

Windows Logs:

Application:

Level: Information; Date and Time: 9/25/2011 10:55:16 AM; Source: Winsrv; Event ID: 10001; Task Category: NoneThe following application attempted to veto the shutdown: schedhlp.exe.

Level: Information; Date and Time: 9/25/2011 11:01:00 AM; Source: Winsrv; Event ID: 10002; Task Category: None

The following application was terminated because it was hung: ClashOfHeroes.exe.

Level: Information; Date and Time: 9/25/2011 11:01:04 AM; Source: Winsrv; Event ID: 10002; Task Category: None

The following application was terminated because it was hung: explorer.exe.

Level: Warning; Date and Time: 9/25/2011 11:02:05 AM; Source: WinLogon; Event ID: 6005; Task Category: None

The winlogon notification subscriber is taking long time to handle the notification event (EndShell).

Level: Warning; Date and Time: 9/25/2011 11:03:01 AM; Source: WinLogon; Event ID: 6006; Task Category: None

The winlogon notification subscriber took 116 second(s) to handle the notification event (EndShell).

Level: Information; Date and Time: 9/25/2011 11:03:01 AM; Source: Windows Error Reporting; Event ID: 1001; Task Category: None

Fault bucket , type 0Event Name: MpTelemetryResponse: Not availableCab Id: 0Problem signature:P1: Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)P2: 3.0.8402.0P3: TimeOutP4: 1.1.7702.0P5: fixedP6: 8 / 2049+P7: 5 / not bootP8: P9: P10: Attached files:C:\Windows\Temp\MPInstrumentation\client_manifest.txtThese files may be available here:C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Microsoft Securi_fb7ef137b9fc95f8461ffeb8533e3eb9ddc817c_cab_0439013aAnalysis symbol: Rechecking for solution: 0Report Id: 9d9d1b92-e786-11e0-b84c-6c626d1c7eb7Report Status: 4(there are two of these messages with the same info as above)

Level: Warning; Date and Time: 9/25/2011 11:04:03 AM; Source: WinLogon; Event ID: 6005; Task Category: None

The winlogon notification subscriber is taking long time to handle the notification event (Logoff).

Level: Warning; Date and Time: 9/25/2011 11:08:04 AM; Source: EventSystem; Event ID: 4627; Task Category: Firing Agent

The COM+ Event System timed out attempting to fire the Logoff method on event class {D5978630-5B9F-11D1-8DD2-00AA004ABD5E} for publisher and subscriber . The subscriber failed to respond within 180 seconds. The display name of the subscription is "Explorer". The HRESULT was 800705b4.

Level: Warning; Date and Time: 9/25/2011 11:08:04 AM; Source: WinLogon; Event ID: 6006; Task Category: None

The winlogon notification subscriber took 300 second(s) to handle the notification event (Logoff).

Re: SSD 510 Series Drive Access Lockup

idata — Sun, 25 Sep 2011 17:02:22 GMT

I googled with keywords "driver detected controller error on Ideport4" and found this post: http://www.techpowerup.com/forums/showthread.php?t=98068 http://www.techpowerup.com/forums/showthread.php?t=98068

The solution in that case was to replace the SATA cable.

Re: SSD 510 Series Drive Access Lockup

idata — Sun, 25 Sep 2011 18:48:08 GMT

I appreciate your responses, and I will ask the shop who built the desktop about this. I do not think this is the issue or will resolve the problem. I think it's an issue with Intel's hardware and/or drivers they must resolve. Lots of people seem to be sharing this problem, and I think Intel may even be aware of the problem.

I will take my desktop to the shop who built it. They did provide high quality and well costructed SATA cable for the SSD drives. I will get their opinion on this issue.

I will also try turning off AHCI in the BIOS to see if the issue goes away. Again, I think it's a hardware or driver issue.

I should have gotten a Mac Pro instead 😕

Re: SSD 510 Series Drive Access Lockup

idata — Sun, 25 Sep 2011 21:25:25 GMT

It looks like SSD drive # 2 (which is my data drive) has gone bad. My OS drive is good. I will have the shop contact Intel for an RMA.

Drive # 2 now consistently fails the Fast Diagnostic Scan. Drive # 1 still passes it for now. I tried switching from AHCI to IDE. This made no difference. Also, now the second drive never completes a chkdsk /f during boot. It only passes a regular chkdsk if I run it from within Windows.

I'm going to try deleting the partition and doing a full diagnostic scan on the drive.

Re: SSD 510 Series Drive Access Lockup

idata — Sun, 25 Sep 2011 22:59:29 GMT

The full format completed relatively quickly. Afterward, the SSD Quick Diagnostic scan passed. Good news, I thought.

However, the Full Diagnostic scan failed the Read scan. It still continued on with the Data Integrity scan. Now at 72%, the Operating System is locked up again.

I was under the impression that a storage device having no moving parts would be more reliable. It looks like I was terribly mistaken! (considering I've not lost data with a new hard drive to date).

At this point, there is nothing else I can do. I'll follow up with the shop who built the computer.

Re: SSD 510 Series Drive Access Lockup

idata — Sun, 25 Sep 2011 23:04:56 GMT

By the way, ideports 4 and 5 are my bluray burners. These are not my SSD drives.

Re: SSD 510 Series Drive Access Lockup

idata — Mon, 26 Sep 2011 00:18:39 GMT

The SSD Toolbox's full scan never got beyond 72%. It would completely freeze (along with Windows) then resume moments later. Windows ended up rebooting itself.

There were no additional details in the Event Viewer in regards to the reboot other than what I alreadly posted above. There were bunches of 3GB txt files on the root of my 😧 drive created by the SSD Toolbox. The files were huge that I did not have a chance to open. When I re-opened the SSD Toolbox, it deleted all the files.

Re: SSD 510 Series Drive Access Lockup

idata — Mon, 26 Sep 2011 14:09:39 GMT

This is an FYI for others experiencing failures with this SSD drive.

So I took my desktop back to the shop who built it. I explained the failures with the second SSD drive to the tech who built it. He hooked up the desktop and powered it on. I logged into Windows and ran the SSD Utility. I then ran the full diagnostic for the 😧 drive. It got beyond 72% and started on a second pass that I never saw before. It looked like it was going to work.. I was puzzled, but I remembered that the failures would happen around two hours after usage. What I did was cancel that test then run 3DMark11. I ran all test and set it to loop on extreme at 1024x768. I ran through all these test then stopped it at pass # 2. Secondly, I used TeraCopy to copy all files from C:\Windows to the 😧 drive. I also copied the eclipse folder to my 😧 drive. This is over 20GB of data. Last, I ran CHKDSK /F on both the C: drive then the 😧 drive. I then rebooted the computer.. CHKDSK started with the 😧 drive and it hung. I brought the tech back over to show the issue. It was at 0% for several minutes, which is abnormal for the first test. I explained that what would eventually happen is it would continue to hang for a very long time followed by showing read errors. After this happens, the Intel diagnostics would also fail after recycling the computer.. The shop has support with Intel, so someone should be able to figure out the failure with this SSD drive.

Re: SSD 510 Series Drive Access Lockup

idata — Mon, 26 Sep 2011 18:03:59 GMT

Thank you for continuing to publish your issues with this drive and attempts to fix them. I'm looking forward to any response you might get from your repair guy.

Re: SSD 510 Series Drive Access Lockup

idata — Tue, 27 Sep 2011 10:46:44 GMT

I got my desktop back. As suggested previously in this thread, the tech used two different SATA cables. I ran the same test prior to taking it home, and it passed.

I deleted the partitions from both SSDs, reformatted, and am reinstalling Windows and all software. One thing I noticed is that the Windows 7 experience index has now changed from 7.8 to 7.9 for the primary hard disk.

After everything is reinstalled, I will know if it is stable.

Re: SSD 510 Series Drive Access Lockup

idata — Wed, 28 Sep 2011 07:45:46 GMT

I have an Intel 510 SSD 120GB and it randomly locks up, very similar to what you have described.

In the last 6 months, I had 48 improper shutdowns logged by the SSD. It would help me greatly to find out what was done to fix your problems so I can look into mine.

I have changed 3 different types of SATA3 cables already, ones that came with the Intel SSD made by Amphenol, ones that came with the Asus P8P67 Pro motherboard, and ones I purchased from Vizo.

i7-2600 w/ Thermalright Archon

Asus P8P67 Pro2 X Asus GTX460 DCU TOP 1GB4 X 4GB Corsair Vengeance DDR3-1600 1.5vIntel 510 SSD 120GBHitachi 7K3000 HDD 1.5TBCoolermaster Silent Pro Gold 800W