Help analyzing w3wp.exe dump file

My iis 6 webserver CPU spikes 100 % when user browse around the websites or
clicks some links, noticed w3wp process is eating all cpu, is there any way
we can find out what part of the app code is causing this CPU spike on my
server, attaching the dump report, could anyone help me in analyzing the
report and find out the root cause CPU spike.. for single user itself it is
reaching 100% cpu

Thanks in advance ---here is the dump report------------------------
--------------------------------------------REPORT---------- ------------------
----------------------------------------------

Analysis Summary
Type Description Recommendation
Information
DebugDiag did not detect any known problems in w3wp.
exe__DefaultAppPool__PID__1708__Date__10_11_2007__Time_10_28 _42PM__531__Manual
Dump.dmp using the current set of scripts.








Analysis Details



Your browser settings are currently prohibiting this report's scripts from
running.

This is preventing some features of this analysis report from displaying
properly. To enable scripts to run, right-click the security warning above
and choose "Allow Blocked Content..." or enable the "Allow active content to
run in files on My Computer*" setting on the Advanced tab of your "Internet
Options" dialog to avoid being prompted in the future





Table Of Contents
w3wp.
exe__DefaultAppPool__PID__1708__Date__10_11_2007__Time_10_28 _42PM__531__Manual
Dump.dmp

Top 5 threads by CPU time

Thread report

HTTP Report



Report for w3wp.
exe__DefaultAppPool__PID__1708__Date__10_11_2007__Time_10_28 _42PM__531__Manual
Dump.dmp




Report for w3wp.
exe__DefaultAppPool__PID__1708__Date__10_11_2007__Time_10_28 _42PM__531__Manual
Dump.dmp
Type of Analysis Performed Hang Analysis
Machine Name xxxxxxxx
Operating System Windows Server 2003 Service Pack 1
Number Of Processors 4
Process ID 1708
Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
System Up-Time 1 day(s) 08:21:43
Process Up-Time 05:11:24



Top 5 Threads by CPU time
Note - Times include both user mode and kernel mode for each thread Thread ID:
29 Total CPU Time: 00:45:59.093 Entry Point for Thread: mscorsvr!
ThreadpoolMgr::intermediateThreadProc
Thread ID: 17 Total CPU Time: 00:41:17.780 Entry Point for Thread:
mscorsvr!ThreadpoolMgr::intermediateThreadProc
Thread ID: 28 Total CPU Time: 00:38:42.890 Entry Point for Thread:
mscorsvr!ThreadpoolMgr::intermediateThreadProc
Thread ID: 22 Total CPU Time: 00:00:26.187 Entry Point for Thread:
mscorsvr!gc_heap::gc_thread_stub
Thread ID: 24 Total CPU Time: 00:00:25.984 Entry Point for Thread:
mscorsvr!gc_heap::gc_thread_stub





Thread report

Thread 0 - System ID 2916
Entry point w3wp!wmainCRTStartup
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.078
Time spent in kernel mode 0 Days 00:00:00.140




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
w3dt!WP_CONTEXT::RunMainThreadLoop+10
w3dt!UlAtqStartListen+2d
w3core!W3_SERVER::StartListen+bd
w3core!UlW3Start+26e
w3wp!wmain+22a
w3wp!wmainCRTStartup+12b
kernel32!BaseProcessStart+23




Back to Top


Thread 1 - System ID 3204
Entry point ntdll!RtlpTimerThread
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.859
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtDelayExecution+c
ntdll!RtlpTimerThread+47
kernel32!BaseThreadStart+34




Back to Top


Thread 2 - System ID 3884
Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.343
Time spent in kernel mode 0 Days 00:00:00.062




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
w3tp!THREAD_POOL_DATA::ThreadPoolThread+33
w3tp!THREAD_POOL_DATA::ThreadPoolThread+24
w3tp!THREAD_MANAGER::ThreadManagerThread+39
kernel32!BaseThreadStart+34




Back to Top


Thread 3 - System ID 3120
Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:01.156
Time spent in kernel mode 0 Days 00:00:00.750




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
w3tp!THREAD_POOL_DATA::ThreadPoolThread+33
w3tp!THREAD_POOL_DATA::ThreadPoolThread+24
w3tp!THREAD_MANAGER::ThreadManagerThread+39
kernel32!BaseThreadStart+34




Back to Top


Thread 4 - System ID 3992
Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.203
Time spent in kernel mode 0 Days 00:00:00.093




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
w3tp!THREAD_POOL_DATA::ThreadPoolThread+33
w3tp!THREAD_POOL_DATA::ThreadPoolThread+24
w3tp!THREAD_MANAGER::ThreadManagerThread+39
kernel32!BaseThreadStart+34




Back to Top


Thread 5 - System ID 1568
Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.765
Time spent in kernel mode 0 Days 00:00:00.203




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
w3tp!THREAD_POOL_DATA::ThreadPoolThread+33
w3tp!THREAD_POOL_DATA::ThreadPoolThread+24
w3tp!THREAD_MANAGER::ThreadManagerThread+39
kernel32!BaseThreadStart+34




Back to Top


Thread 6 - System ID 920
Entry point ntdll!RtlpWaitThread
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.046
Time spent in kernel mode 0 Days 00:00:00.046




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
ntdll!RtlpWaitThread+161
kernel32!BaseThreadStart+34




Back to Top


Thread 7 - System ID 2760
Entry point msvcrt!_endthreadex+2f
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:02.609
Time spent in kernel mode 0 Days 00:00:04.812




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
kernel32!WaitForMultipleObjectsEx+11a
user32!RealMsgWaitForMultipleObjectsEx+141
user32!MsgWaitForMultipleObjects+1f
acsrtl!RemoveWorkItem+27b
msvcrt!free+c8
kernel32!BaseThreadStart+34
kernel32!_SEH_epilog+18




Back to Top


Thread 8 - System ID 3624
Entry point msvcrt!_endthreadex+2f
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
kernel32!WaitForMultipleObjectsEx+11a
user32!RealMsgWaitForMultipleObjectsEx+141
user32!MsgWaitForMultipleObjects+1f
acsrtl!RemoveWorkItem+27b
kernel32!BaseThreadStart+34




Back to Top


Thread 9 - System ID 2256
Entry point msvcrt!_endthreadex+2f
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
kernel32!WaitForMultipleObjectsEx+11a
user32!RealMsgWaitForMultipleObjectsEx+141
user32!MsgWaitForMultipleObjects+1f
acsrtl!RemoveWorkItem+27b
kernel32!BaseThreadStart+34




Back to Top


Thread 10 - System ID 1868
Entry point msvcrt!_endthreadex+2f
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
kernel32!WaitForMultipleObjectsEx+11a
user32!RealMsgWaitForMultipleObjectsEx+141
user32!MsgWaitForMultipleObjects+1f
acsrtl!RemoveWorkItem+27b
kernel32!BaseThreadStart+34




Back to Top


Thread 11 - System ID 2784
Entry point msatq!AtqInitialize+1354
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
msatq!AtqInitialize+1392
kernel32!BaseThreadStart+34




Back to Top


Thread 12 - System ID 3012
Entry point wmisink!CWMIEventSinkWrapper::SetupSubscription+30b
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.562
Time spent in kernel mode 0 Days 00:00:00.031




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
kernel32!WaitForMultipleObjectsEx+11a
kernel32!WaitForMultipleObjects+18
wmisink!CWMIEventSinkWrapper::SetupSubscription+48e




Back to Top


Thread 13 - System ID 1384
Entry point RfFilExt!CMBData::~CMBData+c2
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




This thread is calling an ISAPI Filter RfFilExt



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
RfFilExt!CMBData::~CMBData+f6




Back to Top


Thread 14 - System ID 2796
Entry point w3core!HTTP_COMPRESSION::CompressionThread
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
w3core!HTTP_COMPRESSION::CompressionThread+126
kernel32!BaseThreadStart+34




Back to Top


Thread 15 - System ID 3888
Entry point ntdll!RtlpIOWorkerThread
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtDelayExecution+c
ntdll!RtlpIOWorkerThread+3f
kernel32!BaseThreadStart+34




Back to Top


Thread 16 - System ID 2324
Entry point mscorsvr!ThreadpoolMgr::GateThreadStart
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.046
Time spent in kernel mode 0 Days 00:00:00.015




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtDelayExecution+c
kernel32!SleepEx+68
kernel32!Sleep+f
mscorsvr!ThreadpoolMgr::GateThreadStart+54
kernel32!BaseThreadStart+34




Back to Top


Thread 17 - System ID 4020
Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:31:22.390
Time spent in kernel mode 0 Days 00:09:55.390




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a
mscorsvr!ThreadpoolMgr::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top


Thread 18 - System ID 956
Entry point mscorsvr!DebuggerRCThread::ThreadProcStatic
Create time 10/11/2007 5:17:20 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
kernel32!WaitForMultipleObjectsEx+11a
kernel32!WaitForMultipleObjects+18
mscorsvr!DebuggerRCThread::MainLoop+90
mscorsvr!DebuggerRCThread::ThreadProc+68
mscorsvr!DebuggerRCThread::ThreadProcStatic+b
kernel32!BaseThreadStart+34




Back to Top


Thread 19 - System ID 240
Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
Create time 10/11/2007 5:17:21 PM
Time spent in user mode 0 Days 00:00:00.359
Time spent in kernel mode 0 Days 00:00:00.046




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
mscorsvr!ThreadpoolMgr::CompletionPortThreadStart+49
mscorsvr!ThreadpoolMgr::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top


Thread 20 - System ID 1736
Entry point StubProfiler!DllRegisterServer+18f92
Create time 10/11/2007 5:17:21 PM
Time spent in user mode 0 Days 00:00:00.046
Time spent in kernel mode 0 Days 00:00:00.046




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
StubProfiler!DllRegisterServer+887d
ntdll!RtlImageNtHeader+1b
StubProfiler!DllRegisterServer+13850




Back to Top


Thread 21 - System ID 444
Entry point msvcr80!_threadstartex
Create time 10/11/2007 5:17:21 PM
Time spent in user mode 0 Days 00:00:05.953
Time spent in kernel mode 0 Days 00:00:00.953




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
kernel32!WaitForMultipleObjectsEx+11a
kernel32!WaitForMultipleObjects+18
PerfMon+13992
ntdll!NtQueryInformationProcess+c
msvcr80!_encode_pointer+59 f:\rtm\vctools\crt_bld\self_x86\crt\src\tidtable.
c @ 112 + 6
PerfMon!DllUnregisterServer+7fbb
PerfMon!DllUnregisterServer+34a4d
msvcr80!_callthreadstartex+1b f:\rtm\vctools\crt_bld\self_x86\crt\src\
threadex.c @ 348 + 6
msvcr80!_threadstartex+66 f:\rtm\vctools\crt_bld\self_x86\crt\src\threadex.
c @ 326 + 5
kernel32!BaseThreadStart+34




Back to Top


Thread 22 - System ID 3716
Entry point mscorsvr!gc_heap::gc_thread_stub
Create time 10/11/2007 5:17:21 PM
Time spent in user mode 0 Days 00:00:25.875
Time spent in kernel mode 0 Days 00:00:00.312




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!gc_heap::gc_thread_function+2f
mscorsvr!gc_heap::gc_thread_stub+1e
kernel32!BaseThreadStart+34




Back to Top


Thread 23 - System ID 204
Entry point mscorsvr!gc_heap::gc_thread_stub
Create time 10/11/2007 5:17:21 PM
Time spent in user mode 0 Days 00:00:23.671
Time spent in kernel mode 0 Days 00:00:00.187




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!gc_heap::gc_thread_function+2f
mscorsvr!gc_heap::gc_thread_stub+1e
kernel32!BaseThreadStart+34




Back to Top


Thread 24 - System ID 1208
Entry point mscorsvr!gc_heap::gc_thread_stub
Create time 10/11/2007 5:17:21 PM
Time spent in user mode 0 Days 00:00:25.750
Time spent in kernel mode 0 Days 00:00:00.234




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!gc_heap::gc_thread_function+2f
mscorsvr!gc_heap::gc_thread_stub+1e
kernel32!BaseThreadStart+34




Back to Top


Thread 25 - System ID 3960
Entry point mscorsvr!gc_heap::gc_thread_stub
Create time 10/11/2007 5:17:21 PM
Time spent in user mode 0 Days 00:00:25.406
Time spent in kernel mode 0 Days 00:00:00.203




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!gc_heap::gc_thread_function+2f
mscorsvr!gc_heap::gc_thread_stub+1e
kernel32!BaseThreadStart+34




Back to Top


Thread 26 - System ID 172
Entry point mscorsvr!Thread::intermediateThreadProc
Create time 10/11/2007 5:17:21 PM
Time spent in user mode 0 Days 00:00:02.781
Time spent in kernel mode 0 Days 00:00:00.218




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
kernel32!WaitForMultipleObjectsEx+11a
kernel32!WaitForMultipleObjects+18
mscorsvr!WaitForFinalizerEvent+5a
mscorsvr!GCHeap::FinalizerThreadStart+96
mscorsvr!Thread::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top


Thread 27 - System ID 3804
Entry point mscorsvr!ThreadpoolMgr::TimerThreadStart
Create time 10/11/2007 5:17:23 PM
Time spent in user mode 0 Days 00:00:00.031
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtDelayExecution+c
kernel32!SleepEx+68
mscorsvr!ThreadpoolMgr::TimerThreadStart+30
kernel32!BaseThreadStart+34




Back to Top


Thread 28 - System ID 452
Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
Create time 10/11/2007 5:17:29 PM
Time spent in user mode 0 Days 00:29:18.578
Time spent in kernel mode 0 Days 00:09:24.312




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a
mscorsvr!ThreadpoolMgr::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top


Thread 29 - System ID 3920
Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
Create time 10/11/2007 5:17:30 PM
Time spent in user mode 0 Days 00:34:49.343
Time spent in kernel mode 0 Days 00:11:09.750




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a
mscorsvr!ThreadpoolMgr::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top


Thread 30 - System ID 2296
Entry point mscorsvr!ThreadpoolMgr::WaitThreadStart
Create time 10/11/2007 5:17:34 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.015




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtDelayExecution+c
kernel32!SleepEx+68
mscorsvr!ThreadpoolMgr::WaitThreadStart+45
kernel32!BaseThreadStart+34




Back to Top


Thread 31 - System ID 1580
Create time 12:00:00 AM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!ZwReplyWaitReceivePortEx+c
rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+198
rpcrt4!RecvLotsaCallsWrapper+d
rpcrt4!BaseCachedThreadRoutine+9d
rpcrt4!ThreadStartRoutine+1b
kernel32!BaseThreadStart+34




Back to Top


Thread 32 - System ID 200
Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
Create time 10/11/2007 9:15:03 PM
Time spent in user mode 0 Days 00:00:00.453
Time spent in kernel mode 0 Days 00:00:00.093




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
w3tp!THREAD_POOL_DATA::ThreadPoolThread+33
w3tp!THREAD_POOL_DATA::ThreadPoolThread+24
w3tp!THREAD_MANAGER::ThreadManagerThread+39
kernel32!BaseThreadStart+34




Back to Top


Thread 33 - System ID 3832
Entry point LeakTrack+d6fa
Create time 10/11/2007 9:30:03 PM
Time spent in user mode 0 Days 00:00:00.031
Time spent in kernel mode 0 Days 00:00:00.00




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
LeakTrack+d782
kernel32!BaseThreadStart+34




Back to Top


Thread 34 - System ID 3336
Entry point LeakTrack+d6fa
Create time 10/11/2007 9:30:03 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
LeakTrack+d782
kernel32!BaseThreadStart+34




Back to Top


Thread 35 - System ID 2512
Entry point LeakTrack+c431
Create time 10/11/2007 9:30:03 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
LeakTrack+c44f




Back to Top


Thread 36 - System ID 2776
Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
Create time 10/11/2007 9:36:38 PM
Time spent in user mode 0 Days 00:00:00.296
Time spent in kernel mode 0 Days 00:00:00.171




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
w3tp!THREAD_POOL_DATA::ThreadPoolThread+33
w3tp!THREAD_POOL_DATA::ThreadPoolThread+24
w3tp!THREAD_MANAGER::ThreadManagerThread+39
kernel32!BaseThreadStart+34




Back to Top


Thread 37 - System ID 964
Entry point mscorsvr!Thread::intermediateThreadProc
Create time 10/11/2007 9:49:14 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
kernel32!WaitForMultipleObjectsEx+11a
mscorsvr!Thread::DoAppropriateWaitWorker+c1
mscorsvr!Thread::DoAppropriateWait+46
mscorsvr!WaitHandleNative::CorWaitMultipleNative+ff
0x04642bc7
mscorsvr!CallDescrWorker+30
mscorsvr!MethodDesc::CallDescr+1b8
mscorsvr!MethodDesc::CallDescr+4f
mscorsvr!MethodDesc::Call+97
mscorsvr!ThreadNative::KickOffThread_Worker+9d
mscorsvr!ThreadNative::KickOffThread+c2
mscorsvr!Thread::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top


Thread 38 - System ID 3008
Entry point ntdll!RtlpWorkerThread
Create time 10/11/2007 9:53:42 PM
Time spent in user mode 0 Days 00:00:00.046
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
ntdll!RtlpWorkerThread+3d
kernel32!BaseThreadStart+34




Back to Top


Thread 39 - System ID 3456
Create time 12:00:00 AM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!ZwReplyWaitReceivePortEx+c
rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+198
rpcrt4!RecvLotsaCallsWrapper+d
rpcrt4!BaseCachedThreadRoutine+9d
rpcrt4!ThreadStartRoutine+1b
kernel32!BaseThreadStart+34




Back to Top


Thread 40 - System ID 3192
Create time 12:00:00 AM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!ZwReplyWaitReceivePortEx+c
rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+198
rpcrt4!RecvLotsaCallsWrapper+d
rpcrt4!BaseCachedThreadRoutine+9d
rpcrt4!ThreadStartRoutine+1b
kernel32!BaseThreadStart+34




Back to Top


Thread 41 - System ID 2536
Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
Create time 10/11/2007 10:26:41 PM
Time spent in user mode 0 Days 00:00:17.281
Time spent in kernel mode 0 Days 00:00:03.687




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a
mscorsvr!ThreadpoolMgr::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top


Thread 42 - System ID 416
Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
Create time 10/11/2007 10:26:44 PM
Time spent in user mode 0 Days 00:00:09.250
Time spent in kernel mode 0 Days 00:00:03.406




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a
mscorsvr!ThreadpoolMgr::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top


Thread 43 - System ID 3464
Entry point ole32!CRpcThreadCache::RpcWorkerThreadEntry
Create time 10/11/2007 10:27:25 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtDelayExecution+c
kernel32!SleepEx+68
kernel32!Sleep+f
ole32!CROIDTable::WorkerThreadLoop+14
ole32!CRpcThread::WorkerLoop+1e
ole32!CRpcThreadCache::RpcWorkerThreadEntry+20
kernel32!BaseThreadStart+34




Back to Top


Thread 44 - System ID 1056
Entry point mscorsvr!Thread::intermediateThreadProc
Create time 10/11/2007 10:27:26 PM
Time spent in user mode 0 Days 00:00:00.093
Time spent in kernel mode 0 Days 00:00:00.015




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
kernel32!WaitForMultipleObjectsEx+11a
mscorsvr!Thread::DoAppropriateWaitWorker+c1
mscorsvr!Thread::DoAppropriateWait+46
mscorsvr!WaitHandleNative::CorWaitMultipleNative+ff
0x04642bc7
mscorsvr!CallDescrWorker+30
mscorsvr!MethodDesc::CallDescr+1b8
mscorsvr!MethodDesc::CallDescr+4f
mscorsvr!MethodDesc::Call+97
mscorsvr!ThreadNative::KickOffThread_Worker+9d
mscorsvr!Thread::DoADCallBack+5c
mscorsvr!ThreadNative::KickOffThread+bb
mscorsvr!Thread::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top


Thread 45 - System ID 1700
Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
Create time 10/11/2007 10:27:27 PM
Time spent in user mode 0 Days 00:00:07.484
Time spent in kernel mode 0 Days 00:00:01.812




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a
mscorsvr!ThreadpoolMgr::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top


Thread 46 - System ID 2500
Entry point ntdll!RtlpWorkerThread
Create time 10/11/2007 10:27:45 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.015




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
ntdll!RtlpWorkerThread+3d
kernel32!BaseThreadStart+34




Back to Top


Thread 47 - System ID 716
Entry point mscorsvr!Thread::intermediateThreadProc
Create time 10/11/2007 10:27:51 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




This thread is not fully resolved and may or may not be a problem. Further
analysis of these threads may be required.



Function Source
ntdll!KiFastSystemCallRet
ntdll!NtDelayExecution+c
kernel32!SleepEx+68
mscorsvr!Thread::UserSleep+93
mscorsvr!ThreadNative::Sleep+30
0x04646592
mscorsvr!CallDescrWorker+30
mscorsvr!MethodDesc::CallDescr+1b8
mscorsvr!MethodDesc::CallDescr+4f
mscorsvr!MethodDesc::Call+97
mscorsvr!ThreadNative::KickOffThread_Worker+9d
mscorsvr!Thread::DoADCallBack+5c
mscorsvr!ThreadNative::KickOffThread+bb
mscorsvr!Thread::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top


Thread 48 - System ID 1836
Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
Create time 10/11/2007 10:27:57 PM
Time spent in user mode 0 Days 00:00:00.109
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
mscorsvr!ThreadpoolMgr::CompletionPortThreadStart+49
mscorsvr!ThreadpoolMgr::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top


Thread 49 - System ID 3264
Entry point GdiPlus!BackgroundThreadProc
Create time 10/11/2007 10:28:00 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForMultipleObjects+c
kernel32!WaitForMultipleObjectsEx+11a
user32!RealMsgWaitForMultipleObjectsEx+141
user32!MsgWaitForMultipleObjects+1f
GdiPlus!BackgroundThreadProc+59
kernel32!BaseThreadStart+34




Back to Top


Thread 50 - System ID 1860
Entry point ntdll!RtlpWorkerThread
Create time 10/11/2007 10:28:25 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
ntdll!RtlpWorkerThread+3d
kernel32!BaseThreadStart+34




Back to Top


Thread 51 - System ID 3648
Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
Create time 10/11/2007 10:28:26 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtRemoveIoCompletion+c
kernel32!GetQueuedCompletionStatus+29
mscorsvr!ThreadpoolMgr::CompletionPortThreadStart+49
mscorsvr!ThreadpoolMgr::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top


Thread 52 - System ID 2912
Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
Create time 10/11/2007 10:28:35 PM
Time spent in user mode 0 Days 00:00:01.937
Time spent in kernel mode 0 Days 00:00:00.515




Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a
mscorsvr!ThreadpoolMgr::intermediateThreadProc+44
kernel32!BaseThreadStart+34




Back to Top

HTTP report
IIS ATQ worker thread count 6 Thread(s)
Available ATQ worker thread count 6 Thread(s)
Active client connections 42 client connection(s)



Client Connections
42 connection(s) waiting for the next request.




Script Summary
Script Name Status Error Code Error Source Error Description Source Line
CrashHangAnalysis.asp Completed

--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forums.aspx/iis-general/20071 0/1

Re: Help analyzing w3wp.exe dump file

Nothing unusual in this log.

Why don't you just implement basic performance tracing in your code,
or do basic performance profiling. You need to do either to accomplish
what you want.

DebugDiag is not the right tool to do this because you don't have a
crash, hang, or leak. A CPU spike is not a hang.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On Oct 11, 9:34 pm, "gobinathan" wrote:
> My iis 6 webserver CPU spikes 100 % when user browse around the websites =
or
> clicks some links, noticed w3wp process is eating all cpu, is there any w=
ay
> we can find out what part of the app code is causing this CPU spike on my
> server, attaching the dump report, could anyone help me in analyzing the
> report and find out the root cause CPU spike.. for single user itself it =
is
> reaching 100% cpu
>
> Thanks in advance ---here is the dump report------------------------
> --------------------------------------------REPORT---------- -------------=
--=AD---
> ----------------------------------------------
>
> Analysis Summary =20
> Type Description Recommendation
> Information
> DebugDiag did not detect any known problems in w3wp.
> exe__DefaultAppPool__PID__1708__Date__10_11_2007__Time_10_28 _42PM__531__M=
an=ADual
> Dump.dmp using the current set of scripts.
>
> Analysis Details =20
>
> Your browser settings are currently prohibiting this report's scripts fr=
om
> running.
>
> This is preventing some features of this analysis report from displaying
> properly. To enable scripts to run, right-click the security warning above
> and choose "Allow Blocked Content..." or enable the "Allow active content=
to
> run in files on My Computer*" setting on the Advanced tab of your "Intern=
et
> Options" dialog to avoid being prompted in the future
>
> Table Of Contents
> w3wp.
> exe__DefaultAppPool__PID__1708__Date__10_11_2007__Time_10_28 _42PM__531__M=
an=ADual
> Dump.dmp
>
> Top 5 threads by CPU time
>
> Thread report
>
> HTTP Report
>
> Report for w3wp.
> exe__DefaultAppPool__PID__1708__Date__10_11_2007__Time_10_28 _42PM__531__M=
an=ADual
> Dump.dmp
>
> Report for w3wp.
> exe__DefaultAppPool__PID__1708__Date__10_11_2007__Time_10_28 _42PM__531__M=
an=ADual
> Dump.dmp
> Type of Analysis Performed Hang Analysis
> Machine Name xxxxxxxx
> Operating System Windows Server 2003 Service Pack 1
> Number Of Processors 4
> Process ID 1708
> Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
> System Up-Time 1 day(s) 08:21:43
> Process Up-Time 05:11:24
>
> Top 5 Threads by CPU time
> Note - Times include both user mode and kernel mode for each thread Threa=
d ID:
> 29 Total CPU Time: 00:45:59.093 Entry Point for Thread: mscorsvr!
> ThreadpoolMgr::intermediateThreadProc
> Thread ID: 17 Total CPU Time: 00:41:17.780 Entry Point for Thread:
> mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Thread ID: 28 Total CPU Time: 00:38:42.890 Entry Point for Thread:
> mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Thread ID: 22 Total CPU Time: 00:00:26.187 Entry Point for Thread:
> mscorsvr!gc_heap::gc_thread_stub
> Thread ID: 24 Total CPU Time: 00:00:25.984 Entry Point for Thread:
> mscorsvr!gc_heap::gc_thread_stub
>
> Thread report
>
> Thread 0 - System ID 2916
> Entry point w3wp!wmainCRTStartup
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.078
> Time spent in kernel mode 0 Days 00:00:00.140
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> w3dt!WP_CONTEXT::RunMainThreadLoop+10 =20
> w3dt!UlAtqStartListen+2d =20
> w3core!W3_SERVER::StartListen+bd =20
> w3core!UlW3Start+26e =20
> w3wp!wmain+22a =20
> w3wp!wmainCRTStartup+12b =20
> kernel32!BaseProcessStart+23 =20
>
> Back to Top
>
> Thread 1 - System ID 3204
> Entry point ntdll!RtlpTimerThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.859
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> ntdll!RtlpTimerThread+47 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 2 - System ID 3884
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.343
> Time spent in kernel mode 0 Days 00:00:00.062
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+33 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+24 =20
> w3tp!THREAD_MANAGER::ThreadManagerThread+39 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 3 - System ID 3120
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:01.156
> Time spent in kernel mode 0 Days 00:00:00.750
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+33 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+24 =20
> w3tp!THREAD_MANAGER::ThreadManagerThread+39 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 4 - System ID 3992
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.203
> Time spent in kernel mode 0 Days 00:00:00.093
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+33 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+24 =20
> w3tp!THREAD_MANAGER::ThreadManagerThread+39 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 5 - System ID 1568
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.765
> Time spent in kernel mode 0 Days 00:00:00.203
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+33 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+24 =20
> w3tp!THREAD_MANAGER::ThreadManagerThread+39 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 6 - System ID 920
> Entry point ntdll!RtlpWaitThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.046
> Time spent in kernel mode 0 Days 00:00:00.046
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> ntdll!RtlpWaitThread+161 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 7 - System ID 2760
> Entry point msvcrt!_endthreadex+2f
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:02.609
> Time spent in kernel mode 0 Days 00:00:04.812
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> user32!RealMsgWaitForMultipleObjectsEx+141 =20
> user32!MsgWaitForMultipleObjects+1f =20
> acsrtl!RemoveWorkItem+27b =20
> msvcrt!free+c8 =20
> kernel32!BaseThreadStart+34 =20
> kernel32!_SEH_epilog+18 =20
>
> Back to Top
>
> Thread 8 - System ID 3624
> Entry point msvcrt!_endthreadex+2f
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> user32!RealMsgWaitForMultipleObjectsEx+141 =20
> user32!MsgWaitForMultipleObjects+1f =20
> acsrtl!RemoveWorkItem+27b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 9 - System ID 2256
> Entry point msvcrt!_endthreadex+2f
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> user32!RealMsgWaitForMultipleObjectsEx+141 =20
> user32!MsgWaitForMultipleObjects+1f =20
> acsrtl!RemoveWorkItem+27b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 10 - System ID 1868
> Entry point msvcrt!_endthreadex+2f
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> user32!RealMsgWaitForMultipleObjectsEx+141 =20
> user32!MsgWaitForMultipleObjects+1f =20
> acsrtl!RemoveWorkItem+27b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 11 - System ID 2784
> Entry point msatq!AtqInitialize+1354
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> msatq!AtqInitialize+1392 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 12 - System ID 3012
> Entry point wmisink!CWMIEventSinkWrapper::SetupSubscription+30b
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.562
> Time spent in kernel mode 0 Days 00:00:00.031
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> kernel32!WaitForMultipleObjects+18 =20
> wmisink!CWMIEventSinkWrapper::SetupSubscription+48e =20
>
> Back to Top
>
> Thread 13 - System ID 1384
> Entry point RfFilExt!CMBData::~CMBData+c2
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is calling an ISAPI Filter RfFilExt
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> RfFilExt!CMBData::~CMBData+f6 =20
>
> Back to Top
>
> Thread 14 - System ID 2796
> Entry point w3core!HTTP_COMPRESSION::CompressionThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> w3core!HTTP_COMPRESSION::CompressionThread+126 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 15 - System ID 3888
> Entry point ntdll!RtlpIOWorkerThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> ntdll!RtlpIOWorkerThread+3f =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 16 - System ID 2324
> Entry point mscorsvr!ThreadpoolMgr::GateThreadStart
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.046
> Time spent in kernel mode 0 Days 00:00:00.015
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> kernel32!SleepEx+68 =20
> kernel32!Sleep+f =20
> mscorsvr!ThreadpoolMgr::GateThreadStart+54 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 17 - System ID 4020
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:31:22.390
> Time spent in kernel mode 0 Days 00:09:55.390
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 18 - System ID 956
> Entry point mscorsvr!DebuggerRCThread::ThreadProcStatic
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> kernel32!WaitForMultipleObjects+18 =20
> mscorsvr!DebuggerRCThread::MainLoop+90 =20
> mscorsvr!DebuggerRCThread::ThreadProc+68 =20
> mscorsvr!DebuggerRCThread::ThreadProcStatic+b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 19 - System ID 240
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:00.359
> Time spent in kernel mode 0 Days 00:00:00.046
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> mscorsvr!ThreadpoolMgr::CompletionPortThreadStart+49 =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 20 - System ID 1736
> Entry point StubProfiler!DllRegisterServer+18f92
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:00.046
> Time spent in kernel mode 0 Days 00:00:00.046
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> StubProfiler!DllRegisterServer+887d =20
> ntdll!RtlImageNtHeader+1b =20
> StubProfiler!DllRegisterServer+13850 =20
>
> Back to Top
>
> Thread 21 - System ID 444
> Entry point msvcr80!_threadstartex
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:05.953
> Time spent in kernel mode 0 Days 00:00:00.953
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> kernel32!WaitForMultipleObjects+18 =20
> PerfMon+13992 =20
> ntdll!NtQueryInformationProcess+c =20
> msvcr80!_encode_pointer+59 f:\rtm\vctools\crt_bld\self_x86\crt\src\tidt=
able.
> c @ 112 + 6
> PerfMon!DllUnregisterServer+7fbb =20
> PerfMon!DllUnregisterServer+34a4d =20
> msvcr80!_callthreadstartex+1b f:\rtm\vctools\crt_bld\self_x86\crt\src\
> threadex.c @ 348 + 6
> msvcr80!_threadstartex+66 f:\rtm\vctools\crt_bld\self_x86\crt\src\threa=
dex.
> c @ 326 + 5
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 22 - System ID 3716
> Entry point mscorsvr!gc_heap::gc_thread_stub
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:25.875
> Time spent in kernel mode 0 Days 00:00:00.312
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!gc_heap::gc_thread_function+2f =20
> mscorsvr!gc_heap::gc_thread_stub+1e =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 23 - System ID 204
> Entry point mscorsvr!gc_heap::gc_thread_stub
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:23.671
> Time spent in kernel mode 0 Days 00:00:00.187
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!gc_heap::gc_thread_function+2f =20
> mscorsvr!gc_heap::gc_thread_stub+1e =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 24 - System ID 1208
> Entry point mscorsvr!gc_heap::gc_thread_stub
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:25.750
> Time spent in kernel mode 0 Days 00:00:00.234
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!gc_heap::gc_thread_function+2f =20
> mscorsvr!gc_heap::gc_thread_stub+1e =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 25 - System ID 3960
> Entry point mscorsvr!gc_heap::gc_thread_stub
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:25.406
> Time spent in kernel mode 0 Days 00:00:00.203
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!gc_heap::gc_thread_function+2f =20
> mscorsvr!gc_heap::gc_thread_stub+1e =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 26 - System ID 172
> Entry point mscorsvr!Thread::intermediateThreadProc
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:02.781
> Time spent in kernel mode 0 Days 00:00:00.218
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> kernel32!WaitForMultipleObjects+18 =20
> mscorsvr!WaitForFinalizerEvent+5a =20
> mscorsvr!GCHeap::FinalizerThreadStart+96 =20
> mscorsvr!Thread::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 27 - System ID 3804
> Entry point mscorsvr!ThreadpoolMgr::TimerThreadStart
> Create time 10/11/2007 5:17:23 PM
> Time spent in user mode 0 Days 00:00:00.031
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> kernel32!SleepEx+68 =20
> mscorsvr!ThreadpoolMgr::TimerThreadStart+30 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 28 - System ID 452
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 5:17:29 PM
> Time spent in user mode 0 Days 00:29:18.578
> Time spent in kernel mode 0 Days 00:09:24.312
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 29 - System ID 3920
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 5:17:30 PM
> Time spent in user mode 0 Days 00:34:49.343
> Time spent in kernel mode 0 Days 00:11:09.750
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 30 - System ID 2296
> Entry point mscorsvr!ThreadpoolMgr::WaitThreadStart
> Create time 10/11/2007 5:17:34 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.015
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> kernel32!SleepEx+68 =20
> mscorsvr!ThreadpoolMgr::WaitThreadStart+45 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 31 - System ID 1580
> Create time 12:00:00 AM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!ZwReplyWaitReceivePortEx+c =20
> rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+198 =20
> rpcrt4!RecvLotsaCallsWrapper+d =20
> rpcrt4!BaseCachedThreadRoutine+9d =20
> rpcrt4!ThreadStartRoutine+1b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 32 - System ID 200
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 10/11/2007 9:15:03 PM
> Time spent in user mode 0 Days 00:00:00.453
> Time spent in kernel mode 0 Days 00:00:00.093
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+33 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+24 =20
> w3tp!THREAD_MANAGER::ThreadManagerThread+39 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 33 - System ID 3832
> Entry point LeakTrack+d6fa
> Create time 10/11/2007 9:30:03 PM
> Time spent in user mode 0 Days 00:00:00.031
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> LeakTrack+d782 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 34 - System ID 3336
> Entry point LeakTrack+d6fa
> Create time 10/11/2007 9:30:03 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> LeakTrack+d782 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 35 - System ID 2512
> Entry point LeakTrack+c431
> Create time 10/11/2007 9:30:03 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> LeakTrack+c44f =20
>
> Back to Top
>
> Thread 36 - System ID 2776
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 10/11/2007 9:36:38 PM
> Time spent in user mode 0 Days 00:00:00.296
> Time spent in kernel mode 0 Days 00:00:00.171
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+33 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+24 =20
> w3tp!THREAD_MANAGER::ThreadManagerThread+39 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 37 - System ID 964
> Entry point mscorsvr!Thread::intermediateThreadProc
> Create time 10/11/2007 9:49:14 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> mscorsvr!Thread::DoAppropriateWaitWorker+c1 =20
> mscorsvr!Thread::DoAppropriateWait+46 =20
> mscorsvr!WaitHandleNative::CorWaitMultipleNative+ff =20
> 0x04642bc7 =20
> mscorsvr!CallDescrWorker+30 =20
> mscorsvr!MethodDesc::CallDescr+1b8 =20
> mscorsvr!MethodDesc::CallDescr+4f =20
> mscorsvr!MethodDesc::Call+97 =20
> mscorsvr!ThreadNative::KickOffThread_Worker+9d =20
> mscorsvr!ThreadNative::KickOffThread+c2 =20
> mscorsvr!Thread::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 38 - System ID 3008
> Entry point ntdll!RtlpWorkerThread
> Create time 10/11/2007 9:53:42 PM
> Time spent in user mode 0 Days 00:00:00.046
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> ntdll!RtlpWorkerThread+3d =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 39 - System ID 3456
> Create time 12:00:00 AM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!ZwReplyWaitReceivePortEx+c =20
> rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+198 =20
> rpcrt4!RecvLotsaCallsWrapper+d =20
> rpcrt4!BaseCachedThreadRoutine+9d =20
> rpcrt4!ThreadStartRoutine+1b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 40 - System ID 3192
> Create time 12:00:00 AM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!ZwReplyWaitReceivePortEx+c =20
> rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+198 =20
> rpcrt4!RecvLotsaCallsWrapper+d =20
> rpcrt4!BaseCachedThreadRoutine+9d =20
> rpcrt4!ThreadStartRoutine+1b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 41 - System ID 2536
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 10:26:41 PM
> Time spent in user mode 0 Days 00:00:17.281
> Time spent in kernel mode 0 Days 00:00:03.687
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 42 - System ID 416
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 10:26:44 PM
> Time spent in user mode 0 Days 00:00:09.250
> Time spent in kernel mode 0 Days 00:00:03.406
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 43 - System ID 3464
> Entry point ole32!CRpcThreadCache::RpcWorkerThreadEntry
> Create time 10/11/2007 10:27:25 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> kernel32!SleepEx+68 =20
> kernel32!Sleep+f =20
> ole32!CROIDTable::WorkerThreadLoop+14 =20
> ole32!CRpcThread::WorkerLoop+1e =20
> ole32!CRpcThreadCache::RpcWorkerThreadEntry+20 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 44 - System ID 1056
> Entry point mscorsvr!Thread::intermediateThreadProc
> Create time 10/11/2007 10:27:26 PM
> Time spent in user mode 0 Days 00:00:00.093
> Time spent in kernel mode 0 Days 00:00:00.015
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> mscorsvr!Thread::DoAppropriateWaitWorker+c1 =20
> mscorsvr!Thread::DoAppropriateWait+46 =20
> mscorsvr!WaitHandleNative::CorWaitMultipleNative+ff =20
> 0x04642bc7 =20
> mscorsvr!CallDescrWorker+30 =20
> mscorsvr!MethodDesc::CallDescr+1b8 =20
> mscorsvr!MethodDesc::CallDescr+4f =20
> mscorsvr!MethodDesc::Call+97 =20
> mscorsvr!ThreadNative::KickOffThread_Worker+9d =20
> mscorsvr!Thread::DoADCallBack+5c =20
> mscorsvr!ThreadNative::KickOffThread+bb =20
> mscorsvr!Thread::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 45 - System ID 1700
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 10:27:27 PM
> Time spent in user mode 0 Days 00:00:07.484
> Time spent in kernel mode 0 Days 00:00:01.812
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 46 - System ID 2500
> Entry point ntdll!RtlpWorkerThread
> Create time 10/11/2007 10:27:45 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.015
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> ntdll!RtlpWorkerThread+3d =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 47 - System ID 716
> Entry point mscorsvr!Thread::intermediateThreadProc
> Create time 10/11/2007 10:27:51 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> kernel32!SleepEx+68 =20
> mscorsvr!Thread::UserSleep+93 =20
> mscorsvr!ThreadNative::Sleep+30 =20
> 0x04646592 =20
> mscorsvr!CallDescrWorker+30 =20
> mscorsvr!MethodDesc::CallDescr+1b8 =20
> mscorsvr!MethodDesc::CallDescr+4f =20
> mscorsvr!MethodDesc::Call+97 =20
> mscorsvr!ThreadNative::KickOffThread_Worker+9d =20
> mscorsvr!Thread::DoADCallBack+5c =20
> mscorsvr!ThreadNative::KickOffThread+bb =20
> mscorsvr!Thread::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 48 - System ID 1836
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 10:27:57 PM
> Time spent in user mode 0 Days 00:00:00.109
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> mscorsvr!ThreadpoolMgr::CompletionPortThreadStart+49 =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 49 - System ID 3264
> Entry point GdiPlus!BackgroundThreadProc
> Create time 10/11/2007 10:28:00 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> user32!RealMsgWaitForMultipleObjectsEx+141 =20
> user32!MsgWaitForMultipleObjects+1f =20
> GdiPlus!BackgroundThreadProc+59 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 50 - System ID 1860
> Entry point ntdll!RtlpWorkerThread
> Create time 10/11/2007 10:28:25 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> ntdll!RtlpWorkerThread+3d =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 51 - System ID 3648
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 10:28:26 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> mscorsvr!ThreadpoolMgr::CompletionPortThreadStart+49 =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 52 - System ID 2912
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 10:28:35 PM
> Time spent in user mode 0 Days 00:00:01.937
> Time spent in kernel mode 0 Days 00:00:00.515
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> HTTP report
> IIS ATQ worker thread count 6 Thread(s)
> Available ATQ worker thread count 6 Thread(s)
> Active client connections 42 client connection(s)
>
> Client Connections
> 42 connection(s) waiting for the next request.
>
> Script Summary =20
> Script Name Status Error Code Error Source Error Description Source Line
> CrashHangAnalysis.asp Completed
>
> --
> Message posted via WinServerKB.comhttp://www.winserverkb.com/Uwe/Forums.a=
spx/iis-general/200710/1

Re: Help analyzing w3wp.exe dump file

Nothing unusual with this report.

Why don't you add basic profiling code to the application, or run .Net
Profiling tools, to determine where the time is being spent?

DebugDiag is not the tool for this. Nothing is hanging, leaking, or
crashing.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Oct 11, 9:34 pm, "gobinathan" wrote:
> My iis 6 webserver CPU spikes 100 % when user browse around the websites =
or
> clicks some links, noticed w3wp process is eating all cpu, is there any w=
ay
> we can find out what part of the app code is causing this CPU spike on my
> server, attaching the dump report, could anyone help me in analyzing the
> report and find out the root cause CPU spike.. for single user itself it =
is
> reaching 100% cpu
>
> Thanks in advance ---here is the dump report------------------------
> --------------------------------------------REPORT---------- -------------=
--=AD---
> ----------------------------------------------
>
> Analysis Summary =20
> Type Description Recommendation
> Information
> DebugDiag did not detect any known problems in w3wp.
> exe__DefaultAppPool__PID__1708__Date__10_11_2007__Time_10_28 _42PM__531__M=
an=ADual
> Dump.dmp using the current set of scripts.
>
> Analysis Details =20
>
> Your browser settings are currently prohibiting this report's scripts fr=
om
> running.
>
> This is preventing some features of this analysis report from displaying
> properly. To enable scripts to run, right-click the security warning above
> and choose "Allow Blocked Content..." or enable the "Allow active content=
to
> run in files on My Computer*" setting on the Advanced tab of your "Intern=
et
> Options" dialog to avoid being prompted in the future
>
> Table Of Contents
> w3wp.
> exe__DefaultAppPool__PID__1708__Date__10_11_2007__Time_10_28 _42PM__531__M=
an=ADual
> Dump.dmp
>
> Top 5 threads by CPU time
>
> Thread report
>
> HTTP Report
>
> Report for w3wp.
> exe__DefaultAppPool__PID__1708__Date__10_11_2007__Time_10_28 _42PM__531__M=
an=ADual
> Dump.dmp
>
> Report for w3wp.
> exe__DefaultAppPool__PID__1708__Date__10_11_2007__Time_10_28 _42PM__531__M=
an=ADual
> Dump.dmp
> Type of Analysis Performed Hang Analysis
> Machine Name xxxxxxxx
> Operating System Windows Server 2003 Service Pack 1
> Number Of Processors 4
> Process ID 1708
> Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
> System Up-Time 1 day(s) 08:21:43
> Process Up-Time 05:11:24
>
> Top 5 Threads by CPU time
> Note - Times include both user mode and kernel mode for each thread Threa=
d ID:
> 29 Total CPU Time: 00:45:59.093 Entry Point for Thread: mscorsvr!
> ThreadpoolMgr::intermediateThreadProc
> Thread ID: 17 Total CPU Time: 00:41:17.780 Entry Point for Thread:
> mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Thread ID: 28 Total CPU Time: 00:38:42.890 Entry Point for Thread:
> mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Thread ID: 22 Total CPU Time: 00:00:26.187 Entry Point for Thread:
> mscorsvr!gc_heap::gc_thread_stub
> Thread ID: 24 Total CPU Time: 00:00:25.984 Entry Point for Thread:
> mscorsvr!gc_heap::gc_thread_stub
>
> Thread report
>
> Thread 0 - System ID 2916
> Entry point w3wp!wmainCRTStartup
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.078
> Time spent in kernel mode 0 Days 00:00:00.140
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> w3dt!WP_CONTEXT::RunMainThreadLoop+10 =20
> w3dt!UlAtqStartListen+2d =20
> w3core!W3_SERVER::StartListen+bd =20
> w3core!UlW3Start+26e =20
> w3wp!wmain+22a =20
> w3wp!wmainCRTStartup+12b =20
> kernel32!BaseProcessStart+23 =20
>
> Back to Top
>
> Thread 1 - System ID 3204
> Entry point ntdll!RtlpTimerThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.859
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> ntdll!RtlpTimerThread+47 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 2 - System ID 3884
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.343
> Time spent in kernel mode 0 Days 00:00:00.062
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+33 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+24 =20
> w3tp!THREAD_MANAGER::ThreadManagerThread+39 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 3 - System ID 3120
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:01.156
> Time spent in kernel mode 0 Days 00:00:00.750
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+33 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+24 =20
> w3tp!THREAD_MANAGER::ThreadManagerThread+39 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 4 - System ID 3992
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.203
> Time spent in kernel mode 0 Days 00:00:00.093
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+33 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+24 =20
> w3tp!THREAD_MANAGER::ThreadManagerThread+39 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 5 - System ID 1568
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.765
> Time spent in kernel mode 0 Days 00:00:00.203
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+33 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+24 =20
> w3tp!THREAD_MANAGER::ThreadManagerThread+39 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 6 - System ID 920
> Entry point ntdll!RtlpWaitThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.046
> Time spent in kernel mode 0 Days 00:00:00.046
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> ntdll!RtlpWaitThread+161 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 7 - System ID 2760
> Entry point msvcrt!_endthreadex+2f
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:02.609
> Time spent in kernel mode 0 Days 00:00:04.812
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> user32!RealMsgWaitForMultipleObjectsEx+141 =20
> user32!MsgWaitForMultipleObjects+1f =20
> acsrtl!RemoveWorkItem+27b =20
> msvcrt!free+c8 =20
> kernel32!BaseThreadStart+34 =20
> kernel32!_SEH_epilog+18 =20
>
> Back to Top
>
> Thread 8 - System ID 3624
> Entry point msvcrt!_endthreadex+2f
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> user32!RealMsgWaitForMultipleObjectsEx+141 =20
> user32!MsgWaitForMultipleObjects+1f =20
> acsrtl!RemoveWorkItem+27b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 9 - System ID 2256
> Entry point msvcrt!_endthreadex+2f
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> user32!RealMsgWaitForMultipleObjectsEx+141 =20
> user32!MsgWaitForMultipleObjects+1f =20
> acsrtl!RemoveWorkItem+27b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 10 - System ID 1868
> Entry point msvcrt!_endthreadex+2f
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> user32!RealMsgWaitForMultipleObjectsEx+141 =20
> user32!MsgWaitForMultipleObjects+1f =20
> acsrtl!RemoveWorkItem+27b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 11 - System ID 2784
> Entry point msatq!AtqInitialize+1354
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> msatq!AtqInitialize+1392 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 12 - System ID 3012
> Entry point wmisink!CWMIEventSinkWrapper::SetupSubscription+30b
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.562
> Time spent in kernel mode 0 Days 00:00:00.031
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> kernel32!WaitForMultipleObjects+18 =20
> wmisink!CWMIEventSinkWrapper::SetupSubscription+48e =20
>
> Back to Top
>
> Thread 13 - System ID 1384
> Entry point RfFilExt!CMBData::~CMBData+c2
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is calling an ISAPI Filter RfFilExt
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> RfFilExt!CMBData::~CMBData+f6 =20
>
> Back to Top
>
> Thread 14 - System ID 2796
> Entry point w3core!HTTP_COMPRESSION::CompressionThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> w3core!HTTP_COMPRESSION::CompressionThread+126 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 15 - System ID 3888
> Entry point ntdll!RtlpIOWorkerThread
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> ntdll!RtlpIOWorkerThread+3f =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 16 - System ID 2324
> Entry point mscorsvr!ThreadpoolMgr::GateThreadStart
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.046
> Time spent in kernel mode 0 Days 00:00:00.015
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> kernel32!SleepEx+68 =20
> kernel32!Sleep+f =20
> mscorsvr!ThreadpoolMgr::GateThreadStart+54 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 17 - System ID 4020
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:31:22.390
> Time spent in kernel mode 0 Days 00:09:55.390
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 18 - System ID 956
> Entry point mscorsvr!DebuggerRCThread::ThreadProcStatic
> Create time 10/11/2007 5:17:20 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> kernel32!WaitForMultipleObjects+18 =20
> mscorsvr!DebuggerRCThread::MainLoop+90 =20
> mscorsvr!DebuggerRCThread::ThreadProc+68 =20
> mscorsvr!DebuggerRCThread::ThreadProcStatic+b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 19 - System ID 240
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:00.359
> Time spent in kernel mode 0 Days 00:00:00.046
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> mscorsvr!ThreadpoolMgr::CompletionPortThreadStart+49 =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 20 - System ID 1736
> Entry point StubProfiler!DllRegisterServer+18f92
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:00.046
> Time spent in kernel mode 0 Days 00:00:00.046
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> StubProfiler!DllRegisterServer+887d =20
> ntdll!RtlImageNtHeader+1b =20
> StubProfiler!DllRegisterServer+13850 =20
>
> Back to Top
>
> Thread 21 - System ID 444
> Entry point msvcr80!_threadstartex
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:05.953
> Time spent in kernel mode 0 Days 00:00:00.953
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> kernel32!WaitForMultipleObjects+18 =20
> PerfMon+13992 =20
> ntdll!NtQueryInformationProcess+c =20
> msvcr80!_encode_pointer+59 f:\rtm\vctools\crt_bld\self_x86\crt\src\tidt=
able.
> c @ 112 + 6
> PerfMon!DllUnregisterServer+7fbb =20
> PerfMon!DllUnregisterServer+34a4d =20
> msvcr80!_callthreadstartex+1b f:\rtm\vctools\crt_bld\self_x86\crt\src\
> threadex.c @ 348 + 6
> msvcr80!_threadstartex+66 f:\rtm\vctools\crt_bld\self_x86\crt\src\threa=
dex.
> c @ 326 + 5
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 22 - System ID 3716
> Entry point mscorsvr!gc_heap::gc_thread_stub
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:25.875
> Time spent in kernel mode 0 Days 00:00:00.312
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!gc_heap::gc_thread_function+2f =20
> mscorsvr!gc_heap::gc_thread_stub+1e =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 23 - System ID 204
> Entry point mscorsvr!gc_heap::gc_thread_stub
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:23.671
> Time spent in kernel mode 0 Days 00:00:00.187
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!gc_heap::gc_thread_function+2f =20
> mscorsvr!gc_heap::gc_thread_stub+1e =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 24 - System ID 1208
> Entry point mscorsvr!gc_heap::gc_thread_stub
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:25.750
> Time spent in kernel mode 0 Days 00:00:00.234
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!gc_heap::gc_thread_function+2f =20
> mscorsvr!gc_heap::gc_thread_stub+1e =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 25 - System ID 3960
> Entry point mscorsvr!gc_heap::gc_thread_stub
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:25.406
> Time spent in kernel mode 0 Days 00:00:00.203
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!gc_heap::gc_thread_function+2f =20
> mscorsvr!gc_heap::gc_thread_stub+1e =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 26 - System ID 172
> Entry point mscorsvr!Thread::intermediateThreadProc
> Create time 10/11/2007 5:17:21 PM
> Time spent in user mode 0 Days 00:00:02.781
> Time spent in kernel mode 0 Days 00:00:00.218
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> kernel32!WaitForMultipleObjects+18 =20
> mscorsvr!WaitForFinalizerEvent+5a =20
> mscorsvr!GCHeap::FinalizerThreadStart+96 =20
> mscorsvr!Thread::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 27 - System ID 3804
> Entry point mscorsvr!ThreadpoolMgr::TimerThreadStart
> Create time 10/11/2007 5:17:23 PM
> Time spent in user mode 0 Days 00:00:00.031
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> kernel32!SleepEx+68 =20
> mscorsvr!ThreadpoolMgr::TimerThreadStart+30 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 28 - System ID 452
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 5:17:29 PM
> Time spent in user mode 0 Days 00:29:18.578
> Time spent in kernel mode 0 Days 00:09:24.312
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 29 - System ID 3920
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 5:17:30 PM
> Time spent in user mode 0 Days 00:34:49.343
> Time spent in kernel mode 0 Days 00:11:09.750
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 30 - System ID 2296
> Entry point mscorsvr!ThreadpoolMgr::WaitThreadStart
> Create time 10/11/2007 5:17:34 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.015
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> kernel32!SleepEx+68 =20
> mscorsvr!ThreadpoolMgr::WaitThreadStart+45 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 31 - System ID 1580
> Create time 12:00:00 AM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!ZwReplyWaitReceivePortEx+c =20
> rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+198 =20
> rpcrt4!RecvLotsaCallsWrapper+d =20
> rpcrt4!BaseCachedThreadRoutine+9d =20
> rpcrt4!ThreadStartRoutine+1b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 32 - System ID 200
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 10/11/2007 9:15:03 PM
> Time spent in user mode 0 Days 00:00:00.453
> Time spent in kernel mode 0 Days 00:00:00.093
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+33 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+24 =20
> w3tp!THREAD_MANAGER::ThreadManagerThread+39 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 33 - System ID 3832
> Entry point LeakTrack+d6fa
> Create time 10/11/2007 9:30:03 PM
> Time spent in user mode 0 Days 00:00:00.031
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> LeakTrack+d782 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 34 - System ID 3336
> Entry point LeakTrack+d6fa
> Create time 10/11/2007 9:30:03 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> LeakTrack+d782 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 35 - System ID 2512
> Entry point LeakTrack+c431
> Create time 10/11/2007 9:30:03 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> LeakTrack+c44f =20
>
> Back to Top
>
> Thread 36 - System ID 2776
> Entry point w3tp!THREAD_MANAGER::ThreadManagerThread
> Create time 10/11/2007 9:36:38 PM
> Time spent in user mode 0 Days 00:00:00.296
> Time spent in kernel mode 0 Days 00:00:00.171
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+33 =20
> w3tp!THREAD_POOL_DATA::ThreadPoolThread+24 =20
> w3tp!THREAD_MANAGER::ThreadManagerThread+39 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 37 - System ID 964
> Entry point mscorsvr!Thread::intermediateThreadProc
> Create time 10/11/2007 9:49:14 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> mscorsvr!Thread::DoAppropriateWaitWorker+c1 =20
> mscorsvr!Thread::DoAppropriateWait+46 =20
> mscorsvr!WaitHandleNative::CorWaitMultipleNative+ff =20
> 0x04642bc7 =20
> mscorsvr!CallDescrWorker+30 =20
> mscorsvr!MethodDesc::CallDescr+1b8 =20
> mscorsvr!MethodDesc::CallDescr+4f =20
> mscorsvr!MethodDesc::Call+97 =20
> mscorsvr!ThreadNative::KickOffThread_Worker+9d =20
> mscorsvr!ThreadNative::KickOffThread+c2 =20
> mscorsvr!Thread::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 38 - System ID 3008
> Entry point ntdll!RtlpWorkerThread
> Create time 10/11/2007 9:53:42 PM
> Time spent in user mode 0 Days 00:00:00.046
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> ntdll!RtlpWorkerThread+3d =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 39 - System ID 3456
> Create time 12:00:00 AM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!ZwReplyWaitReceivePortEx+c =20
> rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+198 =20
> rpcrt4!RecvLotsaCallsWrapper+d =20
> rpcrt4!BaseCachedThreadRoutine+9d =20
> rpcrt4!ThreadStartRoutine+1b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 40 - System ID 3192
> Create time 12:00:00 AM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!ZwReplyWaitReceivePortEx+c =20
> rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+198 =20
> rpcrt4!RecvLotsaCallsWrapper+d =20
> rpcrt4!BaseCachedThreadRoutine+9d =20
> rpcrt4!ThreadStartRoutine+1b =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 41 - System ID 2536
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 10:26:41 PM
> Time spent in user mode 0 Days 00:00:17.281
> Time spent in kernel mode 0 Days 00:00:03.687
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 42 - System ID 416
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 10:26:44 PM
> Time spent in user mode 0 Days 00:00:09.250
> Time spent in kernel mode 0 Days 00:00:03.406
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 43 - System ID 3464
> Entry point ole32!CRpcThreadCache::RpcWorkerThreadEntry
> Create time 10/11/2007 10:27:25 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> kernel32!SleepEx+68 =20
> kernel32!Sleep+f =20
> ole32!CROIDTable::WorkerThreadLoop+14 =20
> ole32!CRpcThread::WorkerLoop+1e =20
> ole32!CRpcThreadCache::RpcWorkerThreadEntry+20 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 44 - System ID 1056
> Entry point mscorsvr!Thread::intermediateThreadProc
> Create time 10/11/2007 10:27:26 PM
> Time spent in user mode 0 Days 00:00:00.093
> Time spent in kernel mode 0 Days 00:00:00.015
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> mscorsvr!Thread::DoAppropriateWaitWorker+c1 =20
> mscorsvr!Thread::DoAppropriateWait+46 =20
> mscorsvr!WaitHandleNative::CorWaitMultipleNative+ff =20
> 0x04642bc7 =20
> mscorsvr!CallDescrWorker+30 =20
> mscorsvr!MethodDesc::CallDescr+1b8 =20
> mscorsvr!MethodDesc::CallDescr+4f =20
> mscorsvr!MethodDesc::Call+97 =20
> mscorsvr!ThreadNative::KickOffThread_Worker+9d =20
> mscorsvr!Thread::DoADCallBack+5c =20
> mscorsvr!ThreadNative::KickOffThread+bb =20
> mscorsvr!Thread::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 45 - System ID 1700
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 10:27:27 PM
> Time spent in user mode 0 Days 00:00:07.484
> Time spent in kernel mode 0 Days 00:00:01.812
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 46 - System ID 2500
> Entry point ntdll!RtlpWorkerThread
> Create time 10/11/2007 10:27:45 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.015
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> ntdll!RtlpWorkerThread+3d =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 47 - System ID 716
> Entry point mscorsvr!Thread::intermediateThreadProc
> Create time 10/11/2007 10:27:51 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> This thread is not fully resolved and may or may not be a problem. Further
> analysis of these threads may be required.
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtDelayExecution+c =20
> kernel32!SleepEx+68 =20
> mscorsvr!Thread::UserSleep+93 =20
> mscorsvr!ThreadNative::Sleep+30 =20
> 0x04646592 =20
> mscorsvr!CallDescrWorker+30 =20
> mscorsvr!MethodDesc::CallDescr+1b8 =20
> mscorsvr!MethodDesc::CallDescr+4f =20
> mscorsvr!MethodDesc::Call+97 =20
> mscorsvr!ThreadNative::KickOffThread_Worker+9d =20
> mscorsvr!Thread::DoADCallBack+5c =20
> mscorsvr!ThreadNative::KickOffThread+bb =20
> mscorsvr!Thread::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 48 - System ID 1836
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 10:27:57 PM
> Time spent in user mode 0 Days 00:00:00.109
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> mscorsvr!ThreadpoolMgr::CompletionPortThreadStart+49 =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 49 - System ID 3264
> Entry point GdiPlus!BackgroundThreadProc
> Create time 10/11/2007 10:28:00 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForMultipleObjects+c =20
> kernel32!WaitForMultipleObjectsEx+11a =20
> user32!RealMsgWaitForMultipleObjectsEx+141 =20
> user32!MsgWaitForMultipleObjects+1f =20
> GdiPlus!BackgroundThreadProc+59 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 50 - System ID 1860
> Entry point ntdll!RtlpWorkerThread
> Create time 10/11/2007 10:28:25 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> ntdll!RtlpWorkerThread+3d =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 51 - System ID 3648
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 10:28:26 PM
> Time spent in user mode 0 Days 00:00:00.00
> Time spent in kernel mode 0 Days 00:00:00.00
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtRemoveIoCompletion+c =20
> kernel32!GetQueuedCompletionStatus+29 =20
> mscorsvr!ThreadpoolMgr::CompletionPortThreadStart+49 =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> Thread 52 - System ID 2912
> Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
> Create time 10/11/2007 10:28:35 PM
> Time spent in user mode 0 Days 00:00:01.937
> Time spent in kernel mode 0 Days 00:00:00.515
>
> Function Source
> ntdll!KiFastSystemCallRet =20
> ntdll!NtWaitForSingleObject+c =20
> kernel32!WaitForSingleObjectEx+ac =20
> kernel32!WaitForSingleObject+12 =20
> mscorsvr!ThreadpoolMgr::WorkerThreadStart+3a =20
> mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 =20
> kernel32!BaseThreadStart+34 =20
>
> Back to Top
>
> HTTP report
> IIS ATQ worker thread count 6 Thread(s)
> Available ATQ worker thread count 6 Thread(s)
> Active client connections 42 client connection(s)
>
> Client Connections
> 42 connection(s) waiting for the next request.
>
> Script Summary =20
> Script Name Status Error Code Error Source Error Description Source Line
> CrashHangAnalysis.asp Completed
>
> --
> Message posted via WinServerKB.comhttp://www.winserverkb.com/Uwe/Forums.a=
spx/iis-general/200710/1

Re: Help analyzing w3wp.exe dump file

I dont know what is basic profiling code, i am from system admin side, dont
know much abt coding side.. what do i need to ask my developer to lookin or,
what do i need to ask him to add for this basic profiling.. how do we setup
to figure out the issue... we are running .Net profiler.. but no idea how to
intrepret and debug the issue... desparately looking for some help on this..
since i am managing this app from system side.. dont know how to trouble
shoot the cpu spike issue.. Pls help me

Gobi

David Wang wrote:
>Nothing unusual with this report.
>
>Why don't you add basic profiling code to the application, or run .Net
>Profiling tools, to determine where the time is being spent?
>
>DebugDiag is not the tool for this. Nothing is hanging, leaking, or
>crashing.
>
>//David
>http://w3-4u.blogspot.com
>http://blogs.msdn.com/David.Wang
>//
>
>> My iis 6 webserver CPU spikes 100 % when user browse around the websites or
>> clicks some links, noticed w3wp process is eating all cpu, is there any way
>[quoted text clipped - 1028 lines]
>> --
>> Message posted via WinServerKB.comhttp://www.winserverkb.com/Uwe/Forums.aspx/ii s-general/200710/1

--
Message posted via http://www.winserverkb.com

Re: Help analyzing w3wp.exe dump file

I suspect that you are on the hook looking for help because the
application is CPU spiking and failing some performance metric in
production.

Since you are not responsible for interpreting or debugging anything
(that's the developer's responsibility), you simply need to pass the
hot-potato back to the developer to make him instrument his
application to PROVE where his application is spending its time.
Isolate the application to its own Application Pool and show that a
specific application is taking a long time or a lot of CPU and then
make the developer PROVE where the time or CPU is spent in his
application.

It won't be long before the developer figures out how to insert
profiling code and run a basic performance baseline.

The developer may choose to push back and ask you for more
measurements of database performance, network latency, etc -- but
that's fine. At least you got the developer to tell you his
application's dependencies, which all you to better monitor the
application.

Until you have a way to pass the hot-potato back to the developer, the
developer has no incentive to write code which makes it easier for you
to manage. The more you shield the developer, the worse your job will
become.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Oct 13, 6:07 pm, "gobinathan via WinServerKB.com"
wrote:
> I dont know what is basic profiling code, i am from system admin side, dont
> know much abt coding side.. what do i need to ask my developer to lookin or,
> what do i need to ask him to add for this basic profiling.. how do we setup
> to figure out the issue... we are running .Net profiler.. but no idea how to
> intrepret and debug the issue... desparately looking for some help on this..
> since i am managing this app from system side.. dont know how to trouble
> shoot the cpu spike issue.. Pls help me
>
> Gobi
>
>
>
>
>
> David Wang wrote:
> >Nothing unusual with this report.
>
> >Why don't you add basic profiling code to the application, or run .Net
> >Profiling tools, to determine where the time is being spent?
>
> >DebugDiag is not the tool for this. Nothing is hanging, leaking, or
> >crashing.
>
> >//David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> >//
>
> >> My iis 6 webserver CPU spikes 100 % when user browse around the websites or
> >> clicks some links, noticed w3wp process is eating all cpu, is there any way
> >[quoted text clipped - 1028 lines]
> >> --
> >> Message posted via WinServerKB.comhttp://www.winserverkb.com/Uwe/Forums.aspx/ii s-general/200710/1
>
> --
> Message posted viahttp://www.winserverkb.com- Hide quoted text -
>
> - Show quoted text -

Re: Help analyzing w3wp.exe dump file

Hi Dave thanks for your suggestion, same time i took IISSTATE dump log also..
if some one can interpret and tell me the reason for CPU spike it would be
great,

Problem is same code and app in development environment is working fine.. but
spiking in QA environment that is why the developers are pointing the
environment..,, Is there anything to do with MOM agent monitoring do i have
to install some hotfix for MOM if i run on IIS environment?

Pls help in this, copying the IIS State log

Opened log file 'D:\ProcessMon\IISstate\output\IISState-3584.log'

***********************
Starting new log output
IISState version 3.3.1

Sun Oct 14 01:16:35 2007

OS = Windows 2003 Server
Executable: w3wp.exe
PID = 3584

Note: Thread times are formatted as HH:MM:SS.ms

***********************


IIS has crashed...
Beginning Analysis
DLL (!FunctionName) that failed:




Thread ID: 18
System Thread ID: 6b8
Kernel Time: 1:2:40.109
User Time: 3:15:40.515
Thread Type: Other
# ChildEBP RetAddr
WARNING: Frame IP not in any known module. Following frames may be wrong.
00 0219f774 0986a5e9 0x986beac
01 0219f7d4 08aaf1a4 0x986a5e9
02 0219f840 08aac0cd 0x8aaf1a4
03 0219f87c 08aab633 0x8aac0cd
04 0219f8cc 08aab55b 0x8aab633
05 0219f918 08695a24 0x8aab55b
06 0219f96c 08695243 0x8695a24
07 0219f9c4 04898c18 0x8695243
08 0219fa54 7923c206 0x4898c18
09 0219fa94 791cc3c8 mscorsvr+0x8c206
0a 0219fadc 7923c1c3 mscorsvr+0x1c3c8
0b 0219fb44 022ea0bd mscorsvr+0x8c1c3
0c 0219fc28 038c4cd8 0x22ea0bd
0d 038c4cd8 00000001 0x38c4cd8
Closing open log file D:\ProcessMon\IISstate\output\IISState-3584.log
Opened log file 'D:\ProcessMon\IISstate\output\IISState-3584.log'

***********************
Starting new log output
IISState version 3.3.1

Sun Oct 14 01:19:53 2007

OS = Windows 2003 Server
Executable: w3wp.exe
PID = 3584

Note: Thread times are formatted as HH:MM:SS.ms

***********************




Thread ID: 0
System Thread ID: 9cc
Kernel Time: 0:0:0.46
User Time: 0:0:0.78
Thread Status: Thread is in a WAIT state.
Thread Type: HTTP Compression Thread
# ChildEBP RetAddr
00 0006fc08 7c822124 ntdll!KiFastSystemCallRet
01 0006fc0c 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0006fc7c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0006fc90 5a36467a kernel32!WaitForSingleObject+0x12
04 0006fca0 5a366e63 w3dt!WP_CONTEXT::RunMainThreadLoop+0x10
05 0006fca8 5a3af41d w3dt!UlAtqStartListen+0x2d
06 0006fcb8 5a3bc259 w3core!W3_SERVER::StartListen+0xbd
07 0006ff0c 0100187c w3core!UlW3Start+0x26e
08 0006ff44 01001a23 w3wp!wmain+0x22a
09 0006ffc0 77e523cd w3wp!wmainCRTStartup+0x12b
0a 0006fff0 00000000 kernel32!BaseProcessStart+0x23




Thread ID: 1
System Thread ID: 970
Kernel Time: 0:0:0.15
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 009eff9c 7c821364 ntdll!KiFastSystemCallRet
01 009effa0 7c81fe26 ntdll!NtDelayExecution+0xc
02 009effb8 77e66063 ntdll!RtlpTimerThread+0x47
03 009effec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 2
System Thread ID: 3bc
Kernel Time: 0:0:0.343
User Time: 0:0:1.671
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00c8ff24 7c821bf4 ntdll!KiFastSystemCallRet
01 00c8ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 00c8ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
03 00c8ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
04 00c8ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
05 00c8ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
06 00c8ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 3
System Thread ID: e40
Kernel Time: 0:0:0.343
User Time: 0:0:1.718
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00ccff24 7c821bf4 ntdll!KiFastSystemCallRet
01 00ccff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 00ccff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
03 00ccff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
04 00ccffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
05 00ccffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
06 00ccffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 4
System Thread ID: a88
Kernel Time: 0:0:0.218
User Time: 0:0:1.46
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00d0ff24 7c821bf4 ntdll!KiFastSystemCallRet
01 00d0ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 00d0ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
03 00d0ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
04 00d0ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
05 00d0ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
06 00d0ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 5
System Thread ID: e98
Kernel Time: 0:0:0.484
User Time: 0:0:1.703
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00d4ff24 7c821bf4 ntdll!KiFastSystemCallRet
01 00d4ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 00d4ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
03 00d4ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
04 00d4ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
05 00d4ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
06 00d4ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 6
System Thread ID: 448
Kernel Time: 0:0:0.265
User Time: 0:0:0.78
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 00e0fcec 7c822114 ntdll!KiFastSystemCallRet
01 00e0fcf0 7c83acfd ntdll!NtWaitForMultipleObjects+0xc
02 00e0ffb8 77e66063 ntdll!RtlpWaitThread+0x161
03 00e0ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 7
System Thread ID: ec4
Kernel Time: 0:0:27.375
User Time: 0:0:14.781
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:
\Program Files\Microsoft Application Center\ACSRTL.DLL -
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 00f7fe08 7c822114 ntdll!KiFastSystemCallRet
01 00f7fe0c 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 00f7feb4 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 00f7ff10 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0x141
04 00f7ff2c 602532ef USER32!MsgWaitForMultipleObjects+0x1f
WARNING: Stack unwind information not available. Following frames may be
wrong.
05 00007530 00000000 ACSRTL!RemoveWorkItem+0x27b




Thread ID: 8
System Thread ID: a50
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 00fbfe08 7c822114 ntdll!KiFastSystemCallRet
01 00fbfe0c 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 00fbfeb4 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 00fbff10 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0x141
04 00fbff2c 602532ef USER32!MsgWaitForMultipleObjects+0x1f
WARNING: Stack unwind information not available. Following frames may be
wrong.
05 00fbffb8 77e66063 ACSRTL!RemoveWorkItem+0x27b
06 00fbffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 9
System Thread ID: 160
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 00fffe08 7c822114 ntdll!KiFastSystemCallRet
01 00fffe0c 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 00fffeb4 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 00ffff10 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0x141
04 00ffff2c 602532ef USER32!MsgWaitForMultipleObjects+0x1f
WARNING: Stack unwind information not available. Following frames may be
wrong.
05 00ffffb8 77e66063 ACSRTL!RemoveWorkItem+0x27b
06 00ffffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 10
System Thread ID: f00
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0104fe08 7c822114 ntdll!KiFastSystemCallRet
01 0104fe0c 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0104feb4 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0104ff10 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0x141
04 0104ff2c 602532ef USER32!MsgWaitForMultipleObjects+0x1f
WARNING: Stack unwind information not available. Following frames may be
wrong.
05 0104ffb8 77e66063 ACSRTL!RemoveWorkItem+0x27b
06 0104ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 11
System Thread ID: bb0
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:
\Program Files\Microsoft Application Center\MSATQ.dll -
Thread Type: Other
# ChildEBP RetAddr
00 0114ff4c 7c821bf4 ntdll!KiFastSystemCallRet
01 0114ff50 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 0114ff7c 605a8db1 kernel32!GetQueuedCompletionStatus+0x29
WARNING: Stack unwind information not available. Following frames may be
wrong.
03 0114ffb8 77e66063 MSATQ!AtqInitialize+0x1392
04 0114ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 12
System Thread ID: cc4
Kernel Time: 0:0:0.15
User Time: 0:0:0.31
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:
\Program Files\Microsoft Application Center\WMISINK.dll -
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0118feb4 7c822114 ntdll!KiFastSystemCallRet
01 0118feb8 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0118ff60 77e61075 kernel32!WaitForMultipleObjectsEx+0x11a
03 0118ff7c 60863999 kernel32!WaitForMultipleObjects+0x18
WARNING: Stack unwind information not available. Following frames may be
wrong.
04 00000000 00000000 WMISINK!CWMIEventSinkWrapper::SetupSubscription+0x48e




Thread ID: 13
System Thread ID: cc8
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:
\Program Files\Microsoft Application Center\RfFilExt.dll -
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0120ff1c 7c822124 ntdll!KiFastSystemCallRet
01 0120ff20 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0120ff90 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0120ffa4 607cc9fb kernel32!WaitForSingleObject+0x12
WARNING: Stack unwind information not available. Following frames may be
wrong.
04 0120ffec 00000000 RfFilExt!CMBData::~CMBData+0xf6




Thread ID: 14
System Thread ID: a5c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: HTTP Compression Thread
# ChildEBP RetAddr
00 01ddfa84 7c822124 ntdll!KiFastSystemCallRet
01 01ddfa88 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 01ddfaf8 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 01ddfb0c 5a3b8147 kernel32!WaitForSingleObject+0x12
04 01ddffb8 77e66063 w3core!HTTP_COMPRESSION::CompressionThread+0x126
05 01ddffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 15
System Thread ID: c30
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 01e1ff8c 7c821364 ntdll!KiFastSystemCallRet
01 01e1ff90 7c815267 ntdll!NtDelayExecution+0xc
02 01e1ffb8 77e66063 ntdll!RtlpIOWorkerThread+0x3f
03 01e1ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 16
System Thread ID: 960
Kernel Time: 0:0:0.140
User Time: 0:0:0.593
Thread Type: Other
# ChildEBP RetAddr
00 020dfec0 7c821bf4 ntdll!KiFastSystemCallRet
01 020dfec4 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 020dfef0 791fdb22 kernel32!GetQueuedCompletionStatus+0x29
03 020dff24 791fdacc mscorsvr+0x4db22
04 020dffb8 77e66063 mscorsvr+0x4dacc
05 020dffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 17
System Thread ID: db0
Kernel Time: 0:0:0.31
User Time: 0:0:0.31
Thread Type: Other
# ChildEBP RetAddr
00 0211fe50 7c821364 ntdll!KiFastSystemCallRet
01 0211fe54 77e42439 ntdll!NtDelayExecution+0xc
02 0211febc 77e424b7 kernel32!SleepEx+0x68
03 0211fecc 791bf4f9 kernel32!Sleep+0xf
04 0211ffb8 77e66063 mscorsvr+0xf4f9
05 0211ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 18
System Thread ID: 6b8
Kernel Time: 1:2:40.109
User Time: 3:15:40.515
Thread Type: Other
# ChildEBP RetAddr
WARNING: Frame IP not in any known module. Following frames may be wrong.
00 0219f774 0986a5e9 0x986beac
01 0219f7d4 08aaf1a4 0x986a5e9
02 0219f840 08aac0cd 0x8aaf1a4
03 0219f87c 08aab633 0x8aac0cd
04 0219f8cc 08aab55b 0x8aab633
05 0219f918 08695a24 0x8aab55b
06 0219f96c 08695243 0x8695a24
07 0219f9c4 04898c18 0x8695243
08 0219fa54 7923c206 0x4898c18
09 0219fa94 791cc3c8 mscorsvr+0x8c206
0a 0219fadc 7923c1c3 mscorsvr+0x1c3c8
0b 0219fb44 022ea0bd mscorsvr+0x8c1c3
0c 0219fc28 038c4cd8 0x22ea0bd
0d 038c4cd8 00000001 0x38c4cd8




Thread ID: 19
System Thread ID: c04
Kernel Time: 1:4:43.15
User Time: 3:21:12.140
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0223fc78 7c822124 ntdll!KiFastSystemCallRet
01 0223fc7c 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0223fcec 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0223fd00 791d401f kernel32!WaitForSingleObject+0x12
04 0223fd24 791fdacc mscorsvr+0x2401f
05 0223ffb8 77e66063 mscorsvr+0x4dacc
06 0223ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 20
System Thread ID: 8ac
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0235fe70 7c822114 ntdll!KiFastSystemCallRet
01 0235fe74 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0235ff1c 77e61075 kernel32!WaitForMultipleObjectsEx+0x11a
03 0235ff38 79238fd6 kernel32!WaitForMultipleObjects+0x18
04 0235ffa0 79238f4d mscorsvr+0x88fd6
05 0235ffb0 7923a714 mscorsvr+0x88f4d
06 0235ffb8 77e66063 mscorsvr+0x8a714
07 0235ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 21
System Thread ID: ad4
Kernel Time: 0:0:0.15
User Time: 0:0:0.31
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:
\Program Files\Avicode\Intercept\Agent\v4.0.150\StubProfiler.dll -
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0241f938 7c822124 ntdll!KiFastSystemCallRet
01 0241f93c 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0241f9ac 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0241f9c0 0236b98d kernel32!WaitForSingleObject+0x12
WARNING: Stack unwind information not available. Following frames may be
wrong.
04 0241fde0 02449400 StubProfiler!DllRegisterServer+0x887d
05 0239c6d4 02376960 0x2449400
06 02375470 ffffff48 StubProfiler!DllRegisterServer+0x13850
07 e8f18b56 00000000 0xffffff48




Thread ID: 22
System Thread ID: c2c
Kernel Time: 0:0:0.734
User Time: 0:0:0.687
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:
\Program Files\Avicode\Intercept\Agent\v4.0.150\PerfMon.dll -
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 02fffb20 7c822114 ntdll!KiFastSystemCallRet
01 02fffb24 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 02fffbcc 77e61075 kernel32!WaitForMultipleObjectsEx+0x11a
03 02fffbe8 026c3992 kernel32!WaitForMultipleObjects+0x18
WARNING: Stack unwind information not available. Following frames may be
wrong.
04 02fffeb4 f772fa00 PerfMon+0x13992
05 80a56bcc 00000000 0xf772fa00




Thread ID: 23
System Thread ID: b88
Kernel Time: 0:0:1.375
User Time: 0:1:47.109
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0339fefc 7c822124 ntdll!KiFastSystemCallRet
01 0339ff00 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0339ff70 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0339ff84 791fe6b0 kernel32!WaitForSingleObject+0x12
04 0339ffac 792356bf mscorsvr+0x4e6b0
05 0339ffb8 77e66063 mscorsvr+0x856bf
06 0339ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 24
System Thread ID: 13c
Kernel Time: 0:0:0.640
User Time: 0:1:44.515
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 033dfdfc 7c822124 ntdll!KiFastSystemCallRet
01 033dfe00 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 033dfe70 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 033dfe84 791fe6b0 kernel32!WaitForSingleObject+0x12
04 033dfeac 792356bf mscorsvr+0x4e6b0
05 033dffb8 77e66063 mscorsvr+0x856bf
06 033dffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 25
System Thread ID: 9f0
Kernel Time: 0:0:0.593
User Time: 0:1:46.828
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0341fcfc 7c822124 ntdll!KiFastSystemCallRet
01 0341fd00 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0341fd70 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0341fd84 791fe6b0 kernel32!WaitForSingleObject+0x12
04 0341fdac 792356bf mscorsvr+0x4e6b0
05 0341ffb8 77e66063 mscorsvr+0x856bf
06 0341ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 26
System Thread ID: 420
Kernel Time: 0:0:0.671
User Time: 0:1:44.968
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0345fbfc 7c822124 ntdll!KiFastSystemCallRet
01 0345fc00 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0345fc70 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0345fc84 791fe6b0 kernel32!WaitForSingleObject+0x12
04 0345fcac 792356bf mscorsvr+0x4e6b0
05 0345ffb8 77e66063 mscorsvr+0x856bf
06 0345ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 27
System Thread ID: c8c
Kernel Time: 0:0:0.671
User Time: 0:0:8.562
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 0349fe44 7c822124 ntdll!KiFastSystemCallRet
01 0349fe48 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0349feb8 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0349fecc 7927823e kernel32!WaitForSingleObject+0x12


Thanks
Gobi

David Wang wrote:
>I suspect that you are on the hook looking for help because the
>application is CPU spiking and failing some performance metric in
>production.
>
>Since you are not responsible for interpreting or debugging anything
>(that's the developer's responsibility), you simply need to pass the
>hot-potato back to the developer to make him instrument his
>application to PROVE where his application is spending its time.
>Isolate the application to its own Application Pool and show that a
>specific application is taking a long time or a lot of CPU and then
>make the developer PROVE where the time or CPU is spent in his
>application.
>
>It won't be long before the developer figures out how to insert
>profiling code and run a basic performance baseline.
>
>The developer may choose to push back and ask you for more
>measurements of database performance, network latency, etc -- but
>that's fine. At least you got the developer to tell you his
>application's dependencies, which all you to better monitor the
>application.
>
>Until you have a way to pass the hot-potato back to the developer, the
>developer has no incentive to write code which makes it easier for you
>to manage. The more you shield the developer, the worse your job will
>become.
>
>//David
>http://w3-4u.blogspot.com
>http://blogs.msdn.com/David.Wang
>//
>
>On Oct 13, 6:07 pm, "gobinathan via WinServerKB.com"
>wrote:
>> I dont know what is basic profiling code, i am from system admin side, dont
>> know much abt coding side.. what do i need to ask my developer to lookin or,
>[quoted text clipped - 29 lines]
>>
>> - Show quoted text -

--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forums.aspx/iis-general/20071 0/1

Re: Help analyzing w3wp.exe dump file

This is completely different than CPU spiking. It is a crash of some
code, likely provided by the developer, so you need to have the
developer investigate.

I don't know how your organization is structured nor organized, but it
seems weird that you are somehow responsible for the issues you
describe because you have said that you cannot handle them
technically, yet you do not seem able to get the responsible party to
take action. This is a recipe for disaster.

I have no problems helping you out, but I have to draw the line right
now because you are rapidly depending on external people to support
your organization, and that is not healthy for you nor us.

I can only tell you that you will not find any MOM agent or any
external software written by anyone to resolve your issues. You have
to get your software debugged by its developers. You can use the many
free and powerful tools from Microsoft to help, but your developers
are ultimately responsible resolving the issues

It is classic for the developers to say "it doesn't happen on my box
or development environment, so it's not my issue". What you have to do
is make QA environment be the mirror image of production environment,
at which point you can go back to the developer and say "your code
doesn't work in QA and won't work in production, so you have to fix
it".

If QA environment does not mirror production, that is a serious QA
problem which needs to be resolved. It is not worth anyone's time to
look at crashes and CPU spikes until QA environment represents its
target environment. Otherwise, you're testing against a useless
environment that does not represent production.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Oct 13, 11:32 pm, "gobinathan via WinServerKB.com"
wrote:
> Hi Dave thanks for your suggestion, same time i took IISSTATE dump log al=
so..
> if some one can interpret and tell me the reason for CPU spike it would be
> great,
>
> Problem is same code and app in development environment is working fine..=
but
> spiking in QA environment that is why the developers are pointing the
> environment..,, Is there anything to do with MOM agent monitoring do i ha=
ve
> to install some hotfix for MOM if i run on IIS environment?
>
> Pls help in this, copying the IIS State log
>
> Opened log file 'D:\ProcessMon\IISstate\output\IISState-3584.log'
>
> ***********************
> Starting new log output
> IISState version 3.3.1
>
> Sun Oct 14 01:16:35 2007
>
> OS =3D Windows 2003 Server
> Executable: w3wp.exe
> PID =3D 3584
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
> IIS has crashed...
> Beginning Analysis
> DLL (!FunctionName) that failed:
>
> Thread ID: 18
> System Thread ID: 6b8
> Kernel Time: 1:2:40.109
> User Time: 3:15:40.515
> Thread Type: Other
> # ChildEBP RetAddr =20
> WARNING: Frame IP not in any known module. Following frames may be wrong.
> 00 0219f774 0986a5e9 0x986beac
> 01 0219f7d4 08aaf1a4 0x986a5e9
> 02 0219f840 08aac0cd 0x8aaf1a4
> 03 0219f87c 08aab633 0x8aac0cd
> 04 0219f8cc 08aab55b 0x8aab633
> 05 0219f918 08695a24 0x8aab55b
> 06 0219f96c 08695243 0x8695a24
> 07 0219f9c4 04898c18 0x8695243
> 08 0219fa54 7923c206 0x4898c18
> 09 0219fa94 791cc3c8 mscorsvr+0x8c206
> 0a 0219fadc 7923c1c3 mscorsvr+0x1c3c8
> 0b 0219fb44 022ea0bd mscorsvr+0x8c1c3
> 0c 0219fc28 038c4cd8 0x22ea0bd
> 0d 038c4cd8 00000001 0x38c4cd8
> Closing open log file D:\ProcessMon\IISstate\output\IISState-3584.log
> Opened log file 'D:\ProcessMon\IISstate\output\IISState-3584.log'
>
> ***********************
> Starting new log output
> IISState version 3.3.1
>
> Sun Oct 14 01:19:53 2007
>
> OS =3D Windows 2003 Server
> Executable: w3wp.exe
> PID =3D 3584
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
> Thread ID: 0
> System Thread ID: 9cc
> Kernel Time: 0:0:0.46
> User Time: 0:0:0.78
> Thread Status: Thread is in a WAIT state.
> Thread Type: HTTP Compression Thread
> # ChildEBP RetAddr =20
> 00 0006fc08 7c822124 ntdll!KiFastSystemCallRet
> 01 0006fc0c 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 0006fc7c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 0006fc90 5a36467a kernel32!WaitForSingleObject+0x12
> 04 0006fca0 5a366e63 w3dt!WP_CONTEXT::RunMainThreadLoop+0x10
> 05 0006fca8 5a3af41d w3dt!UlAtqStartListen+0x2d
> 06 0006fcb8 5a3bc259 w3core!W3_SERVER::StartListen+0xbd
> 07 0006ff0c 0100187c w3core!UlW3Start+0x26e
> 08 0006ff44 01001a23 w3wp!wmain+0x22a
> 09 0006ffc0 77e523cd w3wp!wmainCRTStartup+0x12b
> 0a 0006fff0 00000000 kernel32!BaseProcessStart+0x23
>
> Thread ID: 1
> System Thread ID: 970
> Kernel Time: 0:0:0.15
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr =20
> 00 009eff9c 7c821364 ntdll!KiFastSystemCallRet
> 01 009effa0 7c81fe26 ntdll!NtDelayExecution+0xc
> 02 009effb8 77e66063 ntdll!RtlpTimerThread+0x47
> 03 009effec 00000000 kernel32!BaseThreadStart+0x34
>
> Thread ID: 2
> System Thread ID: 3bc
> Kernel Time: 0:0:0.343
> User Time: 0:0:1.671
> Thread Type: HTTP Listener
> # ChildEBP RetAddr =20
> 00 00c8ff24 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00c8ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
> 02 00c8ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
> 03 00c8ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 00c8ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 00c8ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 00c8ffec 00000000 kernel32!BaseThreadStart+0x34
>
> Thread ID: 3
> System Thread ID: e40
> Kernel Time: 0:0:0.343
> User Time: 0:0:1.718
> Thread Type: HTTP Listener
> # ChildEBP RetAddr =20
> 00 00ccff24 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00ccff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
> 02 00ccff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
> 03 00ccff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 00ccffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 00ccffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 00ccffec 00000000 kernel32!BaseThreadStart+0x34
>
> Thread ID: 4
> System Thread ID: a88
> Kernel Time: 0:0:0.218
> User Time: 0:0:1.46
> Thread Type: HTTP Listener
> # ChildEBP RetAddr =20
> 00 00d0ff24 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00d0ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
> 02 00d0ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
> 03 00d0ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 00d0ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 00d0ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 00d0ffec 00000000 kernel32!BaseThreadStart+0x34
>
> Thread ID: 5
> System Thread ID: e98
> Kernel Time: 0:0:0.484
> User Time: 0:0:1.703
> Thread Type: HTTP Listener
> # ChildEBP RetAddr =20
> 00 00d4ff24 7c821bf4 ntdll!KiFastSystemCallRet
> 01 00d4ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
> 02 00d4ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
> 03 00d4ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> 04 00d4ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> 05 00d4ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> 06 00d4ffec 00000000 kernel32!BaseThreadStart+0x34
>
> Thread ID: 6
> System Thread ID: 448
> Kernel Time: 0:0:0.265
> User Time: 0:0:0.78
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr =20
> 00 00e0fcec 7c822114 ntdll!KiFastSystemCallRet
> 01 00e0fcf0 7c83acfd ntdll!NtWaitForMultipleObjects+0xc
> 02 00e0ffb8 77e66063 ntdll!RtlpWaitThread+0x161
> 03 00e0ffec 00000000 kernel32!BaseThreadStart+0x34
>
> Thread ID: 7
> System Thread ID: ec4
> Kernel Time: 0:0:27.375
> User Time: 0:0:14.781
> *** ERROR: Symbol file could not be found. Defaulted to export symbols f=
or C:
> \Program Files\Microsoft Application Center\ACSRTL.DLL -
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr =20
> 00 00f7fe08 7c822114 ntdll!KiFastSystemCallRet
> 01 00f7fe0c 77e6711b ntdll!NtWaitForMultipleObjects+0xc
> 02 00f7feb4 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 00f7ff10 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0x141
> 04 00f7ff2c 602532ef USER32!MsgWaitForMultipleObjects+0x1f
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 05 00007530 00000000 ACSRTL!RemoveWorkItem+0x27b
>
> Thread ID: 8
> System Thread ID: a50
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr =20
> 00 00fbfe08 7c822114 ntdll!KiFastSystemCallRet
> 01 00fbfe0c 77e6711b ntdll!NtWaitForMultipleObjects+0xc
> 02 00fbfeb4 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 00fbff10 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0x141
> 04 00fbff2c 602532ef USER32!MsgWaitForMultipleObjects+0x1f
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 05 00fbffb8 77e66063 ACSRTL!RemoveWorkItem+0x27b
> 06 00fbffec 00000000 kernel32!BaseThreadStart+0x34
>
> Thread ID: 9
> System Thread ID: 160
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr =20
> 00 00fffe08 7c822114 ntdll!KiFastSystemCallRet
> 01 00fffe0c 77e6711b ntdll!NtWaitForMultipleObjects+0xc
> 02 00fffeb4 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 00ffff10 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0x141
> 04 00ffff2c 602532ef USER32!MsgWaitForMultipleObjects+0x1f
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 05 00ffffb8 77e66063 ACSRTL!RemoveWorkItem+0x27b
> 06 00ffffec 00000000 kernel32!BaseThreadStart+0x34
>
> Thread ID: 10
> System Thread ID: f00
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr =20
> 00 0104fe08 7c822114 ntdll!KiFastSystemCallRet
> 01 0104fe0c 77e6711b ntdll!NtWaitForMultipleObjects+0xc
> 02 0104feb4 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 0104ff10 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0x141
> 04 0104ff2c 602532ef USER32!MsgWaitForMultipleObjects+0x1f
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 05 0104ffb8 77e66063 ACSRTL!RemoveWorkItem+0x27b
> 06 0104ffec 00000000 kernel32!BaseThreadStart+0x34
>
> Thread ID: 11
> System Thread ID: bb0
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> *** ERROR: Symbol file could not be found. Defaulted to export symbols f=
or C:
> \Program Files\Microsoft Application Center\MSATQ.dll -
> Thread Type: Other
> # ChildEBP RetAddr =20
> 00 0114ff4c 7c821bf4 ntdll!KiFastSystemCallRet
> 01 0114ff50 77e6611a ntdll!NtRemoveIoCompletion+0xc
> 02 0114ff7c 605a8db1 kernel32!GetQueuedCompletionStatus+0x29
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 03 0114ffb8 77e66063 MSATQ!AtqInitialize+0x1392
> 04 0114ffec 00000000 kernel32!BaseThreadStart+0x34
>
> Thread ID: 12
> System Thread ID: cc4
> Kernel Time: 0:0:0.15
> User Time: 0:0:0.31
> *** ERROR: Symbol file could not be found. Defaulted to export symbols f=
or C:
> \Program Files\Microsoft Application Center\WMISINK.dll -
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr =20
> 00 0118feb4 7c822114 ntdll!KiFastSystemCallRet
> 01 0118feb8 77e6711b ntdll!NtWaitForMultipleObjects+0xc
> 02 0118ff60 77e61075 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 0118ff7c 60863999 kernel32!WaitForMultipleObjects+0x18
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 04 00000000 00000000 WMISINK!CWMIEventSinkWrapper::SetupSubscription+0x48e
>
> Thread ID: 13
> System Thread ID: cc8
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> *** ERROR: Symbol file could not be found. Defaulted to export symbols f=
or C:
> \Program Files\Microsoft Application Center\RfFilExt.dll -
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr =20
> 00 0120ff1c 7c822124 ntdll!KiFastSystemCallRet
> 01 0120ff20 77e6baa8 ntdll!NtWaitForSingleObject+0xc
> 02 0120ff90 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
> 03 0120ffa4 607cc9fb kernel32!WaitForSingleObject+0x12
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 04 0120ffec ...
>
> read more =BB

Re: Help analyzing w3wp.exe dump file

That is issue here dave, The QA is pretty much same as Prod.. here in
management is blaming the environment business is pushing to go with current
buggy code to prod, we said it is not,.. but we are in position that this is
issue in code.. that is why i am looking for some help on analyzing them and
get some clue on what is causing the issue..
If you could shade some light on it.. it would be great

tHnaks
Gobi

David Wang wrote:
>This is completely different than CPU spiking. It is a crash of some
>code, likely provided by the developer, so you need to have the
>developer investigate.
>
>I don't know how your organization is structured nor organized, but it
>seems weird that you are somehow responsible for the issues you
>describe because you have said that you cannot handle them
>technically, yet you do not seem able to get the responsible party to
>take action. This is a recipe for disaster.
>
>I have no problems helping you out, but I have to draw the line right
>now because you are rapidly depending on external people to support
>your organization, and that is not healthy for you nor us.
>
>I can only tell you that you will not find any MOM agent or any
>external software written by anyone to resolve your issues. You have
>to get your software debugged by its developers. You can use the many
>free and powerful tools from Microsoft to help, but your developers
>are ultimately responsible resolving the issues
>
>It is classic for the developers to say "it doesn't happen on my box
>or development environment, so it's not my issue". What you have to do
>is make QA environment be the mirror image of production environment,
>at which point you can go back to the developer and say "your code
>doesn't work in QA and won't work in production, so you have to fix
>it".
>
>If QA environment does not mirror production, that is a serious QA
>problem which needs to be resolved. It is not worth anyone's time to
>look at crashes and CPU spikes until QA environment represents its
>target environment. Otherwise, you're testing against a useless
>environment that does not represent production.
>
>//David
>http://w3-4u.blogspot.com
>http://blogs.msdn.com/David.Wang
>//
>
>On Oct 13, 11:32 pm, "gobinathan via WinServerKB.com"
>wrote:
>> Hi Dave thanks for your suggestion, same time i took IISSTATE dump log also..
>> if some one can interpret and tell me the reason for CPU spike it would be
>[quoted text clipped - 283 lines]
>>
>> read more ?

--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forums.aspx/iis-general/20071 0/1

Re: Help analyzing w3wp.exe dump file

Unless you are the dev, you don't need to figure out what is causing
the issue. If you are looking for help to analyze and get a clue for
what is causing the issue, then you are already lost.

>From a QA perspective, one just needs report on what is going on.

The devs are responsible for analyzing the crash and CPU spike. If
they blame the environment, then you simply need to prove your
statement of "QA is pretty much same as Prod", and they have nothing
to blame and need to go to work to figure out what is going on.

Until you are strong in proving that statement, management will likely
blame QA for stalling and help devs push buggy code to Prod -- because
management wants to see the new features come online -- at which point
it'd fail like it did in QA -- and then management will blame QA for
not finding the bugs before going to Production.

Thus, if QA cannot stand firm on the validity of their results, then
this QA is in deep trouble.

For the crash in IIS State, you need symbols for all product code.
This is stuff that devs need to provide.

As for the CPU spike, you will need dev to add .Net Profiling to their
code to perf-test it and see where the bottleneck lies.

QA is responsible for performing these tasks and reporting results of
them. Dev is responsible for heeding the results and then fixing
issues. In no case should non-dev attempt to debug the issue and do
the dev's job for them.

Sorry for being hard-nosed about it, but I will not be able to help
you further. I sense a political problem within your organization that
is surfacing via this technical issue, and that is beyond the scope of
this newsgroup.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Oct 15, 12:46 pm, "gobinathan via WinServerKB.com"
wrote:
> That is issue here dave, The QA is pretty much same as Prod.. here in
> management is blaming the environment business is pushing to go with current
> buggy code to prod, we said it is not,.. but we are in position that this is
> issue in code.. that is why i am looking for some help on analyzing them and
> get some clue on what is causing the issue..
> If you could shade some light on it.. it would be great
>
> tHnaks
> Gobi
>
>
>
>
>
> David Wang wrote:
> >This is completely different than CPU spiking. It is a crash of some
> >code, likely provided by the developer, so you need to have the
> >developer investigate.
>
> >I don't know how your organization is structured nor organized, but it
> >seems weird that you are somehow responsible for the issues you
> >describe because you have said that you cannot handle them
> >technically, yet you do not seem able to get the responsible party to
> >take action. This is a recipe for disaster.
>
> >I have no problems helping you out, but I have to draw the line right
> >now because you are rapidly depending on external people to support
> >your organization, and that is not healthy for you nor us.
>
> >I can only tell you that you will not find any MOM agent or any
> >external software written by anyone to resolve your issues. You have
> >to get your software debugged by its developers. You can use the many
> >free and powerful tools from Microsoft to help, but your developers
> >are ultimately responsible resolving the issues
>
> >It is classic for the developers to say "it doesn't happen on my box
> >or development environment, so it's not my issue". What you have to do
> >is make QA environment be the mirror image of production environment,
> >at which point you can go back to the developer and say "your code
> >doesn't work in QA and won't work in production, so you have to fix
> >it".
>
> >If QA environment does not mirror production, that is a serious QA
> >problem which needs to be resolved. It is not worth anyone's time to
> >look at crashes and CPU spikes until QA environment represents its
> >target environment. Otherwise, you're testing against a useless
> >environment that does not represent production.
>
> >//David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> >//
>
> >On Oct 13, 11:32 pm, "gobinathan via WinServerKB.com"
> >wrote:
> >> Hi Dave thanks for your suggestion, same time i took IISSTATE dump log also..
> >> if some one can interpret and tell me the reason for CPU spike it would be
> >[quoted text clipped - 283 lines]
>
> >> read more ?
>
> --
> Message posted via WinServerKB.comhttp://www.winserverkb.com/Uwe/Forums.aspx/ii s-general/200710/1- Hide quoted text -
>
> - Show quoted text -

Re: Help analyzing w3wp.exe dump file

Unless you are the dev, you don't need to figure out what is causing
the issue. If you are looking for help to analyze and get a clue for
what is causing the issue, then you are already lost.

>From a QA perspective, one just needs report on what is going on.

The devs are responsible for analyzing the crash and CPU spike. If
they blame the environment, then you simply need to prove your
statement of "QA is pretty much same as Prod", and they have nothing
to blame and need to go to work to figure out what is going on.

Until you are strong in proving that statement, management will likely
blame QA for stalling and help devs push buggy code to Prod -- because
management wants to see the new features come online -- at which point
it'd fail like it did in QA -- and then management will blame QA for
not finding the bugs before going to Production.

Thus, if QA cannot stand firm on the validity of their results, then
this QA is in deep trouble.

For the crash in IIS State, you need symbols for all product code.
This is stuff that devs need to provide.

As for the CPU spike, you will need dev to add .Net Profiling to their
code to perf-test it and see where the bottleneck lies.

QA is responsible for performing these tasks and reporting results of
them. Dev is responsible for heeding the results and then fixing
issues. In no case should non-dev attempt to debug the issue and do
the dev's job for them.

Sorry for being hard-nosed about it, but I will not be able to help
you further. I sense a political problem within your organization that
is surfacing via this technical issue, and that is beyond the scope of
this newsgroup.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Oct 15, 12:46 pm, "gobinathan via WinServerKB.com"
wrote:
> That is issue here dave, The QA is pretty much same as Prod.. here in
> management is blaming the environment business is pushing to go with current
> buggy code to prod, we said it is not,.. but we are in position that this is
> issue in code.. that is why i am looking for some help on analyzing them and
> get some clue on what is causing the issue..
> If you could shade some light on it.. it would be great
>
> tHnaks
> Gobi
>
>
>
>
>
> David Wang wrote:
> >This is completely different than CPU spiking. It is a crash of some
> >code, likely provided by the developer, so you need to have the
> >developer investigate.
>
> >I don't know how your organization is structured nor organized, but it
> >seems weird that you are somehow responsible for the issues you
> >describe because you have said that you cannot handle them
> >technically, yet you do not seem able to get the responsible party to
> >take action. This is a recipe for disaster.
>
> >I have no problems helping you out, but I have to draw the line right
> >now because you are rapidly depending on external people to support
> >your organization, and that is not healthy for you nor us.
>
> >I can only tell you that you will not find any MOM agent or any
> >external software written by anyone to resolve your issues. You have
> >to get your software debugged by its developers. You can use the many
> >free and powerful tools from Microsoft to help, but your developers
> >are ultimately responsible resolving the issues
>
> >It is classic for the developers to say "it doesn't happen on my box
> >or development environment, so it's not my issue". What you have to do
> >is make QA environment be the mirror image of production environment,
> >at which point you can go back to the developer and say "your code
> >doesn't work in QA and won't work in production, so you have to fix
> >it".
>
> >If QA environment does not mirror production, that is a serious QA
> >problem which needs to be resolved. It is not worth anyone's time to
> >look at crashes and CPU spikes until QA environment represents its
> >target environment. Otherwise, you're testing against a useless
> >environment that does not represent production.
>
> >//David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> >//
>
> >On Oct 13, 11:32 pm, "gobinathan via WinServerKB.com"
> >wrote:
> >> Hi Dave thanks for your suggestion, same time i took IISSTATE dump log also..
> >> if some one can interpret and tell me the reason for CPU spike it would be
> >[quoted text clipped - 283 lines]
>
> >> read more ?
>
> --
> Message posted via WinServerKB.comhttp://www.winserverkb.com/Uwe/Forums.aspx/ii s-general/200710/1- Hide quoted text -
>
> - Show quoted text -