Succession of Patterns (Part 1)

Looking at pattern cooperation studies it is easy to see that some patterns precede others, for example, heap corruption might be blocked by a hard error or a message box and therefore block other threads, creating conditions for another pattern to appear, wait chains. Blocked threads may block other coupled processes creating inter-process wait chains. Successive patterns reach the climax at the end and the system is no longer able to generate any other patterns.

The goal here is to find patterns that most likely happen in succession and another pattern series that are less likely to effect other abnormal conditions. Such pattern sequences can help in troubleshooting and finding root causes.

- Dmitry Vostokov @

3 Responses to “Succession of Patterns (Part 1)”

  1. Crash Dump Analysis » Blog Archive » Succession of Patterns (Part 2) Says:

    […] I resume previously introduced memory analysis succession patterns post series. In this part I introduce a case study where Wait Chains (executive resources) and […]

  2. Crash Dump Analysis » Blog Archive » Old Mental Dumps from June 22nd Says:

    […] Succession of Patterns (Part 1) - More work needs to be done here. I recently revived this theme by writing the next post: […]

  3. Crash Dump Analysis » Blog Archive » Notation for Memory and Trace Analysis (Part 1) Says:

    […] part will introduce more categories and propose notational adornments for pattern succession, space differentiation and the inclusion of details in notational […]

Leave a Reply

You must be logged in to post a comment.