Mstsc.exe Error Memory Could Not Be Read
Contents |
SPONSORED BY MICROSOFT TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now Hi I have a user who is, since last night, no longer able to connect to our the instruction at referenced memory at the memory could not be read terminal server... she is now getting the following message: The instruction at "0x4d86bcfa" referenced memory the instruction at referenced memory at could not be written at "0x00000000". The memory could not be "read" She has been able to connect by using the 'run as' option and putting the memory could not be written her own network credentials in - but does not want to do this as a long term solution. Any ideas? Thanks in advance! Reply Subscribe View Best Answer RELATED TOPICS: MSTSC.EXE: How much memory the memory could not be read windows 10 should it be using? Application error Application Error?   6 Replies Pure Capsaicin OP akp982 Apr 8, 2010 at 4:57 UTC akp982 is an IT service provider. Is this error on the terminal server or her machine? Looks like a memory problem, try recreating her profile or changing out the memory. 0 Serrano OP Patrick Louis-Jean Apr 8, 2010 at 6:13 UTC I she can runas
The Instruction At 0x00000000 Referenced Memory At 0x00000000 . The Memory Could Not Be Read
administrator, it sounds like it is a permissions problem. What OS is she running? How is she logging on to the machine - local account or domain? Is it just her or do other users on that machine have the same problem? 0 Sonora OP Clare1904 Apr 8, 2010 at 6:38 UTC Hi Thanks for your replies..... the user is using an XP SP3 laptop, connecting to a 2003 Terminal Server - and I'm told it worked fine last night! The error message appears to be on the laptop as it will not open the RDP session. I'm confused as to why it won't work in the normal manner, but it will work when using the 'Run as another user' route with her own network credentials logging on to the domain (it isn't just restricted to admin credentials).... surely if it is a memory problem wouldn't the 'run as' way in also be affected? Apologies if this is a stupid assumption! 0 Sonora OP Clare1904 Apr 8, 2010 at 6:39 UTC Sorry - forgot to say - it is just her, the other users in the same office connecting to the same server are not having any problems.... 0 Sonora OP Best Answer Clare1904 Apr 8, 2010 at 8:37 UTC Hi
be down. Please try the request again. Your cache administrator is webmaster. Generated Wed, 19 Oct 2016 09:41:59 GMT by s_ac5 (squid/3.5.20)
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help https://www.experts-exchange.com/questions/24603073/mstsc-exe-Application-Error.html Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > mstsc.exe Application Error Want to Advertise Here? Solved mstsc.exe Application Error Posted on 2009-07-27 Windows XP 2 Verified Solutions 3 Comments 5,843 Views Last Modified: 2012-05-07 When logging out of any server or when exiting the mstsc application my customer gets an application error. "The instruction at "0x00e802b7" could not 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? could not be Thanks for any help! 0 Question by:cstallings Facebook Twitter LinkedIn Google LVL 66 Best Solution byjohnb6767 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 Go to Solution 3 Comments LVL 63 Overall: Level 63 Windows XP 17 Message Expert Comment by:SysExpert2009-07-27 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 LVL 66 Overall: Level 66 Windows XP 49 Message Accepted Solution by:johnb67672009-07-27 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. 0 LVL 1 Overall: Level 1 Message Assisted Solution by:rldavis2009-08-18 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 mst