Hi all,
I'm having some issues with my Latitude E5440, it randomly freezes and hangs. This happens a couple of times per day, when this happens the cursor in windows goes 'rotating circle' and nothing responds. When deleting files or creating folders nothing happens.
After a minute or so I can hear the cdrom drive make a 'whizz' noise and everything springs back into life again. When this occurs there is no cdrom in the drive. Whenever this happens an event is logged:
Source: iaStorA
EventID: 129
Description: Reset to device, \Device\RaidPort0, was issued.
I've done some research on this error message and it seems this is caused by ASPM (Active State Power Management) policy for the PCI Express Link State Power Management. Apparently the PCI Express bus goes into some sort of power savings mode but it does not wake up properly when required and it does not respond until Windows resets the bus or device logging that error message.
One advise was to entirely disable ASPM for PCI Express but this is obviously just a workaround as these features are designed to save battery life. I noticed that the problem did not occur when plugged into AC power so I checked the policies:
On battery: Maximum power savings
Plugged in: Moderate power savings
So it seems that the maximum power savings cause the issue. I have set 'Moderate' for 'On battery' now and it seems the issue has gone away. This way you still keep some power saving features. It's now configured like so:
On battery: Moderate power savings
Plugged in: Moderate power savings
For anyone interested, in Windows 7 this is found under the power settings in the control panel. From there edit the advanced settings of the current power plan. There you will find the settings under PCI Express --> Link State Power Management.
I'm using the latest "Intel(R) Series Chipset Family SATA AHCI Controller" driver (25/07/2014 v13.2.4.1000). The operational mode for the SATA controller is set to AHCI in the BIOS and I'm also using the latest BIOS available (A07).
Anyone has any clues to a permanent fix? Would this need raising an issue with MS or Intel? Surely I can't be the only one with this issue?