BMS 4.33 only work in 32-bit mode. 64-bit Crash to desktop

[Fuller0079]

Good morning all. Extremely new here and just trying my best to get this great game working. Currently my problem is as stated in the title. I can get BMS to work in 32-bit mode. After about 3 games it will crash to desktop. I do see something about memory being used up not sure how to fix that. When i open the game in 64-bit mode whenever i commit it will crash to desktop. I have tried changing OS compatiability, Deleting files mentioned in other threads, etc. I just cannot fix this issue. I want to join a squadron but cant until this issue is fixed. Plz help and thank you for any and all suggestions.

[razo]

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

[november123]

Hi Guys, I am hoping one of you will help me, I can run bms 4.33 in 32bit mode flawlessly. However I get the following error when I launch it in 64 bit:

Faulting application name: Falcon BMS.exe, version: 4.14753.0.0, time stamp: 0x562b288d
Faulting module name: logffdriver64.dll, version: 0.0.0.0, time stamp: 0x4dfec990
Exception code: 0xc0000005
Fault offset: 0x0000000000033a34
Faulting process id: 0xe58
Faulting application start time: 0x01d148d98703408e
Faulting application path: C:\Falcon BMS 4.33\Bin\x64\Falcon BMS.exe
Faulting module path: C:\Windows\ForTest\logffdriver64.dll
Report Id: c89e5568-b4cc-11e5-8300-f0795965f85a

Specs:

OS: win 8.1 64 bit
CPU: i5 4460 3.2
Memory 8gb
MB: Asus Z97P
GPU: XFX AMD R7 260x

[CookieMonster]

You are using a force feedback stick? Disable the logffdriver64.dll by renaming it to .off and try again.

[november123]

@CookieMonster:

You are using a force feedback stick? Disable the logffdriver64.dll by renaming it to .off and try again.

Wow!!! You are amazing, I do not know how to thank you!!
Indeed I am using a force feedback stick, you saved me a lot of time, effort. I have been trying to fix this for an entire month!

[CookieMonster]

You got very lucky, I’ve been through this error 2 times before already. There seems to be a general problem with FFB sticks and the 64bit version.

I’m glad my findings could help someone.

https://www.benchmarksims.org/forum/showthread.php?23499-Saitek-Evo-Force-64bit-CTD

[Arty]

This could be my case for the wheel pedals? They r also FFB hmm let’s see.

[Arty]

WOW man…
such luck… couldn’t find which dll was for FFB for my saitek r440 wheel and the first one I renamed SaiQFF04.Dll in C:\Windows\System32 did the trick… now I have rudders…
YYYeeeaaaaa a big thanx m8…

[november123]

@ Arty, all you have to do is hit the start button and search for: event viewer, then click on applications, then Error.
It should show you the crash log for the last application (which is in this case bms 4.33)
The name of the dll file should be mentioned there.

[Darkman]

Please post a bug report using this guide: https://www.benchmarksims.org/forum/showthread.php?6181-How-to-write-good-bug-reports

Remember to zip/7z the crash dump and post a link to it, so the the developers can see what is happening.

[Darkman]

While we’re waiting for the crashdumps some feedback and a suggestion from a developer:

_I tested with some force feedback hardware here (non-Saitek) and had no issues, neither in 4.33 public nor in the dev branch, 32-bit and 64-bit behaved identically.

However: I did some research, and it looks like especially Saitek is known for having buggy 64-bit FF drivers. Most solutions recommend removing the default definition for the Joystick from the registry (written by the driver), so that Windows can re-query the device capabilities and re-create the registry definition at the next restart.

The steps to be taken would be:

• Open the registry editor.

• Navigate to HKEY_CURRENT_USER\System\CurrentControlSet\Control \MediaProperties\PrivateProperties\Joystick\OEM

• Check each subkey (VID_xyz…) in there for the “OEMName” entry. If you found “your” stick, remove the whole corresponding “VID_xyz…” entry.

• Restart Windows(!), and check again.

I’m not saying that this is THE solution, I’m just saying that this is what seems to have helped most users suffering from 64-bit FF issues. Maybe you want to post this info in the public forum and ask for feedback on this? However, if it does not help, of course the CTD dumps are still welcome._

[Arty]

Yea I could do that but the crash log ain’t just there. In my case Falcon isn’t generating any crash log…
So I saw the post for FFB devices I have a FFB device which when I have unplugged Falcon 64bit works so I tried renaming the force feedback dll and it works.