Application Popup Mstsc.exe - Application Error
Contents |
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 mstsc ntdll.dll error Full Time Job Ways to Get Help Expand Search Submit Close Search Login remote desktop connection has stopped working Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > mstsc.exe remote desktop connection stopped working windows 7 Application Error Want to Advertise Here? Solved mstsc.exe Application Error Posted on 2009-07-27 Windows XP 2 Verified Solutions 3 Comments 5,833 Views Last Modified: 2012-05-07 When logging out of any server or
Remote Desktop Connection Has Stopped Working Windows 10
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 windows 10 remote desktop crashing 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! 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 L
Guide to Using Google Chromewindows-10-fast Home > How I fixed the "Remote Desktop connection has stopped working" error in Windows 8.1 How I fixed the "Remote Desktop connection has stopped working" error in Windows 8.1 Posted on December 19, 2014 by vonnie — 54 Comments remote desktop has stopped working windows 10 ↓ Let me tell you a story about a troubleshooting incident I encountered a few weeks
Remote Desktop Crashes Windows 10
ago. I live in New York City. The other day I was trying to use the Microsoft Terminal Services Client (mstsc.exe) to remotely
Remote Desktop Connection Stopped Working Windows 10
connect to a PC in Los Angeles, California but for some inexplicable reason I couldn't connect. Well that's not entirely true; the client actually crashed on connect. After entering my credentials and clicking Connect, the remote computer would log me https://www.experts-exchange.com/questions/24603073/mstsc-exe-Application-Error.html in but then would invariably flash and crash with this troublesome message: The Remote Desktop connection has stopped working. The error is pretty lame if you ask me. Here's the thing: it's already obvious that the Remote Desktop connection stopped working because the client was completely locked up. Therefore, why does Microsoft need to rub it in my face by telling me what is already undeniably true? So yes, I was perturbed. I tried immediately connecting again (just to see if http://www.fixedbyvonnie.com/2014/12/fixed-remote-desktop-connection-stopped-working-error-windows-8-1/ the error would go away) but I got the same result. Rebooting didn't fix anything so I asked a friend to attempt to connect to the same remote computer. Guess what? He didn't have any issues. He connected fine and looked at me like I was stupid. So there was something on my computer that was causing the Remote Desktop application to quit unceremoniously. But what was it? When I looked in the event logs I could see mstsc.exe was the faulting application name. But I already knew that. There was also something in there about vorbis.acm. Faulting module name: vorbis.acm How odd… what is that? Wait a second… I thought to myself: Vorbis… vorbis… where have I heard that before? Isn't that an audio codec or something? I started Googling around and noticed that vorbis, sometimes called Ogg Vorbis, is an open source audio coding format. But it wasn't obvious to me what an audio codec and the Remote Desktop Client had in common. How are the two related? I started searching for clues through the Remote Desktop client tabs: I perused the General tab… nope nothing here. I scrutinized the Display tab… nothing relevant here I clicked through the Local Resources tab… Oh wait.. what is this? Remote audio… configure remote audio settings? I mused to myself: Ah, maybe there's something in here I need to disable? When I clicked in the Remote audio playback s
memory could not be read" With Windows, you never know what crazy error message will one day pop up and scare the heck out of you! One error message that I have seen on http://helpdeskgeek.com/help-desk/instruction-at-referenced-memory-could-not-be-read/ a clients machine recently was: Instruction at 0x000 referenced memory at 0x000. The memory could not be read. Wow! What the heck does that even mean!? Well, just like most Windows errors, it can be a LOT of stuff. This error can be caused by bad memory, a bad CPU, older drivers, hardware conflicts, and a bunch of other stuff! With this type of error, you basically remote desktop have to try a bunch of things and see if something works. Also, think logically about each solution. For example, if your computer is brand new, then you probably don’t have bad memory. Method 1 – Increase Virtual Memory One reason you might be getting this error is if your virtual memory settings are very low. You can right-click on My Computer, go to the Advanced tab, and remote desktop connection click on Settings under Performance. Then click on the Advanced tab again under Performance Options and click the Change button under Virtual memory. Read my previous article on how to optimize the page file size in order to set the value to the appropriate setting for your computer. Restart the computer and see if the problem goes away or not. Method 2 – Uninstall Buggy Software Another reason this may occur outside of possible hardware problems is if you have buggy software installed or visit a website that has buggy code. If you’ve recently installed some program that is not Adobe, Microsoft, Google, or from some other big and reputable company, try to uninstall it and see what happens. A lot of times it can even be popular software that just has bugs in it. Also, this referenced memory error happens in software programs related to firewalls, anti-virus, anti-spyware and the like. If you’re using something like that, try uninstalling and see if the problem goes away. If you have anti-virus software or any type of real-time Internet traffic scanning software, make sure to disable it and see if the problem goes away. If a program is scanning web traffic, you can
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 30 Sep 2016 23:12:25 GMT by s_hv999 (squid/3.5.20)