MrSco

@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.

We've been over this already... I've tested and also my friend using a clone of my drive on a different drive ( ): Different drives (internal/external), different machines (high-end/low-end/in-between), fresh window 10 installs ... they all crash... and the one constant is BigBox.exe. you're NUC hardware argument holds no water unless you have an explanation for BigBox.exe crashing on my 8700 i7 16gb ram 1080Ti GPU. (and my buddy's gaming rig mentioned in his post). I've attached my data folder... ? I'm out of ideas... its gotta be related to the actual software on the drive(s) either the launchbox setup/settings/data or the images or videos themselvess? ... not the hardware though... that's clearly proven with the testing. Data.zip

you keep talking about the NUC like its an underpowered device... the thing is a beast... 6th gen i7 with 8gb ram with 30% ram free while bigbox has been running for hours. Plus I've already stated that I've tested on multiple machines, not just the NUC, one of which is a 8700 core i7 with 16gb and a 1080ti gpu... this isn't a hardware issue... its a software issue. I appreciate the idea of attract mode going too fast causing the issue as that is a software issue and makes more sense. The attract mode setting as it is now has it waiting 30 seconds between scrolls... that seems like plenty of time to catch up. Do you use clear logo images on your game wheels or just text? my wheels all have clear logos for the platform and game names... could bigbox not be able to handle scrolling that many clear logos at attract mode speeds? I really feel like if you had my drive in hand you'd easily be able to reproduce on any machine you plugged it into... it has crashed on every machine i've ran it on, i've let friends borrow and test it on their various laptops and gaming rigs... from slow to super fast and with fresh win10 installs... OS/hardware aint it.

gotcha. I'm back on windows 10 and bigbox performance is restored again... still crashing though of course. I have a clone of the usb drive i'm using if you want I can mail it to you so you can test my actual build/theme/data/hardware and maybe you can shine some light... (i'd say I'd upload it and share a link but its like 2TB and would take a week or more to upload). I've already invested money into purchasing this program so i don't mind paying some shipping to get it working properly. Let me know. thanks!

I tested the latest version of LaunchBox/BigBox 11.4 with the .NET Core 3.1 update and BigBox still crashes the same way while in attract mode. I figured I'd try installing windows 7 64bit on my NUC to see how bigbox likes that environment... it doesn't seem to like it very much. The video performance in bigbox is awful and full of artifacts unless switched from VLC to windows media player in options and even then the wheel scrolls so laggy and slow. at least in windows 10 the wheel and videos play ok for the most part... any idea why windows 7 is so laggy?

Looks like I had a bunch it crashes over the weekend but my Auto-relaunch script worked like a dream. @Jason Carr maybe you can build the auto-relaunch in bigbox as a feature since stability seems to be a known issue...at least until you get it running stable. Also, I think the reason the more people aren’t experiencing these crashes is because they aren’t TRUELY leaving BigBox in attract mode for long stretches of time. The issue only occurs if attract mode is left UNTOUCHED for hours/days. If you interrupt the attract mode but moving joystick or launching a game or back grounding bigbox so it pauses all videos and animations, then you didn’t really do a true attract mode stability test. I believe people (I have one friend who has this issue) are also experiencing bigbox randomly losing foreground focus (which pauses attract mode and animations); in that case attract mode really isn’t “running” during the non-foreground time and can’t be counted toward it’s time of stability... which would make it “appear” to be running for long periods of time.

I am using a workaround currently with AutoHotkey to automatically relaunch Bigbox when closed. It will show a dialog with a cancel button and a 5 second countdown. Once the countdown is reached BigBox is relaunched. Not ideal, but better then no attract mode running at all. I also included most of the rest of my startup scripts in case someone finds them helpful. There may be others out there, but I had some unique issues with an always connected XinMo controller as P1/P2 and swapping to wireless xbox 360 controllers on the fly when connected. (i didn't include xpadder.exe or controllercompanion.exe as those are paid apps. you can just comment those lines out with a ; if you don't have/want those or any other steps to run) (and in case you're wondering, I've tested BigBox.exe directly without launching via my ahk script and it still crashes the same way.) Also, as a side/related note, i'm sure there is another thread for feature suggestions, but since @Jason Carr has been watching this one, maybe LaunchBox/BigBox could get some startup/exit script features when starting up or closing down bigbox? ... then I wouldn't have to roll my own like this. Thanks! launchbox-startup-scripts.zip

interesting... both yours and @Retro808 log files contain errors about " Insufficient available memory" ... my logs don't have that going on.

I just tested on an internal 7200rpm seagate 3TB sata drive and the same crash happened after 26 hours. so far we’ve ruled out: theme drive windows computer specs ... not sure what else is left but a bug in the bigbox.exe...?