8/13 Update on "Bad Context 13x Error" for Intel SSD 320 Series

[idata]

Status:

Intel has reproduced, identified root cause, and developed a firmware update which addresses the Bad Context 13x Error being discussed on the Communities site and elsewhere.

Response plan:

The new firmware update is in final validation testing and is targeted for release on Intel® Communities within the next two weeks. Intel takes firmware updates and issues of reliability very seriously and is taking extra steps to support a smooth release. We appreciate your patience.

What should I do if I have not experienced this issue?

To minimize occurrence, if a system requires a shut down, Intel recommends using that system's standard power shut down sequence. As with any storage device, Intel recommends users frequently back up their data. Download and install the new firmware when it is available. As with our previous firmware updates, a secure erase is not required.

What should I do if I have experienced this issue?

If you have already experienced a drive failure or encounter this problem before the firmware update is released, please contact your Intel representative or Intel customer support (via web: http://www.intel.com/ www.intel.com or phone: http://www.intel.com/p/en_US/support/contact/phone www.intel.com/p/en_US/support/contact/phone) for an SSD replacement. An alternative option is to use the Intel ® SSD Toolbox or similar tools to perform a secure erase in order to restore the SSD to an operational state; all data will be erased. After secure erase, update your SSD with the upcoming firmware. The pending firmware update will not recover user data.

Background:

For users unfamiliar with the issue, an Intel SSD 320 Series drive may exhibit a drive capacity of 8MB and an electronic serial # field containing a message of "BAD_CTX 0000013x" due to an unexpected power loss under specific conditions. Once this error occurs, no data on the SSD can be accessed and the user cannot write to or read from the SSD.

Rgds,

Scott

Intel Corporation

[idata]

Why don't you open a new thread instead of writing here? I don't think the two problems are the same...

[idata]

SSDelightful what is the status with the firmware for the 320 series? Your OP says you fixed the issue but there are all these contradicting posts that the issue is not fixed. Can you explain more about what caused the issue and what you did to fix it, and what may be the cause of the issues that others are still reporting in this thread? I bought Intel for reliability (and encryption) but if the former is no good that's gonna be a problem.

[idata]

The problem seems to be repeatable after installing some (!) Windows 7 updates.I had a crash in November, 2011, did the secure erase, updated the Firmware.Now, 2 months later I got the same problem and it started after today's update.

From time to time, Windows has updates that require to reboot twice: you install updates, shutdown, turn it on, then PC is restarted by Windows and after that - the OS loads with updates. The OS loaded fine, but one of my databases wasn't "accessible". Check Disk shown no errors, but I couldn't copy the files to another drive. The copying hanged and then the drive "disappeared". After reboot, I got the Bad Context Error 136.

Now even after secure erase, the Full Disk Test (thru SDD Toolbox) fails. Returning for an RMA, VERY SORRY for Intel.

I understand that they got a little bit "behind", but this is no excuse to release unstable product.