<?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: Testing a newly build PC</title>
	<atom:link href="http://www.ghacks.net/2008/05/05/testing-a-newly-build-pc/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ghacks.net/2008/05/05/testing-a-newly-build-pc/</link>
	<description>A technology blog covering software, mobile phones, gadgets, security, the Internet and other relevant areas.</description>
	<lastBuildDate>Wed, 25 Nov 2009 09:27:25 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jojo</title>
		<link>http://www.ghacks.net/2008/05/05/testing-a-newly-build-pc/#comment-331267</link>
		<dc:creator>Jojo</dc:creator>
		<pubDate>Mon, 05 May 2008 20:37:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.ghacks.net/?p=4008#comment-331267</guid>
		<description>I had months of grief when I built my new Abit IP35 Pro system starting last Sept. I went through multiple RMA&#039;s.  Also ran Memtest but all checked out.

Finally, a ram stick went dead (Corsair HDX 6400).  I RMA&#039;d both sticks of memory since they are dual channel. THe ram sticks were replaced with v2.1 modules (used to have v1.2). Since replacing the ram, I have had no problems at all.

Moral: Clearly there was something wrong with the old ram.  Running memtest did not catch the problem. Only the failure of the memory lead me to a solution.</description>
		<content:encoded><![CDATA[<p>I had months of grief when I built my new Abit IP35 Pro system starting last Sept. I went through multiple RMA&#8217;s.  Also ran Memtest but all checked out.</p>
<p>Finally, a ram stick went dead (Corsair HDX 6400).  I RMA&#8217;d both sticks of memory since they are dual channel. THe ram sticks were replaced with v2.1 modules (used to have v1.2). Since replacing the ram, I have had no problems at all.</p>
<p>Moral: Clearly there was something wrong with the old ram.  Running memtest did not catch the problem. Only the failure of the memory lead me to a solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rarst</title>
		<link>http://www.ghacks.net/2008/05/05/testing-a-newly-build-pc/#comment-330843</link>
		<dc:creator>Rarst</dc:creator>
		<pubDate>Mon, 05 May 2008 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ghacks.net/?p=4008#comment-330843</guid>
		<description>&quot;Another good way of doing it is to recode a movie from DVD to AVI or AVI to DVD. It will stress the CPU, harddisks, and RAM in a real-world scenario.&quot;

Real world scenario is not a test. It isn&#039;t one and it can&#039;t replace one.

Purpose of dedicated testing software is to test 100% of component under heavy load to make sure it really works. No real world scenario uses 100% of anything in computer.</description>
		<content:encoded><![CDATA[<p>&#8220;Another good way of doing it is to recode a movie from DVD to AVI or AVI to DVD. It will stress the CPU, harddisks, and RAM in a real-world scenario.&#8221;</p>
<p>Real world scenario is not a test. It isn&#8217;t one and it can&#8217;t replace one.</p>
<p>Purpose of dedicated testing software is to test 100% of component under heavy load to make sure it really works. No real world scenario uses 100% of anything in computer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beecher Bowers</title>
		<link>http://www.ghacks.net/2008/05/05/testing-a-newly-build-pc/#comment-330707</link>
		<dc:creator>Beecher Bowers</dc:creator>
		<pubDate>Mon, 05 May 2008 15:51:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.ghacks.net/?p=4008#comment-330707</guid>
		<description>Another good way of doing it is to recode a movie from DVD to AVI or AVI to DVD.  It will stress the CPU, harddisks, and RAM in a real-world scenario.</description>
		<content:encoded><![CDATA[<p>Another good way of doing it is to recode a movie from DVD to AVI or AVI to DVD.  It will stress the CPU, harddisks, and RAM in a real-world scenario.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rarst</title>
		<link>http://www.ghacks.net/2008/05/05/testing-a-newly-build-pc/#comment-330079</link>
		<dc:creator>Rarst</dc:creator>
		<pubDate>Mon, 05 May 2008 11:01:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.ghacks.net/?p=4008#comment-330079</guid>
		<description>memtest86+ ( http://www.memtest.org/ ) is kinda fork of original memtest. We used both at work and my thoughts that + one handles more hardware (especially after recent updates to v2).

S&amp;M is very good CPU stress test, it doesn&#039;t really have home page (just google it) and is mostly known to russian-speaking crowd.

MHDD - great for drive surface testing (again - google it). Must be carfeully used it has functions to mess alot of drive stuff. :)

Passmark burning test (trial, shareware,  http://www.passmark.com/ ) is complete suit for stress testing. It tests pretty much any component separately or in any combination. Very slim (~10Mb unpacked), very nice video testing module, highly configurable... It&#039;s not freeware but it is pretty much ultimate program if you need to test numerous computers.

PS live cds are overkill for testing purposes. Pre-made ones are often outdated or illegal (or both) and making and managing your own is very time-consuming (been there). Since core programs either fit on flopppy or in the corner of flash drive - not worth effort.</description>
		<content:encoded><![CDATA[<p>memtest86+ ( <a href="http://www.memtest.org/" rel="nofollow">http://www.memtest.org/</a> ) is kinda fork of original memtest. We used both at work and my thoughts that + one handles more hardware (especially after recent updates to v2).</p>
<p>S&amp;M is very good CPU stress test, it doesn&#8217;t really have home page (just google it) and is mostly known to russian-speaking crowd.</p>
<p>MHDD &#8211; great for drive surface testing (again &#8211; google it). Must be carfeully used it has functions to mess alot of drive stuff. :)</p>
<p>Passmark burning test (trial, shareware,  <a href="http://www.passmark.com/" rel="nofollow">http://www.passmark.com/</a> ) is complete suit for stress testing. It tests pretty much any component separately or in any combination. Very slim (~10Mb unpacked), very nice video testing module, highly configurable&#8230; It&#8217;s not freeware but it is pretty much ultimate program if you need to test numerous computers.</p>
<p>PS live cds are overkill for testing purposes. Pre-made ones are often outdated or illegal (or both) and making and managing your own is very time-consuming (been there). Since core programs either fit on flopppy or in the corner of flash drive &#8211; not worth effort.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
