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]

What drivers are different? The driver version you stated is the same one in my retail version of Windows 7 x64 for the AHCI controller.

[idata]

weuntouchable,

You didn't read my post. I said some users may not have followed directions and some users HAD LEGIT ISSUES. Evidently you didn't read that part.

The reason why they are replacing the drive is because that it is "a good business practice". It does not mean that there is something wrong with their firmware. This is why they pulled the firmware until they can pinpoint what the source of the issue is.

The firmware has to interact with the computer, therefore in your case the Microsoft OS and vendor chipset drivers become variables that need to be eliminated in order to prove that it is a strictly a firmware issue. In order to prove that this is a firmware issue, one would have to upgrade the drive, then check OUTSIDE of the WIN OS that the the firmware was flashed correctly. If the drive was flashed successfully, then that means that the Intel firmware PLUS SOME OTHER VARIABLE, yet to be identified causes corruption.

The question is can Intel fix the issue through their firmware or does it require a microsoft and/or vendor chipset update. i would hesitate to be so smug in thinking that it is strictly an intel issue and then discover that it is a non-intel issue that intel can't fix. This would not be the first time of something like this happening where there is a incompatibility between the WIN OS and a vendors driver/firmware (i.e. audio, video drivers).

[idata]

dbm,

You apparently failed to read my post where I said its impossible to upgrade the firmware if the SATA ports settings are not correctly configured in the BIOS. That eliminates any user error aside from unplugging the drive or powering down the system during the upgrade. I'm not saying the firmware in and of itself is bad, I'm simply saying that user error can not be the cause of this widespread failure because Intel idiot proofed the update process by detecting what the SATA port is set to and not allowing the drive to be detected if they are not setup properly.

I personally think the problem is either a bad batch of drives or a driver conflict. I don't think the firmware by itself is bad because then 100% of the drives would be bricking. Its the firmware in combination with some other, at this time unknown, factor.

[idata]

Quoted from weuntouchable

"You apparently failed to read my post where I said its impossible to upgrade the firmware if the SATA ports settings are not correctly configured in the BIOS."

Very much incorrect. The instructions with the flash tell you to set your drive to IDE mode in your BIOS. A LOT of people including myself did not do so and flashed the drive with no issues with it still in AHCI mode in the BIOS. Some OEM systems dont even have an option in BIOS to change the ports mode. Fortunatley I have not had any problems in the day and half since. Multiple reboots, couple of sleep cycles, etc.

If it matters - my system is a home built.

Abit IP35 Pro motherboard with an ICH9R chipset.

Windows 7 Ultimate x64 RTM from Technet

The ICH9R controller was in AHCI mode all along, Windows 7 had been running with it in AHCI mode for a couple of weeks since I installed it. It booted from the CD I made and flashed just fine. Rebooted, Win 7 hit and automatically installed new drivers for the SSD. Rebooted again since Win 7 asked it to. Been fine since. The toolkit works and everything.

One thing for me though. I had previously installed the Intel chipset inf drivers and those are the drivers on my AHCI Sata controller. They still are and I'm definitley not planning in trying to change it to the original Windows AHCI driver right now as I'm terrified that will probably hose my SSD.

[idata]

We have the same chipset, and I updated two SSD with no issues, and mine is also home built.

By the way, what inf drivers did you use?