Mstsc.exe Rdp Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related mstsc ntdll.dll error threads Remove From My Forums Answered by: Remote Desktop Client
Remote Desktop Connection Has Stopped Working Windows 7 Ntdll Dll
crashes "faulting application mstsc.exe" Windows Server > Remote Desktop Services (Terminal Services) Question 0 Sign in
Remote Desktop Has Stopped Working Windows 7
to vote We have a problem with crashing RDC clients connecting to Windows 2008 (SP2) Terminal Servers.Disconnections happen at random moments and intervals (both during active
Remote Desktop Stopped Working Windows 7
sessions and idle, varying form 5 - 60 min.)The error in the event log is:faulting application mstsc.exe, version 6.xxxx (both 6.0 and 6.1), faulting module ntdll.dll, version 5.1.2600.5755, fault address 0xxxxx (random)Remote Desktop is situated in an external datacenter and connections happen over the Internet (no VPN). Bandwidth and latency remote desktop has stopped working windows 10 are no issue.Our client uses a very diverse mix of hardware consisting of HP, Dell, Acer and Sony. Problem doesn't occur using Windows Vista or Windows 7.Also, the problem doesn't happen on connections to Server 2003 machines!Problem seems unrelated to network topology (took a PC for troubleshooting to other network locations)Troubleshooting actions so far:Reinstall XP SP3(Re)install RDC 6.1(Re)install Directx 9.0c(Re)install .Net Framework 3.5 SP1Update/downgrade network driversMicrosoft updateDisable VirusscannerDisable sound scheme and sound cardInclude mstsc.exe in DEP exclusion listDisable DirectDraw/Direct3D (dxdiag) Haven't seen the problem in save mode yet, but are still in the process of troubleshouting.Pls advice Monday, September 07, 2009 3:59 PM Reply | Quote Answers 0 Sign in to vote It strongly appears the problem is caused by the presence of the "Broadgun PdfMachine" printer on the local XP client.After removing this printer, the problem seems to be resolved.Not sure if this is a bug in the Broadgun software, the Remote
computer regularly. This has worked flawlessly for months. Suddenly I started to experience that Remote Desktop faulting module name ntdll.dll remote desktop would crash whenever I clicked on a folder in Windows Explorer remote desktop connection has stopped working server 2012 on the remote computer. Very strange. What had changed to suddenly cause this? The Application log remote desktop crashes windows 10 in the Windows Event Log showed the error was related to the remote audio functionality. Apparently, Remote Desktop Connection is using the Ogg Vorbis ACM codec for https://social.technet.microsoft.com/Forums/windowsserver/en-US/5f7b4caa-2297-4f62-b1ae-0d87f21e5f94/remote-desktop-client-crashes-faulting-application-mstscexe?forum=winserverTS remote audio, and this was related to the crash on my local Remote Desktop Connection client. Faulting application name: mstsc.exe, version: 10.0.10049.0 Faulting module name: vorbis.acm, version: 0.0.3.6 Exception code: 0xc0000005 Fault offset: 0x0000000000001f4f Faulting process id: 0x2478 Faulting application path: C:\WINDOWS\system32\mstsc.exe Faulting module path: C:\WINDOWS\system32\vorbis.acm The Fix and the Workaround I recently https://tommynation.com/fix-remote-desktop-connection-stopped-working-error/ installed FL Studio by Image-Line for music production. As it turns out, this was the culprit that caused the issue to appear. Because FL Studio installs a copy of vorbis.acm file into C:\Windows\System32, this interferes with Remote Desktop Connection. The fix: Renaming vorbis.acm in C:\Windows\System32 fixes the issue on 64-bit Windows. The file The permission The fix Note: The file is also present in C:\Windows\SysWOW64 on 64-bit Windows, but didn't need to be renamed on my system for this fix to work. If you can't live with this fix for some reason, you can also try the following workaround: The workaround: Disable remote audio playback in Remote Desktop Connection settings. Click settings Disable the audio That's it, folks! Please leave a comment below if this helped you in any way, or if you found related issues and workarounds that may help others who experience Remote Desktop Connection crashes. Also remember to follow TommyNation.com on Facebook.
Windows XP Pro to Windows 8.0 Pro. I was able to RDP from my Windows 7 Utlimate machine to them while Windows XP Pro https://community.spiceworks.com/how_to/62276-fix-for-rdp-remote-connection-has-stopped-working-after-upgrading-machine-to-windows-8-pro was loaded, but now that Windows 8.0 Pro is loaded, my RDP http://serverfault.com/questions/30304/mstsc-crash-on-connect connects and then fails in less than a minute with the following error message - "Remote connection has stopped working. Checked event viewer mstsc.exe 6.2.9200.16398 5036045e ntdll.dll 6.1.7601.18247 521eaf24 c0000374 00000000000c4102 2860 01cefdee3c13c975 C:\Windows\system32\mstsc.exe C:\Windows\SYSTEM32\ntdll.dll 90947b1d-69e1-11e3-a3bc-001e4ff42b07 Faulting Application name mstsc.exe, version 6.2.9200.16398; time stamp 0x5036045e Faulting module name: ntldll.dll, remote desktop version 6.1.7601.18247, time stamp: 0x521eaf24 Exception code: 0xc0000374 Fault offset: 0z0000000000000c4102f Faulting process id: 0x2860 Faulting application start time: 0x01cefdee3c13c975 Faulting application path: C:\Windows\system32\mstsc.exe Faulting module path C:\windows\system32\ntdll.dll Report ID: 90947b1d-09e1-11e3-a3bc-001e4ff42b07 At first I thought it was possibly the configuration of the new Windows 8.0 Pro machines since they were the only elements that changed, but I found that it is easily has stopped working corrected by going into the RDP Options. Steps (5 total) 1 Open RDP Type in the hostname or IP Address in the Computer 2 Show Options 3 Click on Local Resources Tab 4 In Local Devices and resources section, disable Printers 5 Hit connect button Conclusion Since a number of you may be upgrading from XP due to the End of Support in this coming April, thought I'd add this tidbit to alleviate any aggravation. 7 Comments Pure Capsaicin Little Green Man Dec 24, 2013 at 08:17pm Good info, but your formatting is way off. Try breaking it down into steps using the formatting tools. Pimiento egberto7453 Jan 15, 2014 at 07:34pm Is there anything new on this? I cannot uncheck the printers because it's the most important resource I need.. :/ Serrano Frank B. Jun 26, 2014 at 12:23am Interestingly enough, this suggestion helped resolve the error I was experiencing with remote users connecting to a Windows Server 2012 R2 with remote desktop services enabled. I don't know if not having printers shared and available through RDP will be a pro
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top MSTSC crash on connect up vote 5 down vote favorite 3 We are supporting a client with primarily Windows XP machines. The users need to use Remote Desktop to connect to a terminal server. Unfortunately, after upgrading to SP3 on some machines MSTSC.exe crashes when they try to connect to the terminal server (a Win 2008 machine). The resolution I have found has been to revert to an older version of MSTSC as described here: http://it.tmod.pl/Blog/EntryId/115/Remote-Desktop-Connection-crashes.aspx . Another tech at my company independently arrived at a similar solution. Unfortunately, now some of the user's printers are missing (when connected tot he terminal server). Has anyone else seen this issue? How did you resolve it? windows-xp rdp terminal-server mstsc share|improve this question asked Jun 23 '09 at 13:39 rotard 2331314 Rotard- Can you post the event log that corresponds with the crash? That will help pinpoint which module is faulting. Are you using a program called triCerat Screwdrivers by any chance? –Sean Earp Jun 24 '09 at 23:43 add a comment| 5 Answers 5 active oldest votes up vote 5 down vote i had similar problem, try this: remove content of C:\Documents and Settings\us