BMS 4.33 x64 Crash on launch
-
If you do think you can reproduce some behaviour you do think is a bug then please follow the advice in this post: https://www.benchmarksims.org/forum/showth…od-bug-reports
….priceless
-
Hi all, after spending some time here and there i found like others stated in earlier posts that 64 bit platform selection crash can be fixed by running the BMS shortcut with administrator privileges. All you have to do is right click the “Falcon BMS 4.33” shortcut on the desktop and select properties. In the popup window select Compatibility tab and make sure “Run this program as an administrator” is ticked. Press OK and it should run. The only thing i don’t understand is why in the first place my 4.33 installation run without crashing in windows 10 64bit using the 64bit platform selection from the launcher. It suddenlly stoped working making me look for this fix. If anybody can enlighten me would be great.
-
#| System Information |
Dependency Walker: 2.2.6000 (64-bit)
Operating System: Microsoft Windows NT/2000/XP/2003/Vista based Ultimate (64-bit)
OS Version: 6.01.7601 Service Pack 1
Processor: Intel64 Family 6 Model 23 Stepping 7, GenuineIntel, ~3597MHz OC 3200MHz
Number of Processors: 4, Mask: 0x000000000000000F
Computer Name: ANTONIS
User Name: Antonis
Local Date: Δευτέρα, 9 Νοεμβρίου 2015
Local Time: 7:00:43 μμ GTB Standard Time (GMT+02:00)
OS Language: 0x0408: Greek
Memory Load: 87%
Physical Memory Total: 3.488.735.232 (3328 MB)
Physical Memory Used: 3.044.634.624
Physical Memory Free: 444.100.608
Page File Memory Total: 6.975.590.400
Page File Memory Used: 4.195.536.896
Page File Memory Free: 2.780.053.504
Virtual Memory Total: 8.796.092.891.136
Virtual Memory Used: 234.569.728
Virtual Memory Free: 8.795.858.321.408
Page Size: 0x00001000 (4.096)
Allocation Granularity: 0x00010000 (65.536)
Min. App. Address: 0x0000000000010000 (65.536)
Max. App. Address: 0x000007FFFFFEFFFF (8.796.092.956.671)| Module List |*
-
- Legend: D Delay Load Module ? Missing Module 6 64-bit Module *
-
- Dynamic Module ! Invalid Module *
- E Import/Export Mismatch or Load Failure *
-
Module File Time Stamp Link Time Stamp File Size Attr. Link Checksum Real Checksum CPU Subsystem Symbols Preferred Base Actual Base Virtual Size Load Order File Ver Product Ver Image Ver Linker Ver OS Ver Subsystem Ver
–— --------------------------------------------- ----------------- ----------------- ---------- ----- ------------- ------------- — --------- ---------- ------------------ ----------- ------------ ---------- ------------------ ---------------- ----------- ---------- ------ -------------
[D? ] API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).
[D? ] API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).
[D? ] API-MS-WIN-CORE-WINRT-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).
[D? ] API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).
[D? ] API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).
[D? ] API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL Error opening file. The system cannot find the file specified (2).
[D? ] DCOMP.DLL Error opening file. The system cannot find the file specified (2).
[D? ] IESHIMS.DLL Error opening file. The system cannot find the file specified (2).
D3DX9_43.DLL 26/05/2010 11:41a 22/05/2010 3:21a 1.998.168 AC 0x001E926D 0x001E926D x86 GUI CV 0x–------10000000 Unknown 0x001FF000 Not Loaded 9.29.952.3111 9.29.952.3111 6.1 10.0 6.1 5.0
[ 6.0 1.3.1001.0 6.1 9.0 6.1 5.2| Log |*
Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.#Problem solved
i delete the D3DX9_43.DLL from system32 and syswow64 then i run dxwebsetup and that it!!!
-
-
This post is deleted! -
Gerald, I have multiple other programs that may use that D3dx9_43.dll file. If I try deleting it and running the other program you mention, does it provide an updated version of that file, so my other programs would still run?
-
the deleted D3dx9_43.dll will be recreated again with dxwebsetup.exe so there is no problem , if you want take a backup first D3dx9_43back.dll
-
just to inform I reinstalled 4.33 and the empty Avionics configuration window problem is gone.
Strange problem by being on an SSD disk…
-
OK, I tried Geraki’s suggestion, still does not let the 64 bit version work. Crashes immediately upon hitting launch. Hopefully, the developers will come up with a fix or patch.
-
@Greg:
…. Hopefully, the developers will come up with a fix or patch.
That’s a tall order. How does a dev build a patch for a problem they can’t re-create and that, so far, doesn’t have a clearly identified cause? For most people, this is not happening. Of 20 - 30 people in our wing who I know have upgraded to 4.33, only 1 is having this problem.
It may come down to something the user has to ‘fix’ …. some conflict in Windows or with some device or another. Who knows?
-
- 1
personal computer
-
Same was happening to me and I was able recreate the problem too.
I have to kill all superfluous nvidia processes particularly those for Nvidia geforce experience (beta version that enables remote sharing and streaming). Once i do that it loads up fine however it’s just a workaround.
No idea if this will help anyone else…
-
OK, I found the event log when the 64 bit version of BMS 4.33 crashes when I click on Launch. It is:
Faulting application name: Falcon BMS.exe, version: 4.14753.0.0, time stamp: 0x562b288d
Faulting module name: btmmhook.dll, version: 6.2.0.9603, time stamp: 0x4a8a28c2
Exception code: 0xc0000005I have an Intel 5 computer and Windows 7 64 bit. Can anyone determine from this log what is happening?
-
OK, I got it to work! As the log above shows, the offending file is btmmhook.dll. It is bluetooth related. It is found in C:Program Files/WIDCOMM/Bluetooth Software. I renamed it to btmmhook.bu. Now my 64 bit version of BMS 4.33 works as well! Hooray!! Hopefully this can help someone else.
-
instead of renaming you could update it or stop the Bluetooth service before running 4.33.
-
@Greg:
OK, I got it to work! As the log above shows, the offending file is btmmhook.dll. It is bluetooth related. It is found in C:Program Files/WIDCOMM/Bluetooth Software. I renamed it to btmmhook.bu. Now my 64 bit version of BMS 4.33 works as well! Hooray!! Hopefully this can help someone else.
Consistent issue it seems. Here’s a post from earlier in this thread: https://www.benchmarksims.org/forum/showthread.php?23354-BMS-4-33-x64-Crash-on-launch&p=337650&viewfull=1#post337650
Is your Bluetooth module made by Broadcomm by any chance?
-
Is your Bluetooth module made by Broadcomm by any chance?
yes it is. that name is broadcom drivers
-
I don’t use the Bluetooth service, so not sure how to "stop "it, or update it.
-
Ok guys I think I found the issue. I spent most of the day troubleshooting my install. I know this is going to sound really lame, but it has to do with the number of letters in your call sign. Anything over 11 will cause the Faulting module name: KERNELBASE.dll error. I tested this over and over just to make sure. I was 100% successful in reproducing the error.
Hope this helps.
Steve
-
Same was happening to me and I was able recreate the problem too.
I have to kill all superfluous nvidia processes particularly those for Nvidia geforce experience (beta version that enables remote sharing and streaming). Once i do that it loads up fine however it’s just a workaround.
No idea if this will help anyone else…
Good point, zelegend. It’s beyond me why anyone would want to install all that extra crud that comes with GPU drivers these days. I usually do an advanced / expert install, disable all components except for the drivers themselves (hd audio? PhysX? 3D vision? GF experience? WTF? ;)) and perform a “clean installation” that wipes all my driver settings and starts over fresh.
Whenever I want to take a closer look at driver settings or profiles (which I don’t use, either), I’m more than happy with nv inspector
All the best, Uwe
-
Ok guys I think I found the issue. I spent most of the day troubleshooting my install. I know this is going to sound really lame, but it has to do with the number of letters in your call sign. Anything over 11 will cause the Faulting module name: KERNELBASE.dll error. I tested this over and over just to make sure. I was 100% successful in reproducing the error.
Hope this helps.
Steve
Known and stated that a callsign 12 and above letters is not working.
thanx