[BUG] Chiaki-NG Crash To Desktop on Laptop

[LuffyMugiwara-remote]

Describe the bug
I'm encountering a crashes to desktop on my laptop using either the Vulkan or d3d11va decoders. It seems like the crashes are random (e.g 20 minutes, 1 hours, etc.). The d3d11va decoder seems to be more stable than Vulkan decoder

I'm running Windows 11 with an Intel Iris Graphics cards.

Any suggestions?

Thanks

Debug Log
Please attach a log with verbose logging enabled.

chiaki_session_2024-09-24_16-40-52-769769.log
chiaki_session_2024-09-24_16-50-58-405405.log

To Reproduce
Steps to reproduce the behavior:

1. Chiaki running
2. Crash at random time interval

Expected behavior
No crash to desktop

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [Windows 11]
• Version [Version 10.0.22631 Build 22631]
• Device [HP ENVY x360 Convertible 15m-es1xxx]
• chiaki-ng Version [e.g. 1.9.0]

Additional context
Add any other context about the problem here.

[streetpea]

@LuffyMugiwara-remote Sounds like a driver bug with the driver you are using. Do you have a crash log https://www.partitionwizard.com/partitionmagic/windows-10-crash-log.html?amp?

[LuffyMugiwara-remote]

@streetpea Yeah I found this in the Event viewer. I get this when running the Vulkan decoder

Log Name: Application
Source: Application Error
Date: 9/24/2024 4:41:18 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User:
Computer:
Description:
Faulting application name: chiaki.exe, version: 0.0.0.0, time stamp: 0x66eccdfb
Faulting module name: igvk64.dll, version: 32.0.101.6078, time stamp: 0x66e4b0d6
Exception code: 0xc0000005
Fault offset: 0x000000000029106b
Faulting process id: 0x0x4AA8
Faulting application start time: 0x0x1DB0EBF064F9E5E
Faulting application path: C:\Games\Chiaki-ng-Win\chiaki.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_181a492eed27d42f\igvk64.dll
Report Id: 6e626efd-b3b0-489a-bd3f-08416730a797
Faulting package full name:
Faulting package-relative application ID:
Event Xml:



1000
0
2
100
0
0x8000000000000000

22393


Application




chiaki.exe
0.0.0.0
66eccdfb
igvk64.dll
32.0.101.6078
66e4b0d6
c0000005
000000000029106b
0x4aa8
0x1db0ebf064f9e5e
C:\Games\Chiaki-ng-Win\chiaki.exe
C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_181a492eed27d42f\igvk64.dll
6e626efd-b3b0-489a-bd3f-08416730a797

Let me know if you need any more details

Thanks

[LuffyMugiwara-remote]

@streetpea I also found this log while I was digging in the event viewer. I get this when running the d3d11va decoder

Log Name: Application
Source: Application Error
Date: 9/24/2024 9:35:55 AM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User:
Computer:
Description:
Faulting application name: chiaki.exe, version: 0.0.0.0, time stamp: 0x66eccdfb
Faulting module name: ntdll.dll, version: 10.0.22621.4111, time stamp: 0x518e67bb
Exception code: 0xc0000005
Fault offset: 0x000000000003a056
Faulting process id: 0x0x12EC
Faulting application start time: 0x0x1DB0E8644795156
Faulting application path: C:\Games\Chiaki-ng-Win\chiaki.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: a0b75a93-a38c-4107-9ea5-0fa3fa82830b
Faulting package full name:
Faulting package-relative application ID:
Event Xml:



1000
0
2
100
0
0x8000000000000000

22175


Application




chiaki.exe
0.0.0.0
66eccdfb
ntdll.dll
10.0.22621.4111
518e67bb
c0000005
000000000003a056
0x12ec
0x1db0e8644795156
C:\Games\Chiaki-ng-Win\chiaki.exe
C:\WINDOWS\SYSTEM32\ntdll.dll
a0b75a93-a38c-4107-9ea5-0fa3fa82830b

I'm not sure which decoder I was using during this run.

Log Name: Application
Source: Application Error
Date: 9/18/2024 3:56:24 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User:
Computer:
Description:
Faulting application name: chiaki.exe, version: 0.0.0.0, time stamp: 0x66bac9a7
Faulting module name: igxelpicd64.dll, version: 30.0.101.3111, time stamp: 0x62a284e5
Exception code: 0xc0000005
Fault offset: 0x00000000000ace9e
Faulting process id: 0x0x392C
Faulting application start time: 0x0x1DB0A0447E02973
Faulting application path: C:\Games\Chiaki-ng-Win\chiaki.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b7747399b9541a64\igxelpicd64.dll
Report Id: 61fc80c0-9236-4bf7-b8fe-87c55694481c
Faulting package full name:
Faulting package-relative application ID:
Event Xml:



1000
0
2
100
0
0x8000000000000000

20682


Application




chiaki.exe
0.0.0.0
66bac9a7
igxelpicd64.dll
30.0.101.3111
62a284e5
c0000005
00000000000ace9e
0x392c
0x1db0a0447e02973
C:\Games\Chiaki-ng-Win\chiaki.exe
C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b7747399b9541a64\igxelpicd64.dll
61fc80c0-9236-4bf7-b8fe-87c55694481c

Let me know if you need any more details.

Thanks

[streetpea]

@LuffyMugiwara-remote is your whole laptop shutting down or just chiaki-ng?

[LuffyMugiwara-remote]

@streetpea Just chiaki-ng is crashing to desktop. Laptop and PS5 are still running. I can relaunch Chiaki-ng but will experience a crash to desktop again after a random period of time.

[streetpea]

Ok @LuffyMugiwara-remote i was confused by the title I thought your whole laptop was crashing.

[LuffyMugiwara-remote]

@streetpea Oops my bad. I have updated the title. Any suggestions for the crash to desktop?

[streetpea]

Unfortunately from what you’ve posted I can’t see why it’s crashing. Could you indtall x64dbg and launch the program through there and then wait for the crash and get a stack trace? https://x64dbg.com/ If so I can send you a build of Chiaki-by with debug symbols enabled so I can analyze your dump to fix the crash

[LuffyMugiwara-remote]

@streetpea Yeah I can do that tommorow. You can send me the build and I will run that build via x64dgb.

[LuffyMugiwara-remote]

@streetpea Here is the call stack and the log when encountering a crash the Vulkan decoder. I will try to capture it using the d3d11va decoder.

Let me know if you need anything else

[LuffyMugiwara-remote]

@streetpea Here is the call stack and the log when encountering a crash using d3d11va.

Let me know if you need anything else or want me to try something

[streetpea]

@LuffyMugiwara-remote use this build with debug symbols enabled for the stacktrace https://drive.proton.me/urls/R6Y5T1GJXR#EEF6YkCm2poY

[LuffyMugiwara-remote]

@streetpea I get the following error when attempting to launch that build. Also how I do enable symbols on the stack trace on x64dgb? I do see a symbols tab. Is that what you are referring to?

[streetpea]

The symbols being enabled is something you have to do when making the build. I’ll send you a new build with debug symbols enabled that has that missing dll

[LuffyMugiwara-remote]

@streetpea Perfect. Let me know when you are ready for me to test.

[streetpea]

@LuffyMugiwara-remote try this build https://drive.proton.me/urls/R6Y5T1GJXR#EEF6YkCm2poY now (it's been updated).

[LuffyMugiwara-remote]

@streetpea I have attached the log and the call stack after the crash to desktop using Vulkan

log-20240926-110500.txt
export-20240926-111030.csv

[LuffyMugiwara-remote]

@streetpea I have attached the log and the call stack after the crash to desktop using d3d11va

log-20240926-115539.txt
export-20240926-115526.csv

Let me know if you need anything else

[streetpea]

Which thread actually crashed?

[LuffyMugiwara-remote]

@streetpea From looking at the log. It seems like thread 18436.

[streetpea]

@LuffyMugiwara-remote I think that’s just the last thread loaded not necessarily the one that crashed.

[streetpea]

@luffymugiwara can you do the following:

1. Make chiaki-ng crash.

2. When it does, Go to the Call Stack View: View -> Call Stack (Ctrl+K)

3. Right Click: Copy -> Full Table, To Log

4. Go to the log: View -> Log Window (Ctrl+L)

5. Right Click: Copy

6. Either paste the output into a file and attach or directly paste here

[LuffyMugiwara-remote]

log-20240930-104555.txt

@streetpea Here is the log. This crashed using the Vulkan Decoder Let me know if you need anything else

Also I have attached the suspected call frame that x96dbg refered me to

[LuffyMugiwara-remote]

log-20240930-123537.txt

@streetpea Here is the log. This crashed using the drd11va Decoder Let me know if you need anything else

Also I have attached the suspected call frame that x96dbg refered me to

[streetpea]

so it seems like avbuffer_unref is causing the issue. Probably a driver bug. Do you have any thoughts @nowrep?

[LuffyMugiwara-remote]

@streetpea @nowrep Here is the driver that I'm using if that helps. I'm using the latest.

https://www.intel.com/content/www/us/en/download/785597/intel-arc-iris-xe-graphics-windows.html