vstuart
new Members-
Posts
4 -
Joined
-
Last visited
Profile Information
-
Gender
Male
-
Location
London
vstuart's Achievements
Newbie (1/14)
0
Reputation
-
Hi Pete, I haven't experienced any new problems since testing 4.838, but I still intermittently get BSODs - I believe that this is nothing to do with FSUIPC and is more likely due to an unstable overclock on my new rig. I can't remember ever enabling joystick filtering, but here's my FSUIPC4.ini just in case (N.B. the batch file at the end is re-enabling Windows 7 DWM as per http://forum.avsim.n...-windowed-mode/): [General] UpdatedByVersion=4838 History=U3T2F1M1QU49F70MUZSDE 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=Yes MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=Yes SuppressWindVariance=Yes WindTurbulence=No TurbulenceRate=0.5,2.5 TurbulenceDivisor=40,40,80,80 SuppressAllGusts=Yes 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=No UseProfiles=Yes EnableMouseLook=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.61472.0 SimConnectUsed=10.0.61259.0 [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Rudder Pedals 0.GUID={13546BB0-B0E3-11E1-8001-444553540000} 1=Saitek Pro Flight Yoke 1.GUID={13546BB0-B0E3-11E1-8002-444553540000} [Buttons] ButtonRepeat=20,0 1=P1,14,C66079,0 2=P1,15,C66080,0 3=P1,18,C65759,0 4=P1,19,C65758,0 5=R1,16,C65607,0 6=R1,17,C65615,0 7=P1,6,K123,8 8=P1,7,K120,8 9=P1,20,C65966,0 10=U1,20,C65967,0 11=P1,20,C65971,0 12=U1,20,C65972,0 13=P1,21,C65976,0 14=U1,21,C65977,0 15=P1,21,C65981,0 16=U1,21,C65982,0 17=P1,32,C65875,0 18=R1,33,C65856,0 19=R1,34,C65672,0 20=R1,35,C65857,0 21=R1,36,C65735,0 22=R1,37,C65855,0 23=R1,38,C65671,0 24=R1,39,C65854,0 25=P1,1,K90,14 26=P1,0,K65,14 27=P1,2,K88,14 28=P1,3,K83,14 [AutoSave] Next=1 Interval=1800 Files=1 SaveOnGround=No AutoSaveEnabled=Yes AlsoManage1=PMDG\747400\PanelState\*.FLT.sav AlsoManage2=PMDG\747400\PanelState\*.FLT.0.rte AlsoManage3=PMDG\747400\PanelState\*.FLT.1.rte 1=Sat 172533 [GPSout] GPSoutEnabled=No Port=COM0 Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [WideServer] WideFSenabled=Yes [Sounds] Path=C:\FSX\Sound\ Device1=Primary Sound Driver Device2=Speakers (ASUS Xonar Essence STX Audio Device) Device3=S/PDIF Pass-through Device (ASUS Xonar Essence STX Audio Device) [Axes] 0=0X,256,D,7,0,0,0 1=0Y,256,D,8,0,0,0 2=0R,256,D,3,0,0,0 3=1X,256,D,1,0,0,0 4=1Y,256,D,2,0,0,0 5=1Z,256,D,9,0,0,0 6=1U,256,D,10,0,0,0 [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No MapThr12to34=Yes 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,-1189,896,16383 Elevator=-16384,-642,576,16383 Rudder=-16384,-1871,2176,16383 LeftBrake=-16383,16384/16 RightBrake=-16383,16384/16 Throttle1=-16384,-512,512,16383/32 Throttle2=-16384,-512,512,16383/32 [Programs] Run1=HIDE,"C:\FSX\fsx.bat" [/CODE]
-
No AppHangB1s so far with 4.838 on the two flights I've tried where I would've expected it happen from experience with previous versions of 4.8xx. Will report back if the AppHangB1 freeze manifests again. Thanks for the support on this one Pete! Regards, Vince
-
Thanks for replying Pete. I lowered some sliders but the problem still persists. I dumped the fsx.exe process after tonight's crash (this time occurring at touchdown at Flightbeam KSFO, but it's happened at default airfields too) and ran it through WinDbg - here's the analysis: FAULTING_IP: +0 00000000 ?? ??? EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 0000000000000000 ExceptionCode: 80000003 (Break instruction exception) ExceptionFlags: 00000000 NumberParameters: 0 FAULTING_THREAD: 00000000000012d4 DEFAULT_BUCKET_ID: STATUS_BREAKPOINT PROCESS_NAME: fsx.exe ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached. EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid APPLICATION_VERIFIER_FLAGS: 0 PRIMARY_PROBLEM_CLASS: STATUS_BREAKPOINT BUGCHECK_STR: APPLICATION_FAULT_STATUS_BREAKPOINT LAST_CONTROL_TRANSFER: from 0000000077a28df4 to 0000000077a0f8b1 STACK_TEXT: 000ceb38 77a28df4 000024d4 00000000 00000000 ntdll_779f0000!NtWaitForSingleObject+0x15 000ceb9c 77a28cd8 00000000 00000000 00000000 ntdll_779f0000!RtlpWaitOnCriticalSection+0x13e 000cebc4 610067f9 610f12b4 000100e3 7906b980 ntdll_779f0000!RtlEnterCriticalSection+0x150 WARNING: Stack unwind information not available. Following frames may be wrong. 000ced00 610085c0 000ced2c 000ced30 000ced34 FSUIPC4+0x67f9 000ced24 61036877 000100e3 fffffeea ffffffff FSUIPC4+0x85c0 000cfb1c 07074292 7906b980 00000018 00000000 FSUIPC4!ExGenAddMenu+0xb00c 000cfb3c 07077ead 09496da8 61035a44 00000000 SimConnect+0x4292 000cfb58 610376c0 09507c50 61035a44 00000000 SimConnect!SimConnect_CallDispatch+0x1d 000cfbec 75ef62fa 00050a88 00000400 00000000 FSUIPC4!ExGenAddMenu+0xbe55 000cfc18 75ef6d3a 61037690 00050a88 00000400 user32!InternalCallWinProc+0x23 000cfc90 75f00d27 00000000 61037690 00050a88 user32!UserCallWinProcCheckWow+0x109 000cfcc8 75f0794a 61037690 00050a88 00000400 user32!CallWindowProcAorW+0xab 000cfce8 71d11867 61037690 00050a88 00000400 user32!CallWindowProcA+0x1b 000cfd5c 75ef62fa 00050a88 00000400 00000000 mfc80!_AfxActivationWndProc+0x11c [f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\wincore.cpp @ 449] 000cfd88 75ef6d3a 71d1174b 00050a88 00000400 user32!InternalCallWinProc+0x23 000cfe00 75ef77c4 00000000 71d1174b 00050a88 user32!UserCallWinProcCheckWow+0x109 000cfe60 75ef7bca 71d1174b 00000001 000cfea0 user32!DispatchMessageWorker+0x3bc 000cfe70 20111f4f 00271150 010043e0 010043e0 user32!DispatchMessageA+0xf 000cfea0 2012da10 8df6590c 010043e0 010043e0 api!Ordinal16+0x2839 000cfed0 20111bdd 20111e90 000cff88 01001d19 api!Ordinal221+0x229c 000cfedc 01001d19 01001cf0 010043e0 71d1ccec api!Ordinal16+0x24c7 000cff88 76e4339a fffde000 000cffd4 77a29ef2 fsx+0x1d19 000cff94 77a29ef2 fffde000 771d9d1d 00000000 kernel32!BaseThreadInitThunk+0xe 000cffd4 77a29ec5 0100262e fffde000 00000000 ntdll_779f0000!__RtlUserThreadStart+0x70 000cffec 00000000 0100262e fffde000 00000000 ntdll_779f0000!_RtlUserThreadStart+0x1b STACK_COMMAND: ~0s; .ecxr ; kb FOLLOWUP_IP: FSUIPC4+67f9 610067f9 ff75f0 push dword ptr [ebp-10h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: FSUIPC4+67f9 FOLLOWUP_NAME: MachineOwner MODULE_NAME: FSUIPC4 IMAGE_NAME: FSUIPC4.DLL DEBUG_FLR_IMAGE_TIMESTAMP: 4fcf4463 FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_FSUIPC4.DLL!Unknown BUCKET_ID: X64_APPLICATION_FAULT_STATUS_BREAKPOINT_FSUIPC4+67f9 WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/fsx_exe/10_0_61472_0/475e17d3/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1 Followup: MachineOwner --------- [/CODE] Hopefully that's helpful. I forgot to make a copy of the FSUIPC4.log file before restarting FSX, so I shall make sure to post that on the next crash. Vince
-
Hi Pete, Since I updated FSUIPC from 4.728b to 4.81 a couple of months ago, I have been unable to complete a flight due to FSX crashing with the Event Name "AppHangB1". Since installing a fresh copy of FSX on a completely new computer alongside FSUIPC 4.833, I have been experiencing the same error. Here's an example of one such error log: Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\FSX\fsx.exe Problem signature Problem Event Name: AppHangB1 Application Name: fsx.exe Application Version: 10.0.61472.0 Application Timestamp: 475e17d3 Hang Signature: 3a86 Hang Type: 0 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 2057 Additional Hang Signature 1: 3a8652692d78569f1083282d4d2bfaa4 Additional Hang Signature 2: eb97 Additional Hang Signature 3: eb977c59f3d4ba37a66e0c3e48bd4160 Additional Hang Signature 4: 3a86 Additional Hang Signature 5: 3a8652692d78569f1083282d4d2bfaa4 Additional Hang Signature 6: eb97 Additional Hang Signature 7: eb977c59f3d4ba37a66e0c3e48bd4160[/CODE] which seems to be fairly unhelpful. The crash only seems to occur at the beginning or end of a flight, and even in almost the same location at UK2000's EGLL when I fly from there. Reverting to the old copy of FSUIPC (4.728b) clears up my issues with this particular error, but sadly I've now experienced a crash due to g3d.dll for the first time ever! I don't know if this is relevant or not, but I only fly the PMDG 747-400X, and I use Saitek's Yoke/Quadrant/Rudder all calibrated through FSUIPC. Thanks for your time, Vincent Stuart