MrSco

another crash this time on 11.6 on the NUC (last crash after removing 'bogus' images was on my 8700 i7/1080ti rig)... Faulting application name: BigBox.exe, version: 11.6.0.0, time stamp: 0x5ee99cfc Faulting module name: ntdll.dll, version: 10.0.18362.1049, time stamp: 0xb5beef21 Exception code: 0xc0000374 Fault offset: 0x00000000000f9229 Faulting process id: 0x2ac0 Faulting application start time: 0x01d68e967776e434 Faulting application path: H:\Arcade\LaunchBox\Core\BigBox.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 2d7a28a5-9bc9-4653-bfa9-97617a9974dc Faulting package full name: Faulting package-relative application ID: there was a fault bucket error in the log just after. i attached it as well Report.wer

spoke too soon... just had a crash even with all those (attached list of 300 or so out of 14000+ good images) bogus images removed... Faulting application name: BigBox.exe, version: 11.4.0.0, time stamp: 0x5ee99cfc Faulting module name: ntdll.dll, version: 10.0.19041.488, time stamp: 0x70e69bad Exception code: 0xc0000374 Fault offset: 0x00000000000fed79 Faulting process id: 0x5998 Faulting application start time: 0x01d68e44f565ae94 Faulting application path: H:\Arcade\LaunchBox\Core\BigBox.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 9307b472-7433-4e33-b94d-9d215103f00a Faulting package full name: Faulting package-relative application ID: badpeggy_list.txt

Yea I’ve already deleted the bogus images and have been running attract mode for about 12 hours without a crash yet. We shall see... the scary thing is, all these images were downloaded using launchbox’s database search either from wiki or emumovies. So doing another missing media search would potentially bring all the bogus images right back.

@Jason Carr could it be corrupt images causing the crashes? i found this Bad Peggy (https://superuser.com/a/1083216) program to scan all the image files and its only about halfway done but already found lots of errors ... the clear logo one in particular peaked my interest...

welp, i ran the ffmpeg script to test all the .mp4 files for corruption and they all checked out... no errors found. I did notice that some of the 30 video files are like 30MB... could bigbox be choking on too many videos at a larger size? i may have asked this before but, When you run your tests are you running attract mode with videos for each game that the video plays fullscreen as the entire background? i guess i can check the image files next to rule them out... anyone know a test for image corruption?

I'm running a script against all my video files with ffmpeg to see if it finds any corrupted videos. that should help rule out the media... https://superuser.com/a/1241089

nice, thats not a bad idea. I did another workaround a while back (these crashes have been happening since v10 for about a year or more now)... https://forums.launchbox-app.com/topic/52601-bigbox-crash-while-sitting-idle-doing-attract-mode/?do=findComment&comment=357277 attached to this post is a more recent version of the startup script I use that has an automatic relaunch of bigbox with a countdown to cancel when bigbox is closed/crashes. Also, In case any one is wondering, yes, i tested bigbox.exe running directly and not through autohotkey startup scripts and it still crashes the same way. launchbox_scripts.zip

Still crashes the same way after deleting the settings xml files

@Jason Carr

nothing too much in common between machines. bare bones fresh windows 10 x64 pro all with latest updates - version 2004 (OS Build 19041.508) see above mostly western digital my passport 3.5" usb3 hdd. couple seagate baracuda internal 3tb. and a segate usb3 3.5" external all NTFS

@Jason Carr I couldn't get full screen videos on games (only platforms had fullscreen videos) on version 9.10; it only would show coverflow view for game wheel no matter what view i selected (not sure if i made my data xml cranky by downgrading and upgrading versions so much) ... so i switched to v10.0 for testing where full screen videos would play on all views to make sure its truly stressing... yet another crash after about 8 hours of running on another computer (diff rig from above), running a clone of the same drive... unified redux theme... i7 8700/16gb ram/1080ti ... Faulting application name: BigBox.exe, version: 10.0.0.0, time stamp: 0x5d766db7 Faulting module name: ntdll.dll, version: 10.0.19041.488, time stamp: 0x70e69bad Exception code: 0xc0000374 Fault offset: 0x00000000000fed79 Faulting process id: 0x4734 Faulting application start time: 0x01d68a2aa6320ebe Faulting application path: H:\Arcade\LaunchBox\BigBox.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: ca1af24a-a3cd-405a-897f-0aed302bddcb Faulting package full name: Faulting package-relative application ID:

@Jason Carr i got v9.10 going now. i had to move all the newer updates out of the updates folder so it wouldn't automatically update on launch. i'll let it run on my 8700/1080ti for a while and see how it does and report back. also, here's another crash from a different machine (not the NUC) using a clone of the drive.... Faulting application name: BigBox.exe, version: 11.2.0.0, time stamp: 0x5f08aebb Faulting module name: ntdll.dll, version: 10.0.19041.207, time stamp: 0xcad89ab4 Exception code: 0xc0000374 Fault offset: 0x00000000000fdec9 Faulting process id: 0x1a2c Faulting application start time: 0x01d65bad05da602b Faulting application path: H:\Arcade\LaunchBox\BigBox.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 9973dd89-1178-44f2-95a5-2edd80b658c0 Faulting package full name:

I'm trying to rollback to v9.10 in the LaunchBox/Updates folder. It works for launchbox... but then i go to open bigbox and it immediately installs the latest v11.4 stable version. i turned off auto updates but still no go... how do i roll back?

We’ve gone through the theme angle in this thread already together previously... they all crash. Default, Unified redux (my current preferred) and the color one by viking.

Nah. Bigbox stays performant the whole time it’s running for the most part. If I scrolled the wheel too quickly, sometimes the clear logos would take a second or two to show up. I’ve purged and rebuilt the cache before and it helped But ultimately still crashes

This was the same system but new launchbox 11.5 beta version

I have about 30 platforms with like 13,000 games in total. All with video snaps and images.

Just got a crash after 10 hours or so on latest 11.5 beta... Faulting application name: BigBox.exe, version: 11.5.0.4, time stamp: 0x5ee99cfc Faulting module name: ntdll.dll, version: 10.0.18362.1049, time stamp: 0xb5beef21 Exception code: 0xc0000374 Fault offset: 0x00000000000f9229 Faulting process id: 0x2640 Faulting application start time: 0x01d687b41bd94788 Faulting application path: H:\Arcade\LaunchBox\Core\BigBox.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 3b148de2-ce76-4ee5-ab21-6d9b06637697 Faulting package full name: Faulting package-relative application ID: I'm gonna setup an old v10 build to test... maybe even v9 (this may have started with v10)

does it need to be from the same bigbox release version? if so, i'll need to collect from different computer on v11.4. if not... this bigbox version has changed but there is this... did you ever look at my logs I sent? i never saw a response from you.

Yes. It’s always the same error

If you aren’t willing to dive deeper there’s nothing more I can do on my end. There’s nothing illegal about a dude mailing another dude a hard drive in the mail. that’s just a lame excuse cause you won’t dive deeper. I’ve dived in as deep as it gets. It makes zero sense to do file repairs on a freshly formatted windows install with all the updates. And I’ve done multiple fresh installs. Across multiple different machines. I’ve been debugging and testing your software for the last year dealing with the same issue. I’ve had to code workarounds for your software’s crashes to auto relaunch so my arcade machine stays running. so please don’t tell me I’m not doing my part.

I’ve done multiple fresh installs of windows and different machines altogether. This isn’t windows. It’s bigbox.

yep, we've been through this...

I lowered the speeds to the “slowest” on the attract mode scrolling but still crashed

no, computer is set not to sleep as is the usb drive, plus this happens on internal drives as well and on many different high end machines. also the crash happens randomly... from hours to days sometimes and anything in between.