MrSco
-
Posts
95 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by MrSco
-
-
On 9/11/2020 at 6:05 AM, MrSco said:
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)
1 hour ago, Jason Carr said:@MrSco All good info. I don't see anything new coming to light with those new error messages, unfortunately. The fact that you are seeing the same thing with 10.0 is telling, however, as it looks like it wasn't introduced recently.
I've been testing with zero crashes on all five of my testing machines since Friday. I'm gonna just ask you a bunch of questions in hopes that we can find a lead. Forgive me if I've asked any of these already:
- Is there anything in common on the machines that are crashing (such as a particular USB device attached or a particular piece of software that's installed)?
- What version of Windows 10 are all of the machines running (you can look this up easily by typing winver into the Start menu)?
- By some miracle, does 11.5 resolve the issue (lots of fixes did go into 11.5)?
- What models are the external and internal hard drives/SSDs that you're using?
- What file systems are you using on the drives (NTFS, exFAT, or FAT32)?
I ask these not to blame any of it, but so that I might be able to determine the cause or change something in a test system in order to replicate.
- 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
-
14 hours ago, MrSco said:
@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:
@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:
-
On 9/11/2020 at 9:06 PM, MrSco said:
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?
@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:
-
8 hours ago, Jason Carr said:
@MrSco It will be helpful to know whether you have the issue with those old versions. This is a slightly different fault offset number than the other error I was searching with, so that is helpful as well. I assume it was on a different system?
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?
-
2 hours ago, Jason Carr said:
Also @ItchyRobot and @MrSco remind me what Big Box themes you're using? That may help me reproduce.
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.
-
Just now, wallmachine said:
Sometimes while watching attract mode I see BigBox loose my platform images so maybe something similar happens for you? corrupt caching any one mans guess I tried deleting the BigBox cache from the folder etc no luck
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
-
5 hours ago, Jason Carr said:
@MrSco It will be helpful to know whether you have the issue with those old versions. This is a slightly different fault offset number than the other error I was searching with, so that is helpful as well. I assume it was on a different system?
This was the same system but new launchbox 11.5 beta version
-
4 minutes ago, wallmachine said:
I'm on 16GB RAM & Intel Core i7 7700K and after some time BigBox gets sluggish and crashes even on the default theme (I've provided logs/videos in previous threads/posts). I do have just over 200 platforms and 50k games and know this was an issue a while ago then people stopped complaining about it. Probably unrelated but could be something similar like with LaunchBox when you have heaps of platforms then go to import a large platform it causes the import to take longer/work harder? in my case and others it takes MAME 2hrs when I have 200+ platforms about 30-40 seconds with a fresh copy of LaunchBox and yes, I know this has nothing to do with BigBox but if the culprit is having too many platforms/games causing the crash because BigBox is working overtime and can't keep up?
MrSco how many platforms/games do you have if it's quite a bit this might be hard for Jason to rule out or replicate as from posts I've seen he mentioned he tests with PCs that have around 5k games I think it was
I have about 30 platforms with like 13,000 games in total. All with video snaps and images.
-
16 hours ago, Jason Carr said:
@MrSco Thanks. It is important to use the most up to date version if possible, yes. 11.4 would work, but 11.5-beta-2 would actually be better because we've fixed a number of issues with .NET Core.
I did look at all the logs, yes. Sorry if I didn't respond. I haven't been through this whole thread in detail recently, though, and it's certainly easy to forget some of what we've discussed. I just took a look at the very first post, and noticed that you stated that it started with 10.7. That might be an important lead if we can determine that 10.6 does not have the issue. I can get you a copy of 10.6 if you need.
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)
-
1
-
-
2 minutes ago, Jason Carr said:
I need to know whether all of the numbers specifically are the same:
Faulting module name: ntdll.dll, version: 10.0.18362.418, time stamp: 0x99ca0526 Exception code: 0xc0000374 Fault offset: 0x00000000000f9269 Faulting process id: 0x1c08If not, it would very much help to see what the numbers are on the other systems. I understand that it's the same basic error, but the numbers are the key.
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.
-
Just now, Jason Carr said:
All I'm asking for is for you to confirm that error messages are the same on different machines...that's it. Can you help with that?
Yes. It’s always the same error
-
Just now, Jason Carr said:
I can't help you if you're not willing to dive in deeper. I'm sorry for the issues, but we have thousands of users who do not have these issues at all, and I need your help to troubleshoot it. I don't care if "it's Big Box" or not, I just want to try and fix it. Unfortunately though, I still need your help to get a lead, or I'm stuck dead in the water. I can't fix anything if I don't know what exactly is broken.
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.
-
1 minute ago, Jason Carr said:
That's right, same useless error unfortunately. When I Google that particular error, I get random junk about everything from Red Dead Redemption 2 to Photoshop and all kinds of stuff in between. The best suggestions I've found are to run the Microsoft System File Checker or to uninstall and reinstall ntdll.dll.
I honestly don't think uninstalling and reinstalling ntdll.dll will do any good, but running the system file checker might. Here's the thing, though, can you confirm that you get the same exact error on every machine you've tested it on? Because I'm doubtful that the error will be the same everywhere (that also might be an important clue).
@ItchyRobot What errors are you seeing in the event log?
I’ve done multiple fresh installs of windows and different machines altogether. This isn’t windows. It’s bigbox.
-
1
-
-
2 minutes ago, Jason Carr said:
@ItchyRobot @MrSco Can you guys check your event viewer after a crash? Just type Event Viewer into the Start menu and that should load it up. Then go to Windows Logs (on the left), Application. There should be at least one Error entry related to the crash. If you can copy and paste me all that text, it might help me figure out why the crashes are occurring on your machines. There may be multiple entries that apply. LaunchBox logs may be helpful as well, though iirc I think we've exhausted those and they weren't giving me any clues.
The more I think about this and look into it, the more I'm doubting that we're on the right path, especially if crashes are occurring in less than 15 minutes.
yep, we've been through this...
-
15 hours ago, ItchyRobot said:
I think you may be on to something with the speed settings. I am one of the thorns in your side with this crashing issue; but, after changing from fastest to Average (for min and max), I was able to go an hour without it crashing-I stopped it at an hour, no crash. I usually have a crash within 15 minutes. Though I still do have the issue with having to force close my Bigbox after exiting if I want to open it again... otherwise it says it is already open. I'm sure you already know of this.
I lowered the speeds to the “slowest” on the attract mode scrolling but still crashed
-
29 minutes ago, C-Beats said:
@MrSco is it possible that the PCs you are plugging the external drive to have entered sleep mode? By default Windows shuts off external drives when entering sleep or any "low power" or "power saving" mode. Is it possible those have not been shut off and the OS is killing connection to the drive thus causing issues?
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.
-
27 minutes ago, Jason Carr said:
I'm not an expert on NUC devices, but the NUC is likely an underpowered device when it comes to the GPU and RAM. 8 gigs unfortunately these days is rather underpowered for Windows 10. Even just Firefox as I'm typing this is taking up more than 4 gigs of RAM. I'm not sure what graphics it's running, but I would guess that they're fairly underpowered.
Usually the issue comes more from the wheel scrolling so quickly during moving operations, and image caching, not catching up between moves.
Yes, pretty much everyone uses clear logos, myself included.
Come to think of it, could the issue be that the performance issues and/or crashes are caused by running it off of a slow-ish external drive? That might be worth testing.
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.
-
1 minute ago, Jason Carr said:
Unfortunately I'm doubtful that having the drive would really help here; we've done enough testing to narrow it down to an operating system or hardware configuration/performance thing. I've done some more testing today and I think what's really happening is that Big Box just starts to eventually choke and die when the hardware can't keep up with attract mode. Especially on something like a Nuc, the hardware can get overwhelmed and the software starts falling behind pretty quickly. Attract mode runs on a timer, so if it queues up enough operations, eventually it'll just overflow and die if the hardware can't keep up.
That's a serious challenge to fix, but the simplest thing to do would be to just slow attract mode down. It runs lightning fast currently, which may be the cause of crashes on lower-end systems. I'll look to add a setting for that here soon, which will hopefully help.
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.
-
15 hours ago, Jason Carr said:
Windows 7 isn't optimized with the latest drivers or Microsoft optimizations, so that makes sense. Running Windows 7 at this point in time is definitely not recommended.
It's back to the drawing board then with those crashes, which I still have not been able to replicate with any consistency. I was able to get Big Box to crash once after running attract mode for 4 or 5 days straight a couple weeks back, but that's all I've seen since. Unfortunately I didn't get any leads on what caused that particular crash, but we'll keep our eyes open for anything new to look into.
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!
-
On 7/21/2020 at 11:50 AM, Jason Carr said:
We are currently in the process of upgrading to the latest .NET backend, which could address some of these issues for some people if we're lucky. We'll come back to this after upgrading everything to .NET Core 3.1 to see where we're at.
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?
-
On 7/16/2020 at 2:57 PM, MrSco said:
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!
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!
-
16 minutes ago, Merlin said:
Here is my log to see if anything pops out.
Crashing every 3 to 15 days in attract mode.
Dell Optiplex 7020, i5-4590, 8gb, onboard graphics
If you have any questions for me just post them in this thread
interesting... both yours and @Retro808 log files contain errors about " Insufficient available memory" ... my logs don't have that going on.
-
On 7/6/2020 at 12:39 PM, Jason Carr said:
You can enable debug logs under Tools > Options > Debug in LaunchBox, and then the debug logs will show up under LaunchBox\Logs. That should help us going forward to figure it out.
The mechanical USB hard drive might actually end up being the culprit here, because I really don't do any testing that way currently (maybe I should). The four systems that I test on regularly all use internal SATA SSDs and/or mechanical drives. They're all stable and can run for days on end, so that may be the difference.
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...?
BigBox crash while sitting idle doing attract mode
in Troubleshooting
Posted
@Jason Carr