<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Scottie’s Tech.Info &#187; RAM</title>
	<atom:link href="http://scottiestech.info/tag/ram/feed/" rel="self" type="application/rss+xml" />
	<link>http://scottiestech.info</link>
	<description>A chimpanzee and two trainees could run her!</description>
	<lastBuildDate>Tue, 24 Jan 2012 18:03:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Bad RAM: Recognizing Defective Memory Problems in Your Computer</title>
		<link>http://scottiestech.info/2010/04/25/bad-ram-recognizing-defective-memory-problems-in-your-computer/</link>
		<comments>http://scottiestech.info/2010/04/25/bad-ram-recognizing-defective-memory-problems-in-your-computer/#comments</comments>
		<pubDate>Sun, 25 Apr 2010 14:41:15 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[Do-It-Yourself]]></category>
		<category><![CDATA[memory]]></category>
		<category><![CDATA[RAM]]></category>
		<category><![CDATA[repair]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=387</guid>
		<description><![CDATA[A lot of people think that defective RAM modules are easy to detect. They think that if you get a blue screen of death, the error message will reveal that the memory is bad, and that's that. Problem is, it's nowhere near that simple. There are two steps to diagnosing bad RAM. The first is that you are able to recognize the possible symptoms of bad memory, and the second is actually using a tool to confirm that your theory is correct. Then you just replace the bad module, and off you go. A defective memory stick can cause a LOT of different problems, some of which might surprise you. It may seem that your hard drive is corrupted or defective, when in fact it's the RAM that's bad! It can all get very confusing. And so, here I shall endeavor to describe what to look out for with your RAM, and what to do about it.]]></description>
		<wfw:commentRss>http://scottiestech.info/2010/04/25/bad-ram-recognizing-defective-memory-problems-in-your-computer/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The 3GB Barrier: Why you want a 64-bit OS</title>
		<link>http://scottiestech.info/2009/05/02/the-3gb-barrier-why-you-want-a-64-bit-os/</link>
		<comments>http://scottiestech.info/2009/05/02/the-3gb-barrier-why-you-want-a-64-bit-os/#comments</comments>
		<pubDate>Sat, 02 May 2009 13:12:14 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[OSX]]></category>
		<category><![CDATA[processor]]></category>
		<category><![CDATA[RAM]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[x64]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=166</guid>
		<description><![CDATA[I'm sure you've all heard some hype about 64-bit this and 64-bit that. The thing I read the most is that a 64-bit operating system or piece of software is automagically twice as fast as a 32-bit one. Not so. In any case, most people today are using a 32-bit operating system, but a surprising number have already switched to a 64-bit OS. Or in some cases, a quasi-64-bit OS... There is one true reason though why you will actually want to switch to a 64-bit OS in the near future: the infamous 3GB barrier. Just what the heck is this mystical barrier, and why should you care?]]></description>
		<wfw:commentRss>http://scottiestech.info/2009/05/02/the-3gb-barrier-why-you-want-a-64-bit-os/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

