1 Reply Latest reply on Sep 5, 2013 12:26 PM by Diego_Intel

    Computer will not resume from S4 with IRST

    adamtoth

      I have a Lenovo W530, with a 256 GB mSATA primary disk drive. I've created the hibernation partition exactly as described for the UEFI setup, installed the latest Rapid Storage drivers available, and configured a timeout of 1 minute.

       

      When I put my computer to sleep, the power light is in a slow blinking state, in S3 sleep mode. After 1 minute, the hard drive light comes on indicating it is moving RAM to the SSD, the power light does the rapid flashing, and then the machine goes into low power S4 sleep mode.

       

      When pressing the power button to resume, the power light flashes rapidly, the hard drive light is active, and after about 30 seconds of activity, the computer cold shuts down, and all lights go out. Pressing power again initiates a cold boot, and there are errors in the event viewer about the system not properly shutting down. "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

       

      Very similar symptoms to this post:

       

      Intel Rapid Start Technology - Resume fail - Laptop General Hardware Forum - Laptop - Dell Community

       

      I've updated the BIOS to latest, the IRST drivers to latest, the SSD firmware to latest, the Lenovo Power Management drivers are current, I've disabled the Lenovo 30 day standby feature. This is on Windows 8 with Hibernate turned off.

       

      Any ideas? Can't get IRST to work at all.

        • 1. Re: Computer will not resume from S4 with IRST
          Diego_Intel

          This is an OEM dependent feature, so check with your Original Equipment Manufacturer to see if the system does support this technology and then check directly with Lenovo for information on known issues and the proper configuration for this feature on your system.

           

          In addition be sure to be using the latest software releases from your Original Equipment Manufacturer and avoid using generic versions while troubleshooting this issue.