https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/ Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics Tue, 05 May 2026 11:14:25 +0000 http://wordpress.org/?v=2.3.3 https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-156718 Crash Dump Analysis » Blog Archive » IRP distribution anomaly, inconsistent dump, execution residue, hardware activity, coincidental symbolic information, not my version, virtualized system: pattern cooperation Mon, 07 Jun 2010 23:50:35 +0000 https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-156718 [...] at DriverA timestamp we notice it is much older than expected and Google search points to similar cases (but not for virtualized systems) where it was [...] […] at DriverA timestamp we notice it is much older than expected and Google search points to similar cases (but not for virtualized systems) where it was […]

]]> https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-104815 Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 65b) Mon, 16 Nov 2009 16:33:26 +0000 https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-104815 [...] is a hardware counterpart of Not My Version pattern. Some problems manifest themselves on different hardware not used at the time of the [...] […] is a hardware counterpart of Not My Version pattern. Some problems manifest themselves on different hardware not used at the time of the […]

]]> https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-99962 Crash Dump Analysis » Blog Archive » Truncated dump, spiking thread, not my version and hooked functions: pattern cooperation Tue, 20 Oct 2009 22:59:39 +0000 https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-99962 [...] from Google search we can find that there is newer version available (variant of Not My Version pattern) and even some indication on various forums that the older ones had problems with CPU resource [...] […] from Google search we can find that there is newer version available (variant of Not My Version pattern) and even some indication on various forums that the older ones had problems with CPU resource […]

]]> https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-99872 Crash Dump Analysis » Blog Archive » Invalid handle, stack trace collection, multiple exceptions, invalid pointer, data alignment on page boundary, dynamic memory corruption and not my version: pattern cooperation Tue, 20 Oct 2009 13:05:38 +0000 https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-99872 [...] runtime unless we enable Application Verifier. Looking at DllB version data we see that it is the old component that needs to be [...] […] runtime unless we enable Application Verifier. Looking at DllB version data we see that it is the old component that needs to be […]

]]> https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-98723 Crash Dump Analysis » Blog Archive » Statement current, coupled processes, wait chain, spiking thread, hidden exception, and not my version: memory dump and trace analysis pattern cooperation Mon, 12 Oct 2009 19:08:34 +0000 https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-98723 [...] from the initial coupled pair where nothing was found before. The timestamp of that component was old enough (lmv command) to warrant more attention to it and contact its [...] […] from the initial coupled pair where nothing was found before. The timestamp of that component was old enough (lmv command) to warrant more attention to it and contact its […]

]]> https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-88185 Crash Dump Analysis » Blog Archive » Stack trace collection, suspended threads, not my version, special process, main thread and blocked LPC chain threads: pattern cooperation Tue, 11 Aug 2009 15:04:46 +0000 https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-88185 [...] check its data using lmv WinDbg command and find out that it is old and needs to be updated. But we don’t stop our investigation here. The fact that ServiceA [...] […] check its data using lmv WinDbg command and find out that it is old and needs to be updated. But we don’t stop our investigation here. The fact that ServiceA […]

]]> https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-71974 Crash Dump Analysis » Blog Archive » Blocked thread, historical information, execution residue, hidden exception, dynamic memory corruption, incorrect stack trace and not my version: pattern cooperation Thu, 23 Apr 2009 21:00:09 +0000 https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-71974 [...] the hang happens after printing we detect old printer drivers in the module list (certainly not my version of the environment used for application [...] […] the hang happens after printing we detect old printer drivers in the module list (certainly not my version of the environment used for application […]

]]> https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-46190 Crash Dump Analysis » Blog Archive » Early crash dump, blocked thread, not my version and lost opportunity: pattern cooperation Thu, 09 Oct 2008 15:45:44 +0000 https://www.dumpanalysis.org/blog/index.php/2008/06/19/crash-dump-analysis-patterns-part-65/#comment-46190 [...] NotMyDLL module time stamp we identified Not My Version pattern because we expected much later [...] […] NotMyDLL module time stamp we identified Not My Version pattern because we expected much later […]

]]>