xp remote desktop bluescreen or how to shoot your pc

Regarding commonnality, this issue is a showstopper for anyone planning to
do a desktop virtualization.

I'm currently running XP on VMware platform and this issue is driving me
crazy. I connect to this virtualized XP from various locations, and once I
forget to configure color depth of RDP connection, it's a death sentence for
my desktop - next time I run a "correctly" configured RDP session, it result
in BSoD.

So while I do agree Microsoft probably won't fix this as XP is now nearly
unsupported, I expect this issue to rise again if desktop virtualization
became mainstream while XP is still alive.

> We disagree about the commonality of your reported problem. That's all. It
> exists, no argument there - it's just going to be rare that someone comes
> across it - IMO. Maybe you have a case where it is not rare to change
> bit-rates (disconnect/reconnect twice) without logging off the remote
> computer. I'm not saying the issue doesn't exist, in fact I cannot say this
> any better than I did a while back in this conversation, "To be clearer, I
> wouldn't expect a reaction or a fix if I were you."
>

<snipped>
http://groups.google.com/group/micro...ca8fdb2e87ba5/



tyamadajp wrote:
> Regarding commonnality, this issue is a showstopper for anyone planning
> to
> do a desktop virtualization.
>
> I'm currently running XP on VMware platform and this issue is driving me
> crazy. I connect to this virtualized XP from various locations, and once I
> forget to configure color depth of RDP connection, it's a death sentence
> for
> my desktop - next time I run a "correctly" configured RDP session, it
> result
> in BSoD.
>
> So while I do agree Microsoft probably won't fix this as XP is now nearly
> unsupported, I expect this issue to rise again if desktop virtualization
> became mainstream while XP is still alive.


You mean unless you apply the patch given in the thread, right?

It's not like the fix wasn't posted in the very conversation you were
responding to. See below - the hotfix repaired the error completely.

Here is the relevant section of the conversation with a link to the fix...

Tom wrote:
> May I suggest you to test a more recent build of Rdpdd.dll
> (23-Jan-2009). In my eyes, this problem could be related to this
> issue:
>
> http://support.microsoft.com/kb/963038/en-us

Shenan wrote:
> I agree with the suggestion, although the issue does not give the error(s)
> mentioned in the KB article.
>
> Taking the screenshot out of the recorded examples I gave, you can see
> the bluescreen states:
>
> PAGE_FAULT_IN_NONPAGED_AREA
> STOP: 0x00000050 (0xBC62FFF0, 0x00000000, 0xBF85B6B7,0x00000000)
> win32k.sys - Address BF85B6B7 base at BF800000
>
> The KB Article (http://support.microsoft.com/kb/963038/) refers to this
> error:
> STOP: 0x1000008E (Parameter1, Parameter2, Parameter3, Parameter4) in
> RDPDD.dll
> KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
>
> Screenshot of BlueScreen on Remote Machine:
> http://picasaweb.google.com/lh/photo...eat=directlink
>
> But - what the heck? It's the best possibility yet and all the work is
> done
> except for this last part. So I tried it and recorded the results.
>
> Resultant Video (showing the application of the fix, reboot and test
> results...):
> http://www.youtube.com/watch?v=cWEkACbLYIE
>
> The fix seemed to work perfectly. Good find, Tom.
>
> If you have Windows XP SP3 and your RDPDD.DLL file version is
> 5.1.2600.5749
> or later - you should not have the issue that the OP is reporting.
>
> The videos, pictures and KB article should get you everything you need -
> since you can get the fix by reading the KB article, etc. Apply that
> hotfix
> to all affected machines.
>
> If you just want the hotfix...
> http://support.microsoft.com/hotfix/...x?kbnum=963038
>
> Do the obvious (in case it is not obvious, select the proper language, put
> in a valid email address twice, type the characters you see. When you get
> the email, follow the directions.)
>
> Hopefully that will fix the problem for the OP and is well documented and
> commented about enough to allow those who put effort into it and search
> will
> find the answer they seek. I would ask that the OP comes back and lets us
> know if this resolves the issue for them - but it should - given the video
> evidence. ;-) Would be nice closure, however.

** Although now I would also suggest getting the Remote Desktop Client 7.0
in addition. **

With the above - you should not be struggling anymore.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Jared Davison wrote on 09/09/2009 21:53 ET
> HOTFIX SOLUTION
>
> http://support.microsoft.com/kb/963038/en-u
>
> This is a patch to RDPDD.DLL
>
> Thanks for posting this article as it helped me solve the problem. I ha
> this problem you describe above, and changing the bit depth of rdp clien
> connections causing Blue Screens on the xp remote desktop server side.
> called Microsoft Support and after spending quite a lot of time with them
> they believed me and investigated and found a hotfix on their site that i wa
> unable to find myself. This process took about 3-4 weeks to get the solutio
> from when i first contacted them
>
> I have tried the hotfix on my systems and it appears to work and haven't ha
> any further blue screens so far when changing bit depth
>
> I have since tried to find the link above in google using keywords but i
> didn't come up for me so that could explain why we have struggled to find th
> solution
>
> Hope this helps you too
>
> Kind regard
>
> Jared Daviso
>
My symptoms were exactly the same. I'd connect to an RDP session and i
worke
fine, then I'd connect from another machine (presumably at a differen
resolution and/or bitdepth) and it would crash the computer I was remotin
into
This happened several times in the exact same way, and it took quite a bit o
digging to find a solution

I think it took me longer to find the hotfix since the errors were a littl
different, and taking place in a different sys/dll/file than most

My errors consisted of

0x0000008E or 0x00000050 (had both

Both were taking place in win32k.sys, according to the BSOD

Anyhow, after installing the newest video card drivers and downloading th
hotfix in the youtube video above, my problem was resolved. Thanks a lot fo
this article, as I don't think I would have solved this without both th
articl
and the video.