Resource Monitor enters a non-yielding condition on a server that is running SQL Server

Starting with SQL Server 2008, the Resource Monitor task wakes up periodically to listen to and notify subscribers of low, high, or steady memory events. These memory events may be external to SQL Server (notifications that are system-wide from the operating system) or internal to SQL Server (notifications that are process-wide from the buffer pool). When such notifications occur, various memory consumers trim their memory usage.

Note Consumers can be memory clerks that are cache stores, user stores, or object stores.

If certain memory consumers use a large amount of memory, the trimming that the consumers perform may take a long time to finish.

The Scheduler Monitor task that runs every 5seconds checks whether Resource Monitor has moved from one consumer to another in the past 60 seconds. When the Scheduler Monitor detects that the Resource Monitor has not moved past a consumer for 60 seconds, the Schedule Monitor interprets this as the Resource Monitor entering a non-yielding state, and then the Schedule Monitor logs the error message that is mentioned in the "Symptoms" section.

Note Starting with SQL Server 2019, the 60-second interval is increased to 120 seconds to reduce the frequency of these diagnostic notifications and the generation of memory dump files.

These messages are also raised if the rate at which the Resource Monitor frees memory is less than 2 MB every 5 seconds.

These messages are only an indication that the Resource Monitor is busy cleaning up large consumers, and these messages do not necessarily indicate a problem with the Resource Monitor itself.