Comments on: Registry Corruption: A Case Study https://www.dumpanalysis.org/blog/index.php/2009/08/17/registry-corruption-a-case-study/ Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics Tue, 05 May 2026 15:38:00 +0000 http://wordpress.org/?v=2.3.3 By: Crash Dump Analysis » Blog Archive » Free Stack Traces https://www.dumpanalysis.org/blog/index.php/2009/08/17/registry-corruption-a-case-study/#comment-89473 Crash Dump Analysis » Blog Archive » Free Stack Traces Tue, 18 Aug 2009 15:05:38 +0000 https://www.dumpanalysis.org/blog/index.php/2009/08/17/registry-corruption-a-case-study/#comment-89473 [...] By analogy with the free verse and the anthropologist John Tedlock’s written narratives of Native Americans Zuni where different font size was used for different levels I tried today with a raw stack trace from the previous case study of registry corruption: [...] […] By analogy with the free verse and the anthropologist John Tedlock’s written narratives of Native Americans Zuni where different font size was used for different levels I tried today with a raw stack trace from the previous case study of registry corruption: […]

]]> By: Dmitry Vostokov https://www.dumpanalysis.org/blog/index.php/2009/08/17/registry-corruption-a-case-study/#comment-89462 Dmitry Vostokov Tue, 18 Aug 2009 14:47:47 +0000 https://www.dumpanalysis.org/blog/index.php/2009/08/17/registry-corruption-a-case-study/#comment-89462 I just dumped any parameter accessible from kernel space in search of ASCII or UNICODE values is any :-) I just dumped any parameter accessible from kernel space in search of ASCII or UNICODE values is any :-)

]]> By: Alex https://www.dumpanalysis.org/blog/index.php/2009/08/17/registry-corruption-a-case-study/#comment-89443 Alex Tue, 18 Aug 2009 12:56:00 +0000 https://www.dumpanalysis.org/blog/index.php/2009/08/17/registry-corruption-a-case-study/#comment-89443 How did you know to investigate "f690ace4" ? I would love to be able to debug like this. Seems like black magic but :( -Alex How did you know to investigate “f690ace4″ ?

I would love to be able to debug like this. Seems like black magic but :(

-Alex

]]>