MrSco

Well scratch autohotkey and xpadder off the list of causes... I let BigBox.exe run solo in attract mode for a bit longer than 6 hours and eventually it crashes with the error from my original post. But I’ve tested a couple more times and it’s crashed in 2-4 hours also. So the time it takes seems to be random

well i've been running BigBox now for about 4+ hours and no crashes yet. Usually it would have crashed multiple times (after restarts) by now. The change? I had some autohotkey scripts and xpadder.exe running in the background on boot... i disabled those and just ran BigBox.exe only. one of the autohotkey scripts is used to launch xpadder and bigbox at boot... the other is for some custom controller monitoring to be able to use either the wireless xbox controller or the built-in bartop joystick controls as the first player (toggles the bartop xinmo joysticks enabled/disabled using devcon.exe). i'm not sure which autohotkey script is the issue, or if bigbox doesn't like xpadder running in background? what are you guys using to launch bigbox and other exe's at computer bootup in a silent, clean, hidden manner?

thanks, I'll try sleuthing this week and post back...

I got latest windows updates and it even had an intel graphics driver update And did that too but it’s still crashing the same way.

haven't tried other themes. i've been using this viking colorful theme for a while now (and letting it sit idle on attract mode for many hours) and its worked great up until LaunchBox 10.7 ... now crashes after extended periods of idle.

Roger that.

I think it’s set to VLC... should I try swapping ?

It seems to be crashing every couple hours now... this seems to have started since the last 10.7 update... @Jason Carr any other recent reports like this? Only other thing I can thing of is windows updates... I’m on latest windows 10 1909

I just had BigBox.exe crash on me while it was running for a couple hours just sitting idle going through its random attract mode switching through games and having the videos play. I've had it I've had it do this much longer without issues before. I'm on the latest version of launchbox 10.7... Here is the event log error... Faulting application name: BigBox.exe, version: 10.7.0.0, time stamp: 0x5dd429b2 Faulting module name: ntdll.dll, version: 10.0.18362.418, time stamp: 0x99ca0526 Exception code: 0xc0000374 Fault offset: 0x00000000000f9269 Faulting process id: 0x1c08 Faulting application start time: 0x01d5a46e85993ab6 Faulting application path: H:\Arcade\LaunchBox\BigBox.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: a61fdc1c-b95d-4916-bb93-a9f2f74567bf Faulting package full name: Faulting package-relative application ID: any ideas?

yea, i am using built-in mame ui cancel, but i also have some xpadder stuff going on during launch/exit... i just didn't include in my examples for simplicity. thanks for the help!

I figured out what it was... me being dumb... In my mame emulator setup in LB for autohotkey running script, I had... $Esc:: { Process, Close, {{{StartupEXE}}} } I switched it to ... $Esc:: { WinClose, ahk_class MAME } and now the settings save when exiting mame via launchbox/bigbox.... the Process, Close method must not exit mame gracefully and therefor doesn't save anything. hope this saves someone else some time. thanks everyone for the tips!

Thanks. Me too. I’ll keep tinkering and post back my findings here no matter how stupid I end up looking 😉

0 ... but as I said before, if I launch MAME exe directly everything saves fine. Only when launched with launchbox or big box does it not save

With Mame’s built-in escape key exit

Also, the nvram (midway volume for example) settings don’t save either when launched with LaunchBox. It definitely seems like a permissions issue. But launching as admin has no effect... so weird.