Cause-and-effect relationship between RuntimeBroker.exe and entering and releasing sleep mode

환희 이 1 Reputation point
2021-05-12T07:40:34.787+00:00

Windows 10 1909 English OS is in use.

Entering Powercfg.cpl, the power management option is in use with high performance.
Turn off display: 3 minutes, put computer to sleep: Not applicable status
Advanced Settings: 1) Turn off hard disk after: 0, USB Settings: USB Optional Sleep Settings: Disabled

Fault content is

  1. Turn off the display: Set the computer to sleep mode for 3 minutes: Not applicable state or display turns off and enters sleep mode.

2) Event ID: 187 / This message appears in the Sleep Restore stage.

  • Based on XML of the contents of the log,

Description: The user mode process attempted to change the system state by invoking the SetSuspendState or SetSystemPowerState API.

<Data Name = "ApiCallerNAME"> C:/Windows/System32/RuntimeBroker.exe

Judging from the appearance of , it is determined that the symptoms of the disorder may also be related to Runtime Broker.exe.


RuntimeBroker.exe

1) The exact meaning of this process

2) The association of this process in and out of sleep mode

3) Symptoms of a problem with Runtime Broker.exe

Community Center | Not monitored
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Xing Huang (Shanghai Wicresoft Co,.Ltd.) 171 Reputation points
    2021-05-13T10:15:54.82+00:00

    Hi,

    The Runtime Broker handles checking if an app is declaring all of its permissions (like accessing your Photos) and informing the user whether or not it’s being allowed. If the Runtime Broker has problems, you will encounter high CPU usage or high memory usage. If you want to know what process interrupted the sleep mode, you need to use Performance monitor to check it. We don't know if the Runtime Broker.exe is the culprit. If you want to solve the problems, you can try the following methods:

    1. You can try to use the clean boot to turn off some security software to see if it works.
    2. You can try to turn off the Runtime Broker.exe in the registry by changing its start value to 4.
    3. You can use the command: powercfg/requests in the command prompt as administrator.
    4. You can try to update your system to the latest version.

    Best Regards,
    Ansley

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.