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]

harlekin,

Thanks for the update - a reponse from Intel would be much appreciated!

Let me add though that when I was hit by the bug (/message/132139# 132139 before the firmware update was released), my laptop too was running normally up to that point.

It had a fully charged battery and was docked with DC power attached when Windows froze (no blue screen).

[idata]

System is back up and running. n8 e/o.

[idata]

Guys, Gals - stop diluting the problem. With Mac usage figures around 10% overall and a high likleyhood of people who can install firmware updates also having Windows installed on their Macs it is nothing extraordinary. Plus the problem has effected Macs as well. I myself am writing this on a Macbook Air, and I am not prone to fanboiism.

From the very beginning, when the new problems started to surface this thread was full of the wildest speculations why it certainly would not be firmware related. Well Intel said it was, and they said they fixed it. Which they didn't. So why all of a sudden have they become so quiet - and why are there so many appologists roaming this forums.

Back up ( ) and be sure that the bug will hit you too - its only a matter of time. As long as Intel doesnt speak up again, recognice that you've got a highly faulty product which is prone to fail, and Intel knows it. Still Intel is advertising it as "more failsafe" than every other brand, because otherwhise they have no advertising angle. It is a farce.

[ZStan]

Few ppl complained, thats all, and none had problem after unsafe shutdown....so is not like they did`t fix it, there might be others problems with firmware or just plain bad hw

[idata]

thanks harlekin for your response, I just called the retailer and will have my intel ssd exchanged for another brand.

enough (more then enough) time wasted on this issue, I cannot risk my macbook not booting at a client again.

bye bye, intel. brilliant customer service / care.