Jump to content
The simFlight Network Forums

Recommended Posts

Posted

For three weeks I've been trying to get my FSX on my new pc to work with PMDG 737NGX. I could not load a PMDG aircraft without FSX crashing after 3 % loading.

There's nothing else installed : just FSX (with acceleration) and the PMDG 737NGX.

I could load the default trike and switch to the NGX , save it, end the flight, try to load it : crash

I had a lot of hardware connected which I removed : all was well. I then enabled all hardware one by one and still everything kept working : I could build a flight, save it, restart the computer and load it again : great.

I tried again without changing anything a few days later : at 3 % loading : crash.

I followed the AVSIM crash guide which led me to the point of disabling modules and see if any of these would be the culprit. Lo and behold : I disabled the FSUIPC module and everything worked. I deleted the FSUIPC.ini and everything worked. I then pasted the key assignments from the saved FSUIPC.ini in the new one and FSX crashed again.

My question : is it really the key assignments that's crashing my pc ? I somehow suspect it's something to do with dodgy add-on hardware in wich case I'm out of my depth.

 

I hope Pete or someone can point me in the right direction.

 

cheers

 

Martin

Posted

I followed the AVSIM crash guide which led me to the point of disabling modules and see if any of these would be the culprit. Lo and behold : I disabled the FSUIPC module and everything worked. I deleted the FSUIPC.ini and everything worked. I then pasted the key assignments from the saved FSUIPC.ini in the new one and FSX crashed again.

My question : is it really the key assignments that's crashing my pc ? I somehow suspect it's something to do with dodgy add-on hardware in wich case I'm out of my depth.

 

More information needed I'm afraid. Key assignments themselves can't crash anything because they do nothing unless you actually press the key.

 

First, make sure your FSUIPC4 is up to date -- see the Download Links subforum above. Then show me an FSUIPC log file for a session which crashed, and also your FSUIPC4.INI file. You can paste both here -- use the <> button above the edit area to enclose the text from the files.

 

Pete

Posted

Pete, thanks for your answer, I hope you had a nice holiday.

My FSUIPC is up to date

Here's my FSUIPC.ini :

[General]
UpdatedByVersion=4934
History=MV78QUYMX68RZOAT4KDY8
InitDelayDevicesToo=No
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
DeleteVehiclesForAES=Yes
AutoScanDevices=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=No
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=No
SuppressWindVariance=No
WindTurbulence=No
TurbulenceRate=1.0,5.0
TurbulenceDivisor=20,20,40,40
SuppressAllGusts=No
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
SmoothBySimTime=No
WindSmoothing=No
WindSmoothness=2
WindSmoothAirborneOnly=Yes
PressureSmoothness=0
TemperatureSmoothness=0
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
OwnWeatherChanges=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=Yes
OOMcheck=Yes
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
LuaRerunDelay=66
Console=No
FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0
SimConnectUsed=10.0.61259.0

[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight Yoke
0.GUID={84F6EDF0-1708-11E4-8001-444553540000}
2=Saitek Pro Flight Rudder Pedals
2.GUID={00DDA6C0-1731-11E4-8003-444553540000}
3=UnoJoy Joystick
3.GUID={00DDA6C0-1731-11E4-8004-444553540000}
4=UnoJoy Joystick
4.GUID={00DDA6C0-1731-11E4-8005-444553540000}
1=BU0836X Interface
1.GUID={37E14950-1719-11E4-8005-444553540000}
5=G-Throttles
5.GUID={A080BF00-171D-11E4-8007-444553540000}

[Buttons]
ButtonRepeat=20,10
1=P4,12,K50,9
2=P4,13,K51,9
3=P4,14,K52,9
4=P4,15,K53,9
5=P4,16,K54,9
6=P4,17,K55,9
7=P4,18,K56,9
8=P5,4,C66068,0
9=P5,2,K113,11
10=U5,2,K112,11
11=P5,3,K115,11
12=U5,3,K114,11
13=P5,5,K71,11
14=P0,0,K49,11
18=P1,7,C70087,2
19=P1,6,C70087,0
20=R5,0,C65602,0
21=U5,0,C65697,0
22=P1,5,CM1:1,0
23=P1,0,K50,11
24=P1,3,K77,11
25=P1,4,K78,11
26=P1,1,C65752,0
27=P1,2,C65752,0
28=U1,6,C74183,1

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes
AdvertiseService=1
Port=8002
Port2=9002

[Sounds]
Path=D:\FSX\Sound\
Device1=Primary Sound Driver
Device2=Realtek Digital Output(Optical) (Realtek High Definition Audio)
Device3=Realtek Digital Output (Realtek High Definition Audio)

[Axes]
RangeRepeatRate=10
0=0X,1,D,1,0,0,0
1=0Y,1,D,2,0,0,0
2=2X,1,D,7,0,0,0
3=2Y,1,D,8,0,0,0
4=2R,1,D,3,0,0,0
5=5X,1,D,9,0,0,0
6=5Y,1,D,10,0,0,0
7=5Z,1,D,23,0,0,0
8=5U,1,D,22,0,0,0

[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
Aileron=-16384,0,0,16256
Elevator=-16384,0,512,16383
Rudder=-16384,0,512,16383
Throttle1=-16384,-512,512,16299/32
Throttle2=-16384,-512,512,16214/32
Spoilers=-16384,16383
Flaps=-16350,16350
LeftBrake=-16384,16383/16
RightBrake=-16380,16380/16
SlopeThrottle1=10
SlopeThrottle2=10
SlopeRudder=7

[MacroFiles]
1=tcas

[Keys]
1=65,11,1092,0

And the FSUIPC.log from the time of the crash. :

********* FSUIPC4, Version 4.934 by Pete Dowson *********
Reading options from "D:\FSX\Modules\FSUIPC4.ini"
Running inside FSX on Windows 7
Module base=6E1E0000
User Name="Martin Bunjes"
User Addr="mbunjes@chello.nl"
FSUIPC4 Key is provided
WideFS7 Key is provided
        0 System time = 17/08/2014 15:58:13
        0 FLT UNC path = "D:\Documents\Flight Simulator X Files\"
      717 Trying to connect to SimConnect Acc/SP2 Oct07 ...
      717 FS UNC path = "D:\FSX\"
      858 LogOptions=00000000 00000001
      858 SIM1 Frictions access gained
      858 Wind smoothing fix is fully installed
      858 G3D.DLL fix attempt installed ok
      858 SimConnect_Open succeeded: waiting to check version okay
      858 Trying to use SimConnect Acc/SP2 Oct07
     2246 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
     2246 Initialising SimConnect data requests now
     2246 FSUIPC Menu entry added
     2277 D:\FSX\FLIGHTS\OTHER\FLTSIM.FLT
     2277 D:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
    10452 D:\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.AIR
    10452 Weather Mode now = Theme
    10452 d:\documents\flight simulator x files\ktnt.FLT

Posted

Okay. This points to a corrupted weather file, probably associated with flight KTNT.FLT.  There are two crucial weather files which are used by SimConnect as soon as FSUIPC starts asking for weather data -- the WX file associated with the flight being loaded, and WXStationList.BIN. The WX files are stored next to your FLT files, usually in your FSX documents folder, and the WXStationList.BIN file is in the same folder as your FSX.CFG file. I suggest you delete both. The BIN file will be rebuilt by FSX, and the WX file won't matter if you are using a weather program or some other weather source and don't need the weather saved with the flight.

 

You might also delete the WX file associated with the default flight (D:\FSX\FLIGHTS\OTHER\FLTSIM.WX), although I doubt that this is at fault.

 

Pete

Posted

Deleted both KTNT.wx and WXstationlist.bin

 

Tried loading the saved KTNT flight : FSX crashed at 3%

 

Martin

 

If FSUIPC's log reaching the exact same point?

 

Have you any information about the crash. If it's a normal WQindows reported crash there will be module name and offset details, and an error code. Try looking at the Windows event viewer, application logs. There will be a record, with details, of each crash.

 

Also, it does sound rather like some other corruption in that Flight file. Try creating a new one.

 

Pete

Posted

Here's the information from the event viewer :

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: PMDG_737NGX.DLL, version: 1.0.0.0, time stamp: 0x4f5162a3
Exception code: 0xc0000005
Fault offset: 0x00016c30
Faulting process id: 0x84c
Faulting application start time: 0x01cfba36ffc1c6de
Faulting application path: D:\FSX\fsx.exe
Faulting module path: D:\FSX\GAUGES\PMDG_737NGX.DLL
Report Id: 450896c6-262a-11e4-b169-74d435e52476

I can't create a new flight with the 737NGX : when I choose the airport, the gate or parking, the PMDG aircraft and press fly now, FSX crashes after 3 %

I can create one with the default ultralight, change to the NGX and fly. After saving the same crashes occur. However when i delete the FSUIPC.ini everything works as it should.

Posted

Here's the information from the event viewer :

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: PMDG_737NGX.DLL, version: 1.0.0.0, time stamp: 0x4f5162a3
Exception code: 0xc0000005
Fault offset: 0x00016c30
Faulting process id: 0x84c
Faulting application start time: 0x01cfba36ffc1c6de
Faulting application path: D:\FSX\fsx.exe
Faulting module path: D:\FSX\GAUGES\PMDG_737NGX.DLL
Report Id: 450896c6-262a-11e4-b169-74d435e52476

I can't create a new flight with the 737NGX : when I choose the airport, the gate or parking, the PMDG aircraft and press fly now, FSX crashes after 3 %

I can create one with the default ultralight, change to the NGX and fly. After saving the same crashes occur. However when i delete the FSUIPC.ini everything works as it should.

 

Okay. It's an access violation in the PMDG module identified. You need to report this problem to PMDG because the crash is actually in their DLL. Maybe you could try uninstalling and re-installing the 737NGX first, because it could be a corruption, but if it is a bug then only they can track it because they have the source code and can pin-point the position of the error in their DLL from the information above.

 

I suspect the fact that it only crashes when FSUIPC is setup just so is to do with memory patterns or timing. This is often the way with some bugs, especially those involving unintentionally using uninitialised variables. But without something actually wrong with PMDG_737NGX.DLL (maybe only your copy, through corruption), there's no way anything in FSUIPC can cause that DLL to crash.

 

Pete

Posted

Thanks for your time and effort Pete.

I already reinstalled the PMDG twice so it could indeed be in my copy.

I'll submit a ticket to PMDG.

 

Martin

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.