SSD slowdown after BSOD

Hi all! I have an 840 Evo 120 GB (latest firmware, OP and RAPID enabled) on my Aspire 5750G and it was really fast... but a few days ago after a bsod (it dealt with Daemon Tool) and several restarts, my SSD dramatically slowed down in all its tasks. After looking everywhere for a solution, I decided to write here hoping there's someone who can help me! I think that some SSD auto-protect settings has been enabled since the bsod and now performances are really poor; or worse it could have been electrostatic discharge.. what do you think about? Here's some benchmarks.

1) pciide driver / Test ran in safe mode (30/Jun/14)


2) iaStorA driver / Test ran in normal mode / Intel RST drivers: 11.5.something / (30/Jun/14)


3) iaStorA driver / Test ran in normal mode / Intel RST drivers: 12.9.0.1001 (30/Jun/14)


And these are two magician tests:

1) 17/Oct/ 13


2) 30/Jun/14


Results are pretty clear... I don't know what to do guys, one moment all works perfectly and the day after the breakdown. Help me!!!

P.S. Sorry for my English

 

Have you tried (in order and without using the computer for 'work'):

uninstalling/disabling RAPID,
disabling the pagefile,
disabling the hibernation file
disabling System Restore and
disabling the sleep timers.

and let the system idle for a few hours (I recommend at least 6-8 hours - overnight is ideal)?


After doing the above, enable the services you need, install and enable RAPID again (there is a new version available: 4.4) if you must and see if your performance has been restored.


Good luck.

 

@ tilleroftheearth I've already tried some of the hints you listed but not every step, I'm gonna try this. Just to be clear when you say "let the system idle" for 6-8 h do you mean system has booted etc or I have to boot in the bios and leave it that way? (I read somewhere that it might be a solution)

1) It's a clean install
2) AHCI has been always turned on
3) Yes, my SATA port is SATA 3
4) I'm currently using ESET NOD32. I haven't scanned the system yet but I doubt it's a virus-driven issue, I haven't downloaded anything suspicious (I'm gonna do it anyway)
5) As far as I know PCIIDE should be the standard (Windows) driver for the IDE protocol. Running in safe mode involved using this driver. However I didn't know RAPID would work better along with MSAHCI.

By the way in the meantime I uninstalled Intel RST drivers and restored the standard one (it's called storahci.sys but I read it should work exactly as msahci). The last bench showed increased values for sequential r/w but they didn't improve the actual speed (from boot time to open applications etc).
Here's the screen (I temporarily re-enabled RAPID):



Passing by 4K scores, access times seem ridicolously high to me

 

Thanks for your reply and for the EVO&msahci pair, I'll keep it in mind. I thought about cloning the SSD on an external HD and then format the drive and perform a clean install of the OS again. By now two things could have happened in my opinion: 1) some settings have changed due to auto-protect of the SSD (if it exists something like this); 2) The several power-cycles during BSODs modified something at low level in the SSD.
In the worst case I could take advantage of warranty.
I'll keep you updated

Well I performed data wiping through Secure Erase provided by Samsung Magician, then I installed Windows 8 again and here's the benchmark at first boot:



And this is after I updated the Intel Chipset Driver:



As you can see in both cases the default driver is storahci so I think that maybe is simply an evolution of msahci from Windows 7.
Now SSD speed is as fast as it used to be but it's still a mistery to me what was causing troubles. I'm gonna recover the old OS backup and.. let's see what happens

 

Ok gentlemen I found what caused the SSD to be so sluggish. Well... it was "Driver Verifier Manager", accessible by typing "verifier" in "Run" (image below)



I tried the third option, translated means "Delete existing options". Alright, let's reboot... After the reboot I didn't believe it, my laptop is now as fast as before.
Long story short, imho power-cyclings caused BSODs, BSODs must have enabled some unwanted option in this Driver Verifier Manager (maybe about AHCI driver, I have to find it out) and here is the slowdown.

Solution comes out when you don't think about it