Jump to content
Corsair Community

Intermittent Disk Lock-Up


akjohnston

Recommended Posts

Hi,

I have a problem on my big Alienware laptop which seems to be related to the SSD, so I'm hoping someone here can help.

 

Randomly, a couple of times a day on average, my hard disks just "lock" for about a minute. The symptoms are:

  • Disk activity light stays ull on for about a minute
  • No disk access is possible during that time
  • There may be an error in the system event log "The driver detected a controller error on \Device\Ide\IdePort0."

At the end of the lock-up the system may simply recover and continue without problems, or it may crash with a BSOD.

 

This seems to be related to the SSD, as it started when I changed my primary drive to an SSD (the system was OK when on a traditional primary drive). However I have had the same problem with two different SSDs from two different sources, so it's not related to the specific disk or Corsair-specific.

 

This is really annoying, as otherwise my system's very fast and reliable. It does seem to be triggered by two or more processes hitting the storage concurrently - it often happens when I'm doing something in a VM and on the host. On the other hand if I'm careful to execute big disk jobs such as compacting a VM with the system otherwise quiescent it's usually OK.

 

Things I have already tried to improve matters include:

  • Re-installing Windows from scratch
  • Trying both Intel Rapid Storage Technology and Microsoft drivers
  • Upgrading the firmware of both SSD and motherboard
  • Setting the BIOS to RAID or AHCI

None of these makes any difference, although the problem does seem to be a bit worse with the Intel RST drivers and bit better with the Microsoft drivers.

 

Please can anyone think of anything else I can try or check?

 

Thanks

Andrew

Link to comment
Share on other sites

Hi,

My machine is an Alienware M17xR3, with a Corsair SSD as disk 0, and a maxstor XT as second disk.

 

I don't think I have any power saving settings for the disks, but I'll check. the problem isn't triggered by a timeout, as it can occur immediately after booting.

 

Any other ideas?

Thanks

Andrew

Link to comment
Share on other sites

  • 2 weeks later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...