BMS 4.33 x64 Crash on launch
-
- 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
-
-
Geraki, are you still having this situation with the 0xc00007b error ? Here is what I did… based on a thread I found within DCS forums. ( I was trying to install DCS 1.5 open beta ) I downloaded Visual C++ 2013. When extracted, 3 files develop. 2 we can use and install, 1 will not install . It tells you that if you try to install it. I then REINSTALLED Visual C++ 2013 using the repair function. It worked for me, I hope it does for you.
-
Hey everyone,
Same issues for me, tried installing/reinstalling twice, no luck. I do have Bluetooth, but its built into my computer, and I have had no luck trying to disable it. Couldn’t find a Wincom folder, or even the .dll file mentioned, and my call sign is less then 12 characters long. Works fine in 32bit, just not in 64. Which brings me to my question, is there a difference in running it in 32bit instead of 64?
Adam/Jet Lag
-
Oh, here are my specs
Asus Desktop G20AJ Series
Intel Core i7-4790 3.60ghz
Windows 8.1 64x
Nvidia Geforce GTX 760 4gb mem
16gb ramAdam/Jet Lag
-
Hey everyone,
So, I might of found a possible solution, especially with people with Asus rigs that run Virtuwatt. Disable it, completely. 64x booted up just fine. Didn’t go into any missions or anything, will test it out and update.
Adam/Jet Lag
-
Was really to tell u to do the same thing. Glad u found out.
-
Thanks anyways Arty, and works fine, flew some missions, no issues at all.
Adam/Jet Lag
-
Almost a week Falcon BMS 4.33 worked fine, but as of today are constantly crashes. When I start the launcher I get a black screen picture and then the simulation minimized, if I click on it hears the music and again minimize, if I try by right-clicking got a message as shown below. Does someone have a similar problem and how to solve it?
I have Win7x64. I have no connecting BT devices, I reinstalled DirectX, reinstalled BMS 4.33 …
My problem was solved by installing .NET Framework 4.6
-
Initially installed and ran 4.33 just fine…. plugged in my TM Cougar and continuous crashes. Disabled Cougar in Device Manager and still crashing. Can run 4.32 with no problems.
Got an error message to the effect of “Bridging device … yada yada”. It hasn’t reappeard.