Jump to content
LaunchBox Community Forums

BigBox doesn't start all the time


CyberMonkey

Recommended Posts

This problem just started happening this past week.
BigBox doesn't like to open all the time, will get a black screen and then it does back to my desktop. If trying to start it again, it errors stating there's already an instance of it running, and sure enough checking the Task Manager it's there.
Though, it does seem to work just fine if I start LaunchBox first and then go into BigBox from there.

Below is the error log states everytime it fails to actaully start. Any assistance would be appreciated:

 

2024-10-27 03:17:19 AM FIRST CHANCE EXCEPTION: Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request..
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
2024-10-27 03:17:19 AM FIRST CHANCE CONTINUED INNER EXCEPTION: The I/O operation has been aborted because of either a thread exit or an application request.

2024-10-27 03:17:19 AM FIRST CHANCE EXCEPTION: Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request..
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
   at System.Net.Security.SslStream.ReadAsyncInternal[TIOAdapter](TIOAdapter adapter, Memory`1 buffer)
2024-10-27 03:17:19 AM FIRST CHANCE CONTINUED INNER EXCEPTION: The I/O operation has been aborted because of either a thread exit or an application request.

2024-10-27 03:17:19 AM FIRST CHANCE EXCEPTION: Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request..
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
   at System.Net.Security.SslStream.ReadAsyncInternal[TIOAdapter](TIOAdapter adapter, Memory`1 buffer)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2024-10-27 03:17:19 AM FIRST CHANCE CONTINUED INNER EXCEPTION: The I/O operation has been aborted because of either a thread exit or an application request.
 

Link to comment
Share on other sites

  • 5 weeks later...

Hi @CyberMonkey sorry for the issues here, may I confirm a few things to try and narrow this down:

- What version of LaunchBox do you have installed?

- Where is your LaunchBox directory location (i.e SSD, Network Drive, Cloud storage etc)

- What theme are you using within Big Box

- What are the specs of the machine you're running (CPU, GPU, RAM, etc)

- Can you elaborate a bit more on the frequency to which this happens? You mention it happens (sometimes), though are you able to reproduce this, or it appears to happen randomly?

Let me know and we'll see if we can get you sorted.

Link to comment
Share on other sites

The version of Launchbox is 13.17 which I believe is the current version

The directory is located on a separate drive for installs.

The theme I am using in Big Box is a theme called CleanBG.

The specs on the PC:  Intell Core i5 CPU; Nvidia GTX 1080; Ram is 32GB

 

It happens pretty often; I would say about 8 out of 10 times when trying to open Big Box directly.

I use Nexus Dock and have a shortcut to BigBox on it, I thought that was the issue, but even when trying to open BigBox directly through Windows Explorer or even via the start menu the issue happens.

 

Link to comment
Share on other sites

Hi @CyberMonkey thanks for the update there. 

The next step here would be to identify if the issue is something within your LaunchBox build, or something in your environment. 

An easy way to test this is to install a separate instance of LaunchBox (you can use the installer located in your LaunchBox > Updates folder). Install it in a similar location, apply your license and try to load BIg Box, does the issue still occur?

If so, it indicates there is something within your specific Windows environment that is having issues, but if not it may be something with your specific LaunchBox build.

That will help us know where to look next. Please let us know and we'll get you sorted.

Cheers,

Link to comment
Share on other sites

Heya,

I'm seeing the same behavior on my arcade cabinet, and this also started very recently (within the last 2 months). I would say it happens once every 2-weeks on average. My cabinet is set on a timer, which powers it down (at the wall plug) at night, then turns it on again in the AM. So this is a straight cold boot each time. Normally, I come into the office and see it powered up and waiting at the BigBox game selector scroll wheel, but I have seen it at the windows screen three times now, and when i try to run BigBox, it pops up that same error message the OP had. I have to task manager kill it, then run it again to fix it.

  • LaunchBox - v13.17
  • LB directory location - SSD
  • Theme - default
  • Machine specs 
    • CPU - Intel Core i% @3.2Ghz
    • GPU - nVidia GeForce GTX 1070
    • Ram - 16 GB

 

Link to comment
Share on other sites

Hi @CommanderDoug

Thanks for the report there and sorry for the issues. If it's possible, could I suggest you try the same next steps I mentioned to CyberMonkey, being that we want to identify if the issues occur on a brand new build of LaunchBox. 

I realise it's a pain to test this, but it will help us narrow down if the issues lies within your Windows environment or the specific build of LaunchBox. You can just install a new instance, install a few games and see if it happens. I realise that is easier said that done since the issue occurs intermittently, but if it's at all possible it will hep us massively narrow down where to look next. 

Cheers,

Link to comment
Share on other sites

So, I have it setup as "portable".
I deleted it from the SSD it's on, copied the setup from the USB I keep a copy on and the problem still persists on that one PC.
When I run it off the USB drive on the computer in the computer room it always works fine. I have the same setup saved to a SD card I have in my ROG Ally, and it works just fine.
All three machines are Windows 11, so there much be something about that one PC within the Windows environment that it is not jiving well.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...