<?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>How can I view the KMDF log for my driver?</title><link>http://blogs.msdn.com/doronh/archive/2006/07/31/684531.aspx</link><description>A lot of developers have a great experience with KMDF, but then they sometimes hit a wall. They add a chunk of code and the drivers start failing because something in the new code was not implemented correctly. The first question that comes to mind is</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Customizing the KMDF log for your driver</title><link>http://blogs.msdn.com/doronh/archive/2006/07/31/684531.aspx#685757</link><pubDate>Wed, 02 Aug 2006 01:56:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:685757</guid><dc:creator>A Hole In My Head</dc:creator><description>Yesterday&lt;br&gt;I talked about the KMDF log. &amp;nbsp;The KMDF log is a great tool to debug why a DDI call has failed...</description></item></channel></rss>