/AzurePipelines run

@microsoft-github-policy-service agree

/AzurePipelines run

/AzurePipelines run

@stephengillie it seems that that dependency is installed with graphics drivers which is probably why I haven't heard anybody complain about it. I added it. Thank you for your patience.

/AzurePipelines run

Manual Validation ended with:

Faulting application name: chiaki.exe, version: 1.9.1.0, time stamp: 0x6731a7cb
Faulting module name: chiaki.exe, version: 1.9.1.0, time stamp: 0x6731a7cb
Exception code: 0xc0000005
Fault offset: 0x000000000005db0e
Faulting process id: 0x25bc
Faulting application start time: 0x01db3561e649b654
Faulting application path: C:\Program Files\chiaki-ng\chiaki.exe
Faulting module path: C:\Program Files\chiaki-ng\chiaki.exe
Report Id: b294148e-305f-420c-a82f-559afcc7e905
Faulting package full name:
Faulting package-relative application ID:

Fault bucket 1571553288640585701, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: chiaki.exe
P2: 1.9.1.0
P3: 6731a7cb
P4: chiaki.exe
P5: 1.9.1.0
P6: 6731a7cb
P7: c0000005
P8: 000000000005db0e
P9:
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA4D.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB19.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB2A.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB3F.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB50.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_chiaki.exe_441459e35264f7e28f20536c483284c5ba995bd8_0e021de8_6a93495e-5199-434c-9724-e5b7ccdbbeeb

Analysis symbol:
Rechecking for solution: 0
Report Id: b294148e-305f-420c-a82f-559afcc7e905
Report Status: 268435456
Hashed bucket: c0989a27d960fa0c35cf4763bb04dfe5
Cab Guid: 0

Edit: formatting.

@ stephengillie it seems that that dependency is installed with graphics drivers which is probably why I haven't heard anybody complain about it. I added it. Thank you for your patience.

It's my pleasure to help. The dependency might be missing from the VMs as they have inferior graphics drivers - if it's not necessary in most PCs then it should probably be removed.

Manual Validation ended with the errors above being logged in the Event Log. The application window didn't open - I don't have more info about why, but if you have any troubleshooting suggestions, I'd be happy to try them.

@stephengillie is it possible to run debugview https://learn.microsoft.com/en-us/sysinternals/downloads/debugview on the system and see if any logs pop up in there?

@stephengillie according to Khronos who makes Vulkan, you shouldn’t include Vulkan-1.dll with your application and should install allow the drivers to update it or users to manually update it if their drivers are too old. https://github.com/KhronosGroup/Vulkan-Loader/blob/main/docs/LoaderApplicationInterface.md#bundling-the-loader-with-an-application so I should probably take that added dependency out.

Apologies for the delay in responding - I'm dealing with capacity issues. Yes, feel free to remove the dependency. I am unsure about getting debugview onto the VM - does it have a PackageIdentifier in the repo?

@stephengillie you can download the exe for debugview directly from sysinternals using this link https://live.sysinternals.com/Dbgview.exe with curl or wget. A zip file with all debug view files is here: https://download.sysinternals.com/files/DebugView.zip

it’s also available via chocolatey via

choco install dbgview

https://community.chocolatey.org/packages/dbgview

There are winget packages for many of the sysinternals under manifests/m/Microsoft/SysInternals/ but debug view doesn’t appear to be one of them

@stephengillie did you ever get a chance to try out debugview?

Unfortunately, it didn't find any logs on the VM.

Hmm. Maybe it needs administrative access to run based on that popup. If you start debug view first and then leave it open when launching chiaki-ng various logs should appear in debug view but I never got that popup window so it's possible it doesn't have the necessary access on your system.

@stephengillie did you open DebugView first and then leave it open when launching chiaki-ng?

I haven't used DebugView before, sorry. This seems to be a problem with the VM driver:

• [New Feature]: Upgrade manual validation hardware #107639
• Support OpenGL for package validation. #12906