cancel
Showing results for 
Search instead for 
Did you mean: 

Firmware update now available - Addresses Bad Context 13x Error

Alan_F_Intel
New Contributor III
New Contributor III

Status:

Intel has posted a firmware update for the Intel® SSD 320 Series (firmware 4PC10362) which addresses the Bad Context 13x Error being discussed on the Communities site and elsewhere. You can download the new firmware here:

http://www.intel.com/go/ssdfirmware www.intel.com/go/ssdfirmware

Also posted at this link are Read Me, Release Notes, and SSD Firmware Update Tool Guidelines which provide detailed firmware update instructions and other relevant information such as the most current firmware revision available.

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

In order to provide the best user experience, Intel always recommends users download and install the latest firmware. As with any storage device, Intel recommends users frequently back up their data and periodically check for firmware updates. The http://www.intel.com/go/ssdtoolbox Intel® SSD Toolbox provides a host of utilities to monitor your SSD, including displaying detailed information such as the currently installed firmware revision.

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

If you have already experienced a drive failure or encounter this problem before the firmware update was 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 new firmware. The 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" caused by 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,

Alan

NVM Solutions Group

94 REPLIES 94

idata
Esteemed Contributor III

I guess it is a good sign that nobody seems to have issues anymore?

idata
Esteemed Contributor III

Umm.. Slow down right there. I had a 320 300GB drive that I had been using for a couple of months. Made a backup and then updated the firmware over the weekend. Yesterday while I was working the system freezed completely powered it off and booted up and was greeted to a no operating system found message. Extracted the drive and confirm that I know have the dread 8MB bug AFTER applying the firmware fix. Not a happy camper right now and I have a few more of these things. Now I am thinking that I never should have applied the update.

idata
Esteemed Contributor III

Dear Corporation, how long do we have to wait this time? 6 months, 5 years? How can I get my money back for 3 SSD I can't use (two of them with 8Mb bug, recovered) 3 months already? I believe seller won't take it back easily, as they "working" now. Your support is silent as lambs. Will you provide any memo that you refund money to distributors in this particular case? I have great plans on intel SSDs, but your "get lost" reaction ruined it, not bug itself (bug happens).

idata
Esteemed Contributor III

Wrong approach, courthouse language is the ONLY language corporations like intel understand, otherwise you're wasting your time.

idata
Esteemed Contributor III

Help! I'm trying to apply the update, but the ISO won't boot correctly, it's buggy. I'm getting the following message:

----- begin excerpt -----

InitDiskCONFIG.SYS error in line 0

>>>SSHELL=A:\command.com /P

^

bad or missing Command Interpreter: A:\command.com /P

Enter the full shell command line:

------ end excerpt ------

I've tried a variety of entries, nothing worked so far. I tried unpacking the .exe in the disk, can't seem to do that either.

Any suggestions?