xardius99

Seems the stuttering problem was when running arcade games via Mame so i fixed that by running through Retroarch with an arcade core. Did not play extensively tonight, maybe an hour or so, but no shutdowns

I did not physically remove any disk during the Windows reinstall, but i did try to execute steps 5 to 10 from inside Windows-Command Prompt and it didnt work (prior to the reinstall). At this point, I've spent the last 2 days reinstalling and configuring all my games and apps, so I will wait for further instability before redoing the suggested 20 steps. I was going to test BB stability yesterday but I was having problems with audio syncing between my PC and my TV. Before reinstall, i initially had same problem and forgot how it was resolved but both monitors were running 60 Hz. Now i'm stuck with my PC monitor at 60 Hz and my 4k TV at 30 Hz (even though i manually changed the res to 1080p in Windows display settings)....

I went ahead and plugged in my USB Windows 11 key and proceeded to the Windows install process. I deleted, formatted then did some more deletion for good measure on my problematic drive first. The reason for more deletion is that when I formatted, it recreated extra partitions. So i just deleted those and left them as "unallocatted partitions". Next, i tried rebooting into Windows to check on Disk Management utility.... and it wouldn't boot up. So your theory was correct, it was using my old SSD as the boot-up sector. Proceeded then to format my new disk (and losing tons of stuff that i will have to redownload, my fault lol) . But, lo and behold, i dont get a prompt to boot into another OS... so it goes straight into Windows ... BUT : Disk Management shows the same EFI partition on the old disk However, i am optimistic that all should be good now. In the process of doing Windows updates and reinstalling everything. Will post to update on the situation, resolved or not.

" If there is an EFI partition on it, then there really shouldn't be and will continue to mess up booting. If this is the case you will need to wipe this drive FIRST and THEN shutdown the PC and physically uninstall it.." I tried to do a format of the non-boot problematic drive (via clicking on the drive in Windows Explorer and choosing Format) . However, the EFI and recovery partitions are still there and didn't get deleted.....weird... What is the suggested way of wiping the problematic drive ?

I think you are on to something there, here is my Disk Management as we speak : My C drive is my boot drive, but i can see that there are remaining EFI partitions on my old drive ( labeled as F drive ). I am pretty certain i reformatted that drive before installing on the new one. I will go ahead and redo the OS installation as you suggested. Thanks for the input !

Nope, still shutting down...

Going to start Volume Shadow copy manually in Windows Tools-Services and see if that helps...

Got a shutdown running BigBox even though automatic recovery was disabled

Well i had Windows 11 previously installed on my old NvMe SSD. When i got my new NvMe SSD, once i started the installation process : 1) I completely formatted the old SSD, then 2) installed a fresh copy on the new SSD. Edit : Is there anyway to rectify the situation outside of redoing a wholesale reformat/reinstall ? (and would that even change anything with the VSS problem ?)

I am also going to try testing using Launchbox (without BigBox) tonight if i still get shutdowns.

I have noticed during boot-up that the computer asks me to choose between 2 different volumes of Windows 11 (even though i formatted my old drive with previous install). I don't know if that could have any impact whatsoever with the VSS problem....

I recently did a fresh reinstall of Win11 since i bought a new Crucial NvMe SSD. We are talking about 2 weeks ago. Since that time, i have installed / reinstalled a multitude of games (single-player, MMOs, , other emulators like Ryujinx that i launch separately from Launchbox), and i leave my PC on 24/7 as mentioned earlier. The only time the PC shutdowns in when running BigBox. But this occurred also before the Windows reinstall on my older (2020) Samsung Evo 970 NvMe SSD. I have done a bit of searching before posting here and I concur that it is not a frequent problem. I only found 1 other post on the internet on this subject and it was not resolved. However, i have gone ahead and turned off automatic system backup of my main drive and will do more testing tonight. Thanks all for your input, it is greatly appreciated btw. I would really like to enjoy BigBox as the majority of you

I just recently did a fresh install of Windows 11 so i hadn't checked System Recovery option. Noticed that it was turned on for my main SDD drive and i just turned it off. But other than that, i have no other application that I can think of which does automated backing up of files... Edit : Also, just to add that i usually leave my PC on 24/7 and i play alot of modern PC games and this kind of random wholesale shutdown of the PC never happens.

Here is the log for event 8193 (see below), the same type of crashes continued occurring during the evening

Well i did some more testing since adding the .Net Core v7.0 and Launchbox beta v13.6.1. Decided to put back my original theme (3D Dimensions) also. Was really stable for almost 2 hours straight (cycling through many arcade roms, playing up to a minute then switching to another). Then it crashed again :