It depends on what is actually happening, and without being able to reproduce the problem here I can only guess. Wouldbit be possible to build in a failsafe ino timers themselves? That before they fire they check a variable? I also heard the Surface Pro laptops have (had?) multiple power saving related issues. TL DR: Microsoft has made a huge mess with this. However, this might be too late - if the application does not receive that critical PBT_APMSUSPEND notification and thus does not kill the timers before the fact, it can happen that on resume the timers will start firing immediately and continuously even before the application has had time to process the Resume notification (in which case it won't until the timers have finished firing every single one of the missed 'ticks'). Just in case, when I get a notification that the system has just returned from suspend and the timers are still active (they shouldn't be), I kill them anyway to try and prevent them from firing continuously. Obviously the timers will remain 'dormant' if the notification is not received, ready to unleash hell as soon as the system wakes up again. just before the system is suspended) I kill the multimedia timers so they don't start firing continuously when the system resumes. Now, as I explained above, when receiving a PBT_APMSUSPEND event (i.e.

There is no reply to this post, and thus no resolution. They are only notified when the system resumes. HOWEVER, I also spotted a post from a developer complaining that, at least under XP SP3, if ForceCritical is set to TRUE applications do NOT receive the notification that the system is about to be suspended (PBT_APMSUSPEND). According to the documentation, ForceCritical 'has no effect'. Here is where it gets tricky though: to put the system into a power saving mode, you use SetSuspendState, which has a ForceCritical parameter. Besides PBT_APMSUSPEND there is also a PBT_APMSTANDBY, but the documentation says it's not used/supported. The documentation itself regarding power events is confusing enough. Are you sure you don't mean Sleep instead of Standby?Īnyway, in case you - or someone else - is curious I've been looking a bit more into this. One more thing: Standby is not the same as Suspend (Sleep).

Winstep nexus ultimate 17.1