Crashing on startup

Have started testing Audirvana Studio and have hit a speedbump with what looks like the Qobuz integration.
While scrolling through the Artists under Favorites Audirvana core dumped then crashed. Since then I’ve been lucky if I’m able to get the program open for more than a minute before it ungracefully (without dump file) crashes again. Most of the time it will blink on in my system tray before crashing, and if I’m lucky it will open up enough for me to be able to start scrolling through the Artists before conking out again.

This is what I see in the Audivana.log file

2021-05-17 07:56:06,812 [1] INFO Audirvana.App - ============= Started Logging, Audirvana 1.0.0 =============
2021-05-17 07:56:10,759 [4] DEBUG Audirvana.App - RemoteServer: Server started and advertised on port 59510
2021-05-17 07:56:20,997 [1] INFO Audirvana.App - ============= Started Logging, Audirvana 1.0.0 =============
2021-05-17 07:57:05,631 [1] INFO Audirvana.App - ============= Started Logging, Audirvana 1.0.0 =============
2021-05-17 07:57:17,689 [1] INFO Audirvana.App - ============= Started Logging, Audirvana 1.0.0 =============
2021-05-17 07:57:21,699 [5] DEBUG Audirvana.App - RemoteServer: Server started and advertised on port 59586

The Audirvana.dmp file looks to be 0 bytes in size.

I’m running Windows 10 20H2 19042.985

After going away and getting a coffee I was able to get back in and navigate my catalog, however after getting about 10 seconds into a song it core dumped.

Link to the dump file - https://1drv.ms/u/s!AhyE48hFKiI4geYxeZkxGQVgykkjYg?e=VTm4WF

it looks like the constant crashing at startup may have been caused by the software trying to analyse this file https://1drv.ms/u/s!AhyE48hFKiI4geYy8HNSbJiWIW_M8Q?e=RLUSRG based on the following error being thrown constantly in my event logs

Fault bucket 2254166430647627140, type 5
Event Name: MoBEX
Response: Not available
Cab Id: 0

Problem signature:
P1: Audirvana.Audirvana-4118-9684-d80dbb7827cd_1.0.0.0_x64__fec4hfhj3emgj
P2: praid:App
P3: 1.0.0.10000
P4: 60a14f83
P5: ntdll.dll
P6: 10.0.19041.964
P7: bd2c3c23
P8: 00000000000a4cf8
P9: c0000409
P10: 0000000000000023

Attached files:
\?\C:\Users\timothy.rose\Music\noise coming through ceiling 7th of april.m4a
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6799.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6BEF.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6C10.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6C1F.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6C4F.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Audirvana.Audirv_ce137fff75da3adeabfc0affd2d8b49a578f77b_1b4dd534_e3481fa3-4882-4796-a1b9-dd32df7c3042

Analysis symbol:
Rechecking for solution: 0
Report Id: 0d096e4d-76e4-4c81-b79b-89c2e0f6e72b
Report Status: 268435456
Hashed bucket: 8d8d250dcde2c11c3f48686cf35cad84
Cab Guid: 0

I’ve been leaving the program running in the background and it seems to crash at random while it’s Analyzing audio files.

The most recent error:

Faulting application name: Audirvana.exe, version: 1.0.0.10000, time stamp: 0x60a14f83
Faulting module name: ntdll.dll, version: 10.0.19041.964, time stamp: 0xbd2c3c23
Exception code: 0xc0000409
Fault offset: 0x00000000000a4db8
Faulting process id: 0x7b2c
Faulting application start time: 0x01d74adb792e3636
Faulting application path: C:\Program Files\WindowsApps\Audirvana.Audirvana-4118-9684-d80dbb7827cd_1.0.0.0_x64__fec4hfhj3emgj\Audirvana\Audirvana.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: b44c2ac6-c20e-43b6-96ff-1208258ffa41
Faulting package full name: Audirvana.Audirvana-4118-9684-d80dbb7827cd_1.0.0.0_x64__fec4hfhj3emgj
Faulting package-relative application ID: App

Hello @afro-san,

Can you send us this crash report at support@audirvana.com ?

I’ve emailed through the crash report - it looks like the cause so far seems to be any non-standard mp3/flac etc files. I’ve removed the phone recording that caused the original crash, the podcast series that caused the latest crash, and a set of flacs that had Japanese characters in the metadata and so far it has been running fine - it even finished doing it’s analysis of all my music.

Thank you for sending this crash, we will take a look at it as soon as possible.