mstsc.exe Application Error

When logging out of any server or when exiting the mstsc application my customer gets an application error.
"The instruction at "0x00e802b7" referenced memory at "0x00000008". The memory could not be "read". Click on OK to terminate the program.
He has XP SP3 with mstsc version 6.0.6001.18000 (longhorn_rtm.080118-1840)
I have tried to rename the files mstsc.exe and mstscax.dll to .bak, and rebooted, but that did not help. I also deleted the bcache2.bmc file as well. I also tred to reregister the dll file. Should I remove XP3 to use an older version of RDP?
Thanks for any help!
cstallingsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SysExpertCommented:
1) It could be a hardware issues, especially RAM, so run a RAm diagnostic for a few hours

2) Not sure if t is worthwhile to uninstall SP3. Did it work previous to the SP3 update ?

I hope this helps !
0
johnb6767Commented:
Delete the following from c:\windows\system32\dllcache

mstsc.exe
mstscax.dll
mstsmhst.dll
rdpdd.dll
rdpsnd.dll
rdpdr.sys
rdpwsx.dll
rdpclip.exe

Then rename them to *.old in c:\windows\system32

Then replace them from the most recent versions in C:\WINDOWS\$NtServicePackUninstall$.

If needed you might need to unregister them if possible, and then reregister them.

This will basically rebuild the files needed for RDP.<!-- richText -->
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rldavisCommented:
Just one comment on Johnb6767's excellent solution above.  
The mstscax.dll date needs to match the mstsc.exe date.  On one machine where I corrected this there was a newer mstscax.dll and it would not work with the original mstsc.exe copied out of the $NtServicePackUninstall$.  
I just did a search for the mstscax.dll and copied the one with a matching date to the mstsc.exe to the c:\windows\system32 directory.  

Great solution John.  
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.