Remote Control reboots laptop

[DaGbyte]

I have an easily reproducable issue. I am running XP SP2 on my laptop and whenever I remote into via RDP (termial services) and try to copy a file to the clipboard, to copy to my local machine, the laptop bluescreens and reboots.

I viewed the bugcheck and the only thing that jumps out at me indicates there is an issue with the remote deskop application. I've run all critical updates but cannot fix the issue. RDP works just fine otherwise, just when I copy anything to the clipboard remotely, it reboots.

Has anyone seen anything like this? Any ideas how to fix the problem? It's not a component I can remove and re-install, so I'm kinda stumped....

-DaG

[jftuga]

You could try reinstalling SP2.

-John

[cluberti]

What exactly was the stop error, and what was the callstack information below it?

[DaGbyte]

Listed below is the bugcheck. My guess is something got corrupted. Just what and how to fix it remains a mystery...

Microsoft ® Windows Debugger Version 6.5.0003.7

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Temp\Mini102805-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***

****************************************************************************

* Symbol loading may be unreliable without a symbol search path. *

* Use .symfix to have the debugger choose a symbol path. *

* After setting your symbol path, use .reload to refresh symbol locations. *

****************************************************************************

Executable search path is:

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image ntoskrnl.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0

Debug session time: Fri Oct 28 08:02:40.921 2005 (GMT-5)

System Uptime: 2 days 0:56:05.632

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image ntoskrnl.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

....................................................................................................

....................

Loading unloaded module list

................

Loading User Symbols

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 0, b2426188, b2425e84}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image rdpdr.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for rdpdr.sys

*** ERROR: Module load completed but symbols could not be loaded for rdpdr.sys

*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

*************************************************************************

*** WARNING: Unable to verify timestamp for termdd.sys

*** ERROR: Module load completed but symbols could not be loaded for termdd.sys

*** WARNING: Unable to verify timestamp for RDPWD.SYS

*** ERROR: Module load completed but symbols could not be loaded for RDPWD.SYS

*** WARNING: Unable to verify timestamp for TDTCP.SYS

*** ERROR: Module load completed but symbols could not be loaded for TDTCP.SYS

Probably caused by : rdpdr.sys ( rdpdr+25f49 )

Followup: MachineOwner

---------

[cluberti]

Well, since it's only a minidump and not a kernel or complete memory dump the info is very limited, plus you don't have the _NT_SYMBOL_PATH environment variable set to C:\WebSYMBOLS;srv*C:\WebSYMBOLS*HTTP://MSDL.MICROSOFT.COM/DOWNLOAD/SYMBOLS;C:\WebSYMBOLS, but I can still see some file issues with termdd and rdpdr.

Have you tried doing a repair installation on this machine, or even an sfc /scannow? Also, was this machine built with a stock Windows CD, or was the install source modified with a 3rd party tool?

[DaGbyte]

Not quite sure what you mean about the debug stuff - I'm not very up on that.

It was built with a corp XP copy w/SP slipstreamed into it. I'll try to reapply SP2 and see if that helps....