 




<?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: STOP 0X00000050 on bootup, both normal and safe mode</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/stop-0x00000050-on-bootup-both-normal-and-safe-mode/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/stop-0x00000050-on-bootup-both-normal-and-safe-mode/</link>
	<description></description>
	<lastBuildDate>Mon, 20 May 2013 12:39:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: mwiemers</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/stop-0x00000050-on-bootup-both-normal-and-safe-mode/#comment-77835</link>
		<dc:creator>mwiemers</dc:creator>
		<pubDate>Fri, 04 Jun 2010 17:22:54 +0000</pubDate>
		<guid isPermaLink="false">#comment-77835</guid>
		<description><![CDATA[Just as followup, and to close this thread:
I tried all of these suggestions and more - never found a way around the STOP error.  
» Used the BlueScreenView utility to analyze minidump files, which showed that the bootup kernel NTOSKRNL.EXE was the process causing the error.  This would explain why it would not boot into Safe Mode.  I find notes that a virus can alter this process, but a full scan with the hard drive in a USB enclosure showed no indications of viral infection, so it appears that we were unfortunate enough to have a hard drive that happened to be corrupted in a bad location.
» Finally gave up on fixing the existing installation &amp; reinstalled onto a new, larger hard drive.]]></description>
		<content:encoded><![CDATA[<p>Just as followup, and to close this thread:<br />
I tried all of these suggestions and more &#8211; never found a way around the STOP error.<br />
» Used the BlueScreenView utility to analyze minidump files, which showed that the bootup kernel NTOSKRNL.EXE was the process causing the error.  This would explain why it would not boot into Safe Mode.  I find notes that a virus can alter this process, but a full scan with the hard drive in a USB enclosure showed no indications of viral infection, so it appears that we were unfortunate enough to have a hard drive that happened to be corrupted in a bad location.<br />
» Finally gave up on fixing the existing installation &amp; reinstalled onto a new, larger hard drive.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.013 seconds using memcached
Object Caching 268/271 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-20 13:04:50 -->