<?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: win32k.sys blue screen of death and how to fix it</title>
	<atom:link href="http://www.marcusmccurdy.com/2009/03/05/win32ksys-blue-screen-of-death-and-how-to-fix-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.marcusmccurdy.com/2009/03/05/win32ksys-blue-screen-of-death-and-how-to-fix-it/</link>
	<description>My personal blog about games, movies, blogging, and technology.</description>
	<lastBuildDate>Wed, 24 Mar 2010 11:13:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rob MacDonald</title>
		<link>http://www.marcusmccurdy.com/2009/03/05/win32ksys-blue-screen-of-death-and-how-to-fix-it/comment-page-1/#comment-257</link>
		<dc:creator>Rob MacDonald</dc:creator>
		<pubDate>Fri, 24 Jul 2009 08:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcusmccurdy.com/?p=206#comment-257</guid>
		<description>and this:
0: kd&gt; .trap 0xfffffffff69839d8
ErrCode = 00000000
eax=00000002 ebx=00000000 ecx=00000000 edx=00000000 esi=e1b01eb0 edi=804fab14
eip=bf80a499 esp=f6983a4c ebp=f6983a5c iopl=0         nv up ei ng nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010283
win32k!xxxMsgWaitForMultipleObjects+0xb6:
bf80a499 ff              ???</description>
		<content:encoded><![CDATA[<p>and this:<br />
0: kd&gt; .trap 0xfffffffff69839d8<br />
ErrCode = 00000000<br />
eax=00000002 ebx=00000000 ecx=00000000 edx=00000000 esi=e1b01eb0 edi=804fab14<br />
eip=bf80a499 esp=f6983a4c ebp=f6983a5c iopl=0         nv up ei ng nz na po cy<br />
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010283<br />
win32k!xxxMsgWaitForMultipleObjects+0xb6:<br />
bf80a499 ff              ???</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob MacDonald</title>
		<link>http://www.marcusmccurdy.com/2009/03/05/win32ksys-blue-screen-of-death-and-how-to-fix-it/comment-page-1/#comment-256</link>
		<dc:creator>Rob MacDonald</dc:creator>
		<pubDate>Fri, 24 Jul 2009 08:09:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcusmccurdy.com/?p=206#comment-256</guid>
		<description>Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini072409-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Jul 24 08:17:33.031 2009 (GMT+1)
System Uptime: 0 days 0:12:00.734
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, bf80a499, f69839d8, 0}

Probably caused by : hardware ( win32k!xxxMsgWaitForMultipleObjects+b6 )

Followup: MachineOwner
---------

0: kd&gt; !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: bf80a499, The address that the exception occurred at
Arg3: f69839d8, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
win32k!xxxMsgWaitForMultipleObjects+b6
bf80a499 ff              ???

TRAP_FRAME:  f69839d8 -- (.trap 0xfffffffff69839d8)
ErrCode = 00000000
eax=00000002 ebx=00000000 ecx=00000000 edx=00000000 esi=e1b01eb0 edi=804fab14
eip=bf80a499 esp=f6983a4c ebp=f6983a5c iopl=0         nv up ei ng nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010283
win32k!xxxMsgWaitForMultipleObjects+0xb6:
bf80a499 ff              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  4

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  csrss.exe

MISALIGNED_IP: 
win32k!xxxMsgWaitForMultipleObjects+b6
bf80a499 ff              ???

LAST_CONTROL_TRANSFER:  from bf89b736 to bf80a499

FAILED_INSTRUCTION_ADDRESS: 
win32k!xxxMsgWaitForMultipleObjects+b6
bf80a499 ff              ???

STACK_TEXT:  
f6983a5c bf89b736 00000002 8708fba8 bf89e684 win32k!xxxMsgWaitForMultipleObjects+0xb6
f6983d30 bf8846e9 bf9ab400 00000001 f6983d54 win32k!xxxDesktopThread+0x339
f6983d40 bf8010ed bf9ab400 f6983d64 0072fff4 win32k!xxxCreateSystemThreads+0x6a
f6983d54 8054162c 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
f6983d54 7c90e514 00000000 00000022 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!xxxMsgWaitForMultipleObjects+b6
bf80a499 ff              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!xxxMsgWaitForMultipleObjects+b6

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

Followup: MachineOwner
---------

0: kd&gt; lmvm hardware
start    end        module name</description>
		<content:encoded><![CDATA[<p>Microsoft (R) Windows Debugger Version 6.11.0001.404 X86<br />
Copyright (c) Microsoft Corporation. All rights reserved.</p>
<p>Loading Dump File [C:\WINDOWS\Minidump\Mini072409-04.dmp]<br />
Mini Kernel Dump File: Only registers and stack trace are available</p>
<p>Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols<br />
Executable search path is:<br />
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible<br />
Product: WinNt, suite: TerminalServer SingleUserTS Personal<br />
Built by: 2600.xpsp_sp3_gdr.090206-1234<br />
Machine Name:<br />
Kernel base = 0&#215;804d7000 PsLoadedModuleList = 0&#215;8055d720<br />
Debug session time: Fri Jul 24 08:17:33.031 2009 (GMT+1)<br />
System Uptime: 0 days 0:12:00.734<br />
Loading Kernel Symbols<br />
&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;<br />
&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.<br />
Loading User Symbols<br />
Loading unloaded module list<br />
&#8230;&#8230;&#8230;&#8230;<br />
*******************************************************************************<br />
*                                                                             *<br />
*                        Bugcheck Analysis                                    *<br />
*                                                                             *<br />
*******************************************************************************</p>
<p>Use !analyze -v to get detailed debugging information.</p>
<p>BugCheck 1000008E, {c000001d, bf80a499, f69839d8, 0}</p>
<p>Probably caused by : hardware ( win32k!xxxMsgWaitForMultipleObjects+b6 )</p>
<p>Followup: MachineOwner<br />
&#8212;&#8212;&#8212;</p>
<p>0: kd&gt; !analyze -v<br />
*******************************************************************************<br />
*                                                                             *<br />
*                        Bugcheck Analysis                                    *<br />
*                                                                             *<br />
*******************************************************************************</p>
<p>KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)<br />
This is a very common bugcheck.  Usually the exception address pinpoints<br />
the driver/function that caused the problem.  Always note this address<br />
as well as the link date of the driver/image that contains this address.<br />
Some common problems are exception code 0&#215;80000003.  This means a hard<br />
coded breakpoint or assertion was hit, but this system was booted<br />
/NODEBUG.  This is not supposed to happen as developers should never have<br />
hardcoded breakpoints in retail code, but &#8230;<br />
If this happens, make sure a debugger gets connected, and the<br />
system is booted /DEBUG.  This will let us see why this breakpoint is<br />
happening.<br />
Arguments:<br />
Arg1: c000001d, The exception code that was not handled<br />
Arg2: bf80a499, The address that the exception occurred at<br />
Arg3: f69839d8, Trap Frame<br />
Arg4: 00000000</p>
<p>Debugging Details:<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>EXCEPTION_CODE: (NTSTATUS) 0xc000001d &#8211; {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.</p>
<p>FAULTING_IP:<br />
win32k!xxxMsgWaitForMultipleObjects+b6<br />
bf80a499 ff              ???</p>
<p>TRAP_FRAME:  f69839d8 &#8212; (.trap 0xfffffffff69839d8)<br />
ErrCode = 00000000<br />
eax=00000002 ebx=00000000 ecx=00000000 edx=00000000 esi=e1b01eb0 edi=804fab14<br />
eip=bf80a499 esp=f6983a4c ebp=f6983a5c iopl=0         nv up ei ng nz na po cy<br />
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010283<br />
win32k!xxxMsgWaitForMultipleObjects+0xb6:<br />
bf80a499 ff              ???<br />
Resetting default scope</p>
<p>CUSTOMER_CRASH_COUNT:  4</p>
<p>DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT</p>
<p>BUGCHECK_STR:  0&#215;8E</p>
<p>PROCESS_NAME:  csrss.exe</p>
<p>MISALIGNED_IP:<br />
win32k!xxxMsgWaitForMultipleObjects+b6<br />
bf80a499 ff              ???</p>
<p>LAST_CONTROL_TRANSFER:  from bf89b736 to bf80a499</p>
<p>FAILED_INSTRUCTION_ADDRESS:<br />
win32k!xxxMsgWaitForMultipleObjects+b6<br />
bf80a499 ff              ???</p>
<p>STACK_TEXT:<br />
f6983a5c bf89b736 00000002 8708fba8 bf89e684 win32k!xxxMsgWaitForMultipleObjects+0xb6<br />
f6983d30 bf8846e9 bf9ab400 00000001 f6983d54 win32k!xxxDesktopThread+0&#215;339<br />
f6983d40 bf8010ed bf9ab400 f6983d64 0072fff4 win32k!xxxCreateSystemThreads+0&#215;6a<br />
f6983d54 8054162c 00000000 00000022 00000000 win32k!NtUserCallOneParam+0&#215;23<br />
f6983d54 7c90e514 00000000 00000022 00000000 nt!KiFastCallEntry+0xfc<br />
WARNING: Frame IP not in any known module. Following frames may be wrong.<br />
00000000 00000000 00000000 00000000 00000000 0&#215;7c90e514</p>
<p>STACK_COMMAND:  kb</p>
<p>FOLLOWUP_IP:<br />
win32k!xxxMsgWaitForMultipleObjects+b6<br />
bf80a499 ff              ???</p>
<p>SYMBOL_STACK_INDEX:  0</p>
<p>SYMBOL_NAME:  win32k!xxxMsgWaitForMultipleObjects+b6</p>
<p>FOLLOWUP_NAME:  MachineOwner</p>
<p>IMAGE_NAME:  hardware</p>
<p>DEBUG_FLR_IMAGE_TIMESTAMP:  0</p>
<p>MODULE_NAME: hardware</p>
<p>FAILURE_BUCKET_ID:  IP_MISALIGNED</p>
<p>BUCKET_ID:  IP_MISALIGNED</p>
<p>Followup: MachineOwner<br />
&#8212;&#8212;&#8212;</p>
<p>0: kd&gt; lmvm hardware<br />
start    end        module name</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob MacDonald</title>
		<link>http://www.marcusmccurdy.com/2009/03/05/win32ksys-blue-screen-of-death-and-how-to-fix-it/comment-page-1/#comment-255</link>
		<dc:creator>Rob MacDonald</dc:creator>
		<pubDate>Fri, 24 Jul 2009 08:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcusmccurdy.com/?p=206#comment-255</guid>
		<description>Hello Marcus,
I have followed your post re: debug and got the following reply which makes no sense to me. Any idea what it means?
Thanks for your help so far
Rob</description>
		<content:encoded><![CDATA[<p>Hello Marcus,<br />
I have followed your post re: debug and got the following reply which makes no sense to me. Any idea what it means?<br />
Thanks for your help so far<br />
Rob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: emir0721</title>
		<link>http://www.marcusmccurdy.com/2009/03/05/win32ksys-blue-screen-of-death-and-how-to-fix-it/comment-page-1/#comment-245</link>
		<dc:creator>emir0721</dc:creator>
		<pubDate>Fri, 08 May 2009 06:01:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcusmccurdy.com/?p=206#comment-245</guid>
		<description>Thanks for that very helpful post. My computer crashed and showed me a &quot;blue screen&quot; that was apparently caused by a faulty RAM stick.

Since you&#039;re into computers, I&#039;m inviting you to join BetaArchive.co.uk. You can share your knowledge with other enthusiasts. It&#039;s a pretty amazing community if you ask me.</description>
		<content:encoded><![CDATA[<p>Thanks for that very helpful post. My computer crashed and showed me a &#8220;blue screen&#8221; that was apparently caused by a faulty RAM stick.</p>
<p>Since you&#8217;re into computers, I&#8217;m inviting you to join BetaArchive.co.uk. You can share your knowledge with other enthusiasts. It&#8217;s a pretty amazing community if you ask me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcus</title>
		<link>http://www.marcusmccurdy.com/2009/03/05/win32ksys-blue-screen-of-death-and-how-to-fix-it/comment-page-1/#comment-233</link>
		<dc:creator>Marcus</dc:creator>
		<pubDate>Fri, 13 Mar 2009 02:07:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcusmccurdy.com/?p=206#comment-233</guid>
		<description>Yeah funny story about that screen saver I put it on my work computer then went to lunch and I freaked out for a second when I came back and saw the screen saver up because I completely forgot about it.</description>
		<content:encoded><![CDATA[<p>Yeah funny story about that screen saver I put it on my work computer then went to lunch and I freaked out for a second when I came back and saw the screen saver up because I completely forgot about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shameen Azeez</title>
		<link>http://www.marcusmccurdy.com/2009/03/05/win32ksys-blue-screen-of-death-and-how-to-fix-it/comment-page-1/#comment-230</link>
		<dc:creator>Shameen Azeez</dc:creator>
		<pubDate>Wed, 11 Mar 2009 10:27:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcusmccurdy.com/?p=206#comment-230</guid>
		<description>yeah and trying to be sarcastic still sounds offensive
btw i got the BSOD screensaver :P</description>
		<content:encoded><![CDATA[<p>yeah and trying to be sarcastic still sounds offensive<br />
btw i got the BSOD screensaver <img src='http://www.marcusmccurdy.com/wordpress/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Moose</title>
		<link>http://www.marcusmccurdy.com/2009/03/05/win32ksys-blue-screen-of-death-and-how-to-fix-it/comment-page-1/#comment-229</link>
		<dc:creator>Moose</dc:creator>
		<pubDate>Tue, 10 Mar 2009 21:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcusmccurdy.com/?p=206#comment-229</guid>
		<description>What? I don&#039;t get it . . . haha (sarcasm detector beeping). But speaking truthfully, you do have to be a bit careful, which stinks for me because in real life I&#039;m really sarcastic.</description>
		<content:encoded><![CDATA[<p>What? I don&#8217;t get it . . . haha (sarcasm detector beeping). But speaking truthfully, you do have to be a bit careful, which stinks for me because in real life I&#8217;m really sarcastic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shameen Azeez</title>
		<link>http://www.marcusmccurdy.com/2009/03/05/win32ksys-blue-screen-of-death-and-how-to-fix-it/comment-page-1/#comment-228</link>
		<dc:creator>Shameen Azeez</dc:creator>
		<pubDate>Tue, 10 Mar 2009 15:22:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcusmccurdy.com/?p=206#comment-228</guid>
		<description>yeah sarcasm never works :P

btw great work marcus on jennettes website :O</description>
		<content:encoded><![CDATA[<p>yeah sarcasm never works <img src='http://www.marcusmccurdy.com/wordpress/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
<p>btw great work marcus on jennettes website :O</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Moose</title>
		<link>http://www.marcusmccurdy.com/2009/03/05/win32ksys-blue-screen-of-death-and-how-to-fix-it/comment-page-1/#comment-227</link>
		<dc:creator>Moose</dc:creator>
		<pubDate>Sun, 08 Mar 2009 13:21:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcusmccurdy.com/?p=206#comment-227</guid>
		<description>Just careful, Shameen :). On the internet you have to be cautious about offending people....</description>
		<content:encoded><![CDATA[<p>Just careful, Shameen <img src='http://www.marcusmccurdy.com/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> . On the internet you have to be cautious about offending people&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shameen Azeez</title>
		<link>http://www.marcusmccurdy.com/2009/03/05/win32ksys-blue-screen-of-death-and-how-to-fix-it/comment-page-1/#comment-226</link>
		<dc:creator>Shameen Azeez</dc:creator>
		<pubDate>Sun, 08 Mar 2009 10:06:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcusmccurdy.com/?p=206#comment-226</guid>
		<description>you&#039;re far too modest :P</description>
		<content:encoded><![CDATA[<p>you&#8217;re far too modest <img src='http://www.marcusmccurdy.com/wordpress/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
