Process 0:0:0 (0x788) Worker 0x000000100066E160 appears to be non-yielding on Scheduler 9. Thread creation time: 13305485289867. Approx Thread CPU Used: kernel 180 ms, user 1157790 ms. Process Utilization 76%. System Idle 0%. Interval: 1280289 ms.

轩辕 龙 1 Reputation point
2022-08-21T15:15:07.91+00:00

Process 0:0:0 (0x788) Worker 0x000000100066E160 appears to be non-yielding on Scheduler 9. Thread creation time: 13305485289867. Approx Thread CPU Used: kernel 180 ms, user 1157790 ms. Process Utilization 76%. System Idle 0%. Interval: 1280289 ms.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,310 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Erland Sommarskog 106.5K Reputation points
    2022-08-21T15:33:15.543+00:00

    A non-yielding scheduler is often a token of a bug in SQL Server. First make sure that you have the latest Cumulative Update installed (share the output of SELECT @@version if you are uncertain.) If the issue persists, open a support case with Microsoft. (Which in the end should be no of cost to you, under the assumption of that it is a bug.)

    0 comments No comments

  2. 轩辕 龙 1 Reputation point
    2022-08-21T15:37:26.507+00:00

    Microsoft SQL Server 2019 (RTM-CU16-GDR) (KB5014353) - 15.0.4236.7 (X64) May 29 2022 15:55:47 Copyright (C) 2019 Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Linux (CentOS Linux 7 (Core)) <X64>


  3. CathyJi-MSFT 21,121 Reputation points Microsoft Vendor
    2022-08-22T02:51:45.457+00:00

    Hi @轩辕 龙 ,

    Please apply the latest CU17 to SQL server 2019 as Erland suggested. You can get it from here.

    You got this error message under which situation? Please check if below two situations meet your environment.

    KB4541303 - FIX: Non-yielding Scheduler error may occur with Always On availability group in Microsoft SQL Server
    Non-yielding scheduler error in large memory server if the lock pages in memory option is disabled

    If they are all not work, you need to ask professional engineer for help(raise a case with MS), and they will deal with your problem separately and confidentially, they can access your environment. Unfortunately, it’s difficult for us to help due to nature of the issue.
    https://support.microsoft.com/en-us/assistedsupportproducts


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    0 comments No comments