CTD UPON LAUNCH
-
Hi Senior Members:
I’ve been unable to start BMS when I key in the LAUNCH Tab. I’m getting the initial BMS Tommo window but, within seconds I’ve got a a CTD situation. I’ve tried 32 and 64 bit pre-launch designations with no joy. I’ve also reviewed my User > Log files for any sign of problems. Frankly however, it’s all Greek to me. Please see the attached three Log Files below. Maybe someone out there can make sense of them and offer suggestions for a fix. HELP - PLEASE!!!
Mike
-
Log files are completely normal, though the last_flight_faults would suggest you have been able to get airborne previously. Is that the case? Have you changed anything since (drivers, Windoze Update etc)?
-
Hi Darkman and thanks for getting back to me:
Nope, I didn’t change a thing. I shut down my system as normal yesterday and, when I started up this am and attempted to launch BMS - CTD was the result. Just finished my 5th reinstall including a regedit. Note that I only reinstalled the U1 Base. No joy - CTD again. I’ve consulted the posts on this subject from Ironman56, Razzo and, PizzaTheHut and, have applied their recommendations. Again, no joy. I’m at a loss and don’t know what else to do.
Mike
-
Are those the only the logs you get ?
please add -mono to your desktop shortcut and attach that also it may hold a clue
-
Hi Ninja:
I believe you’ve asked for a screenshot of my Desktop. If so I’ve attached it below. If not, can you guide me on how to add - mono to my desktop shortcut. Sorry about my limited tech skills.
Sys Specs: Win 10 Pro [64], MSI Game Pro MOBO, i7 CPU, 32GB, 2 x ASUS Nvidia 970 GPU’s w/ SLI bridge, WD 500Gb SSd, WD 2Tb SATA HHD, Toshiba 2Tb SATA HHD, Samsung 23" Curved Mon, ASUS 19" Touchscreen Mon, MIMO USB 7" Touchsreen Mon, TM Cougar TQS w/ TUSBA, TM Warthog FCS, TM Rudder, TM MFD’s, Track IRv5, Gametrix Jetseat.
-
heya sure first highlight your desktop BMS icon right click select properties you will target location
just below that a textbox which has the path in quotes " " so right after the last " add -mono and -window press apply then start BMS again
once it ctd’s go to your log directory and paste the contents of the xlog file
-
I’ve consulted the posts on this subject from Ironman56, Razzo and, PizzaTheHut and, have applied their recommendations.
Mike
And what recommendations did you attempt doing to resolve the issue from those guys??
Please post you’re Rig specs including OS.
C9
-
@Cloud:
Please post you’re Rig specs including OS.
He already did, 2 posts above yours.
Did Microsoft update Windoze 10 with some more spyware twixt your successful and unsuccessful attempts to run BMS? It wouldn’t be the first time that a Windows 10 update screwed things up.
I wouldn’t waste time on reinstalling, unless you know that you’ve screwed something up messing about with your BMS installation (and even then just restoring the files from a back up is a better option). Clearly from your explanation above that’s not the case here anyway, which makes me suspect Win10, or driver updates, or something else as yet unknown.
-
-
make sure to turn of Nvidia Geforce experience if installed as this has been known to cause problems
-
I’m getting an invalid path notification.
-
I tried switching between 32 and 64 bit as well as clearing BMS in End Task.
-
NO NO, you need to modify the Target box, not the Start in box!!
And please answer my question in post 7 about what recommendations you attempted.
C9
-
Yeah. I don’t plan on doing any more reinstalls at this point - makes no sense. I had my BMS running about a month ago under Win 8.1 with no problem. However, when I upgraded to U3 I got the Blue Screen of Death. I tried everything under the sun to get my sys to boot again. No luck, so I went out and got a new 500Gb SSD and a 2Tb HHD. Also upgraded to Win 10 Pro at the same time and got my rig back up although I had to reinstall everything (TM HOTAS & Rudder, Monitors, DCS and BMS, etc.) - the whole shabang. I initially had BMS running after this rebuild, but again as I’ve indicated it just started to CTD.
-
Again. It was suggested that I switch from 64 to 32 bit in the launch screen. This worked but after shutting down for the night and and trying to launch this am - CTD. And I also inserted the recommended -mono -window add in the target box. I might be placing it in the wrong string configuration. See the attachment below and advise. Please bare with me - I’m a newbie.
-
Move the close " quote from the end of the line to just after the .exe. The -Mono and -window switches don’t belong within the quotes.
It should look like this: “C:\Falcon BMS 4.33 U2\Launcher.exe” -Mono -window
Mine says U2 and your says U1, don’t worry about that. Just move that close quite.
Also, did you try deleting the dx9display.dsp file??
C9
-
Thanks C9 for working with me on this issue. I appreciate your knowledge and help. Ok. I’ve added the -Mono -window string to the end of the Target line as you instructed. The only 2 log files are attached below. Also, I did not delete the dx9display.dsp file. I’ll do so now.
Thanks again,
Mike
-
Thanks C9 for working with me on this issue. I appreciate your knowledge and help. Ok. I’ve added the -Mono -window string to the end of the Target line as you instructed. The only 2 log files are attached below. Also, I did not delete the dx9display.dsp file. I’ll do so now.
Thanks again,
Mike
You’re welcome.
Those two error logs you have are normal. They generate everytime BMS is launched. Don’t worry about them. The logs that we’re interested in are Crash logs and xlogs.
They look like this: 2017-02-19_174001_crash and 2017-02-19_164306_xlog
Also, the dx9dislay.dsp file is in your User/Config folder. It will regenerate when you launch BMS.
C9
-
I went looking but couldn’t find it. So here’s my Dumb question. Where do I find the dx9display.dsp file?
-
I answered it above your post. User/Config folder.
C9
