<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Clear Indications of Bad Memory or Dimm Socket</title>
	<link>http://www.terminally-incoherent.com/blog/2007/07/19/clear-indications-of-bad-memory-or-dimm-socket/</link>
	<description>Utterly random, incoherent and disjointed rants and ramblings...</description>
	<pubDate>Tue, 02 Dec 2008 16:03:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: vacri</title>
		<link>http://www.terminally-incoherent.com/blog/2007/07/19/clear-indications-of-bad-memory-or-dimm-socket/#comment-5393</link>
		<pubDate>Mon, 23 Jul 2007 03:56:51 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2007/07/19/clear-indications-of-bad-memory-or-dimm-socket/#comment-5393</guid>
					<description>I have one on a bootcd somewhere that a sysadmin mate made, it's a linux memtest and does a decent job. Couldn't find that disk here at work, so I downloaded the &lt;a href="http://oca.microsoft.com/en/windiag.asp" rel="nofollow"&gt;Microsoft Online Crash Analysis memtest tool&lt;/a&gt; which seems to do the trick... and I just never bothered finding the other disk :)

 I don't know whether the MS one is an excellent tool or just an average one, but it seems to have worked fine for me so far.</description>
		<content:encoded><![CDATA[<p>I have one on a bootcd somewhere that a sysadmin mate made, it&#8217;s a linux memtest and does a decent job. Couldn&#8217;t find that disk here at work, so I downloaded the <a href="http://oca.microsoft.com/en/windiag.asp" rel="nofollow">Microsoft Online Crash Analysis memtest tool</a> which seems to do the trick&#8230; and I just never bothered finding the other disk <img src="http://www.terminally-incoherent.com/blog/wp-includes/images/smilies/icon_smile.gif" alt=")" class="wp-smiley" /> </p>
<p> I don&#8217;t know whether the MS one is an excellent tool or just an average one, but it seems to have worked fine for me so far.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Luke</title>
		<link>http://www.terminally-incoherent.com/blog/2007/07/19/clear-indications-of-bad-memory-or-dimm-socket/#comment-5342</link>
		<pubDate>Fri, 20 Jul 2007 14:54:31 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2007/07/19/clear-indications-of-bad-memory-or-dimm-socket/#comment-5342</guid>
					<description>So, can you recommend any good memory testing tools? I think I have one or two in my toolbox, but I'd love to hear what you use.</description>
		<content:encoded><![CDATA[<p>So, can you recommend any good memory testing tools? I think I have one or two in my toolbox, but I&#8217;d love to hear what you use.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: vacri</title>
		<link>http://www.terminally-incoherent.com/blog/2007/07/19/clear-indications-of-bad-memory-or-dimm-socket/#comment-5335</link>
		<pubDate>Fri, 20 Jul 2007 07:40:50 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2007/07/19/clear-indications-of-bad-memory-or-dimm-socket/#comment-5335</guid>
					<description>Another time to suspect bad memory is when the computer is suffering random syptoms with no rhyme or reason. I've had computers that didn't have a pattern to their failure - might not make it past POST one time, the next it might work fine, the next Windows might freeze, the next one application exits with an unusual error, etc - which came good by replacing the RAM.

Also try a memory tester - since I found out about memory test bootable CDs, I haven't had a stick of bad memory that wasn't detected by the CD. Saves having to pull a 'puter out of it's nest of cables and whatnot.</description>
		<content:encoded><![CDATA[<p>Another time to suspect bad memory is when the computer is suffering random syptoms with no rhyme or reason. I&#8217;ve had computers that didn&#8217;t have a pattern to their failure - might not make it past POST one time, the next it might work fine, the next Windows might freeze, the next one application exits with an unusual error, etc - which came good by replacing the RAM.</p>
<p>Also try a memory tester - since I found out about memory test bootable CDs, I haven&#8217;t had a stick of bad memory that wasn&#8217;t detected by the CD. Saves having to pull a &#8216;puter out of it&#8217;s nest of cables and whatnot.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Luke</title>
		<link>http://www.terminally-incoherent.com/blog/2007/07/19/clear-indications-of-bad-memory-or-dimm-socket/#comment-5330</link>
		<pubDate>Thu, 19 Jul 2007 22:15:10 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2007/07/19/clear-indications-of-bad-memory-or-dimm-socket/#comment-5330</guid>
					<description>&lt;strong&gt;Criag&lt;/strong&gt; - actually, I almost never throw out bad RAM. I put it in a box labeled BAD RAM. I always figure I will use it for something cool. Haven't figured what I'd do with them.

I also have around 20 bad laptop hard drives stacked up on the shelf behind me. Partly because I don't feel like figuring out the proper way of disposing them with regards to confidentiality policies and etc. Every once in a while I take one of them apart to get the cool magnets and the shiny platter out of it. I have several of them hinging off my lamp at work. :)

&lt;strong&gt;Starhawk&lt;/strong&gt; - You may or may not get memory read errorsIf the DIMM socket on the motherboard is going bad, you will likely see behavior like the above.</description>
		<content:encoded><![CDATA[<p><strong>Criag</strong> - actually, I almost never throw out bad RAM. I put it in a box labeled BAD RAM. I always figure I will use it for something cool. Haven&#8217;t figured what I&#8217;d do with them.</p>
<p>I also have around 20 bad laptop hard drives stacked up on the shelf behind me. Partly because I don&#8217;t feel like figuring out the proper way of disposing them with regards to confidentiality policies and etc. Every once in a while I take one of them apart to get the cool magnets and the shiny platter out of it. I have several of them hinging off my lamp at work. <img src="http://www.terminally-incoherent.com/blog/wp-includes/images/smilies/icon_smile.gif" alt=")" class="wp-smiley" /> </p>
<p><strong>Starhawk</strong> - You may or may not get memory read errorsIf the DIMM socket on the motherboard is going bad, you will likely see behavior like the above.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Starhawk</title>
		<link>http://www.terminally-incoherent.com/blog/2007/07/19/clear-indications-of-bad-memory-or-dimm-socket/#comment-5328</link>
		<pubDate>Thu, 19 Jul 2007 21:47:04 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2007/07/19/clear-indications-of-bad-memory-or-dimm-socket/#comment-5328</guid>
					<description>Oddly enough I've never had memory go out on any of my machines (crossing fingers now haha). hard drives yes memory no. But i would have expected memory read write errors so  thanks for the info gives me a clue to know what to look out for.</description>
		<content:encoded><![CDATA[<p>Oddly enough I&#8217;ve never had memory go out on any of my machines (crossing fingers now haha). hard drives yes memory no. But i would have expected memory read write errors so  thanks for the info gives me a clue to know what to look out for.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Craig Betts</title>
		<link>http://www.terminally-incoherent.com/blog/2007/07/19/clear-indications-of-bad-memory-or-dimm-socket/#comment-5326</link>
		<pubDate>Thu, 19 Jul 2007 21:14:37 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2007/07/19/clear-indications-of-bad-memory-or-dimm-socket/#comment-5326</guid>
					<description>Don't forget to destroy the bad memory after you confirm it's death.  Too many people will see it in the trash and take it back out, especially fellow admins.  I can't tell you the number of times I have had to troubleshoot the same issue only because some admin tried to help save money by picking through the trash.  Same goes with bad network patch cables . . . cut the ends off for added insurance that it will never reappear in your stockpile.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t forget to destroy the bad memory after you confirm it&#8217;s death.  Too many people will see it in the trash and take it back out, especially fellow admins.  I can&#8217;t tell you the number of times I have had to troubleshoot the same issue only because some admin tried to help save money by picking through the trash.  Same goes with bad network patch cables . . . cut the ends off for added insurance that it will never reappear in your stockpile.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.011 seconds -->
