BMS 4.33 x64 Crash on launch
-
i have 4 Hubs all powered by 12V source, power is not the issue for sure.
-
I get ctd when I change the fov from default.
Try it every one getting g ctd change the fov back to 60 no more crashes after exiting a flight etc etc
-
Mine’s crashing, too.
Had a quick flight after reconfiguring my hardware in 4.32 - went to do the same in 4.33 (first attempt) and it crashed. I have gone through the configuration GUI and set it up the same as 4.32 but on trying to launch I get all the windows opening (including exports) with no images (so just the windows) and finally an error message, which actually says that the cause of the crash is D3DGear!
D3DGear is my recording software, but even if I make sure it’s off (including the task manager), the error message still blames it. Struggle to believe an inactive prog is causing BMS to not launch.
Anyway, it’s very late here and my head is pounding already - I’ve read the whole thread and I will try some other possible solutions tomorrow. My rig is almost identical to the OP and I’m running Win7 HP64 with an i5 2500k at 4.3GHz, 16GB DDR3 and a GTX970 4GB on 3 monitors using nvidia surround. I’ll try it on one and other things tomorrow and report back.
-
I’tried change FOV, no effect. What intrigues me why it works in previous 4.32 and crashes in new one. But is okay, very soon me or someone will find a solution.
-
Indeed. My 32 bit BMS 4.33 is working just fine - as others, it’s just the 64bit exe that has issues. My 64bit DCS World is working just fine, so it isn’t a general issue.
I really don’t want to have to uninstall D3DGear after having got it set up just how I want it, so if necessary I’ll just stick with the 32bit BMS. To start with, the error was blamed on D3DGear.exe
After I killed the process and made sure no services etc were running I tried again and this time the error blamed D3DGear.dll
I did have this once in the past with the Steam version of FSX, which also crashed on start-up and also quoted D3DGear as the cause, but that turned out to actually be something else, because now they are working at the same time without issue. I had done a complete Windows reinstall in between it not working and working.
Mysterious…
-
Hi Everybody,
Had the same problem not being able to launch the X64 version of the executable.
The solution as far as I’m concerned was to simply delete de profile Nvidia created in control panel for the Falcon Bms executable. Not the launcher.
From then on I was able to launch the X64 Falcon exe.A friend of mine had the same issue and he did fix it the same way. So maybe a solution after all….
Brgrds,
Pacific
-
well this is one part of the mystery… seems that that nvidia profiles for bms is a verified problem but not the total solution for 64bit of BMS 4.33.
-
As a new member, I find it disappointing when all I see here are wild guesses and a complete lack of any sort of informed input.
-
Hi Everybody,
Had the same problem not being able to launch the X64 version of the executable.
The solution as far as I’m concerned was to simply delete de profile Nvidia created in control panel for the Falcon Bms executable. Not the launcher.
From then on I was able to launch the X64 Falcon exe.A friend of mine had the same issue and he did fix it the same way. So maybe a solution after all….
Brgrds,
Pacific
Isn’t a solution for me.
the only install that has an nVidia CPL profile is “Launcher.exe” - doesn’t say whether it’s for 4.32 or 4.33 or even both. Aside from that, it’s an nVidia created profile, and you can’t delete those - it says so at the bottom of the dialogue box and the delete button is greyed out. Be interested to hear how you did it?
As a new member, I find it disappointing when all I see here are wild guesses and a complete lack of any sort of informed input.
That’s called people trying to help - and it’s better than nothing, if the cause is not known. Whereas clever remarks are very easy to make (but don’t incline people to help with an issue).
-
Same problem with 0xc00000007b application error
system1 : win extreme 7 64 bit SSD kingston 128GB CPU QX9770 4MB
I change HDD WD serial ata and the game there work ok in 64 bit Windows ultimate
So the problem is targeted even in Windows extreme 7 64 bit or in SSD kingston hard drive.
some new finds from Dependency Walker for BMS 4.33.exe x64
looklike the d3dx9_43 is x86 and not x64
-
That’s called people trying to help - and it’s better than nothing, if the cause is not known. Whereas clever remarks are very easy to make (but don’t incline people to help with an issue).
You might look at it that way, but it does not change the fact that it is the truth.
This is the latest release which obviously has issues when installed on a system that most users will have these days. I have yet to see a post by one of the development team in response to this issue, all I do see is a series of wild and, although I am sure not intended as such, unhelpful “guesses” as to a solution.
I know this may be contentious, but personally I don’t want 100 “people” to guess at a solution, I would prefer informed advice from 1 “expert”, thanks.
-
You might look at it that way, but it does not change the fact that it is the truth.
No, it’s an opinion and arguably an uninformed one at that.
This is the latest release which obviously has issues when installed on a system that most users will have these days. I have yet to see a post by one of the development team in response to this issue, all I do see is a series of wild and, although I am sure not intended as such, unhelpful “guesses” as to a solution.
Well the fact that the entire team of developers and beta testers have not encountered these issues during several years of development would suggest otherwise, and are you sure you know who is in the development team?
I know this may be contentious, but personally I don’t want 100 “people” to guess at a solution, I would prefer informed advice from 1 “expert”, thanks.
Then why post it? What do you hope to achieve by posting in a ‘contentious’ manner? What is your desired intention? People that have found solutions that have worked for them have taken the time to share their experience with others. Their solution may not work for you, but sooner or later someone may post something that does, or would you prefer to wait for informed advice from an “expert” who cannot reproduce this problem?
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/showthread.php?6181-How-to-write-good-bug-reports
-
You are of course correct, I am a new member and so obviously have no idea who is in the development team. One thing I do know though is that I am obviously not alone here in having a similar problem that “developers and beta testers have not encountered … during several years of development” and judging by the responses in this entire thread, not one of this dedicated team has posted here so far. At least I hope that is the case.
I am not convinced that the “infinite monkeys with infinite typewriters” approach is the best way to tackle problems, but as I said, I am new here.
-
Same problem with 0xc00000007b application error
system1 : win extreme 7 64 bit SSD kingston 128GB CPU QX9770 4MB
I change HDD WD serial ata and the game there work ok in 64 bit Windows ultimate
So the problem is targeted even in Windows extreme 7 64 bit or in SSD kingston hard drive.
some new finds from Dependency Walker for BMS 4.33.exe x64
looklike the d3dx9_43 is x86 and not x64
#| 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.# -
-
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