2 Replies Latest reply on Apr 29, 2012 1:01 PM by NUT65

    Another failing 520 (SSDSC2CW120A310)

    NUT65

      I have enjoyed my X25-M drive for nearly a year without any problem, so this month I got myself a 120GB 520 drive... that has turned out to be a disaster so far.

       

      I had installed it as my boot drive, and used Acronis to get an image of my system on the drive. No problem, except I started getting the dreaded BugCheck F4 errors.

       

      My system:

      Asus P6T WS Pro (x58)
      Sata: Intel ICH10R (rev 12)
      Driver: iaStor 10.8.0.1003

       

      1st April: CRITICAL_OBJECT_TERMINATION BugCheck F4, {3, fffffa801174ab30, fffffa801174ae10, fffff800039965f0}

      EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

       

      2nd April: CRITICAL_OBJECT_TERMINATION BugCheck F4, {3, fffffa8010888b30, fffffa8010888e10, fffff800029db5f0}

      EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

       

      4rd April: CRITICAL_OBJECT_TERMINATION BugCheck F4, {3, fffffa801183b060, fffffa801183b340, fffff800029d45f0}

      EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

       

      6th April (#1): CRITICAL_OBJECT_TERMINATION BugCheck F4, {3, fffffa8010844630, fffffa8010844910, fffff800029d15f0}

      EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

       

      6th April (#2): CRITICAL_OBJECT_TERMINATION BugCheck F4, {3, fffffa80108a8b30, fffffa80108a8e10, fffff8000299c5f0}

      EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

       

      At that point I had more then enough, and put my trusty X25-M back in my system, re-imaged it and back in (stable) business.

       

      The 'broken' 520 is attached, so I started with a secure erase. After rebooting my system I wanted to check the drive, but again, it was partially missing at show from Disk Manager: http://www.helpwithwindows.com/img/DiskMan-SSD.jpg and SSD Toolbox: http://www.helpwithwindows.com/img/IntelSSDToolbox-520-missing.jpg

       

      I had spend the extra $$ to buy Intel in the hope of a quality product, but I'm now quite disappointed.

       

      I'll try to get this drive replaced and see how that goes.

       

      Also noted the crazy SMART details claiming the drive had been on for 102+ years and a gazillion errors (I know, seems an error in interpreting the raw SMART data by the toolbox software, but that is something that should have been fixed by now).

       

      Arie