It is the same error. Intels Update Tool doesnt show the last two digits of the serial. Parted Magic showed the serial as BAD_CTX 00000130 which is the 13x error we are discussing in this thread. I havent taken a screenshot from the Parted Magic info screen, but I've checked the serial twice before starting the secure erase. I'm a 100% sure of it.
Parted Magic 6.6 (Bootdisk, just burn it to a CD or DVD and boot it up) was able to secure erase the disk (no Intel SSD Toolbox, and therefore no two SATA Ports and another bootable Windows installation needed, for a step by step visit http://blog.corsair.com/?p=4484 ) which restored the 160GB (from 8mb shown before), as with everyone who was cought by the bug, all data is lost though. Luckily (!) I had a full disk Backup from four days ago. Which is now already restoring.
About 40min left to be up and running again.
I figure it is about time now to discuss, why suddently, after the firmware update - the 13x error starts appearing while Windows is running perfectly fine, on a Laptop with full batteries and whilst being connected to power. This was not a behavior we witnessed before. Intel has by far worsened the problem with the current firmware update - so please, give out a statement already.
Having the SSD fail once a month, with total data loss isn't a fair prospect. Fix it.
It looks like a LOT more problems occur on Windows systems, rather than on Macs ...
This is what I thought as well and why I asked several times in this thread if any Mac users who run solely OSX had problems after the firmwareupdate too.
My SSD runs smooth so far (osx 10.6, macbook pro) since the (painful) upgrade.
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.
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.
Thanks for the update - a reponse from Intel would be much appreciated!
Let me add though that when I was hit by the bug (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).