Mstsc Application Error The Instruction At
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 terminal server... she is the instruction at 0x referenced memory at now getting the following message: The instruction at "0x4d86bcfa" referenced memory at "0x00000000". The memory the instruction at referenced memory at arma 3 could not be "read" She has been able to connect by using the 'run as' option and putting her own network credentials the instruction at referenced memory at could not be written 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 should it be using? Application error the instruction at referenced memory at dayz 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 administrator, it sounds like it is a permissions problem. What
The Instruction At Referenced Memory At Windows 10
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 - the user was complaining so much about having to access via 'run as' I decided to restore machine
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: MSTSC Application Error Windows Server >
The Instruction At 0x00000000 Referenced Memory At 0x00000000 . The Memory Could Not Be Read
Remote Desktop Services (Terminal Services) Question 0 Sign in to vote I am the instruction at 0x00007f windows 10 having a strange problem with MSTSC, everytime a user tries running MSTSC it comes up with application error and the instruction at 0x00007 windows 10 closes on all the machines they are using. They do have a roaming profile, so I am wondering whether the profile is corrupt but how can it affect running MSTSC? I have https://community.spiceworks.com/topic/94810-mstsc-exe-application-error logged onto the machine and tried running MSTSC and it works but I do have admin rights. The OS is Windows XP SP3 and trying to connect to Server 2000. Wednesday, September 23, 2009 2:35 PM Reply | Quote Answers 0 Sign in to vote Hi,I got round the problem by creating a new profile and all seems fine now it must have got https://social.technet.microsoft.com/Forums/windowsserver/en-US/07628215-fa88-4fda-ba63-fba3a06a8216/mstsc-application-error?forum=winserverTS corrupted.The information from the Application Log just after it crashes in order:1 - ERROR: Faulting application mstsc.exe, version 6.0.6001.18000, faulting module mstscax.dll, version 6.0.6001.18266, fault address 0x0015bcfa.2 - INFORMATION: The application, C:\WINDOWS\system32\mstsc.exe, generated an application error The error occurred on 09/24/2009 @ 12:22:02.515 The exception generated was c0000005 at address 4D86BCFA (mstscax)3 - ERROR: Faulting application mstsc.exe, version 6.0.6001.18000, faulting module mstscax.dll, version 6.0.6001.18266, fault address 0x0015bcfa. Marked as answer by Fayraz Tuesday, September 29, 2009 8:30 AM Friday, September 25, 2009 3:03 PM Reply | Quote All replies 0 Sign in to vote Hi, The RD Client references some things in the user's roaming profile. For example, if you rename HKCU\Software\Microsoft\Terminal Services Client\ registry key in the problem user's profile and then have them launch mstsc does the problem remain?Another thing that roams is the default.rdp file, but I doubt that would cause crashing.It does not roam, but have you tried deleting their TS bitmap cache files? They are named bcache2.bmc, bcache22.bmc and are located under the user's local Application Data. If the above does not help you may be forced to give them a new profile.Thanks.-TP Wednesday, September 2
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 http://helpdeskgeek.com/help-desk/instruction-at-referenced-memory-could-not-be-read/ message that I have seen on a clients machine recently was: Instruction http://ask-leo.com/how_do_i_fix_the_instruction_at_referenced_memory_at_the_memory_could_not_be_read.html 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 the instruction a bunch of other stuff! With this type of error, you basically 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 the instruction at virtual memory settings are very low. You can right-click on My Computer, go to the Advanced tab, and 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
look at the other types of information that should accompany a general question such as this. by Leo A. Notenboom, © 2007 I keep getting an error which says: The instruction at 0x7c901010 referenced memory at 0x0000001c The memory could not be read. I was wondering if you could help me please. • Probably not. That error message, by itself, is kind of like taking your car to your auto mechanic and saying "something's broken". It's nowhere near enough information to even begin to have a clue as to what's going on. That mechanic is going to respond by asking you a bunch of questions. So will I. • The single most important question that I would ask first is this: What were you doing or trying to do when this happened? Your auto mechanic's probably going to ask a similar question. How's it broken? What were you doing when it broke? For your computer: Were you just sitting there and it popped up on its own? Does it happen only when you do certain things like browse the web or run a specific program? Can you reproduce it reliably, and if so what are the steps to doing so? All of that information is attempting to identify if perhaps a specific piece of software is causing the problem. Then, presumably, we might be able to repair that software. • My next question is equally important: What your computer's configuration? That auto mechanic has the luxury of seeing the car you brought in for service. When you ask someone a question on the internet, they can't see your computer, so you'll need to indicate just what it is your using. "Depending on the additional information you provide there might be more questions." Windows XP? SP2 installed? Windows Vista? How much memory is in your computer? Disk space? Free disk space? Anything that might be related to the answer to the first question? (for example if it only happens when you access a particular piece of hardware, what are the specifications for that hardware?) If the problem seems to be internet or mail related, what browser are you using? W