<?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: System freezing up? Check your hardware</title>
	<atom:link href="http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/</link>
	<description>I write stuff. Mostly about Windows. Sometimes I get paid for it.</description>
	<lastBuildDate>Wed, 08 Feb 2012 01:55:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Louis Sabet</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-154569</link>
		<dc:creator>Louis Sabet</dc:creator>
		<pubDate>Mon, 19 Feb 2007 10:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-154569</guid>
		<description>I feel I should add that it&#039;s possible some of the freezes people are experiencing (and there seem to be quite a lot of people, myself included who are experiencing them) could be down to early/flaky drivers.
I&#039;ve checked everything in my machine. New HD, swapped DIMMS, replaced GPU, disabled onboard sound, removed unnecessary cards, USB devices, everything, and still I get random freezes.
XP never once failed for me, so I&#039;ll be using that for a while until I get to the bottom of it.
My current theory is motherboard drivers, since they&#039;re the only thing I&#039;ve not been able to try/replace (none available from what I can tell).
Theoretically a driver failure would result in a BSOD (as I understand it), as that&#039;s what happened with XP, which at least allowed you to diagnose the problem, but all I get with Vista is freezes, and a corresponding big fat nothing in the event log.
It&#039;s true that this type of freeze is highly likely to be hardware related, but given that the drivers are fairly closely involved in the kernel&#039;s ability to do anything useful with the system, if they keel over in an unexpected way, it&#039;s possible the kernel itself might keel over in an unexpected way too.
Feel free to blast my theories back down to earth :-)</description>
		<content:encoded><![CDATA[<p>I feel I should add that it&#8217;s possible some of the freezes people are experiencing (and there seem to be quite a lot of people, myself included who are experiencing them) could be down to early/flaky drivers.</p>
<p>I&#8217;ve checked everything in my machine. New HD, swapped DIMMS, replaced GPU, disabled onboard sound, removed unnecessary cards, USB devices, everything, and still I get random freezes.</p>
<p>XP never once failed for me, so I&#8217;ll be using that for a while until I get to the bottom of it.</p>
<p>My current theory is motherboard drivers, since they&#8217;re the only thing I&#8217;ve not been able to try/replace (none available from what I can tell).</p>
<p>Theoretically a driver failure would result in a BSOD (as I understand it), as that&#8217;s what happened with XP, which at least allowed you to diagnose the problem, but all I get with Vista is freezes, and a corresponding big fat nothing in the event log. </p>
<p>It&#8217;s true that this type of freeze is highly likely to be hardware related, but given that the drivers are fairly closely involved in the kernel&#8217;s ability to do anything useful with the system, if they keel over in an unexpected way, it&#8217;s possible the kernel itself might keel over in an unexpected way too.</p>
<p>Feel free to blast my theories back down to earth <img src='http://www.edbott.com/weblog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jackie Gleason</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-154564</link>
		<dc:creator>Jackie Gleason</dc:creator>
		<pubDate>Sat, 17 Feb 2007 19:08:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-154564</guid>
		<description>I might have to argue this theory as I have 2 computers both running Vista and both seem to be freezing up due to Pandora. Not sure what the issue is but it seems to be a software. It freezes up in both Mozilla and Firefox and the machines are a compaq, and a custom. At first I thought it had something to do with my GeForce MX 4000 card but now I do not think so. Sucks cause I LOVE PANDORA!</description>
		<content:encoded><![CDATA[<p>I might have to argue this theory as I have 2 computers both running Vista and both seem to be freezing up due to Pandora. Not sure what the issue is but it seems to be a software. It freezes up in both Mozilla and Firefox and the machines are a compaq, and a custom. At first I thought it had something to do with my GeForce MX 4000 card but now I do not think so. Sucks cause I LOVE PANDORA!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ogden</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-154378</link>
		<dc:creator>Ogden</dc:creator>
		<pubDate>Mon, 29 Jan 2007 19:36:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-154378</guid>
		<description>I HAVE a similar problem ... XP just freezes ... I had two 512 MB RAM sticks installed .. microsoft&#039;s windiag utility didn&#039;t show any errors on any of my RAM sticks ....
Yesterday I removed one of the memory sticks and computer didn&#039;t freeze for the next 24 hours ... after that I replaced that stick with the other stick that I thought was faulty ... and still no freeze ups after 6 hours ..... My computer used to freeze in maximum 2.5 hours with the two sticks installed ....</description>
		<content:encoded><![CDATA[<p>I HAVE a similar problem &#8230; XP just freezes &#8230; I had two 512 MB RAM sticks installed .. microsoft&#8217;s windiag utility didn&#8217;t show any errors on any of my RAM sticks &#8230;.<br />
Yesterday I removed one of the memory sticks and computer didn&#8217;t freeze for the next 24 hours &#8230; after that I replaced that stick with the other stick that I thought was faulty &#8230; and still no freeze ups after 6 hours &#8230;.. My computer used to freeze in maximum 2.5 hours with the two sticks installed &#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-154084</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Thu, 28 Dec 2006 19:00:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-154084</guid>
		<description>I too had random windows XP freeze ups.  This article was an interesting read and when I pulled 1GB out and saw my PC run without lockups on the 1GB left I was impressed.  It is nice to see someone adding value to the net instead of regurgitating things elsewhere.
Thanks a lot.</description>
		<content:encoded><![CDATA[<p>I too had random windows XP freeze ups.  This article was an interesting read and when I pulled 1GB out and saw my PC run without lockups on the 1GB left I was impressed.  It is nice to see someone adding value to the net instead of regurgitating things elsewhere.</p>
<p>Thanks a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Minatel: ASP.NET, XML, CSS, Ajax Book Editor</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-138332</link>
		<dc:creator>Jim Minatel: ASP.NET, XML, CSS, Ajax Book Editor</dc:creator>
		<pubDate>Wed, 06 Sep 2006 00:17:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-138332</guid>
		<description>&lt;strong&gt;Bad RAM, Ed Bott, and Upgrading and Repairing PCs&lt;/strong&gt;
Allow me for a moment to digress from Wrox and get back to one of my old all-time favorite books from a former employer, Upgrading and Repairing PCs (pick any edition) by Scott Mueller. Super-Windows sleuth Ed Bott was commenting</description>
		<content:encoded><![CDATA[<p><strong>Bad RAM, Ed Bott, and Upgrading and Repairing PCs</strong></p>
<p>Allow me for a moment to digress from Wrox and get back to one of my old all-time favorite books from a former employer, Upgrading and Repairing PCs (pick any edition) by Scott Mueller. Super-Windows sleuth Ed Bott was commenting</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-137869</link>
		<dc:creator>Joseph</dc:creator>
		<pubDate>Mon, 04 Sep 2006 21:13:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-137869</guid>
		<description>Could it be that Windows Live One Care isn&#039;t necessarily the problem, but rather that program revealed a hardware problem (e.g. maybe a piece of bad RAM is only being hit when that program is running)?</description>
		<content:encoded><![CDATA[<p>Could it be that Windows Live One Care isn&#8217;t necessarily the problem, but rather that program revealed a hardware problem (e.g. maybe a piece of bad RAM is only being hit when that program is running)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Dimmick</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-137698</link>
		<dc:creator>Mike Dimmick</dc:creator>
		<pubDate>Mon, 04 Sep 2006 08:45:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-137698</guid>
		<description>MrG: if the hardware supports it, Windows Server 2003 Enterprise Edition supports hot-add memory (reference: http://www.microsoft.com/whdc/system/pnppwr/hotadd/hotaddmem.mspx). Virtually any server with SCSI, SATA or Serial Attached SCSI (SAS) drives supports hot-swap of disks, although of course if you&#039;re not to lose any data, the disks must be part of a fault-tolerant set.
If you&#039;re running Exchange Server, it&#039;s recommended to disable hot-add memory support. Exchange has some pretty serious memory management issues, so it&#039;s best to a) dedicate a server to running Exchange and b) follow all of Microsoft&#039;s memory configuration recommendations.</description>
		<content:encoded><![CDATA[<p>MrG: if the hardware supports it, Windows Server 2003 Enterprise Edition supports hot-add memory (reference: <a href="http://www.microsoft.com/whdc/system/pnppwr/hotadd/hotaddmem.mspx" rel="nofollow">http://www.microsoft.com/whdc/system/pnppwr/hotadd/hotaddmem.mspx</a>). Virtually any server with SCSI, SATA or Serial Attached SCSI (SAS) drives supports hot-swap of disks, although of course if you&#8217;re not to lose any data, the disks must be part of a fault-tolerant set.</p>
<p>If you&#8217;re running Exchange Server, it&#8217;s recommended to disable hot-add memory support. Exchange has some pretty serious memory management issues, so it&#8217;s best to a) dedicate a server to running Exchange and b) follow all of Microsoft&#8217;s memory configuration recommendations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MrG</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-137428</link>
		<dc:creator>MrG</dc:creator>
		<pubDate>Sun, 03 Sep 2006 11:11:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-137428</guid>
		<description>Wow! Bob. What is your secret?
 &#039;I have a Dell PowerEdge 600SC server running Windows Server 2003. It’s about 3-1/2 years old, and it has been running nonstop with virtually no problems for all that time. Over the years, I’ve added some big hard drives, and about a year and a half ago I replaced the original 2GB of RAM with 4GB so I could run multiple virtual machines on this box.&#039;
How did you replace the hard drives and RAM with out powering the system down? I think we should be told. This could revolutionise tech support : )</description>
		<content:encoded><![CDATA[<p>Wow! Bob. What is your secret?</p>
<p> &#8216;I have a Dell PowerEdge 600SC server running Windows Server 2003. It’s about 3-1/2 years old, and it has been running nonstop with virtually no problems for all that time. Over the years, I’ve added some big hard drives, and about a year and a half ago I replaced the original 2GB of RAM with 4GB so I could run multiple virtual machines on this box.&#8217;</p>
<p>How did you replace the hard drives and RAM with out powering the system down? I think we should be told. This could revolutionise tech support : )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claus Valca</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-137218</link>
		<dc:creator>Claus Valca</dc:creator>
		<pubDate>Sat, 02 Sep 2006 16:44:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-137218</guid>
		<description>Ed,
In a timely coincidence, my Dad brought me his XP system that was locking up bad just after he logged onto his desktop.
Through a lengthy troubleshooting session, I ended up hunting down the culprit as being Microsoft&#039;s Automatic Updates process (wuauclt.exe).  I also worked out a &quot;workaround&quot; for him.
Don&#039;t know if this will help you, but it was very enlightening.
I posted an extensive log of the troubleshooting steps on my blog:
&lt;a href=&quot;http://grandstreamdreams.blogspot.com/2006/09/thawing-xp-system.html&quot; rel=&quot;nofollow&quot;&gt;Thawing an XP System&lt;/a&gt;
--Claus</description>
		<content:encoded><![CDATA[<p>Ed,</p>
<p>In a timely coincidence, my Dad brought me his XP system that was locking up bad just after he logged onto his desktop.</p>
<p>Through a lengthy troubleshooting session, I ended up hunting down the culprit as being Microsoft&#8217;s Automatic Updates process (wuauclt.exe).  I also worked out a &#8220;workaround&#8221; for him.</p>
<p>Don&#8217;t know if this will help you, but it was very enlightening.</p>
<p>I posted an extensive log of the troubleshooting steps on my blog:</p>
<p><a href="http://grandstreamdreams.blogspot.com/2006/09/thawing-xp-system.html" rel="nofollow">Thawing an XP System</a></p>
<p>&#8211;Claus</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-137117</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Sat, 02 Sep 2006 07:03:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-137117</guid>
		<description>Ed,
Excellent post. System Freezes in Windows 2000, XP and 2003 are almost always hardware related since these version of windows are very recoverable from software errors. This has been one of my longest issues getting through to people. You have no idea how many people blame Microsoft for their defective hardware. Overclockers are notorious. Which is why I made a simply troubleshooting guide:
http://mywebpages.comcast.net/SupportCD/DiagnoseXP.html</description>
		<content:encoded><![CDATA[<p>Ed,</p>
<p>Excellent post. System Freezes in Windows 2000, XP and 2003 are almost always hardware related since these version of windows are very recoverable from software errors. This has been one of my longest issues getting through to people. You have no idea how many people blame Microsoft for their defective hardware. Overclockers are notorious. Which is why I made a simply troubleshooting guide:</p>
<p><a href="http://mywebpages.comcast.net/SupportCD/DiagnoseXP.html" rel="nofollow">http://mywebpages.comcast.net/SupportCD/DiagnoseXP.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-136974</link>
		<dc:creator>Max</dc:creator>
		<pubDate>Fri, 01 Sep 2006 19:18:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-136974</guid>
		<description>I still wouldn&#039;t rule out Windows One Care as the source. I had the same problem(s): repeated random freeze-ups w/BSOD. I tore out my hair trying to figure it out - checking hardware, memory, Event Viewer for clues, etc. Uninstalling One Care solved the problem two months ago. I really think that is a buggy program that should still be in beta.</description>
		<content:encoded><![CDATA[<p>I still wouldn&#8217;t rule out Windows One Care as the source. I had the same problem(s): repeated random freeze-ups w/BSOD. I tore out my hair trying to figure it out &#8211; checking hardware, memory, Event Viewer for clues, etc. Uninstalling One Care solved the problem two months ago. I really think that is a buggy program that should still be in beta.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Serdar</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-136781</link>
		<dc:creator>Serdar</dc:creator>
		<pubDate>Fri, 01 Sep 2006 04:54:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-136781</guid>
		<description>Spot on as always, Ed.  I&#039;ve found that random lockups with no corresponding dump are almost always caused by bad memory (or a bad / flaky video card), a faulty power supply or a hard drive going south.  I&#039;ve had all three in different measures over time, so I&#039;ve gotten used to the &quot;feel&quot; (the pattern of failure) in each as well...</description>
		<content:encoded><![CDATA[<p>Spot on as always, Ed.  I&#8217;ve found that random lockups with no corresponding dump are almost always caused by bad memory (or a bad / flaky video card), a faulty power supply or a hard drive going south.  I&#8217;ve had all three in different measures over time, so I&#8217;ve gotten used to the &#8220;feel&#8221; (the pattern of failure) in each as well&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-136729</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Fri, 01 Sep 2006 01:57:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-136729</guid>
		<description>I had the same problem about 6 months ago.  Unexplained crashes, freeze ups. Think Ed suggested I try checking the memory, which I did and sure enough - a bad RAM chip, which I replaced and all has been well ever since.
Mark</description>
		<content:encoded><![CDATA[<p>I had the same problem about 6 months ago.  Unexplained crashes, freeze ups. Think Ed suggested I try checking the memory, which I did and sure enough &#8211; a bad RAM chip, which I replaced and all has been well ever since.</p>
<p>Mark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: System freezing up? Check your RAM! &#187; The PC Doctor</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-136613</link>
		<dc:creator>System freezing up? Check your RAM! &#187; The PC Doctor</dc:creator>
		<pubDate>Thu, 31 Aug 2006 19:21:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-136613</guid>
		<description>[...] Ed Bott&#160; looks at how a faulty RAM module can cause your system to crash and freeze up: [...]</description>
		<content:encoded><![CDATA[<p>[...] Ed Bott&nbsp; looks at how a faulty RAM module can cause your system to crash and freeze up: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl</title>
		<link>http://www.edbott.com/weblog/2006/08/system-freezing-up-check-your-hardware/comment-page-1/#comment-136519</link>
		<dc:creator>Carl</dc:creator>
		<pubDate>Thu, 31 Aug 2006 14:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.edbott.com/weblog/?p=1451#comment-136519</guid>
		<description>Just to clarify - the things that Ed talks about are a lot more likely, but if one of those doesn&#039;t clear it up, look at the power supply.</description>
		<content:encoded><![CDATA[<p>Just to clarify &#8211; the things that Ed talks about are a lot more likely, but if one of those doesn&#8217;t clear it up, look at the power supply.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

