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 Tuesday at 11:28 AM 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.