TRIM update hosed my Windows 7 install

[idata]

Just did the firmware update and it hosed my Windows 7 installation. The updater showed a successful firware update. Initially the computer booted just fine, but once I was within Windows it installed some drivers and asked for a reboot. That's when the trouble started. Now the drive won't boot Windows 7 anymore. I don't know if it's a Dell problem or Intel problem. The Dell BIOS claims a SMART error. I have a Dell XPS 8000.

[idata]

This is 100% the firmware problem and 0% user error because the firmware won't allow you to update your drive if the SATA ports are configured incorrectly. Where is there any room for user error in the procedure when the firmware update won't work unless things are set properly. Maybe a person could have powered down or disconnected the drive causing it to corrupt, but this is way too widespread for that to be the case. You don't know what you are talking about trying to push the blame to the end user. Intel has replaced every drive from those who have requested a RMA due to the firmware upgrade, so they are obviusly admitting they did something wrong here. Lets also not ignore that this was their second major screwup with this particular drive, or did everyone all ready forget the BIOS password recall.

[idata]

dbm, you are quite correct. I was pointing out that it was either the windows driver corrupting things post-1st boot or something in the firmware that does not like the hardware; the latter I struggle to see how it works due the the successful post-firmware boot. It is, in the case of the former, v.extreme for a windows driver to hose the basic settings of a drive and this is the worrying aspect of this issue Post boot-problems are then not OS issues with a driver it seems - they are more fundamental.

Hmm .. wonder if the version of Windows 7 Mine was not the retail but the final MSDN version available for some 4 weeks prior to launch. We know the release one has had changes. I have also had to refuse a LAN driver update from Windows update as it always stops my interface from working. I see someone also had a Windows server 2008 problem with the update.

[idata]

Good point justguy. My Win7 version was the Technet version. I thought no matter where you got the RTM release they would all be same build. Maybe there is something that is different.

[idata]

Yes and no weuntouchable.

The issue appears to arise once you reboot and Windows 7 loads a new driver for the re-flashed drive. It is only then that people have issues at the next reboot. It thus appears to be an issue that the driver initiates and it seems to be this s/w that then hoses the drives.

However, the driver interacts with the firmware so, yes, you can fairly point the finger at the firmware as this is the changed element of the system. However, it is also an MS driver at issue here ... I suspect there are some interesting phone calls between Intel and MS at present.

My working driver is 21/6/2006 : 6.1.7600.16385

It is the same driver all the SATA drives use.

[idata]

Yup - I know for certain my MSDN version is not identical to the released one I have on other office machines in the UK; some drivers have been updated as far as I can tell. Did not really pay attention to other changes.