<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Major chkdsk Bug in Windows 7 RTM</title>
	<atom:link href="http://www.bluescreenofdeath.org/?feed=rss2&#038;p=94" rel="self" type="application/rss+xml" />
	<link>http://www.bluescreenofdeath.org/?p=94</link>
	<description>Bloggings of a Technology Enthusiast</description>
	<lastBuildDate>Thu, 12 Nov 2009 16:14:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Avedis</title>
		<link>http://www.bluescreenofdeath.org/?p=94&#038;cpage=1#comment-200</link>
		<dc:creator>Avedis</dc:creator>
		<pubDate>Thu, 12 Nov 2009 16:14:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluescreenofdeath.org/?p=94#comment-200</guid>
		<description>I had the same problem when i had to upgrade from vista to windows 7 home, igot the blue screen of death  shortly after installation.Is there some kind of fix or patch,PLEASE!!!</description>
		<content:encoded><![CDATA[<p>I had the same problem when i had to upgrade from vista to windows 7 home, igot the blue screen of death  shortly after installation.Is there some kind of fix or patch,PLEASE!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://www.bluescreenofdeath.org/?p=94&#038;cpage=1#comment-177</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Sat, 08 Aug 2009 09:55:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluescreenofdeath.org/?p=94#comment-177</guid>
		<description>If MS would actually let some competent programmers LOOK AT &quot;their&quot; code, they could have it fixed in hours.  That&#039;s why the OS model is now the only way to develop software and operating systems.  &quot;Security&quot; throuh obscurity doesn&#039;t work any more.</description>
		<content:encoded><![CDATA[<p>If MS would actually let some competent programmers LOOK AT &#8220;their&#8221; code, they could have it fixed in hours.  That&#8217;s why the OS model is now the only way to develop software and operating systems.  &#8220;Security&#8221; throuh obscurity doesn&#8217;t work any more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Price</title>
		<link>http://www.bluescreenofdeath.org/?p=94&#038;cpage=1#comment-172</link>
		<dc:creator>Ryan Price</dc:creator>
		<pubDate>Fri, 07 Aug 2009 18:45:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluescreenofdeath.org/?p=94#comment-172</guid>
		<description>The manufacturers one still do it and this is on an Intel chipset with 9.0 drivers installed..so this isnt a bug in the driver..its the actual process.</description>
		<content:encoded><![CDATA[<p>The manufacturers one still do it and this is on an Intel chipset with 9.0 drivers installed..so this isnt a bug in the driver..its the actual process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Owen</title>
		<link>http://www.bluescreenofdeath.org/?p=94&#038;cpage=1#comment-171</link>
		<dc:creator>Owen</dc:creator>
		<pubDate>Fri, 07 Aug 2009 16:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluescreenofdeath.org/?p=94#comment-171</guid>
		<description>&lt;a href=&quot;#comment-137&quot; rel=&quot;nofollow&quot;&gt;@Ryan Price &lt;/a&gt; 
&lt;i&gt;If its a controller driver how do you explain that it happens across , Intel, Nvidia, and any other maker’s.&lt;/i&gt;
Well, the previous post implies that it&#039;s when you use the generic (ie. MS supplied) chipset driver instead of the manufacturer supplied/specific ones. So the bug is in that.</description>
		<content:encoded><![CDATA[<p><a href="#comment-137" rel="nofollow">@Ryan Price </a><br />
<i>If its a controller driver how do you explain that it happens across , Intel, Nvidia, and any other maker’s.</i><br />
Well, the previous post implies that it&#8217;s when you use the generic (ie. MS supplied) chipset driver instead of the manufacturer supplied/specific ones. So the bug is in that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emanem</title>
		<link>http://www.bluescreenofdeath.org/?p=94&#038;cpage=1#comment-169</link>
		<dc:creator>Emanem</dc:creator>
		<pubDate>Fri, 07 Aug 2009 16:14:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluescreenofdeath.org/?p=94#comment-169</guid>
		<description>Lol, but W7 seems a bad KDE/Gnome desktop...Really was expecting for something better...</description>
		<content:encoded><![CDATA[<p>Lol, but W7 seems a bad KDE/Gnome desktop&#8230;Really was expecting for something better&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tightsystem.com &#187; Windows 7 bug likely not a &#8217;showstopper&#8217;</title>
		<link>http://www.bluescreenofdeath.org/?p=94&#038;cpage=1#comment-168</link>
		<dc:creator>tightsystem.com &#187; Windows 7 bug likely not a &#8217;showstopper&#8217;</dc:creator>
		<pubDate>Fri, 07 Aug 2009 03:47:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluescreenofdeath.org/?p=94#comment-168</guid>
		<description>[...] issue, noted on several enthusiast sites this week, involves a fairly arcane process used to check for problems in a particular disk. Under certain [...]</description>
		<content:encoded><![CDATA[<p>[...] issue, noted on several enthusiast sites this week, involves a fairly arcane process used to check for problems in a particular disk. Under certain [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dhisnotnull</title>
		<link>http://www.bluescreenofdeath.org/?p=94&#038;cpage=1#comment-167</link>
		<dc:creator>dhisnotnull</dc:creator>
		<pubDate>Fri, 07 Aug 2009 01:35:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluescreenofdeath.org/?p=94#comment-167</guid>
		<description>I tried in a 2Gb of ram Celeron, memory usage elevated to about 1.5Gb but the system did not crash nor slowed down think this is by design as steven stated
&lt;strong&gt;&lt;a href=&quot;http://www.chris123nt.com/2009/08/03/critical-bug-in-windows-7-rtm#comment-11469&quot; rel=&quot;nofollow&quot;&gt;Steven Sinofsky&lt;/a&gt; :&lt;/strong&gt;
... but that was resolved by design since we actually did design it to use more memory.  But the design was to use more memory on purpose to speed things up, but never unbounded — we requset the available memory and operate within that leaving at least 50M of physical memory.  Our assumption was that using /r means your disk is such that you would prefer to get the repair done and over with rather than keep working.
&lt;/blockquote&gt;
This is not a critical bug, since its seldomly use and /r mostly used on old hard disk that just about to kill itself</description>
		<content:encoded><![CDATA[<p>I tried in a 2Gb of ram Celeron, memory usage elevated to about 1.5Gb but the system did not crash nor slowed down think this is by design as steven stated<br />
<strong><a href="http://www.chris123nt.com/2009/08/03/critical-bug-in-windows-7-rtm#comment-11469" rel="nofollow">Steven Sinofsky</a> :</strong><br />
&#8230; but that was resolved by design since we actually did design it to use more memory.  But the design was to use more memory on purpose to speed things up, but never unbounded — we requset the available memory and operate within that leaving at least 50M of physical memory.  Our assumption was that using /r means your disk is such that you would prefer to get the repair done and over with rather than keep working.</p>
<p>This is not a critical bug, since its seldomly use and /r mostly used on old hard disk that just about to kill itself</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thranx</title>
		<link>http://www.bluescreenofdeath.org/?p=94&#038;cpage=1#comment-165</link>
		<dc:creator>Thranx</dc:creator>
		<pubDate>Thu, 06 Aug 2009 20:23:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluescreenofdeath.org/?p=94#comment-165</guid>
		<description>&lt;a href=&quot;#comment-137&quot; rel=&quot;nofollow&quot;&gt;@Ryan Price  &lt;/a&gt; 

It happens cross platform because it&#039;s the generic device driver.  Unless you manually install the driver for the specific controller on each system, it&#039;ll use the generic MS one.  If the problem&#039;s in the driver, then you&#039;ll see it regardless of make/model without installing the proper driver.</description>
		<content:encoded><![CDATA[<p><a href="#comment-137" rel="nofollow">@Ryan Price  </a> </p>
<p>It happens cross platform because it&#8217;s the generic device driver.  Unless you manually install the driver for the specific controller on each system, it&#8217;ll use the generic MS one.  If the problem&#8217;s in the driver, then you&#8217;ll see it regardless of make/model without installing the proper driver.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shiro</title>
		<link>http://www.bluescreenofdeath.org/?p=94&#038;cpage=1#comment-164</link>
		<dc:creator>Shiro</dc:creator>
		<pubDate>Thu, 06 Aug 2009 19:39:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluescreenofdeath.org/?p=94#comment-164</guid>
		<description>Windows 7 RC here. 1,5Gb of RAM. Checkin error with &#039;/r&#039; option through explorer. It takes 800 Mb in a few seconds. I cancel the operation and qafter 30 seconds it free the 800Mb without problem.</description>
		<content:encoded><![CDATA[<p>Windows 7 RC here. 1,5Gb of RAM. Checkin error with &#8216;/r&#8217; option through explorer. It takes 800 Mb in a few seconds. I cancel the operation and qafter 30 seconds it free the 800Mb without problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Microsoft Shoots Down &#34;Critical&#34; Windows 7 Bug &#124; DUOWAN</title>
		<link>http://www.bluescreenofdeath.org/?p=94&#038;cpage=1#comment-155</link>
		<dc:creator>Microsoft Shoots Down &#34;Critical&#34; Windows 7 Bug &#124; DUOWAN</dc:creator>
		<pubDate>Thu, 06 Aug 2009 04:49:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluescreenofdeath.org/?p=94#comment-155</guid>
		<description>[...] blog, noting a report from the &#8220;bluescreenofdeath.org&#8221; blog, claimed that running a chkdsk command with the [...]</description>
		<content:encoded><![CDATA[<p>[...] blog, noting a report from the &#8220;bluescreenofdeath.org&#8221; blog, claimed that running a chkdsk command with the [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
