Production database stuck with Non-yielding Scheduler in logs

Hi, yesterday my Production Instance got stuck and when checked the logs there were multiple messages.

My environment is version 2017 running on CentOS linux

Clusterless Availability group is also configured.

2022-03-21 15:50:21.08 Server ***Unable to get thread context for spid 0
2022-03-21 15:50:21.09 Server * *******************************************************************************
2022-03-21 15:50:21.09 Server *
2022-03-21 15:50:21.10 Server * BEGIN STACK DUMP:
2022-03-21 15:50:21.10 Server * 03/21/22 15:50:21 spid 412
2022-03-21 15:50:21.11 Server *
2022-03-21 15:50:21.11 Server * Non-yielding Scheduler
2022-03-21 15:50:21.11 Server *
2022-03-21 15:50:21.12 Server * *******************************************************************************
2022-03-21 15:50:21.13 Server Stack Signature for the dump is 0x000000000000018E
2022-03-21 15:50:25.64 Server Process 0:0:0 (0x12fac) Worker 0x0000001583B5A160 appears to be non-yielding on Scheduler 11. Thread creation time: 13292329020696. Approx Thread CPU Used
: kernel 0 ms, user 54650 ms. Process Utilization 66%. System Idle 0%. Interval: 73891 ms.

...skipping one line
2022-03-21 15:50:25.66 Server Process 0:0:0 (0x13264) Worker 0x0000001D51872160 appears to be non-yielding on Scheduler 12. Thread creation time: 13292329833388. Approx Thread CPU Used
: kernel 0 ms, user 54660 ms. Process Utilization 66%. System Idle 0%. Interval: 73912 ms.