<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Getting the Crashing Stack From a Bugcheck</title><link>http://blogs.msdn.com/itgoestoeleven/archive/2008/05/07/getting-the-crashing-stack-from-a-bugcheck.aspx</link><description>Sorry for the long delay on posting - I have been slammed lately. I decided to write a post about debugging and take a short break from the bare metal stuff we have been discussing as of late. :) When a bugcheck occurs in Windows, the following basic</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Getting the Crashing Stack From a Bugcheck</title><link>http://blogs.msdn.com/itgoestoeleven/archive/2008/05/07/getting-the-crashing-stack-from-a-bugcheck.aspx#8466547</link><pubDate>Wed, 07 May 2008 21:43:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8466547</guid><dc:creator>Rhynogruv</dc:creator><description>&lt;p&gt;fyi - you can use dp(s) for pointer-size-agnostic memory dumping instead of dd(s)/dq(s)&lt;/p&gt;</description></item><item><title>re: Getting the Crashing Stack From a Bugcheck</title><link>http://blogs.msdn.com/itgoestoeleven/archive/2008/05/07/getting-the-crashing-stack-from-a-bugcheck.aspx#8538356</link><pubDate>Fri, 23 May 2008 13:07:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8538356</guid><dc:creator>nksingh</dc:creator><description>&lt;p&gt;This is really useful to know!&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;
&lt;p&gt;-(One of your next door neighbors).&lt;/p&gt;</description></item><item><title>re: Getting the Crashing Stack From a Bugcheck</title><link>http://blogs.msdn.com/itgoestoeleven/archive/2008/05/07/getting-the-crashing-stack-from-a-bugcheck.aspx#8968046</link><pubDate>Sun, 28 Sep 2008 17:54:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8968046</guid><dc:creator>Shabbir</dc:creator><description>&lt;p&gt;Why don't you provide a debugger extension to dump the saved stack.&lt;/p&gt;</description></item><item><title>re: Getting the Crashing Stack From a Bugcheck</title><link>http://blogs.msdn.com/itgoestoeleven/archive/2008/05/07/getting-the-crashing-stack-from-a-bugcheck.aspx#9914173</link><pubDate>Wed, 28 Oct 2009 16:41:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9914173</guid><dc:creator>rClark</dc:creator><description>&lt;p&gt;I am very happy to come upon this tidbit because I had determined that the bug check took up the stack. &amp;nbsp;However, when I do dqs (on Windows 7), no symbols are loaded. &amp;nbsp;Further examination of values on the stack display ????????`????????&lt;/p&gt;
&lt;p&gt;. &amp;nbsp;What to do? &amp;nbsp;Thanks&lt;/p&gt;</description></item></channel></rss>