1 2 Previous Next 25 Replies Latest reply on Oct 16, 2011 10:50 AM by ryomitomo

    SSD 510 Series Drive Access Lockup

    Dryne

      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.

        • 1. Re: SSD 510 Series Drive Access Lockup
          cjwilson1

          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).

          • 2. Re: SSD 510 Series Drive Access Lockup
            Dryne

            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.

            • 3. Re: SSD 510 Series Drive Access Lockup
              Dryne

              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.

              • 5. Re: SSD 510 Series Drive Access Lockup
                Dryne

                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.

                • 6. Re: SSD 510 Series Drive Access Lockup
                  Dryne

                  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.

                  • 7. Re: SSD 510 Series Drive Access Lockup
                    Dryne

                    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.

                    • 8. Re: SSD 510 Series Drive Access Lockup
                      Dryne

                      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: None
                      General: 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.log
                      the 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 found
                      Reason Code: 0x500ff
                      Shutdown Type: power off
                      Comment:

                      • 9. Re: SSD 510 Series Drive Access Lockup
                        Dryne

                        Windows Logs:

                        Application:
                        Level: Information; Date and Time: 9/25/2011 10:55:16 AM; Source: Winsrv; Event ID: 10001; Task Category: None
                        The 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 <GPClient> 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 <GPClient> 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 0
                        Event Name: MpTelemetry
                        Response: Not available
                        Cab Id: 0
                        Problem signature:
                        P1: Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)
                        P2: 3.0.8402.0
                        P3: TimeOut
                        P4: 1.1.7702.0
                        P5: fixed
                        P6: 8 / 2049+
                        P7: 5 / not boot
                        P8:
                        P9:
                        P10:
                        Attached files:
                        C:\Windows\Temp\MPInstrumentation\client_manifest.txt
                        These files may be available here:
                        C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Microsoft Securi_fb7ef137b9fc95f8461ffeb8533e3eb9ddc817c_cab_0439013a
                        Analysis symbol:
                        Rechecking for solution: 0
                        Report Id: 9d9d1b92-e786-11e0-b84c-6c626d1c7eb7
                        Report 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 <Sens> 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 <Sens> took 300 second(s) to handle the notification event (Logoff).

                        • 10. Re: SSD 510 Series Drive Access Lockup
                          L10090

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

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

                          • 11. Re: SSD 510 Series Drive Access Lockup
                            Dryne

                            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 :/

                            • 12. Re: SSD 510 Series Drive Access Lockup
                              Dryne

                              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.

                              • 13. Re: SSD 510 Series Drive Access Lockup
                                Dryne

                                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.

                                • 14. Re: SSD 510 Series Drive Access Lockup
                                  Dryne

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

                                  1 2 Previous Next