<?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: Analyze and Repair PC Hardware</title> <atom:link href="http://www.ghacks.net/2008/03/25/analyze-and-repair-pc-hardware/feed/" rel="self" type="application/rss+xml" /><link>http://www.ghacks.net/2008/03/25/analyze-and-repair-pc-hardware/</link> <description>A technology news blog covering software, mobile phones, gadgets, security, the Internet and other relevant areas.</description> <lastBuildDate>Sat, 11 Feb 2012 22:58:45 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: z0iid</title><link>http://www.ghacks.net/2008/03/25/analyze-and-repair-pc-hardware/comment-page-1/#comment-283879</link> <dc:creator>z0iid</dc:creator> <pubDate>Tue, 25 Mar 2008 22:23:51 +0000</pubDate> <guid
isPermaLink="false">http://www.ghacks.net/2008/03/25/analyze-and-repair-pc-hardware/#comment-283879</guid> <description>If you can boot into the windows recovery console, you can run &quot;chkdsk /r&quot;.  You can run ntfsdos from the Ultimate Boot CD, but you don&#039;t get the chkdsk options.  You can just run it, but not in repair mode.
First attack for blue screens?  F8 and select &quot;last known good configuration&quot;.  Occasionally, this does actually work.  If that doesn&#039;t, I do an harddrive scan (using the Ultimate Boot CD) based on the manufacturer of the HD.  This may take some time, but sometimes you will find that the hard drive is &quot;failing&quot; and should be replaced.
At this point, you can slave up the drive and backup important files.  If the drive still isn&#039;t &quot;visible&quot; as a drive letter when slaved up, but shows up in mass storage devices - then you may need to use recovery software.  My software of choice is EasyRecovery Professional.
As Martin says, occasionally you run up against bad memory or a processor, but the majority of the time (and I do this for a large organization) it has something to do with the harddrive or filesystem.</description> <content:encoded><![CDATA[<p>If you can boot into the windows recovery console, you can run &#8220;chkdsk /r&#8221;.  You can run ntfsdos from the Ultimate Boot CD, but you don&#8217;t get the chkdsk options.  You can just run it, but not in repair mode.</p><p>First attack for blue screens?  F8 and select &#8220;last known good configuration&#8221;.  Occasionally, this does actually work.  If that doesn&#8217;t, I do an harddrive scan (using the Ultimate Boot CD) based on the manufacturer of the HD.  This may take some time, but sometimes you will find that the hard drive is &#8220;failing&#8221; and should be replaced.</p><p>At this point, you can slave up the drive and backup important files.  If the drive still isn&#8217;t &#8220;visible&#8221; as a drive letter when slaved up, but shows up in mass storage devices &#8211; then you may need to use recovery software.  My software of choice is EasyRecovery Professional.</p><p>As Martin says, occasionally you run up against bad memory or a processor, but the majority of the time (and I do this for a large organization) it has something to do with the harddrive or filesystem.</p> ]]></content:encoded> </item> <item><title>By: Kirk</title><link>http://www.ghacks.net/2008/03/25/analyze-and-repair-pc-hardware/comment-page-1/#comment-283826</link> <dc:creator>Kirk</dc:creator> <pubDate>Tue, 25 Mar 2008 19:32:52 +0000</pubDate> <guid
isPermaLink="false">http://www.ghacks.net/2008/03/25/analyze-and-repair-pc-hardware/#comment-283826</guid> <description>sometimes , mostly motherboard is the damage when there&#039;s nothing u can see in the monitor.</description> <content:encoded><![CDATA[<p>sometimes , mostly motherboard is the damage when there&#8217;s nothing u can see in the monitor.</p> ]]></content:encoded> </item> <item><title>By: colin_w</title><link>http://www.ghacks.net/2008/03/25/analyze-and-repair-pc-hardware/comment-page-1/#comment-283757</link> <dc:creator>colin_w</dc:creator> <pubDate>Tue, 25 Mar 2008 16:39:01 +0000</pubDate> <guid
isPermaLink="false">http://www.ghacks.net/2008/03/25/analyze-and-repair-pc-hardware/#comment-283757</guid> <description>Good example of troubleshooting BSOD. The first Podnutz podcast also deals with BSOD problems at boot up. Podnutz is a relatively new podcast on DIY computer repair. Well worth listening to:
http://podnutz.com/</description> <content:encoded><![CDATA[<p>Good example of troubleshooting BSOD. The first Podnutz podcast also deals with BSOD problems at boot up. Podnutz is a relatively new podcast on DIY computer repair. Well worth listening to:</p><p>http://podnutz.com/</p> ]]></content:encoded> </item> </channel> </rss>
