RC stop working+CTD

[asanal 32]

I am experiencing a new problem..I am trying to use RC contact with PMDG 737 NGX. Keep getting the following error message and FSX crashes.Will you please advise how can I solve this problem,Thanks DescriptionA problem caused this program to stop interacting with Windows.Faulting Application Path: D:\Radar Contact\rcv4x\rcv4.exeProblem signatureProblem Event Name: AppHangB1Application Name: rcv4.exeApplication Version: 4.3.0.3845Application Timestamp: 45cb842dHang Signature: 555fHang Type: 0OS Version: 6.1.7600.2.0.0.256.1Locale ID: 1033Additional Hang Signature 1: 555fc8132c2e1d54821f0ea65ffc4668Additional Hang Signature 2: 5cfeAdditional Hang Signature 3: 5cfe69ae665971cc56fa13261fd75c77Additional Hang Signature 4: 555fAdditional Hang Signature 5: 555fc8132c2e1d54821f0ea65ffc4668Additional Hang Signature 6: 5cfeAdditional Hang Signature 7: 5cfe69ae665971cc56fa13261fd75c77

[ronzie 21]

Is it just the NGX? While I believe it does not use FSUIPC4 check that version number in your modules folder. It should be as of today FSUIPC4 update 4.722 FSUIPC 4.722. See the links pinned topic. Now FSUIPC4 accesses FSX via SimConnect so there might be a problem there. In addition if you recently did a Win VISTA upgrade they added some certificate checking so find your Win certificates tab and insure FSX and RCv4 exes are permitted without a check. Does it happen as soon as you click the start button in RC (with your NGX up and parked somewhere running in FSX)? The only way RC connects with FS is via FSUIPC4 for FSX. The NGX does use a lot of resources. RC is a low resource user. Make sure you have sufficient RAM and close any not needed applications. Also:http://forum.simflight.com/topic/69049-pmdg-737-ngx-and-fsuipc/

[asanal 32]

Ron,Thank you for your reply. 1- I have FSUICP 4.703. I will update to 4.722. 2-No Vista 3-NO, it happens after take-off or during the CRZ. 4- I have 6GB memory. Do you think I should increase to 8GB ? 5-http://forum.simflig...ngx-and-fsuipc/ It is very informative , but Pete Dawson's explanations are much technical then my PC level of knowledge' 6-Tonight I made a flight again, with PMDG737NGX KJFK-KMCO I received RC error and in my second attempt, I received the following error: DescriptionFaulting Application Path: D:\FSX\fsx.exeProblem signatureProblem Event Name: BEXApplication Name: fsx.exeApplication Version: 10.0.61637.0Application Timestamp: 46fadb14Fault Module Name: unknownFault Module Version: 0.0.0.0Fault Module Timestamp: 00000000Exception Offset: 2b5d4801Exception Code: c0000005Exception Data: 00000008OS Version: 6.1.7600.2.0.0.256.1Locale ID: 1033Extra information about the problemLCID: 1033

[ronzie 21]

ok, you have Win 7. First, RC failed. Your next failure was FSX. The exception failure code in your FSX failure indicates FSX was going into an illegal part of RAM. If you alt-tab around on an RC hang do you see any other error windows possibly buried under the FSX window? RC4 will hang if FSX terminates abnormally and you can't alt-tab to RC to use the Quit button. You can then only delete the RC application in the task manager. The error messages regarding RC state it is a hung application. You have plenty of RAM. So far you state it only happens with the NGX in the air. Operating with another aircraft on the same flight plan do things go OK? What other applications are running at the same time? Try some tests to keep it simple: First just use FSX and the 737NG. Second add RC to the mix. Don't run any weather add-ons or FSX real weather. If you get a crash try using a different route to insure it is not a scenery issue. A good short one is KMSP to KMDW such as this route: KMSP FGT SHUZE UKN DBQ CVA CVA42 BDF MOTIF MINOK JOT KMDW. 31,000 feet (FL 310) should do it. This is the KMSP DP (SID) UKN3.DBQ to the CVA VOR and then a DME off it to BDF VOR entering the MOTIF STAR for KMDW. Here is the plan in FS9 format: [flightplan]title=KMSP to KMDWdescription=KMSP, KMDWtype=IFRroutetype=3cruising_altitude=29000departure_id=KMSP, N44* 52.55', W093* 13.18',+000841.00departure_position=30Ldestination_id=KMDW, N41* 47.09', W087* 45.08',+000620.00departure_name=MINNEAPOLIS-ST_PAUL_INTL/WOLD-destination_name=CHICAGO_MIDWAY_INTLwaypoint.0=KMSP, A, N44* 52.55', W093* 13.18', +000000.00,waypoint.1=FGT, V, N44* 37.51', W093* 10.55', +06000.00,waypoint.2=SHUZE, I, N44* 21.27', W092* 50.26', +14000.00,waypoint.3=UKN, V, N43* 16.48', W091* 32.14', +29000.00,waypoint.4=DBQ, V, N42* 24.05', W090* 42.32', +29000.00,waypoint.5=CVA, V, N41* 42.30', W090* 28.59', +29000.00,waypoint.6=CVA42, I, N41* 15.55', W089* 45.43', +29000.00,waypoint.7=BDF, V, N41* 09.35', W089* 35.16', +29000.00,waypoint.8=MOTIF, I, N41* 13.46', W088* 30.03', +18000.00,waypoint.9=MINOK, I, N41* 28.07', W088* 21.47', +12000.00,waypoint.10=JOT, V, N41* 32.47', W088* 19.06', +11000.00,waypoint.11=KMDW, A, N41* 47.09', W087* 45.08', +000000.00, which I fly in the FS9 PMDG 737NG. CVA42 may be left out if you are creating the plan. Don't paste in the plan above if you do drop it. Here is a real Southwest Airlines filed route and translated to waypoints: KMSP UKN3 DBQ CVA MOTIF3 KMDW Name Type Latitude Longitude KMSP Origin Airport 44.8819567 -93.2217656FGT VOR-TAC (NAVAID) 44.6309444 -93.1820556LOAFR Reporting Point 44.4695278 -92.9799444 SHUZE Reporting Point 44.3575556 -92.8406944 BROTA Reporting Point 44.2205000 -92.6711667 UKN VOR-TAC (NAVAID) 43.2800833 -91.5373611 ( ARTCC Boundary Crossing not a waypoint 43.0932778 -91.3588056) CASSY Reporting Point 42.7446389 -91.0291389DBQ VOR-TAC (NAVAID) 42.4014722 -90.7090833 CVA VOR-TAC (NAVAID) 41.7085556 -90.4833056 BDF VOR-TAC (NAVAID) 41.1597222 -89.5878611 MOTIF Reporting Point 41.2295833 -88.5010000 MINOK Reporting Point 41.4688611 -88.3632778 JOT VOR-TAC (NAVAID) 41.5464167 -88.3184167 KMDW Destination Airport 41.7859722 -87.7524167 Where it states Reporting Point they are referring to an intersection. FL310 was filed for cruise. You can use this one hour flight as a test for the different conditions. This relocates your flight in case it is another issue perhaps with scenery or AI. Some virus checkers check for updates every fifteen minutes or so and might interfere with FS. Norton is one. You can try running a log in RC but if it crashes it may not save things. The new PMDG 737NGX forum in the PMDG support forum on AVSIM might have answers for you. It seems to be system dependent. According to Pete Dowson there may be system timing issues causing SimConnect errors if I recall. I think the hang error in RC is just a symptom, not the error, being triggered by an FSX failure.

[ubersu 78]

Ron,Thank you for your reply. 1- I have FSUICP 4.703. I will update to 4.722. 2-No Vista 3-NO, it happens after take-off or during the CRZ. 4- I have 6GB memory. Do you think I should increase to 8GB ? 5-http://forum.simflig...ngx-and-fsuipc/ It is very informative , but Pete Dawson's explanations are much technical then my PC level of knowledge' 6-Tonight I made a flight again, with PMDG737NGX KJFK-KMCO I received RC error and in my second attempt, I received the following error: DescriptionFaulting Application Path: D:\FSX\fsx.exeProblem signatureProblem Event Name: BEXApplication Name: fsx.exeApplication Version: 10.0.61637.0Application Timestamp: 46fadb14Fault Module Name: unknownFault Module Version: 0.0.0.0Fault Module Timestamp: 00000000Exception Offset: 2b5d4801Exception Code: c0000005Exception Data: 00000008OS Version: 6.1.7600.2.0.0.256.1Locale ID: 1033Extra information about the problemLCID: 1033

Just a suggestion - run FSX and RC from the right click menu item 'run as administrator'; this should eliminate any possible permission issues.... DJ

[asanal 32]

Ron,Today. I will do test flights as you recommended and will inform the resultsDJ.I am not so sure, but I usually start with right click.THX

[ronzie 21]

If DJ's suggestion works set up your shortcut for RC and FSX. Right click on those and in its advanced proprties set it to run as admin. Now this elevates privileges of the actual application and is different than user access rights.

[asanal 32]

Today I made four flights from KMSP to KMDW with same flight plan you provided to me. First Flight 1- PMDG 737 NGX, no-Addons ( RC/FS Weather/REX/FsPassengers). Climbing to FL 310, FSX freeze at FL210. ( This is known issue at PMDG 737NGX forums. One member said, when he saw FSX freeze, He hear 737NGX sounds are continuing,He waited 10 minutes ,then suddenly FSX started. , I watied 12 minutes suddenly my full screen mode switched to Windowed screen mode and FSX started and arrive at KMDW with out CTD. Second Flight 1- 737 NGX with only RC. 737NGX arrived at KMDW with out CTD Third Flight 1-737 NGX with RC & FsPassangers.During the taxi CH Yoke/Pedals stop working.Also 737 NGX sound faded away.( Yesterday when I was reviewing FSUIPC4 update 4.722 . If I understood correctly FSUIPC mixing up with controls.a- I opened the CH Control Manager>Test/Calibration>Click Rescan for CH Flight Sim Yoke and Pro Pedals. 737 NGX controls again activated. Flight arrived at KMDW without CTDb- For sound solution , I opened FSX Setting Sound screen. I noticed Windows sound section switched back to Default Sound audio for Speakers and Microphone. I again switched back to "Sound PlasterX-Fi extrema Audio" 737NDX sound back.Arrived at KMDW with out CTD, (Sound lost possibly caused by FSUIPC) Forth Flight1-737NGX with RC,FsP/REX during the crz flight controls off. I went to same procedure with CH to activate the 737NGX sounds, Flight arrived at KMDWa- I will avoid KJFK-KMCO route any longer,because my CTD experienced all happens on than route. Here is my report

[ubersu 78]

Today I made four flights from KMSP to KMDW with same flight plan you provided to me. First Flight 1- PMDG 737 NGX, no-Addons ( RC/FS Weather/REX/FsPassengers). Climbing to FL 310, FSX freeze at FL210. ( This is known issue at PMDG 737NGX forums. One member said, when he saw FSX freeze, He hear 737NGX sounds are continuing,He waited 10 minutes ,then suddenly FSX started. , I watied 12 minutes suddenly my full screen mode switched to Windowed screen mode and FSX started and arrive at KMDW with out CTD. Second Flight 1- 737 NGX with only RC. 737NGX arrived at KMDW with out CTD Third Flight 1-737 NGX with RC & FsPassangers.During the taxi CH Yoke/Pedals stop working.Also 737 NGX sound faded away.( Yesterday when I was reviewing FSUIPC4 update 4.722 . If I understood correctly FSUIPC mixing up with controls.a- I opened the CH Control Manager>Test/Calibration>Click Rescan for CH Flight Sim Yoke and Pro Pedals. 737 NGX controls again activated. Flight arrived at KMDW without CTDb- For sound solution , I opened FSX Setting Sound screen. I noticed Windows sound section switched back to Default Sound audio for Speakers and Microphone. I again switched back to "Sound PlasterX-Fi extrema Audio" 737NDX sound back.Arrived at KMDW with out CTD, (Sound lost possibly caused by FSUIPC) Forth Flight1-737NGX with RC,FsP/REX during the crz flight controls off. I went to same procedure with CH to activate the 737NGX sounds, Flight arrived at KMDWa- I will avoid KJFK-KMCO route any longer,because my CTD experienced all happens on than route. Here is my report

Well, I suspect that you have problems with the NGX that really don't have much to do with RC... from my own experience with RC (thousands of hours in FS9 and FSX) I'd say it's one of the most stable add-ons available. The NGX seems to cause issues on some systems that can cause problems all over the system - there is no way that your controller and sound should be affected by the plane or cause you to have to reset them in flight. Some of the issues that have been reported are very unclear as to cause and I suspect it's going to be awhile before they are sorted out. The BEX error code that you saw reported is one of those issues - it can happen with many programs in Windows and after much research, I'd have to say that no one, including Microsoft, is sure of the cause. My own belief is that is an indicator of general system instability. There are a couple of things to try - make sure that Windows UAC is off and DEP is off except for system modules. The Windows help file will tell you how if you are unfamiliar with these things. If you go into the control panel you should see your SoundBlaster listed as the default audio device - if you do not, then make it so. Oddly enough, I had some sound issues with the MD-11 and changing to the default setting in FSX cleared them up although I have no idea what the difference is between that and selecting the device directly. Hope some of this might help... DJ

[asanal 32]

You are right. I am utilizing RC maybe from day one. I never remember having a major problem with it. RC is one of the most stable add-ons in simworld. I cant say for NGX ,but I believe Developer will solve these problems..I checked control panel. SoundBalster selected as default device.Also UAC is OFF. I don't know where DEP located, but will find it.Thanks

[ronzie 21]

FSUIPC has nothing to do with sound. As far as controls it will not do anything unless you turn on those features and for that you would need a user paid registration version. The only FS wide control is the control filtering option which attempts to remove intermittent controller electronic noise from its own components or to spikes present in some USB components. Other controller settings can be mapped for all aircraft or specific to the one loaded at setup. Regarding your crash on the KJFK to KMCO route their might be several sources: 1. A scenery problem enroute usually with a texture. Airport scenery is loaded for some distance around your aircraft as is surface scenery.2. Encountering an AI aircraft with a bad texture. Many are loaded around your aircraft position.3. If on the NGX only something in its navaid database or terminal procedure database (FMC) looked at during the flight for this route.4. If on other aircraft then a flight plan problem. You might use a different season for the KJFK - KMCO route to see if that changes anything. That would change scenery textures. You could also try without AI enabled. The New York City area of three airports (JFK, LGA, and EWR) plus the smaller feeder airports is probably the most congested area for ai. Chicago is also heavily congested but not quite as bad. You have the two major airports in Chicago and then Milwaukee, Wisconsin and Gary, Indiana as major airports that can contribute to AI. These areas put a strain on FS resources.

[asanal 32]

Ron.Thank you for youm time. My FSX problem is no longer involve with RC forums. I will try to see, where I can get help.I have registered FSUIPC and didn't touch any things on FSUIPC except wind smoothing.I got another BEX error during the flight KJFK to KDMS at Fl310. DJ explained well. It looks like even Microsoft doesn't know the reason why BEX is pupping up.Unfortunately my luck, It selected my PC,One day if problem solution found I will inform you.Thanks again.