BMS 4.33 x64 Crash on launch
-
Hi there,
had crash issues with x64 version too.
The problem was the driver for the “Games Power” Flight Control System.
Uninstalled it and everything is working fine.Running 4.33 on Windows 10 Pro x64.
Have a nice day,
Joerg (shmalee)
-
Thanks for the tips on posting the logs, now can we focus on the problem? Anyone know if the BMS tech folks visit this forum? Any ideas/suggestions on how to fix this?
Anyone here is some sort of tech
Have you updated your drivers?
Runned as admin?
Disabled the integrated gpu via device-manager?
-
Also any Force feedback sticks or devices users just locate the force feedback dll file and rename it. Worked for me.
Worked for me to!
-
What is and how to locate the feedback and solve this problem please help!!!
-
Please help what is force feedback and how to solve the problem.can’t lunch 64bit!! please help
-
Locate the dll file responsible for forcefeedback. you’ll find it in the device driver folder.
Rename it. Like from filename.dll to filename.xxxdll
If you don’t know which file it is try renaming one file every time and test until you find the one that is responsible for crashing BMS.All the above assuming you have a forcefeedback capable device like a joystick or wheels.
-
Please also post about your Windows 10 version/build number (start > run > type winver and enter)
The RC version 10.0 build 19240 was working ok with bms, the newer version 1511 build 10586.71 (November update) always produces a CTD upon entering 3D, only way is to have the main bms window not in full screen.
Still investigating for a solution.
-
the newer version 1511 build 10586.71 (November update) .
yes i have this version of windows,so will should i wait from new update for bms or what? thanks!
-
Any idea when the next update might be as I am having this issue when I added a new joystick device to my setup. I know 4.33 was working before this and I really can’t unplug anything
Moose, have a look at this thread: https://www.benchmarksims.org/forum/showthread.php?24018-Have-to-unplug-DirectX-devices-to-get-BMS-to-run-feedback-requested&p=344607&viewfull=1#post344607
With your complex setup you might well be suffering from the same issue, a fix for which should be in the next update we expect.
-
Hi guys,
Update: I got it to work in 32 bit (although I cant seem to use my Thrustmaster T.Flight. 32 bit runs as admin and win xp compatibility (64 bit exe cannot be set to win xp apparently)You shouldn’t need to do any of that. Something else is wrong here.
That you don’t see your game controller is unusual, probably a problem with driver installation.
-
I have problem in Win10 with NVIDIA GPU in Laptop;
I have solved problem using win7 compatibility option, NVIDIA control panel(to use full option of GPU), 32bit operation.
-
The thing is to have 64 bit running and not 32.
-
Hello Guys! Same problem here…but with a new version Falcon BMS 4.33 U1…
And I had same problem with Falcon BMS 4.33…
I have a I5, Nvidia GTX 970, SSD 500G, 8GB Ram and doesnt work 64bits version, Windows 10 Professional 64bits, with all drivers updated. -
@rhw:
Hello Guys! Same problem here…but with a new version Falcon BMS 4.33 U1…
And I had same problem with Falcon BMS 4.33…
I have a I5, Nvidia GTX 970, SSD 500G, 8GB Ram and doesnt work 64bits version, Windows 10 Professional 64bits, with all drivers updated.As am I. Fresh install of 4.33 U1. i5, GTX 970. SSD, 16GB RAM, W10 64bit.
32-bit runs fines. 64-bit crashes on launch.
-
Hey guys,had the same problem on an MSI-GE62, win10 version 10.0.10586, nvidia optimus driving a GTX960M plus integrated graphics.
running 4.33U1, entering 3d in 64 bits mode always crashed the sim, 32 bits mode worked without any problems.
as reported here by others, the workaround to enable 64 bits mode was to enable Cockpit Display in External Windows under External Display in Configuration>Hardware: the 3d world will then start in a window and run just fine.
guess we have to wait for a full troubleshoot but that’s fine enough for the moment. keep up the good work boys
-
Hello, I am running Windows 10 PRO 64 bit OS and the program (both in 32 or 64 bit mode) fails to launch with this in the crash Log
Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in:
000000000451E69D Falcon BMS.exe, ParticleSystem::LoadParameters()+6925 byte(s), d:\wip\bms\svn\source\rel-4.33\graphics\objects\particlesystem.cpp, line 4453+16 byte(s)
Exception handler called in UnhandledExceptionHandler.
Read from location 0000000000000484 caused an access violation.
Bytes at CS:RIP: F3 0F 51 44 01 4C F3 0F 59 05 B5 AB AA 00 F3 0FSystem Information:
‘C:\Falcon BMS 4.33 U1\Bin\x64\Falcon BMS.exe’, run by Computer21.
Error occurred at 11:56:48 on 2016-04-17.
Version: Falcon BMS 4.33.1 (x64) 15227
Not in game
Theater terrain path: ‘C:\Falcon BMS 4.33 U1\Data\Terrdata\korea’
Operating System: unknown Windows version (6.2.9200) Platform 2 .
Computer Name: DESKTOP-6QI4S8T Domain: WORKGROUP.
12 logical processor(s), type 8664.
CPU: Intel Core i7-5930K CPU @ 3.50GHz. GenuineIntel. Stepping: 2 Model: F Family: 6.
GPU 0: NVIDIA GeForce GTX 970. Vendor: 4318. Device: 5058. SubSys: 2431654666. Revision: 161.Any assistance would be appreciated.
-
@fjp:
Hello, I am running Windows 10 PRO 64 bit OS and the program (both in 32 or 64 bit mode) fails to launch with this in the crash Log
Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in:
000000000451E69D Falcon BMS.exe, ParticleSystem::LoadParameters()+6925 byte(s), d:\wip\bms\svn\source\rel-4.33\graphics\objects\particlesystem.cpp, line 4453+16 byte(s)
Exception handler called in UnhandledExceptionHandler.
Read from location 0000000000000484 caused an access violation.
Bytes at CS:RIP: F3 0F 51 44 01 4C F3 0F 59 05 B5 AB AA 00 F3 0FSystem Information:
‘C:\Falcon BMS 4.33 U1\Bin\x64\Falcon BMS.exe’, run by Computer21.
Error occurred at 11:56:48 on 2016-04-17.
Version: Falcon BMS 4.33.1 (x64) 15227
Not in game
Theater terrain path: ‘C:\Falcon BMS 4.33 U1\Data\Terrdata\korea’
Operating System: unknown Windows version (6.2.9200) Platform 2 .
Computer Name: DESKTOP-6QI4S8T Domain: WORKGROUP.
12 logical processor(s), type 8664.
CPU: Intel Core i7-5930K CPU @ 3.50GHz. GenuineIntel. Stepping: 2 Model: F Family: 6.
GPU 0: NVIDIA GeForce GTX 970. Vendor: 4318. Device: 5058. SubSys: 2431654666. Revision: 161.Any assistance would be appreciated.
Attach your logs in a zipped folder or put them in a code
-
This post is deleted! -
Sorted issue out!
-
I also have issues with 64 bit BMS 4.33.1. It launch fine, but when entering the 3D world, it would freeze, and the only way out is through killing BMS with task manager. However, because I have Visual Studio installed in my machine, when I choose not to kill it, but debug it instead, Visual Studio asks for source file named “d3ddevice.cpp”. I hope the devs may find this useful.
Edit 1:
- My machine is HP ENVY 15-k019nr Notebook PC (Intel CoreTM i7-4510U, 2GB NVIDIA GeForce 840M, 1TB Hard Drive, 8GB RAM -> Upgraded to 16GB, Windows 8.1 -> Updated to Windows 10 Pro x64 (10.0.10586)).
- Moreover, as I believe it has been stated before, running x64 in windowed mode is working well, and 32bit windowed or fullscreen is well. Running as Administrator doesn’t fix it, and disabling bluetooth also doesn’t fix it.
Edit 2:
- Callstack from Visual Studio
> Falcon BMS.exe!D3DDevice::SetDisplayMode(const DisplayMode3D & DisplayMode3D) Line 662 C++ Falcon BMS.exe!FalconDisplayConfiguration::_EnterMode3D() Line 645 C++ Falcon BMS.exe!FalconMessageHandler(HWND__ * hwnd, unsigned int message, unsigned __int64 wParam, __int64 lParam) Line 3046 C++ [External Code] Falcon BMS.exe!FalconDisplayConfiguration::Run() Line 462 C++ Falcon BMS.exe!HandleWinMain(HINSTANCE__ * hInstance, HINSTANCE__ * lpCmdLine, char *) Line 979 C++ Falcon BMS.exe!WinMainWrapper(void * pData) Line 1039 C++ Falcon BMS.exe!ThreadUnhandledExceptionWrapper(int(*)(void *) pFunc, void * pData) Line 1567 C++ Falcon BMS.exe!WinMain(HINSTANCE__ * hInstance, HINSTANCE__ * hPrevInstance, char * lpCmdLine, int nCmdShow) Line 1065 C++ [External Code] ```- Locals
-
this 0x000000000c7aac60 {Falcon BMS.exe!D3DDevice kObj} {m_pD3D=0x000000000e180740 <information not="" available,="" no="" symbols="" loaded="" for="" d3d9.dll="">...} D3DDevice * Adapter Variable is optimized away and not available. adapterToUse 0 unsigned int BehaviorFlags 68 unsigned long
-
DisplayMode3D {adapterMode={hardware=true fullscreen=true adapter=0 ...} bitDepth=32 multiSampleType=D3DMULTISAMPLE_NONE (0) ...} const DisplayMode3D & FBHLF Variable is optimized away and not available. hr Variable is optimized away and not available. hr Variable is optimized away and not available. hr1 Variable is optimized away and not available. hrCaps Variable is optimized away and not available. hrCDF Variable is optimized away and not available. hrCDT Variable is optimized away and not available. hrClear Variable is optimized away and not available. hrFBDTF Variable is optimized away and not available. hrMSRT Variable is optimized away and not available. hrPresent Variable is optimized away and not available. hrReset1 Variable is optimized away and not available. hrReset2 Variable is optimized away and not available.
-
Identifier {Driver=0x000000000014ef40 "èï\x14" Description=0x000000000014f140 "\x1" DeviceName=0x000000000014f340 "G" ...} _D3DADAPTER_IDENTIFIER9 iDeviceType D3DDEVTYPE_HAL (1) _D3DDEVTYPE pSurfMSRT Variable is optimized away and not available. refcount Variable is optimized away and not available.</information>