Non-yielding Scheduler

Question

Hello,

I have 2 SQL Server 2016 SP2-CU10 Production instances running one server A.

Today, i noticed below error in both the instances at the same time.

===============================

***Unable to get thread context for spid 0
* Non-yielding Scheduler
Stack Signature for the dump is 0x0000000000000151
Process 0:0:0 (0xb258) Worker 0x000002B624E56160 appears to be non-yielding on Scheduler 127. Thread creation time: 13243550549459. Approx Thread CPU Used: kernel 15 ms, user 0 ms. Process Utilization 90%. System Idle 74%. Interval: 70014 ms.
DumpCallbackHk::CollectFiles: at 481 failed at CreateCabFile with error: 0x80004005

Timeout waiting for external dump process 63000.

Pls suggest.

Answer 1

The latest patch released for SQL Server 2016 SP2 is CU14 cumulative-update-14-for-sql-server-2016-sp2 I strongly suggest you to apply this and see if the issue gets fixed.

Non yielding schedulers are mostly due to bug in SQl Server code which are eventually fixed in SP/CU release. If the upgrade to CU14 does not fixes the issue you need to raise case with MS. Unfortunately its difficult to help due to nature of the issue.

Answer 2

Hello shashank,

Thanks, I have already applied th CU13 on my pre production landscape, so will rollforward the same in production very soon and will check if it resolved.,

we have a policy of n-1 for patches.