<?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>Hardware bitflipping</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/04/08/hardware-bitflipping.aspx</link><description>Hello all; my name is Scott Olson and I work as an Escalation Engineer for Microsoft Global Escalation Services team in Platforms support, and I wanted to share an interesting problem that came up recently. A co-worker was running Windows Vista Ultimate</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Hardware bitflipping</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/04/08/hardware-bitflipping.aspx#8381855</link><pubDate>Fri, 11 Apr 2008 23:00:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8381855</guid><dc:creator>Ralph Gifford</dc:creator><description>&lt;p&gt;Very interesting. &amp;nbsp;I have issue with my wifes PC and would want to try this fix on that.&lt;/p&gt;</description></item><item><title>re: Hardware bitflipping</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/04/08/hardware-bitflipping.aspx#8392126</link><pubDate>Mon, 14 Apr 2008 14:31:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8392126</guid><dc:creator>Bender</dc:creator><description>&lt;p&gt;Very nice article. Good thing that hardware issues can also be diagnosed with a memory test like the Vista integrated or memtest86+. Good news for the non-kernel debugger enlightened users like me :)&lt;/p&gt;</description></item><item><title>NTDebugging Puzzler 0x00000004: This didn’t puzzle the Debug Ninja, how about you?</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/04/08/hardware-bitflipping.aspx#8450564</link><pubDate>Fri, 02 May 2008 16:49:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8450564</guid><dc:creator>Microsoft Advanced Windows Debugging and Troubleshooting</dc:creator><description>&lt;p&gt;Hello NTDebuggers, we have been very impressed with the responses we’ve gotten to our previous puzzlers&lt;/p&gt;
</description></item><item><title>2009 Q1 link clearance: Microsoft blogger edition</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/04/08/hardware-bitflipping.aspx#9523315</link><pubDate>Tue, 31 Mar 2009 19:56:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9523315</guid><dc:creator>The Old New Thing</dc:creator><description>&lt;p&gt;From elsewhere in the collective.&lt;/p&gt;
</description></item><item><title>re: Hardware bitflipping</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/04/08/hardware-bitflipping.aspx#9525157</link><pubDate>Wed, 01 Apr 2009 07:03:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9525157</guid><dc:creator>Igor Levicki</dc:creator><description>&lt;p&gt;Strange way of approaching the troubleshooting.&lt;/p&gt;
&lt;p&gt;I would have booted into DOS and used goldmen or memtest86+ to check for memory errors -- that would catch the bit without any of the above brainstorming over a crash dump being required.&lt;/p&gt;
&lt;p&gt;Furthermore, you usually do not add RAM sticks with different timings, bank sizes, or voltage requirements to the system -- if you can't find the same RAM you pull the old one out.&lt;/p&gt;
&lt;p&gt;2.1V is probably not neccessary unless it is a higher clocked / high performance DDR2 memory, better check the specification, RAM can overheat and the BIOS can enable thermal throttling so the system might run slower with more voltage than neccessary.&lt;/p&gt;
&lt;p&gt;Finally, if they installed 4 RAM sticks instead of 2 then the &amp;quot;solution&amp;quot; of rising voltage might have to do with RAM but with crappy mainboard and northbridge which aren't able to supply enough &amp;quot;juice&amp;quot; to drive all 4 memory modules.&lt;/p&gt;
&lt;p&gt;In any case, I would try running goldmem and memtest86+ at 1.9v, 1.95v, etc until I find the minimum voltage at which the system is stable.&lt;/p&gt;</description></item><item><title>re: Hardware bitflipping</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/04/08/hardware-bitflipping.aspx#9528955</link><pubDate>Thu, 02 Apr 2009 13:51:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9528955</guid><dc:creator>wolf550e</dc:creator><description>&lt;P&gt;memtest86 should be able to diagnose such a problem, without digging into windows.&lt;/P&gt;</description></item><item><title>re: Hardware bitflipping</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/04/08/hardware-bitflipping.aspx#9546407</link><pubDate>Sun, 12 Apr 2009 18:50:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9546407</guid><dc:creator>David Soussan</dc:creator><description>&lt;p&gt;This is exactly the kind of walk-through that teaches tips and techniques everyone computer literate and in charge of designing, building, and supporting systems should add to their tool belt. I want to say that this hasn't helped me resolve a problem right now, but adding skills is always a good thing. But there isn't a 'not yet' button.&lt;/p&gt;
&lt;p&gt;When I press the shiny green button for &amp;quot;Did this blog post help you resolve a problem?&amp;quot;, I get an error:&lt;/p&gt;
&lt;p&gt;500 - Internal server error.&lt;/p&gt;
&lt;p&gt;There is a problem with the resource you are looking for, and it cannot be displayed.&lt;/p&gt;
&lt;p&gt;Keep these articles coming!&lt;/p&gt;
&lt;p&gt;And yes, memory testing programs can and do find problems. But I've seen strange errors that testing programs don't find but operating systems, applications, and games do find. Ask me about the 6502 add bug sometime... (showing my gray hair)&lt;/p&gt;</description></item></channel></rss>