Windows 10 Screen Saver getting killed when display is turned off due to powersave timeout.

liz08

Active Member
Joined
Oct 9, 2017
Messages
21
I have a frontend application always running and receiving windows messages.
When screen saver timeout is less than powersave timeout, my screen saver is getting killed and my frontend application is not receiving WM_POWERBROADCAST message when the displaying is going for sleep. Also due to user activity( like mouse move/ keyboard event) , if i am trying to wake up the display immediately , my frontend application is still not receiving the WM_POWERBROADCAST message.
Can you please let me know why my application is not receiving WM_POWERBROADCAST message?
 
Solution
It seems like your application is not receiving the WM_POWERBROADCAST message consistently when the screen saver or power saving mode is triggered. This issue could be due to various reasons. Here are some possible explanations and solutions:
  1. Message Blocking by Other Prioritized Messages:
    • The issue might be that other messages are being processed in your application's message queue before the WM_POWERBROADCAST message. Ensure that you have a mechanism to prioritize or handle important messages promptly.
    []Thread Blocking:
    • Check if the thread in your application responsible for processing messages, including WM_POWERBROADCAST, is not blocked or occupied with other tasks...
Sort by date Sort by votes
It seems like your application is not receiving the WM_POWERBROADCAST message consistently when the screen saver or power saving mode is triggered. This issue could be due to various reasons. Here are some possible explanations and solutions:
  1. Message Blocking by Other Prioritized Messages:
    • The issue might be that other messages are being processed in your application's message queue before the WM_POWERBROADCAST message. Ensure that you have a mechanism to prioritize or handle important messages promptly.
    []Thread Blocking:
    • Check if the thread in your application responsible for processing messages, including WM_POWERBROADCAST, is not blocked or occupied with other tasks. Ensure it stays responsive to messages.
    [    ]Message Handling Errors:
    • Make sure that your application's message handling logic for WM_POWERBROADCAST is correct and not causing the message to be missed or overlooked unintentionally.
    []Time Critical Operations:
    • If your application performs time-critical operations or lengthy tasks when receiving the message, it might miss subsequent messages. Try to keep message processing lightweight.
    [    ]Event Registration:
    • Verify that your application is properly registered to receive power broadcast messages. Check the event registration code or setup that listens for these messages.
    []Message Filtering:
    • Check if your application is filtering out specific messages, including WM_POWERBROADCAST, due to wrongly implemented message filtering logic.
    [    ]System-Wide Hooks or Interference:
    • Some system-wide hooks or third-party applications might be intercepting or blocking system messages. Ensure that there are no conflicts with other software.
  2. Debugging and Logging:
    • Implement logging or debugging mechanisms in your application to track the flow of messages, especially the WM_POWERBROADCAST message, to identify where it might be getting lost. By investigating these possible reasons and ensuring that your application handles power notification messages correctly and efficiently, you should be able to resolve the issue of missing WM_POWERBROADCAST messages in your frontend application.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.