Originally Posted by docp
system is set in AHCI mode from bios , I dont know why its not showing here.
where can I confirm its AHCI?
you would not be able to install that Intel driver it the bios was not set to AHCI or RAID mode. So, you are most definitely running it in AHCI mode.
Tight on time here so I will try to type quickly and get the main points across.
Bios related issues and SF controlled drives: Intel may have tested this drive more than others prior to releasing it.. but I can tell you without doubt that it was not purely by choice. It merely took them that long to get the OS's drivers and power mgmt(both BIOS and OS) to jive with the controllers limitations. Not to mention that they pooled together all the fixes and troubleshooting done by the umpteen other companies who had been using it for more than a year by that time. Not all is as it seems and there surely are many combo's of bios/OS/drivers that they have not validated.
Best way that I know of to reduce those incompatibilities is to:
flash the latest bios
latest drivers(both IME and sata related)
reduce, or even eliminate, power saving features in bios AND OS(tough to do on mobile platforms)
ONLY use an OS that's been validated on the hardware in question
As for the various bays used to run SSD's. Just because it's spec'd for sata3 means squat for how it's been hooked into the bios and there's a hell of a lot of incompatibilities flying around the net right now. Wiring, bios, power mgmt, OS used.. you name it.
Also keep in mind that W8 has given tons of issues for many around the net(SSD and HDD based systems) from mixing and matching the various drivers, bios, and OROM's. This can, and has, resulted in all sorts of issues.. including lost or corrupted drives.
Mobile platform users should also be aware that there are still some major incompatibilities with certain SSD firmwares and the sure fire way to make sure you're not an unsuspecting guinea pig is to see if that soem hardware combo is available from that specific mfgr. If it is not?.. then you are working with invalidated hardware/software combo's and need to tread lightly with mission critical data and make regular backups. Dell has, and still is, known to be one of the worst out there in that regard. So, I generally tell most people that.. if you can't get it spec'd that way from the factory?.. good luck with it.. because you'll need it and it'll be hit or miss.
To the OP of this thread. I would highly recommend installing this suspect drive as a spare on another PC to make an image, secure erase, and reimage it with the same backup image. Especially after hitting it with those particular random/incompressible benchmarks.. and extra especially if it was filled more than 70% at the time of testing.
Update firmware once more. Not sure if Intel allows overflashing an already updated firmware.. but if it does, that assures you have refreshed the code and may eliminate any corruption of that physical space.
At the very least.. for troubleshooting purposes.. I would eliminate many of the various power saving features to help reduce variable. Move from S3 to S1 in the bios. Set to high-performance power plan and in advanced pwr mgmt options to never shut the harddrive down. An overnight idle will usually be sufficient for the drive to maximize/optimize it's available space.
I would also lean down the amount of data stored prior to idling the machine either in the bios or at login screen to better allow the firmware to clean the physical space and assure you have alrger fresh block pool to test with.
PS. if you want top speeds for benchmarks?.. do the above mentioned power mgmt tweaks and disable speedstep(EIST) to get them. Is completely reversible and you don't have to live with them longterm. That will just let you know what the hardware will allow(minus some OS/boot drive overhead, of course).
Bout all I have time for right now but hopefully you can pick something good out of all that. I HIGHLY doubt that the drive is at fault from a physical standpoint and has to do more with bios/power mgmt/ software. But the ONLY way to test that for sure is to tweak away and test?.. or have the drive replaced and reimage that EXACT OS BACKUP while running the same exact bios. If the problem remained after that replacement was swapped in?.. you have to either work around the firmwares limitations with some of the above mentioned?.. or go towards another SSD controller.
BUT.. it is a Dell we're talking about here.. and Sandforce is NOT the only one having issue on their hardware. Good luck with it.