Crash Dump Analysis Patterns (Part 62)

Software ageing can be the cause of the problem. Sometimes a look at the following WinDbg output can give irresistible temptation to suggest periodic reboots:

Debug session time: Wed April 28 15:36:52.330 2008 (GMT+0)
System Uptime: 124 days 6:27:16.658

The suggested pattern name is Overaged System.

- Dmitry Vostokov @ -

3 Responses to “Crash Dump Analysis Patterns (Part 62)”

  1. Chae Says:


    Following is what happened one of our overaged servers. Virtual Memory Address fragmentation seems inevitable even if we’re using LFH (Low Fragmentation Heap). This machine have had plenty of free physical memory but we had to restart the service.

    Usually large Uncommitted Ranges are bad but in this case 200 UCR caused 98% Virtual Address Fragmentation though which is a little bit strange.

    0:020> !heap -s
    Heap Flags Reserv Commit Virt Free List UCR Virt Lock Fast
    (k) (k) (k) (k) length blocks cont. heap
    006c0000 00001002 2565820 7232 658924 1302 160 200 0 44f3b4 LFH
    External fragmentation 18 % (160 free blocks)
    Virtual address fragmentation 98 % (200 uncommited ranges)

  2. Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 73) Says:

    […] to Overaged System sometimes we can see Young System pattern. This means that the system didn’t have time to […]

  3. Crash Dump Analysis » Blog Archive » Insufficient memory, handle leak, wait chain, deadlock, inconsistent dump and overaged system: pattern cooperation Says:

    […] We also notice the system uptime which might suggest that all these abnormalities had been gradually accumulated (see Overaged System): […]

Leave a Reply