Comments on: Crash Dump Analysis Patterns (Part 29)

By: Dmitry Vostokov

Dmitry Vostokov — Fri, 22 Mar 2013 13:20:46 +0000

High contention may also be visible from non-locked objects too:

0: kd> !locks -v
**** DUMP OF ALL RESOURCE OBJECTS ****

Resource @ nt!ExpFirmwareTableResource (0xfffff80001a315c0) Available

Resource @ nt!PsLoadedModuleResource (0xfffff80001a596a0) Available

Resource @ nt!MmSectionExtendResource (0xfffff80001a59440) Available

Resource @ nt!MmSectionExtendSetResource (0xfffff80001a594c0) Available
Contention Count = 68

Resource @ nt!SepRmDbLock (0xfffff80001a2e340) Available
Contention Count = 1710

Resource @ nt!SepRmDbLock (0xfffff80001a2e3a8) Available
Contention Count = 387

Resource @ nt!SepRmDbLock (0xfffff80001a2e410) Available
Contention Count = 256

Resource @ nt!SepRmDbLock (0xfffff80001a2e478) Available
Contention Count = 212

Resource @ nt!SepRmGlobalSaclLock (0xfffff80001a2e4e0) Available

Resource @ nt!SepLsaAuditQueueInfo (0xfffff80001a2e240) Available

Resource @ nt!SepLsaDeletedLogonQueueInfo (0xfffff80001a2e0e0) Available

Resource @ 0xfffffa804dc09920 Available

Resource @ nt!PnpRegistryDeviceResource (0xfffff80001a8f9e0) Available
Contention Count = 23562

Resource @ nt!PopPolicyLock (0xfffff80001a3b9e0) Available
Contention Count = 19

Resource @ 0xfffffa80b04008d0 Available

Resource @ 0xfffffa80b0400850 Available

Resource @ CI!g_StoreLock (0xfffff88000c05cc0) Available

Resource @ nt!CmpRegistryLock (0xfffff80001a10000) Available
Contention Count = 21297917

[…]

By: Crash Dump Analysis » Blog Archive » Contention Patterns

Crash Dump Analysis » Blog Archive » Contention Patterns — Tue, 21 Sep 2010 10:46:55 +0000

[…] High Contention (executive resources) […]

By: Crash Dump Analysis » Blog Archive » Insufficient memory, handle leak, process factory, high contention and busy system: pattern cooperation

Fri, 13 Aug 2010 19:10:40 +0000

[…] also see extremely high executive resource contention and various signs of a busy system like the fact that all processors are busy and very high number […]

By: Crash Dump Analysis » Blog Archive » Icons for Memory Dump Analysis Patterns (Part 49)

Fri, 18 Jun 2010 10:47:24 +0000

[…] we introduce an icon for High Contention (executive resources) […]

By: Crash Dump Analysis » Blog Archive » Succession of Patterns (Part 2)

Crash Dump Analysis » Blog Archive » Succession of Patterns (Part 2) — Thu, 03 Jun 2010 23:22:31 +0000

[…] see High Contention (executive resources) pattern. What we actually see is a runaway system […]

By: Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 29b)

Wed, 10 Sep 2008 13:46:36 +0000

[…] we discussed High Contention pattern in kernel mode involving executive resources. The same pattern can be observed in user […]

By: Dmitry Vostokov

Dmitry Vostokov — Wed, 09 Jul 2008 13:51:52 +0000

In user space we can see contention too:

0:070> !locks

CritSec +32b870 at 0032b870
WaiterWoken No
LockCount 0
RecursionCount 1
OwningThread 6f8c
EntryCount 0
ContentionCount 7f3c6
*** Locked

CritSec +3680a50 at 03680a50
WaiterWoken No
LockCount 0
RecursionCount 1
OwningThread 6f8c
EntryCount 0
ContentionCount 0
*** Locked

CritSec +261f86c at 0261f86c
WaiterWoken No
LockCount 0
RecursionCount 1
OwningThread 6f8c
EntryCount 0
ContentionCount 0
*** Locked

Scanned 3248 critical sections