1-2 of 2 Answers
You need to setup the display to do nothing when lid is close in the Control Panel > Power Options. If power state is in Hibernate mode, the only way to wake it up is by pressing the power button.
Sorry, there was a problem. Please try again later.From what I've read, this seems to be caused by a power profile conflict between the MyAsus app, Armoury Crate power settings, and/or the built-in MS power profile. Try setting all of them to Balanced and see if the problem persists. If you do switch power profiles, only switch them in ONE of the above applications while leaving the others as-is. I think what happens is the power profile apps override one another but don't negate the effects of the other profiles. So, like, if my battery is set to Balanced in the battery app, but I set it to high-performance in MyAsus, then set my CPU profile to Optimized in Armoury, it causes a profile conflict where wake/sleep functions may not work as intended as they are contingent upon the power profile you set in the system. You could try uninstalling Armoury Crate entirely as it's a fairly chunky application and does affect numerous system functions. Of course you'll lose all abilities gained from the application, but it will free up a significant amount of RAM and uninstall any driver configs that may be interfering with the system. **NOTE** IF YOU DO THAT BE SURE TO SET ALL ARMOURY SETTINGS FOR THE CPU/GPU BACK TO STOCK OR THEY WILL BE LOCKED AT THE PREVIOUS SETTING UNTIL YOU REINSTALL IT. This can lead to hardware damage, or even total system failure as Armoury Crate is essentially an overclocking utility that rewrites the systems various clock speeds and power profiles. You could also try simply uninstalling and reinstalling it. In either case, revert the Armoury settings back to stock. You dont want your system spooling up at 4.xGhz without a controller for the battery/board/chip. MS driver updates could also be the culprit. Unfortunately, there's really no way to tell exactly without doing some hands-on troubleshooting via the various applications. I've had this happen on more laptops than I care to remember. It's usually an internal conflict with the drivers for the various profile applications. I hope this helps resolve your issue.
Sorry, there was a problem. Please try again later.
