Solved Crash to Desktop Falcon BMS 4.37.3 Unplayable issue (LG 29WP60G-B Ultra Wide Monitor + Gigabyte GTX 1650 4GB GDDR6 Graphics Card )
-
@jayb said in Crash to Desktop Falcon BMS 4.37.3 Unplayable issue (LG 29WP60G-B Ultra Wide Monitor + Gigabyte GTX 1650 4GB GDDR6 Graphics Card ):
@john1974 Has anything changed regarding sound devices or cabling? Does it ctd in every training TE, for instance the ground ops one from ramp ?
no changes in sound devices and cabling, just switched video cards. Yes i tried all parts of the sim, from trainings to campaigns even dogfight, it CTD’s the moment it says ‘please wait until your cockpit is setup’ message.
I guess in future, it’s best that the BMS Launcher has the ability to do the automatic upload of the CTD crash dumps rather than having to discuss this and making guesses. I just thought i’d share this so the developers are aware of it. Even if they can also test it on the SAME machine as I have with the same Gigabyte GTX 1650 GDDR6 OC Low Profile video card brand, it would be great.
It’s a cheap PC, I mean for $50 dollars on eBay it’s a good buy to test it out, it’s only the video card that’s very expensive seeing that supply of parts is low due to the ongoing war and economic status.
Anyways, I will rerun the Stress test to push this beyond limits of the card, and see if it crashes my PC then I know that I got a defective card, but so far after the previous Stress tests i’ve done, the card Passed with no issues.
-
29 minutes of run on OCCT with error detection and the card is running well so far
as you can see at 100% load, draw power TDP is only at 64.2W, not even hitting the max 75W let alone going past that.
-
test completed…No Errors found, no crashes, no hangups
-
have u tried uninstall and re install?
Also u don’t have any crashlogs so something forcefully causes Falcon to crash.
It might help if you enable full crash dumps from windows.
https://forum.falcon-bms.com/topic/20866/enabling-dump-files-at-all-times-and-creating-frozen-game-dump-files -
@john1974 Yet when I load BMS 4.37.3.2, the moment it says… 'please wait until your cockpit is setup’, it goes into a FREEZE and then it CTD’s…
Did you consider to scale down to 4.37U3 ? just to make a move…
-
The reason for my inquiry wrt sound is that you actually make it into 3D. But once the script has run you ctd. That could be related to in-game sounds kicking off
-
@Arty I did set the crash logs and followed the guide…please see below:
-
@Coral36 yup i just did that as well…re-installed without the Hotfixes. Same issue CTD.
-
@john1974 sorry if I missed … did you try the max frame rate = 20 test?
just something easy to try, and should eliminate concern over power draw
-
Here’s a link to the Crash Dump, I zipped only 1 of the dump and uploaded to my dropbox just to see if anyone can help.
If any developer knows what’s going on, please help. Thanks.
Here’s a screenshot of the dumps being generated everytime it CTD’s
as for Logs, all it says “dtc_last_flight_faults.txt” with zero byte
-
Not specific to this issue but there has been a number of these CTD-with-no-logfile lately. It happened to me and on occasion someone reports a similar incident here. Really hard to figure out what happened. Could be issues in the hardware/driver layer sitting between BMS and Windows.
-
@jayb yes I’m taking a look at the dmp and this seems like something that should have generated a crash_log.txt file … meta-bug
-
Taking a look… it does appear to be a breakpoint exception on the render thread. Not sure cause yet, or why there’s no log generated.
0:031> !analyze -v ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 6233 Key : Analysis.Elapsed.mSec Value: 6658 Key : Analysis.IO.Other.Mb Value: 45 Key : Analysis.IO.Read.Mb Value: 261 Key : Analysis.IO.Write.Mb Value: 535 Key : Analysis.Init.CPU.mSec Value: 21781 Key : Analysis.Init.Elapsed.mSec Value: 1490868 Key : Analysis.Memory.CommitPeak.Mb Value: 291 Key : Failure.Bucket Value: BREAKPOINT_80000003_Falcon_BMS.exe!bp::RendererD3D11::executeCameraDrawList Key : Failure.Hash Value: {28a57d9b-e970-76f9-c752-9c3e55777f48} Key : Timeline.OS.Boot.DeltaSec Value: 9700 Key : Timeline.Process.Start.DeltaSec Value: 30 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 Key : WER.Process.Version Value: 4.37.3.1358 FILE_IN_CAB: Falcon BMS.exe.12888.dmp NTGLOBALFLAG: 0 PROCESS_BAM_CURRENT_THROTTLED: 0 PROCESS_BAM_PREVIOUS_THROTTLED: 0 APPLICATION_VERIFIER_FLAGS: 0 CONTEXT: (.ecxr) rax=000000008899000c rbx=0000000000000000 rcx=000000000300da90 rdx=00007ff92d8d2390 rsi=00000002e1ef8d60 rdi=0000000035defea0 rip=000000000463cacd rsp=0000000035defd50 rbp=0000000035defdb9 r8=00000000030583e0 r9=0000000000000000 r10=0000000035def640 r11=0000000035def5a0 r12=0000000000000000 r13=00000002e1efcca0 r14=000000002ef5e4a0 r15=0000000000000001 iopl=0 nv up ei ng nz na po nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000286 Falcon_BMS!bp::RendererD3D11::executeCameraDrawList+0x4fd: 00000000`0463cacd cc int 3 Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 000000000463cacd (Falcon_BMS!bp::RendererD3D11::executeCameraDrawList+0x00000000000004fd) ExceptionCode: 80000003 (Break instruction exception) ExceptionFlags: 00000000 NumberParameters: 1 Parameter[0]: 0000000000000000 PROCESS_NAME: Falcon BMS.exe ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached. EXCEPTION_CODE_STR: 80000003 EXCEPTION_PARAMETER1: 0000000000000000 STACK_TEXT: 00000000`35defd50 00000000`0463c4ba : 00000000`3ae88a00 ffffffff`ff676901 00000000`35defea0 00000000`35defeb0 : Falcon_BMS!bp::RendererD3D11::executeCameraDrawList+0x4fd 00000000`35defe20 00000000`0463b471 : 00000000`2ef50066 00000002`dd080040 00000000`3a8897d0 00000000`00000738 : Falcon_BMS!bp::RendererD3D11::executeFrameDrawList+0x24a 00000000`35defea0 00000000`0463b378 : 00000002`dd080040 00000000`00000000 00000016`885032ad 00000000`2efd8090 : Falcon_BMS!bp::RendererD3D11::renderThreadCB+0xf1 00000000`35deff00 00007ff9`32cc7344 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Falcon_BMS!bp::RendererD3D11::renderThread+0x38 00000000`35deff30 00007ff9`33ba26b1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14 00000000`35deff60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21 FAULTING_SOURCE_LINE: E:\BMS\bms-code\Graphics\Bluebox\Engine\D3D11\RendererD3D11.cpp FAULTING_SOURCE_FILE: E:\BMS\bms-code\Graphics\Bluebox\Engine\D3D11\RendererD3D11.cpp FAULTING_SOURCE_LINE_NUMBER: 1716 FAULTING_SOURCE_CODE: No source found for 'E:\BMS\bms-code\Graphics\Bluebox\Engine\D3D11\RendererD3D11.cpp' SYMBOL_NAME: Falcon_BMS!bp::RendererD3D11::executeCameraDrawList+4fd MODULE_NAME: Falcon_BMS IMAGE_NAME: Falcon BMS.exe STACK_COMMAND: ~31s; .ecxr ; kb BUCKET_ID_MODPRIVATE: 1 FAILURE_BUCKET_ID: BREAKPOINT_80000003_Falcon_BMS.exe!bp::RendererD3D11::executeCameraDrawList OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 IMAGE_VERSION: 4.37.3.1358 FAILURE_ID_HASH: {28a57d9b-e970-76f9-c752-9c3e55777f48} Followup: MachineOwner ---------
-
@airtex2019 There goes my sound issue theory In my defense, some weird stuff from over the years has been due to sound devices
-
@john1974 this crash is a breakpoint-exception, caused by an unexpected error response from DirectX.
searching the forum, the only other case I found hitting this, was some utter newb named airtex2019 back a few years ago.
in my case, it was triggered when using [Alt+Enter] to switch from fullscreen to borderless. and the error code from DirectX (in your dump file) seems similar to that.
are you doing anything that would entail a mode switch? or running with any overlay windows (RTT) or stuff like MSI Afterburner / RivaTuner / Intel Perfmon etc?
-
@airtex2019 said in Crash to Desktop Falcon BMS 4.37.3 Unplayable issue (LG 29WP60G-B Ultra Wide Monitor + Gigabyte GTX 1650 4GB GDDR6 Graphics Card ):
@john1974 this crash is a breakpoint-exception, caused by an unexpected error response from DirectX.
searching the forum, the only other case I found hitting this, was some utter newb named airtex2019 back a few years ago.
in my case, it was triggered when using [Alt+Enter] to switch from fullscreen to borderless. and the error code from DirectX (in your dump file) seems similar to that.
are you doing anything that would entail a mode switch? or running with any overlay windows (RTT) or stuff like MSI Afterburner / RivaTuner / Intel Perfmon etc?
@airtex2019 not really doing any [ALT] + [ENTER] switch.
I just have a 11.6" 2nd Prechen brand monitor that I use for the Thrustmaster MFD with the RTTClient that I use, but that’s currently off, and the CTD happens even when that is ON or OFF.
But as far as any switching is concern, nothing at all, No ALT Enters that i’m doing.
-
let me upload the latest Crash Dump and see if you find anything.
-
here’s my latest crash dump file
https://www.dropbox.com/scl/fi/i5hgp9zlxgx08hnftb41o/Falcon-BMS.exe.11480.zip?rlkey=8rwhm4p37so1ce2r42efzfbdv&dl=0I also recorded a video of it in MP4 so you guys/gals can see what happens whenever it crashes
https://www.dropbox.com/scl/fi/eb3vqkti4pz3vf0w1pjjy/BMS-Crash-Video.mp4?rlkey=uqbn9ht20xxr9mt2xdb6b36gj&dl=0please ignore the buzzing noise, it’s my phone, I have an old phone (BlackBerry) hehe
This never happened when I had the Zotac GTX 1050 TI 4GB GDDR5 Low Profile (brand new, a week old) installed…and now with my newer Gigabyte GTX 1650 GDDR6 OC Low Profile, this is now happening.
-
here’s the Crash Dump of the one that’s on the video I uploaded
Maybe someone can tell what’s going on please…thanks.
Anyways looking forward to a fix for this.
Happy New Year to everyone out there. All the best in 2024!
-
@john1974 same breakpoint / same unexpected DX error code, indicating the render-target device was reset
want to try something… it’s grasping at straws, but easy to try and easy to un-do … and does no harm to leave.
my working theory => Windows graphics driver timeout-detection-and-recovery (TDR) is resetting the graphics driver
the default timeout is 2 sec which is maybe a little aggressive for your older system running a flightsim presumably with all CPU cores maxed out
https://learn.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys
how about try doubling that to 4 seconds?
:: Run from an elevated (admin) cmd prompt reg add HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers /v TdrDelay /t REG_DWORD /d 4
or do it manually with RegEdit
(probably need to reboot, afterward)
per the MS docs, you can also try
/v TdrLevel /t REG_DWORD /d 0
to turn off TDR, but I would not recommend leaving that disabled forever