This error started popping up a couple of days ago and I can't get rid of it. FSX loads on Win7 PC, flt plan selected, go to parking, bring up RC4, and all seems ok. RC4 flt plan loaded and RC4 started as usual but within a few minutes I hear "ding" and RC is no longer working. The reason is always the same: run-time error 76...... fsuipcRC4code." I have not changed any settings that I know of.Today, I reinstalled fsuipc 4.7, and the latest makerunways, then ran makerunwys both within FSX and from within RC4 but no fix from that.Should I uninstall/reinstall RC4? or is there something else to try first?This is a completely new problem to me. RC4 has been on this PC for months without problems.Thanks for any help.Neal H

http://forum.simflight.com/topic/66139-updated-modules/ and get 4.705 just to be up to date. Read the notes on 4.705 on that page.Can you describe what phase RC4 is in when the error occurs? Does it happen with a different flight plan? Do you get it just running RC and FSX with a default aircraft without any other add-ons running? Does it happen if you decrease your AI percent?If we still need to troubleshoot, then start FS, load your flight ready to go, and then RC, click debug, load your flight plan, and run RC until you get the error. If RC is still running alt-tab to it and hit quit. Then follow the instructions about sending the log in as pinned at the forum top.I assume you have started FSX and RC with shortcuts and their advanced properties set to run as admin.In all of your security application RC and FSX must be set as trusted applications. Since the error doesn't show up until a few minutes in if it seems to be time sensitive but not involved with any particular function I'd check your security settings.http://forum.avsim.net/topic/329362-runtime-error-76/page__p__1942297__hl__run-time+error__fromsearch__1#entry1942297An RC4 reinstallation should not be necessary.See if any additional application is loading down your CPU.

This error started popping up a couple of days ago and I can't get rid of it. FSX loads on Win7 PC, flt plan selected, go to parking, bring up RC4, and all seems ok. RC4 flt plan loaded and RC4 started as usual but within a few minutes I hear "ding" and RC is no longer working. The reason is always the same: run-time error 76...... fsuipcRC4code." I have not changed any settings that I know of.Today, I reinstalled fsuipc 4.7, and the latest makerunways, then ran makerunwys both within FSX and from within RC4 but no fix from that.Should I uninstall/reinstall RC4? or is there something else to try first?This is a completely new problem to me. RC4 has been on this PC for months without problems.Thanks for any help.Neal H

did you change antivirus programs? update to antivirus program?it's a permissions problem, often times because an antivirus program will allow rc to run for a while, then decide, it looks to much like a virus. then it denies me read/write access where i used to have itif that doesn't help, make a log, instructions pinned to the top of the forum. duplicate the problem, and email me the log, zipped.also make sure you don't have any special characters in the departure or arrival gates.jd

The Problem is Solved and it doesn't make any sense to me. I cloned my hard drive last week from an SSD to a WD Raptor (need more space). After the RC4 problem started several other add-ons began erratic ops and a couple would not work at all. Yesterday, after RC4 started getting ERROR 52, I put the original drive back in place and everything is now operating the way it is supposed to.I thought a clone was supposed to be identical to the original :(

It depends which drive your cloning and whether your clone program supports SSD to HD cloning. If you have multiple drives and you are are cloning your second volume you need to insure drive data kept in the registry hasn't changed for drive assignments and your cloned drive does indeed have the same drive letter assigned to the cloned volume/partitions.It sounds like you may need to perhaps change some options in your cloning program. Some RAW cloners use direct calls to the drives BIOS (built in to the drive's firmware, not your motherboard BIOS). If you are cloning from one type of drive to another, not a similar type, that could be a problem. I'm not familiar with at the BIOS level how an SSD looks compared to an HD.I use Win XP SP3 and use a cloning application that boots from a CD. They upgraded the version to include VISTA and Win 7 plus XP and it created a clone that would not boot unless I used an emergency boot floppy. Apparently it assumed I had default Win 32 cluster sizes and it did some rounding and padding on the clone. I did specify AS IS cloning without partition/cluster realignment. They replicated the error in their lab and now, nine months later, it is ready for release in the next upgrade they say. I will give them credit in keeping me informed. I did supply them with several diagnostic dumps for utilities they provided.So it depends on the physics of the drives and the cloning coding. If this is a cloner that creates a compressed image and then decompresses to your raw clone it depends exactly on how they do it.I guess this is now an issue for some hardware forum.Anyway, I'm glad you found your problem and got back to an operating system.

The Problem is Solved and it doesn't make any sense to me. I cloned my hard drive last week from an SSD to a WD Raptor (need more space). After the RC4 problem started several other add-ons began erratic ops and a couple would not work at all. Yesterday, after RC4 started getting ERROR 52, I put the original drive back in place and everything is now operating the way it is supposed to.I thought a clone was supposed to be identical to the original :(