Now this really takes some nerves… Without having made any further changes regarding connecting/disconnecting any internal devices of my notebook, I’ve just been able to start the x64 exe for one single time. It took some time with a black screen and then it suddenly loaded the main menu. Normally, I would’ve seen this black screen along with the error message “… has stopped working” right away after hitting “Launch” in the launcher. I then closed BMS and tried to do it again - no luck as if nothing happend. Not working. O.o
Latest posts made by Tonga
-
RE: BMS 4.33 x64 Crash on launch
-
RE: BMS 4.33 x64 Crash on launch
Hi Arty,
thanks for answering! You’re right, that is a possibility of course and I followed this idea. What I did was uninstalling the touchpad, trying my luck with an external keyboard, uninstalling and reinstalling my WiFi devices, sound devices etc. I also got hold of a collection of older graphics drivers, about 6 different versions, and I unfortunately here I am again, no luck. What really boggles my mind is the fact that the x86 version is running without any problems while the x64 version seems to be even more stubborn than a donkey.
The term “StackHash_2264” in the error message also was subject to a pretty thorough google research conducted afterwards, and it does happen with lot’s of other software as well. Some even reported that the NVIDIA 3D stereoscopic drivers caused such problems - I don’t even have such installed. There doesn’t seem to exist a clear pattern or anything that would make for one definite answer to the problem. Unfortunately I have no other notebook system to test this on.
-
RE: BMS 4.33 x64 Crash on launch
Hi everyone,
the x64 crash issue has been keeping me busy as well for quite a while now and I still had no luck solving this problem.
I’m running BMS 4.33 on a Win7 Lenovo IdeaPad Z570 containing a relatively old Intel i7-2630QM CPU @ 2.00 GHz along with 16 GB RAM (upgraded from 4 GB). This notebook has the NVIDIA Optimus stuff built in, meaning it has an internal Intel 3000HD graphics chip together with a dedicated GeForce 540M with current drivers (358.87). Given this hardware constellation, the most common reason for any irregularities when starting up a game, especially black screens with sound running, is VSync - for whatever reason. I’ve pretty much given up on that, turning it on mostly fixes it, just like BMS 4.33 in the 32 bit version. So, all good there. BMS is installed to “C:\GAMES\Falcon BMS”.The 64bit version however simply won’t launch at all. At first, I got the very same error message as Lawlcat did. I tried running the launcher and the x64 exe with administrator privileges, but that didn’t do anything for me. Reading this thread, I then turned off everything related to Bluetooth, which indeed helped in the sense that now the error message has changed.
Hope it’s okay to post the message in German language:
Problemsignatur: Problemereignisname: APPCRASH Anwendungsname: Falcon BMS.exe Anwendungsversion: 4.14753.0.0 Anwendungszeitstempel: 562b288d Fehlermodulname: StackHash_2264 Fehlermodulversion: 0.0.0.0 Fehlermodulzeitstempel: 00000000 Ausnahmecode: c0000005 Ausnahmeoffset: 000007fefa030004 Betriebsystemversion: 6.1.7601.2.1.0.768.3 Gebietsschema-ID: 1031 Zusatzinformation 1: 2264 Zusatzinformation 2: 2264db07e74365624c50317d7b856ae9 Zusatzinformation 3: 875f Zusatzinformation 4: 875fa2ef9d2bdca96466e8af55d1ae6e
I then installed .NET 4.6 manually, reassured myself that all current Windows updates were applied, and still no luck. Creating or deleting a profile in the NVIDIA driver unfortunately doesn’t change anything as well. Upgrading to Windows 10 isn’t a real option for me at the moment because the Z570 isn’t officially supported for Win 10 by Lenovo which means that most drivers don’t really work, the touchpad and keyboard won’t work properly and quite a bunch of other issues…
Btw - there are no peripherals connected at all, not even a simple USB mouse, let alone any joysticks, wheels etc.
I should probably say as well that I turned off intro movies in the launcher - they did work but I just prefer a direct launch.My brain is getting low on fuel and ammo, so maybe you guys still have any idea on how one could get this to work…
Cheers,
Tonga