BMS 4.33 crash on Game start with 64bit

[Memphis291]

Hello everybody,

at first thanks to the whole BMS Team for BMS 4.33 providing to us.
I unfortunately have one major issue that I cant really reproduce.

Each time when I want to run BMS 4.33 with 64 Bit enabled, it is crashing with the usual “Falcon BMS is no more working” Errormessage.
I have no issues while running the Game in 32 Bit Mode, its only while switching to 64Bit.

EDIT: The Game was started with and without Administrator rights, no difference.

These are the System Specs:

• Win 10Pro 64Bit
• AMD FX-8350
• 32GB DDR3 RAM

Those are the entries from the Crash logs

1.) ErrorsInSFX.txt

LoadSFX() didn't load 264:D:\BMS\Falcon BMS 4.33\Data\Sounds\engines/fighter/a-10/Ext.ogg
LoadSFX() didn't load 277:D:\BMS\Falcon BMS 4.33\Data\Sounds\sndAero1.ogg
LoadSFX() didn't load 330:D:\BMS\Falcon BMS 4.33\Data\Sounds\engines\fighter\SndAbInt2.ogg
LoadSFX() didn't load D:\BMS\Falcon BMS 4.33\Data\Sounds\F-18\flare.ogg

2.) ErrorsInClassTable.txt

This file is restarted each session
PtHeaderDataTable[0].features[0]=0 >= Objective[0]'s Features 0
PtHeaderDataTable[0].features[1]=0 >= Objective[0]'s Features 0
PtHeaderDataTable[0].features[2]=0 >= Objective[0]'s Features 0
PtHeaderDataTable[0].features[3]=0 >= Objective[0]'s Features 0
PtHeaderDataTable[0].features[4]=0 >= Objective[0]'s Features 0

Those files are also updating each time I start the Game in 32Bit, but it wont crash then. Any Ideas what else it can be?

I have closed as many other programs as possible, to exclude certain Programs that might cause the issue…no luck. So I am out of Ideas now.

Thanks

regards

Memphis

[razo]

Make sure you have all drivers updated

[Memphis291]

Thanks for the reply, but all drivers are up to date

[razo]

https://www.benchmarksims.org/forum/showthread.php?23354-BMS-4-33-x64-Crash-on-launch

maybe you have same problem

[raven6]

Check that your screen resolution matches your BMS screen resolution. After the last update(W10), I couldn’t start BMS and making them both the same corrected the problem.
I’ll find the link to the same problem and post here.