<?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>My Blog &#187; bug</title>
	<atom:link href="http://bitlords.com/wp/category/bug/feed/" rel="self" type="application/rss+xml" />
	<link>http://bitlords.com/wp</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sat, 12 Dec 2009 07:04:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Saboteur Launch Plagued By Problems With ATI Cards</title>
		<link>http://rss.slashdot.org/~r/Slashdot/slashdot/~3/-db4Jm9gmoQ/emSaboteurem-Launch-Plagued-By-Problems-With-ATI-Cards</link>
		<comments>http://rss.slashdot.org/~r/Slashdot/slashdot/~3/-db4Jm9gmoQ/emSaboteurem-Launch-Plagued-By-Problems-With-ATI-Cards#comments</comments>
		<pubDate>Wed, 09 Dec 2009 05:58:00 +0000</pubDate>
		<dc:creator>Soulskill</dc:creator>
				<category><![CDATA[bug]]></category>
		<category><![CDATA[anonymous reader]]></category>
		<category><![CDATA[ATI]]></category>
		<category><![CDATA[ati video card]]></category>
		<category><![CDATA[card]]></category>
		<category><![CDATA[crash]]></category>
		<category><![CDATA[current state]]></category>
		<category><![CDATA[December]]></category>
		<category><![CDATA[final game]]></category>
		<category><![CDATA[front page]]></category>
		<category><![CDATA[game]]></category>
		<category><![CDATA[game crash]]></category>
		<category><![CDATA[logo]]></category>
		<category><![CDATA[majority]]></category>
		<category><![CDATA[marketshare]]></category>
		<category><![CDATA[mistake]]></category>
		<category><![CDATA[Nvidia]]></category>
		<category><![CDATA[page]]></category>
		<category><![CDATA[Pandemic]]></category>
		<category><![CDATA[pandemic studios]]></category>
		<category><![CDATA[patch]]></category>
		<category><![CDATA[Read]]></category>
		<category><![CDATA[reader]]></category>
		<category><![CDATA[Saboteur]]></category>
		<category><![CDATA[screen]]></category>
		<category><![CDATA[Slashdot]]></category>
		<category><![CDATA[stage]]></category>
		<category><![CDATA[state]]></category>
		<category><![CDATA[story]]></category>
		<category><![CDATA[Studios]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[title]]></category>
		<category><![CDATA[video]]></category>
		<category><![CDATA[Vista]]></category>
		<category><![CDATA[website]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">tag:rss.slashdot.org://52546a3b6c7b8663ce53d1a05d924c08</guid>
		<description><![CDATA[An anonymous reader writes "So far, there are over 35 pages of people posting about why EA released Pandemic Studios' final game, Saboteur, to first the EU on December 4th and then, after knowing full well it did not work properly, to the Americas on December 8th. They have been promising to work on a patch that is apparently now in the QA stage of testing. It is not a small bug; rather, if you have an ATI video card and either Windows 7 or Windows Vista, the majority (90%) of users have the game crash after the title screen. Since the marketshare for ATI is nearly equal to that of Nvidia, and the ATI logo is adorning the front page of the Saboteur website, it seems like quite a large mistake to release the game in its current state."<p><a href="http://games.slashdot.org/story/09/12/09/0542246/emSaboteurem-Launch-Plagued-By-Problems-With-ATI-Cards?from=rss"><img src="http://slashdot.org/slashdot-it.pl?from=rss&#38;op=image&#38;style=h0&#38;sid=09/12/09/0542246"></a></p><p><a href="http://games.slashdot.org/story/09/12/09/0542246/emSaboteurem-Launch-Plagued-By-Problems-With-ATI-Cards?from=rss">Read more of this story</a> at Slashdot.</p>
<p><a href="http://feedads.g.doubleclick.net/~at/CnoFsPzsOnWWJmlAychB3xQ2wtw/0/da"><img src="http://feedads.g.doubleclick.net/~at/CnoFsPzsOnWWJmlAychB3xQ2wtw/0/di" border="0"></img></a><br />
<a href="http://feedads.g.doubleclick.net/~at/CnoFsPzsOnWWJmlAychB3xQ2wtw/1/da"><img src="http://feedads.g.doubleclick.net/~at/CnoFsPzsOnWWJmlAychB3xQ2wtw/1/di" border="0"></img></a></p><img src="http://feeds.feedburner.com/~r/Slashdot/slashdot/~4/-db4Jm9gmoQ" height="1">]]></description>
		<wfw:commentRss>http://rss.slashdot.org/~r/Slashdot/slashdot/~3/-db4Jm9gmoQ/emSaboteurem-Launch-Plagued-By-Problems-With-ATI-Cards/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Microsoft Investigates Windows 7 &#8220;Black Screen of Death&#8221;</title>
		<link>http://rss.slashdot.org/~r/Slashdot/slashdot/~3/qB6pthpor5I/Microsoft-Investigates-Windows-7-Black-Screen-of-Death</link>
		<comments>http://rss.slashdot.org/~r/Slashdot/slashdot/~3/qB6pthpor5I/Microsoft-Investigates-Windows-7-Black-Screen-of-Death#comments</comments>
		<pubDate>Tue, 01 Dec 2009 17:38:00 +0000</pubDate>
		<dc:creator>timothy</dc:creator>
				<category><![CDATA[bug]]></category>
		<category><![CDATA[25 november]]></category>
		<category><![CDATA[amp]]></category>
		<category><![CDATA[behavior]]></category>
		<category><![CDATA[BlackSOD]]></category>
		<category><![CDATA[company]]></category>
		<category><![CDATA[DEATH]]></category>
		<category><![CDATA[duguk]]></category>
		<category><![CDATA[ERROR]]></category>
		<category><![CDATA[firm]]></category>
		<category><![CDATA[GMT]]></category>
		<category><![CDATA[investigation]]></category>
		<category><![CDATA[kd]]></category>
		<category><![CDATA[latest security]]></category>
		<category><![CDATA[mdash]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[none]]></category>
		<category><![CDATA[November]]></category>
		<category><![CDATA[operating]]></category>
		<category><![CDATA[operating systems]]></category>
		<category><![CDATA[problem]]></category>
		<category><![CDATA[quot]]></category>
		<category><![CDATA[Read]]></category>
		<category><![CDATA[screen]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[Slashdot]]></category>
		<category><![CDATA[story]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[the]]></category>
		<category><![CDATA[TUESDAY]]></category>
		<category><![CDATA[Update]]></category>
		<category><![CDATA[Vista]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[windows updates]]></category>

		<guid isPermaLink="false">tag:rss.slashdot.org://7dc4093daf56afb61f2bb31c1a3bf344</guid>
		<description><![CDATA[duguk writes "Microsoft has confirmed that it is investigating a problem described as the 'black screen of death,' which affects Windows 7 &#8212; and reports suggest it affects Vista and XP, too. The firm said it was looking into reports that suggest its latest security update, released on Tuesday 25 November, caused the problem. The error means that users of Windows 7 and earlier operating systems see a totally black screen after logging on to the system." Update: 12/01 22:35 GMT by KD : Microsoft now says that its November Windows updates are not causing the BlackSOD: "The company has found those reports to be inaccurate and our comprehensive investigation has shown that none of the recently released updates are related to the behavior described in the reports."<p><a href="http://tech.slashdot.org/story/09/12/01/1725249/Microsoft-Investigates-Windows-7-Black-Screen-of-Death?from=rss"><img src="http://slashdot.org/slashdot-it.pl?from=rss&#38;op=image&#38;style=h0&#38;sid=09/12/01/1725249"></a></p><p><a href="http://tech.slashdot.org/story/09/12/01/1725249/Microsoft-Investigates-Windows-7-Black-Screen-of-Death?from=rss">Read more of this story</a> at Slashdot.</p>
<p><a href="http://feedads.g.doubleclick.net/~at/GdA1F5s-r_O8QbvzhgvKrVvI74k/0/da"><img src="http://feedads.g.doubleclick.net/~at/GdA1F5s-r_O8QbvzhgvKrVvI74k/0/di" border="0"></img></a><br />
<a href="http://feedads.g.doubleclick.net/~at/GdA1F5s-r_O8QbvzhgvKrVvI74k/1/da"><img src="http://feedads.g.doubleclick.net/~at/GdA1F5s-r_O8QbvzhgvKrVvI74k/1/di" border="0"></img></a></p><img src="http://feeds.feedburner.com/~r/Slashdot/slashdot/~4/qB6pthpor5I" height="1">]]></description>
		<wfw:commentRss>http://rss.slashdot.org/~r/Slashdot/slashdot/~3/qB6pthpor5I/Microsoft-Investigates-Windows-7-Black-Screen-of-Death/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dell Defect Turning 2.2GHz CPU Into 100MHz CPU?</title>
		<link>http://rss.slashdot.org/~r/Slashdot/slashdot/~3/gqKm1QJlonA/Dell-Defect-Turning-22GHz-CPU-Into-100MHz-CPU</link>
		<comments>http://rss.slashdot.org/~r/Slashdot/slashdot/~3/gqKm1QJlonA/Dell-Defect-Turning-22GHz-CPU-Into-100MHz-CPU#comments</comments>
		<pubDate>Mon, 30 Nov 2009 21:04:00 +0000</pubDate>
		<dc:creator>ScuttleMonkey</dc:creator>
				<category><![CDATA[bug]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[CPUs]]></category>
		<category><![CDATA[Dell Forums]]></category>
		<category><![CDATA[Dell Latitude]]></category>
		<category><![CDATA[detail]]></category>
		<category><![CDATA[e6400]]></category>
		<category><![CDATA[information]]></category>
		<category><![CDATA[intensive task]]></category>
		<category><![CDATA[issue]]></category>
		<category><![CDATA[laptops]]></category>
		<category><![CDATA[maximum]]></category>
		<category><![CDATA[maximums]]></category>
		<category><![CDATA[message]]></category>
		<category><![CDATA[message boards]]></category>
		<category><![CDATA[page]]></category>
		<category><![CDATA[PDF]]></category>
		<category><![CDATA[problem]]></category>
		<category><![CDATA[public information]]></category>
		<category><![CDATA[Read]]></category>
		<category><![CDATA[recall]]></category>
		<category><![CDATA[Report]]></category>
		<category><![CDATA[report pdf]]></category>
		<category><![CDATA[Room]]></category>
		<category><![CDATA[room temperatures]]></category>
		<category><![CDATA[scours]]></category>
		<category><![CDATA[Slashdot]]></category>
		<category><![CDATA[story]]></category>
		<category><![CDATA[task]]></category>
		<category><![CDATA[theoretical maximum]]></category>
		<category><![CDATA[Throttlegate]]></category>
		<category><![CDATA[user]]></category>
		<category><![CDATA[video]]></category>

		<guid isPermaLink="false">tag:rss.slashdot.org://3f76f757ceb0a67ac1eb1781b487b436</guid>
		<description><![CDATA[jtavares2 writes "In what is being dubbed Throttlegate, scores of users on many message boards have been complaining about nexplicably aggressive throttling policies on their Dell Latitude E6500 and E6400 laptops which cause their CPUs to be throttled to less than 5% of their theoretical maximums even while at room temperatures. In many cases, the issue can be triggered just by playing a video or performing some other trivial, but CPU intensive, task. After being banned [PDF] from the Dell Forums for revealing 'non-public information,' one user went so far as to write and publish a 59-page report [PDF] explaining and diagnosing the throttling problem in incredible detail. Dell seems to be silent on the issue, but many users are hoping for a formal recall."<p><a href="http://hardware.slashdot.org/story/09/11/30/1818207/Dell-Defect-Turning-22GHz-CPU-Into-100MHz-CPU?from=rss"><img src="http://slashdot.org/slashdot-it.pl?from=rss&#38;op=image&#38;style=h0&#38;sid=09/11/30/1818207"></a></p><p><a href="http://hardware.slashdot.org/story/09/11/30/1818207/Dell-Defect-Turning-22GHz-CPU-Into-100MHz-CPU?from=rss">Read more of this story</a> at Slashdot.</p>
<p><a href="http://feedads.g.doubleclick.net/~at/qHwLsjaneWYNKXRZLBVN_VZB2EM/0/da"><img src="http://feedads.g.doubleclick.net/~at/qHwLsjaneWYNKXRZLBVN_VZB2EM/0/di" border="0"></img></a><br />
<a href="http://feedads.g.doubleclick.net/~at/qHwLsjaneWYNKXRZLBVN_VZB2EM/1/da"><img src="http://feedads.g.doubleclick.net/~at/qHwLsjaneWYNKXRZLBVN_VZB2EM/1/di" border="0"></img></a></p><img src="http://feeds.feedburner.com/~r/Slashdot/slashdot/~4/gqKm1QJlonA" height="1">]]></description>
		<wfw:commentRss>http://rss.slashdot.org/~r/Slashdot/slashdot/~3/gqKm1QJlonA/Dell-Defect-Turning-22GHz-CPU-Into-100MHz-CPU/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

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