June 22, 2009 at 3:54 am
i am seeing below errors from the morning. Even after reboot we are seeing these errors. This is affecting performance.
Could you please suggest some work around? its very urgent.
2009-06-22 05:34:24.22 Server Potential image corruption/hotpatch detected. This may be a sign of a hardware problem or caused by presence of CLR/jitted images on the stack. Check SQLDUMPER_ERRORLOG.log for details.
2009-06-22 05:34:31.58 Server Process 506:0:0 (0x1d50) Worker 0x545E40E8 appears to be non-yielding on Scheduler 5. Thread creation time: 12890026035744. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 3%. System Idle 95%. Interval: 5890188 ms.
2009-06-22 05:34:41.58 Server Process 460:0:0 (0x1ed8) Worker 0x5418C0E8 appears to be non-yielding on Scheduler 2. Thread creation time: 12889787111176. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 3%. System Idle 95%. Interval: 6490207 ms.
2009-06-22 05:34:46.58 Server Process 465:0:0 (0x2034) Worker 0x5504E0E8 appears to be non-yielding on Scheduler 13. Thread creation time: 12890002671063. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 3%. System Idle 95%. Interval: 6190198 ms.
2009-06-22 05:34:46.58 Server Process 415:0:0 (0x1f8) Worker 0x2134E0E8 appears to be non-yielding on Scheduler 15. Thread creation time: 12890105161787. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 3%. System Idle 95%. Interval: 6130196 ms.
2009-06-22 05:35:06.58 Server Process 547:0:0 (0x2dd0) Worker 0x4B9940E8 appears to be non-yielding on Scheduler 1. Thread creation time: 12890044807030. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 3%. System Idle 95%. Interval: 5470175 ms.
2009-06-22 05:35:16.58 Server Process 236:0:0 (0x1fd8) Worker 0x3A0B60E8 appears to be non-yielding on Scheduler 3. Thread creation time: 12889967935818. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 3%. System Idle 95%. Interval: 4810153 ms.
2009-06-22 05:35:16.58 Server Process 479:0:0 (0x262c) Worker 0x1F9560E8 appears to be non-yielding on Scheduler 14. Thread creation time: 12889918464531. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 3%. System Idle 95%. Interval: 6010192 ms.
2009-06-22 05:35:21.58 Server Process 429:0:0 (0x15ac) Worker 0x43C280E8 appears to be non-yielding on Scheduler 9. Thread creation time: 12890003250222. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 3%. System Idle 95%. Interval: 6611680 ms.
June 22, 2009 at 4:49 am
This indicate a thread is locked out.
You need to apply the hotfix for Windows Server 2003 SP1 that is described in Microsoft Knowledge Base 919341.
Check the link http://support.microsoft.com/kb/922658
Verify with MS support team before applying the hotfix.
"More Green More Oxygen !! Plant a tree today"
June 22, 2009 at 4:58 am
Is it windows level? But we have SP2 on both windows and SQL. How can i proceed with debugging the issue.
Additional info:
-> Server is on cluster
Memory configuration
Total Physical Memory: 20,477 MB
Available Physical Memory: 5,155 MB
I assume that thread will be released, if it is locked out after reboot. One more thing, when ever i run a query, a stack dump is being opened.
June 22, 2009 at 5:40 am
I just disabled an audit trigger now and i think errors gone down. But still need to recycle service to clear everything..
Thanks,
Sudhie.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply