Getting BSOD with Corsair SSD Force 3 240 GB on Windows 7 64bits

[Chivukula]

I have a Lenovo T410 Laptop, on which I replaced the boot disk with a Force 3 240GB. I am having little trouble at start, although after: BIOS upgrade, AHCI upgrade (Intel version) and firmware upgrade (1.3.3) the system boots and works. Nevertheless I still have an asymmetrical BSOD.

Sometimes I also lose access to the SSD at reboot, removing power typically resolve the matter any recommendation on solving this matter?

[Vicky Woodley]

Having the exact same issue and assuming I just have a lemon as I have owned more than a few other brands with no troubles. I am going to exchange and attempt the similar drive once more. I hope that the new-fangled drive works as I was an enormous fan of Corsair product. Am losing many hours of work and family time.

[Hymavath]

If you are still having trouble after upgrading the firmware, it is recommended to carry out a SecureErase and a clean Win 7 installation. It's worth attempt.

[Amadou]

One can also notice that the physical memory dump FAILED with rank 0xC0000010 that, in my view, is also a matter of the SSD not being available. Lastly, when the system first rebooted, the disk was not reachable, another reboot solved the matter.

#define STATUS_DELETE_PENDING ((NTSTATUS) 0xC0000056)

[Guntoor]

TW ntstatus 0xC0000010, which is the error notified during the memory dump is:

#define STATUS_INVALID_DEVICE_REQUEST ((NTSTATUS) 0xC0000010)

This seems to demonstrate that the drive is in fact not noticeable at the time of the memory dump.

[Denholm]

The last two-three times it happens after a few minutes of usage after a resume from sleep. The laptop recovers from sleep without any trouble, although it freezes, disk access led blinks progressively and then I acquire a blue screen. This morning, the case was a little bit dissimilar, the all PC froze after 5 minutes of practice, I had to cut the power to regain access to it.

After most of the crash I got the windows 7 repair tools running, without finding any solution, I just ran the sfc 

/scannow:
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Windows\system32>

[Gameli]

I established the driver management console that it is the actual driver used. I will de-activate the registry trick and perceive how it goes. In the mean time, I had two complete freezes of the system, and one blue screen. Those where
during normal practice of the system, not correct after a resume from sleep. None of these events produce a dump file. The mistake of the blue screen remains the identical, mistake in accessing the pagefile.I'll let you know how it
goes with the LPM removed.

[JErastus]

I presume there is no workaround for this destructive technique, you can backup your OS and restore it after SecureErase, although there is a little possibility that the matter will be restored as well. Only a clean installation will
help in this case.

[ErikaGeek]

My lpm setup

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port0]
"AN"=dword:00000000
"LPM"=dword:00000001
"LPMSTATE"=dword:00000000
"LPMDSTATE"=dword:00000001
"GTF"=dword:00000001
"DIPM"=dword:0000000

[Naq]

Anyhow, if you have Intel RST installed, it is suggested to disable LPM for the port your SSD is associated. I attached records with .reg files to enable/disable LPM on Port 0 or on all ports.