hooked up to TV via a dedicated HDMI...here's a couple of the different error logs. they all seem different? .not sure what the issue is...any help is much appreciated.
1.
Faulting application name: BigBox.exe, version: 13.3.0.0, time stamp: 0x63cf74d2
Faulting module name: ntdll.dll, version: 10.0.22000.1880, time stamp: 0x40303075
Exception code: 0xc0000006
Fault offset: 0x0000000000039e01
Faulting process id: 0x16c0
Faulting application start time: 0x01d98602514d9a54
Faulting application path: R:\Launchbox\Core\BigBox.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 5788b6f2-a12d-4fdd-8d5e-15af273b3410
Faulting package full name:
Faulting package-relative application ID:
2.
Windows cannot access the file R:\Launchbox\ThirdParty\Chromium\libcef.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program CefSharp.BrowserSubprocess because of this error.
Program: CefSharp.BrowserSubprocess
File: R:\Launchbox\ThirdParty\Chromium\libcef.dll
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: C000000E
3.
Log Name: Application
Source: Windows Error Reporting
Date: 5/13/2023 6:22:26 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: mariogame
Description:
Fault bucket 1729641004646706626, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: LaunchBox.exe
P2: 13.3.0.0
P3: 63cf74d2
P4: ntdll.dll
P5: 10.0.22000.1880
P6: 40303075
P7: c0000005
P8: 00000000000a8a77
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5420abe9-1526-4917-883d-52e81df2c52a.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.18ef1e4c-d0e1-47f0-8da9-b8e2ecef2183.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4bb4a32b-4ffb-4ae7-befe-df77ce927dc4.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.3cb5d97d-cf17-4af2-ba52-2a0e62ed45b3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4bdb9748-cdd5-4c9d-872a-3e576971b465.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LaunchBox.exe_3c0919576ff3877b7ad358ac8aedd83954997_9c13cd35_41b643fa-61f2-4dd1-82cc-c5e95fb6c8b2
Analysis symbol:
Rechecking for solution: 0
Report Id: b68a43ce-40a7-4ce1-9b6b-abf8cc3e5d64
Report Status: 268566528
Hashed bucket: 100b8b77cfd2aa7aa800eb5466eaadc2
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-05-14T01:22:26.1093860Z" />
<EventRecordID>5489</EventRecordID>
<Correlation />
<Execution ProcessID="2188" ThreadID="0" />
<Channel>Application</Channel>
<Computer>mariogame</Computer>
<Security />
</System>
<EventData>
<Data>1729641004646706626</Data>
<Data>4</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>LaunchBox.exe</Data>
<Data>13.3.0.0</Data>
<Data>63cf74d2</Data>
<Data>ntdll.dll</Data>
<Data>10.0.22000.1880</Data>
<Data>40303075</Data>
<Data>c0000005</Data>
<Data>00000000000a8a77</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5420abe9-1526-4917-883d-52e81df2c52a.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.18ef1e4c-d0e1-47f0-8da9-b8e2ecef2183.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4bb4a32b-4ffb-4ae7-befe-df77ce927dc4.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.3cb5d97d-cf17-4af2-ba52-2a0e62ed45b3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4bdb9748-cdd5-4c9d-872a-3e576971b465.tmp.txt</Data>
<Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LaunchBox.exe_3c0919576ff3877b7ad358ac8aedd83954997_9c13cd35_41b643fa-61f2-4dd1-82cc-c5e95fb6c8b2</Data>
<Data>
</Data>
<Data>0</Data>
<Data>b68a43ce-40a7-4ce1-9b6b-abf8cc3e5d64</Data>
<Data>268566528</Data>
<Data>100b8b77cfd2aa7aa800eb5466eaadc2</Data>
<Data>0</Data>
</EventData>
</Event>