BrewerA Posted May 24 Share Posted May 24 I have an issue that involves multiple components from different vendors. I am looking for help isolating an issue I am having and maybe you can give me some direction on diagnostics of your specific components. Below is the summary of components. Arcade Cabinet fitted with the following: Hardware Ultimarc I-PAC Ultimate I/O board GoldLeaf RGB buttons 2xServoStik Joysticks w/ ServoStik Control Board SpinTrak Rotary Control U-Trak Arcade Trackball w/ U-Trak RGB LED illumination kit UltraStik 360FS Flight Stik Software Bigbox/Launchbox front-end over Windows 10 Professional LEDBlinky software integrated with Launchbox/ServoStik/RGB button control The cabinet is setup to launch directly into Big Box as the Windows shell during bootup. Big Box loads, LEDBlinky engages and plays the button and trackball animations, and then one sees the playlist of games to select. At this time the only thing that is odd after the animation is the following buttons illuminated. I was never encountering the issue as I know what buttons to push and navigate but if I push a few buttons (it is repeatable if I push Player 1 button 3 and 6 at the same time) at once the whole Big Box front end crashes. The error I see in the Windows Event Viewer is: Level Date and Time Source Event ID Task Category Error 5/24/2024 11:52:01 AM Application Error 1000 (100) "Faulting application name: BigBox.exe, version: 13.14.0.0, time stamp: 0x65ab0000 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00007ffdfe09a933 Faulting process id: 0x22d0 Faulting application start time: 0x01daae0b39c8d00d Faulting application path: D:\Emulation\LaunchBox\Core\BigBox.exe Faulting module path: unknown Report Id: cb4f81cc-0fed-4522-8f2e-e25b1bd7157f Faulting package full name: Faulting package-relative application ID: " The only way I can get it going again is to do a control-alt-delete and choose task manager and select the run option to launch the Big Box executable. Since there are many components in the system I am asking what type of logging I can enable or test for your side of things to help solve this problem. I am aware that the Big Box executable is crashing app but am unsure if it is the "keyboard" combo of the I-PAC or the LEDBlinky software or just Big Box. Do you have any advice in helping to isolate and solve this issue? Quote Link to comment Share on other sites More sharing options...
Retro808 Posted May 25 Share Posted May 25 Do you get any type of crash error or BB just closes? I would double check your input mappings and make sure you do not have anything mapped to the option for "Exit" as the option is to Exit BB and not to exit a game. Quote Link to comment Share on other sites More sharing options...
BrewerA Posted May 26 Author Share Posted May 26 BB just closes with an windows event log entry. I will double check all mappings in BB. Maybe just remove them all as a test. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted May 28 Share Posted May 28 If the Event Viewer has an app crash log there will be two of them for the crash, one log just saying the app crashed and the other with the actual exception. The text you posted appears to be the "it crashed" log which won't be helpful at all. The other log should at least list a reason for the crash. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.