So I guess nobody knows anything? That is sad
First install the Rapid Storage drivers.
After that install the old Turbo Memory driver - Not the Matrix Storage.
That is what I already tried, I mentioned it by this in the original post:
"When installing the Matrix Storage Technology again (to have the Turbo Memory working again), the installer warns me that I have newer storage drivers already installed and asks me if I want to continue. The big mistake is that it is trying to install an older AHCI driver than I already have installed using RST. So when I answer "yes", I get older AHCI drivers and my eSATA stops working."
I already had the "INVM110ENU.exe" installer file on my drive (available as the most recent driver on the page you gave me link to). It asked me if I want to install older drivers as previously (cannot insert images here, who knows why, so it is here:http://i55.tinypic.com/25pk67n.png ).
Currently, my eSATA drive is working and I have Rapid Storage Technology installed. However, in the Device Manager, there is Intel Turbo Memory Controller with a yellow exclamation mark and description "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)".
Any other ideas?
sorry, i forgot: now go into the device manager, click the Turbo memory an select the right driver (intel turbo memory) . this works fine for me, because i had the same problem an this was the solution :-)
Well, I don't believe that it was not neccessary... I let it change the drivers for older version and everything is suddendly working (including eSATA). Probably some update from M$ (maybe SP1) fixed that issue. However, after filling the Intel memory with my everyday applications, I see absolutely no difference in speed of launch. Everything seems to be read from HDD anyway as I see it reading very intensively when launching the applications. The other problem is that now I have ITMService.exe running and eating 50-60% of my dual-core CPU continuously. My computer is running for about 6 hours with no change in this behavior. According to Google I am not the only one with this problem but Intel does not seem to care about this issue. I regret paying for such "technology"!
I only have a 1gb module and therefore there is no user pinning (ITMService.exe). but you are right - shame on intel for this c....y piece of s..t !
I also struggled all night to solve the conflict between Matrix Storage and "Trouble" memory... My problem is a little bit different though. I found out older version of Matrix storage (8.x) prevents the Windows 7 (64) update and defender from working normally (service cannot be started etc). Therefore, I updated the matrix storage driver to 9.x and up (aka Rapid storage), but this kills the Turbo memory (error code 19). I took me several hours to try out all the combinations of drivers for these two devices, and realized it was the problem of Mcafree... So my suggestion is removing the antiviurs software before the trouble shooting.
Sys info and working driver versions:
Thinkpad T400 Win7 64
Hard Drive: WD5000BPKT
intel ICH9M-E/M SATA AHCI 10.1.0.1008
Turbo memory 126.96.36.1992
Hm, I thought everything was working fine, but, as usually, I was wrong. From time to time (usually once a week) my laptop stops responding completely and the music currently playing gets stuttered in an unlistenable loop. I then have to shut it down forcefully by holding the power button.
When this happens, my eSATA drive is still spinning but its power/activity LED is off. After booting the system again and re-plugging the drive, it does not do anything in the computer. I have to turn the drive off and then back on for it to be recognized. Back in time, when I was creating this discussion, these symptoms occurred immediately after plugging the eSATA drive in. So now it is just random. I would sell the "trouble memory" if there was anyone needing/wanting it but this would be problematic as it is no longer supported by Intel and is causing such problems we all are describing.
Looks like some very, very poorly programmed sh*t from Intel hit us...