Analysis Summary
Type Description Recommendation
Error Detected a serious critical section related problem in dump_PID_19116.dmp
Lock at 0x00436ca0 is Uninitialized
Impact analysis
7.69% of threads blocked
(Threads 5 6 7 8 11 14 16 17 18 19 21 23 26 28 30 33 35 37 38 39 40 44 46 51 55 56 57 59 61 62 64 65 425)
The following functions are involved in the root cause
clr!CrstBase::Enter+111
The following modules are involved in the root cause
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll from Microsoft Corporation
The following vendors were identified for follow up based on root cause analysis
Microsoft Corporation
Please follow up with the vendors identified above
Error In dump_PID_19116.dmp GC is running in this process. The Thread that triggered the GC is 422 When a GC is running the .NET objects are not in a valid state and the reported analysis may be inaccurate. Also, the thread that triggered the Garbage collection may or may not be a problematic thread. Too many garbage collections in a process are bad for the performance of the application. Too many GC's in a process may indicate a memory pressure or symptoms of fragmenation. Review the blog ASP.NET Case Study: High CPU in GC - Large objects and high allocation rates for more details
Warning The following threads in dump_PID_19116.dmp are waiting for .net garbage collection to finish. Thread 422 triggered the garbage collection.
( 139 147 148 150 220 221 224 225 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 420 421 423 )
33.33% of threads blocked
When a GC is running the .NET objects are not in a valid state and the reported analysis may be inaccurate. Also, the thread that triggered the Garbage collection may or may not be a problematic thread. Too many garbage collections in a process are bad for the performance of the application. Too many GC's in a process may indicate a memory pressure or symptoms of fragmenation. Review the blog ASP.NET Case Study: High CPU in GC - Large objects and high allocation rates for more details
Warning The following threads in dump_PID_19116.dmp are waiting in a WaitOne
( 149 )
0.23% of threads blocked
Typically threads waiting in WaitMultiple are monitoring threads in a process and this may be ignored, however too many threads waiting in WaitOne\WaitMultiple may be a problem. Review the callstack of the threads waiting to see what they are waiting on
Warning The following threads in dump_PID_19116.dmp are waiting in System.Threading.Monitor.Wait
( 424 )
0.23% of threads blocked
Threads waiting in Monitor.Wait are actually waiting to re-acquire a lock which they released. The signal to reacquire the lock will be given by a call to Monitor.Pulse or Monitor.PulseAll or when the timeout is hit.
Look at the callstack of the thread to see which function is making a call to Monitor.Wait and then review code to find out the function which is supposed to call Monitor.Pulse or Monitor.PulseAll and see why that function is not getting called.
Information The following threads in dump_PID_19116.dmp are waiting in a WaitMultiple
( 267 268 )
0.47% of threads blocked
Information
The process w3wp.exe in dump_PID_19116.dmp is a 64 bit application. Some of the native (non-.NET) analysis, such as COM call information, may be missing. Further manual inspection of the dump may be required to extract such information.
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
dump_PID_19116.dmp
Top 5 threads by CPU time
.NET Analysis Report
Locked critical section report
Thread report
COM+ STA ThreadPool Report
Well-Known COM STA Threads Report
Report for dump_PID_19116.dmp
Report for dump_PID_19116.dmp
Type of Analysis Performed Hang Analysis
Machine Name CIHCISPWEBA266
Operating System Windows Server 2008 R2 Service Pack 1
Number Of Processors 64
Process ID 19116
Process Image c:\Windows\System32\inetsrv\w3wp.exe
System Up-Time 00:00:00
Process Up-Time 1 day(s) 15:53:27
Top 5 Threads by CPU time
Note - Times include both user mode and kernel mode for each thread Thread ID: 146 Total CPU Time: 01:27:47.388 Entry Point for Thread: ntdll!RtlUserThreadStart+1d
Thread ID: 161 Total CPU Time: 00:08:36.877 Entry Point for Thread: ntdll!RtlUserThreadStart+1d
Thread ID: 203 Total CPU Time: 00:05:52.047 Entry Point for Thread: ntdll!RtlUserThreadStart+1d
Thread ID: 199 Total CPU Time: 00:05:47.226 Entry Point for Thread: ntdll!RtlUserThreadStart+1d
Thread ID: 218 Total CPU Time: 00:05:44.340 Entry Point for Thread: ntdll!RtlUserThreadStart+1d
.NET Analysis Report
CLR Information
.NET Threads Summary
CLR Information
CLR version = 4.0.30319.34209
CLR Debugger Extension = C:\Program Files\DebugDiag\Exts\psscor4.dll
.NET Threads Summary
Failed to request ThreadStore
Locked critical section report
Critical Section 0x00436ca0
Lock State Uninitialized
Lock Count 33
Recursion Count 1
Entry Count 0
Contention Count 0
Spin Count 0
Owner Thread System ID 28096 (not present in dump)
Here is the Thread 422:
Thread 422 - System ID 30532
Entry point ntdll!RtlUserThreadStart+1d
Create time 8/12/2015 12:36:18 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.
.NET Call Stack
Function
System.GC._Collect(Int32, Int32)
System.GC._Collect(Int32, Int32)
Full Call Stack
Function Source
ntdll!ZwWaitForSingleObject+a
KERNELBASE!WaitForSingleObjectEx+79
clr!CLREventWaitHelper2+38
clr!CLREventWaitHelper+1f
clr!CLREventBase::WaitEx+70
clr!SVR::gc_heap::wait_for_gc_done+55
clr!SVR::GCHeap::GarbageCollectGeneration+f5
clr!SVR::GCHeap::GarbageCollect+88
clr!GCInterface::Collect+56
System_Drawing_ni+64745
System_Drawing_ni+65ef3
System_Drawing_ni+65d89
0x000007fe`968314e9
0x000007fe`96d9b2d7
0x000007fe`96d9af76
0x000007fe`96d9ad22
0x000007fe`96d9a78f
0x000007fe`968628d1
0x000007fe`9683edee
0x000007fe`9566aea4
0x000007fe`9683eadb
0x000007fe`96862813
0x000007fe`968624fc
0x000007fe`96862224
0x000007fe`96862026
0x000007fe`9650f4f9
0x000007fe`96861f35
0x000007fe`96861d56
0x000007fe`96861717
0x000007fe`9685e088
0x000007fe`9685df5c
0x000007fe`94f9d5dc
0x000007fe`94fa5667
mscorlib_ni+4a39a5
mscorlib_ni+4a3719
mscorlib_ni+4a36f7
mscorlib_ni+d6f63d
clr!CallDescrWorkerInternal+83
clr!CallDescrWorkerWithHandler+4a
clr!MethodDescCallSite::CallTargetWorker+251
clr!ThreadNative::KickOffThread_Worker+105
clr!ManagedThreadBase_DispatchInner+2d
clr!ManagedThreadBase_DispatchMiddle+6c
clr!ManagedThreadBase_DispatchOuter+75
clr!ManagedThreadBase_DispatchInCorrectAD+15
clr!Thread::DoADCallBack+2a1
clr!ManagedThreadBase_DispatchInner+69
clr!ManagedThreadBase_DispatchMiddle+6c
clr!ManagedThreadBase_DispatchOuter+75
clr!ManagedThreadBase_FullTransitionWithAD+2f
clr!ThreadNative::KickOffThread+d2
clr!Thread::intermediateThreadProc+7d
kernel32!BaseThreadInitThunk+d
ntdll!RtlUserThreadStart+1d
Need help to analyse as to what caused the crash.
Appreciate all the help; please let me know if I may add any further details to this.
Regards,
Madhyam
↧
IIS App Pool crashes with WAS; below is the initial section of Crash Hang Report generated
↧