And one that has been fixed a very loooong time ago, so I don't understand why it's rearing its ugly head again - it certainly does not happen here in any of my computers that go to Sleep. It will magically return to life once that happens (but, of course, nobody is going to sit there for 10 minutes or more staring at an unresponsive application).Īnyway, as you can see this is a well known issue. That continuous firing of the timers causes the application to stop responding to user input, using up all the available CPU, until the timers have fired the number of times they would have had the computer not been asleep. With a 10ms trigger, imagine how many times they must fire continuously to make up for a computer that has been in Sleep for a few hours. These are special very high-resolution timers (they can fire at 10 millisecond intervals), and that is why they are used for Nexus effect animations, but they do have a serious undocumented issue that also bit Mozilla's Firefox in the rear for a long time: if your computer goes to Sleep or Hibernation, when it comes back to 'life' the multimedia timers, instead of resuming from where they were, start firing continuously to make up for the lost time.

Nexus uses something called the Multimedia Timers to control animation timings. You must have a dual-core CPU, so 50% usage means Nexus is maxing out one of the cores. This has happened every single time that I have resumed from sleep.

Only thing that can be done is force shutdown of Nexus and restart.

Even after waiting 5 minutes, the dock remains frozen and high CPU usage. Upon examining Task Manager, I find that Nexus is 50% of CPU. Waking up from sleep on my Surface Pro 3, the dock is frozen.

Winstep nexus ultimate 16.2 patch