Crashing navigating files

[BlackPredator72]

OS:  

My issue started with the implementation of .NET 9.0.

Until version 13.18, I didn’t have any problems, but from 13.19 to 13.21 beta 3, the same issue persists.

Everything works perfectly in Launchbox, except when I have to browse for a location while adding a game. For example, when inserting media or selecting the ROM/executable file of a game: the folder opens, but instantly, the BCOD (Blue Circle of Death) appears.

And after a few seconds, I’m back at the desktop. In the Event Viewer, I see this, but I don’t know what it means:

Toepassingsnaam met fout: LaunchBox.exe, versie: 13.21.0.3, tijdstempel: 0x67d30000
Naam van foutmodule: ntdll.dll, versie: 10.0.26100.3775, tijdstempel: 0x5e4be250
Uitzonderingscode: 0xc0000409
Foutoffset: 0x000000000011e216
Foutproces-id: 0x47A8
Begintijd van foutieve toepassing: 0x1DBB36EA560323E
Faulting-toepassingspad: C:\Users\visse\LaunchBox\Core\LaunchBox.exe
Faulting-modulepad: C:\WINDOWS\SYSTEM32\ntdll.dll
Rapport-id: ad6df754-dc37-4cde-953a-4e8204d9c261
Faulting-pakket volledige naam: 
Faulting-pakket-relatieve toepassings-id:  

- System 

  - Provider 

   [ Name]  Application Error 
   [ Guid]  {a0e9b465-b939-57d7-b27d-95d8e925ff57} 
 
   EventID 1000 
 
   Version 0 
 
   Level 2 
 
   Task 100 
 
   Opcode 0 
 
   Keywords 0x8000000000000000 
 
  - TimeCreated 

   [ SystemTime]  2025-04-22T10:10:07.2458190Z 
 
   EventRecordID 27317 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  25140 
   [ ThreadID]  25396 
 
   Channel Application 
 
   Computer GAMEPCDAVE2023 
 
  - Security 

   [ UserID]  S-1-5-21-157999631-2574045945-3901820913-1001 
 

- EventData 

  AppName LaunchBox.exe 
  AppVersion 13.21.0.3 
  AppTimeStamp 67d30000 
  ModuleName ntdll.dll 
  ModuleVersion 10.0.26100.3775 
  ModuleTimeStamp 5e4be250 
  ExceptionCode c0000409 
  FaultingOffset 000000000011e216 
  ProcessId 0x47a8 
  ProcessCreationTime 0x1dbb36ea560323e 
  AppPath C:\Users\visse\LaunchBox\Core\LaunchBox.exe 
  ModulePath C:\WINDOWS\SYSTEM32\ntdll.dll 
  IntegratorReportId ad6df754-dc37-4cde-953a-4e8204d9c261 
  PackageFullName  
  PackageRelativeAppId  

Co-Pilot says the following about this event:

"Based on the details, it looks like the error originates from ntdll.dll, which is a core Windows system file. The exception code 0xc0000409 often indicates a stack buffer overrun, meaning that something—potentially LaunchBox or a related dependency—is causing Windows to terminate the process for security reasons."

The strange thing is that it doesn’t always happen, sometimes I can add media or ROMs without crashing, but most of the time, I can’t.

I already downgraded back to 13.18, and everything works fine, but when I update to the latest version, the issue returns.

I also reported a bug, but I hope someone else has encountered the same issue, which is why I’m posting it here too.

Additionally, I’ve already tried reinstalling Launchbox in a different location, but that didn’t solve the problem either.

Edited April 22 by BlackPredator72

[C-Beats]

There is typically two error logs one that shows the data you've shown and the other with an actual error message. Sounds like this may not be a .NET exception being raised so that MAY not be true but worth checking as the other log generally has much more information. It sounds like there may be some issue with the Windows instance since the DLL is an OS dll. I'd suggest opening command prompt as admin and type the following "svc /scannow" (without quotes) and let that run and see if it identifies any issues with your system files.

[BlackPredator72]

On 4/22/2025 at 2:44 PM, C-Beats said:

There is typically two error logs one that shows the data you've shown and the other with an actual error message. Sounds like this may not be a .NET exception being raised so that MAY not be true but worth checking as the other log generally has much more information. It sounds like there may be some issue with the Windows instance since the DLL is an OS dll. I'd suggest opening command prompt as admin and type the following "svc /scannow" (without quotes) and let that run and see if it identifies any issues with your system files.

Thanks for moving my question to its own topic.

I’ve already tried those solutions, including the commands mentioned here: Use the System File Checker tool to repair missing or corrupted system files.

Yesterday, I reinstalled Windows 11 over the current version while keeping all my data and apps. Starting completely from scratch would be way too much work, so I chose this approach.

However, the issue persists. It seems to be related to Launchbox, as everything works on version 13.18, but not on later versions. Perhaps it’s the combination of factors. Also, why am I the only one experiencing this?

[faeran]

What language is your OS in? and what language do you use inside of LaunchBox?

[BlackPredator72]

2 hours ago, faeran said:

What language is your OS in? and what language do you use inside of LaunchBox?

Both are in Dutch

[MysterNybble]

Would you be willing to produce a crash dump that we could analyze? 

If so, download this https://learn.microsoft.com/sysinternals/downloads/procdump

From an admin elevated command prompt from where you placed procdump, run

procdump -e -ma Path\To\LaunchBox\Core\LaunchBox.exe

Then go and make LaunchBox crash - that should create a file from wherever you ran procdump from - then, using your favorite secure file sharing service, send us a link to support@ email or through our bug report system at https://feedback.launchbox.gg/

I'm not confident we'll see anything useful, but without any other errors from your machine, I'm hopeful 🤞

(let me know if you need any help with the above steps / command)

[BlackPredator72]

On 4/24/2025 at 12:47 AM, MysterNybble said:

Would you be willing to produce a crash dump that we could analyze? 

If so, download this https://learn.microsoft.com/sysinternals/downloads/procdump

From an admin elevated command prompt from where you placed procdump, run

procdump -e -ma Path\To\LaunchBox\Core\LaunchBox.exe

Then go and make LaunchBox crash - that should create a file from wherever you ran procdump from - then, using your favorite secure file sharing service, send us a link to support@ email or through our bug report system at https://feedback.launchbox.gg/

I'm not confident we'll see anything useful, but without any other errors from your machine, I'm hopeful 🤞

(let me know if you need any help with the above steps / command)

I updated to the latest LaunchBox version (13.21), but unfortunately, the issue persists. To troubleshoot, I tried the following commands:

C:\Users\visse\LaunchBox>procdump -e -ma C:\Users\visse\LaunchBox\launchbox.exe
C:\Users\visse\LaunchBox>procdump64 -e -ma C:\Users\visse\LaunchBox\LaunchBox.exe
C:\Users\visse\LaunchBox>procdump64 -e -ma C:\Users\visse\LaunchBox\Core\LaunchBox.exe
C:\Users\visse\LaunchBox>I:\Downloads\Procdump\procdump64.exe -e -ma C:\Users\visse\LaunchBox\launchbox.exe

Each time, I received the following error message:

ProcDump v11.0 - Sysinternals process dump utility
Copyright (C) 2009-2022 Mark Russinovich and Andrew Richards
Sysinternals - www.sysinternals.com

No process matching the specified name can be found.
Try elevating the command prompt or using PsExec to make one as SYSTEM.
        psexec.exe -s -d -i cmd.exe
        procdump.exe -accepteula ...

However, using the process ID (PID) instead worked successfully:

I:\Downloads\Procdump\procdump64.exe -e -ma 22368

This created a dump file: LaunchBox.exe_250425_104025.dmp (size: 3.5 GB)

I uploaded the dump file to the topic I previously created on the LaunchBox Feedback page, titled: "Crash to desktop when adding game or media.

[BlackPredator72]

I'm on 13.22 beta 3 and still having the same issues.

Has anybody looked in to .dmp file I've send to Feedback page?

[penfoldcrumbs]

Hi,

I am also experiencing this issue. Anytime I open the file explorer within LaunchBox (13.22), to add roms etc, LaunchBox crashes without error. Reproducible every time.

Logs are on my other machine, can post exception here later today.

[BlackPredator72]

On 7/24/2025 at 11:49 AM, penfoldcrumbs said:

Hi,

I am also experiencing this issue. Anytime I open the file explorer within LaunchBox (13.22), to add roms etc, LaunchBox crashes without error. Reproducible every time.

Logs are on my other machine, can post exception here later today.

Yes please, sharing the exception could be really helpful. Hopefully if more users report this, it’ll prompt the devs to take a closer look.

[BlackPredator72]

Launchbox 13.24 beta 1 still the same problem

Trying to manually add some media for a new game and

Crash...back to desktop

[BlackPredator72]

You know what makes this so annoying? Every time I want to add a new game to LaunchBox, I can only enter the name. Most of the time, it's a new Windows game, so LaunchBox doesn't recognize it at all. That means I have to manually search online for the cover image, banner, logo, and gameplay screenshots. I also download the video using a YouTube MP4 downloader.

Then I have to rename every media file to match the game's title. After that, I move each file to the correct folder inside LaunchBox, like Media > Images or Media > Videos. Finally, I have to manually enter the game's directory and the .exe file into the right field so the game can actually launch.

Normally, you'd just click the Browse button and select the media or the executable file directly. But in this case, everything has to be done manually, and it's a real hassle.

So hopefully someone can take another look at this at some point. It would be great if the process could be streamlined a bit.

[C-Beats]

Honestly sounds like you have an issue with explorer and Win32 processes on your computer. If File Explorer is crashing when you press browse that's not our code running and is native Windows calls. If you haven't already make sure to run command prompt as admin and run "DISM.exe /Online /Cleanup-Image /RestoreHealth" (without the quotes) first and let it run. This ensure Windows has the latest and correct definitions for what files your OS should be using. Then run "sfc /scannow" (again, without the quotes) and let it run and see if it corrects anything. If it does restart your computer.

File explorer and those Win32 processes also REALLY lag behind if you have network locations not actually hooked in and communicating properly. I have a network drive that is often off and Windows still tries to ping the thing when File Explorer first opens and it causes issues and extreme delays at times in my own File Explorer processes across several apps (and even Windows itself). Sometimes you can alleviate the issues with it doing so by opening File Explorer in windows FIRST, and THEN doing it in the app. I believe it has a sort of response cache it'll utilize and causes it to happen far less often (or least does on my machine).

Also some of what you're doing is still WAY more work than you'd need to do even if you can't run File Explorer via LB. For example import the game (can do multiple by just drag/dropping files from File Explorer to LaunchBox) and then in the import options check the box that says something like "Use Folder Name for Game Name" should help if the exe is some random filename. If it doesn't rename the title and then in the edit game window immediately press "Search for Metadata" and then pick the game from the drop down. Then you can go to the Images or Video tab and grab images for it from there, or when you're done doing that for all the games you are imported just run the Download Metadata/Media wizard. If THAT doesn't find the images you need and you have to manually grab them, instead of manually moving/renaming them just open the Edit Game window for the game you're adding them to and then go to the Images tab and drag the files to the preview area. Now set the Image Type for those images that you added and save the Window. We'll copy the images to where they need to go and name them correctly for you.