Graceful Exit from Audirvana and regular Crash Dumps

Don’t get me wrong - I love this program and how I can use it to stream Hi-Res and all sorts of other Audio around my house to a myriad of devices.

And it does that very well. However it does frustrate me (and it may be my ignorance here) that the program is some quirky install outside of the standard windows installation directories and does not have a graceful exit button - as you would find in a ‘File> Exit’ in most windows apps.

About a third of the time, I am forced to use the ‘X’ in the top right hand corner of the program to exit it, the app crashes and generates a mini dump.

I use the program to stream music across to the bedroom and have that running all night - but often upon returning to my PC in the morning to shut it down - I find it crashed and having set up another Mini Dump

So two things - am I alone on a Windows 11 system seeing multiple crashes and ungraceful exits a week. Secondly is there a graceful exit button or key sequence for the application?

Hi @bladeraptor,

If you have some crashes, you need to send us the latest one generated that is on your desktop folder (the file is named audirvana_studio.dmp) at support@audirvana.com.

Can you please elaborate on what you are talking about? The X button at the top right corner is the button to close the app, as any other app on Windows.

Actually Audirvana does a standard Windows Microsoft Store installation. All Microsoft Store installations install in (your words) some ‘quirky’ directory outside the ‘normal’ (“windows\program files”) folders you are probably used to. You’ll have to direct your frustration to Microsoft, because this is standard windows behaviour when installing Microsoft Store programs. I don’t know if you ever did, but then you can see they all behave the same as Audirvana.

What is the difference between ‘File\Exit’ or the ‘X’ in the upper right corner? They both do exactly the same ‘graceful’ thing. There is no difference (in any Windows program) in using one over the other (both options trigger the same windows ‘close’ message internally in a program).

I use Audirvana in Windows 11 and I don’t have your experience with crashes. Maybe there is something with your specific system (ASIO driver, sound driver problem, settings in Audirvana etc. etc.). @Antoine already asked you to send a crash dmp when that happens. What you also can do is copy and paste your debug info here so forum members can maybe give some advice about some (potential) problems in your system or in your Audirvana Settings.

I (sorry if I am repeating myself again) don’t get it either what you mean with ‘graceful exit button’. In any Windows program there is the ‘X’ in the upper right corner or the standard keyboard shortcut ‘Alt-F4’ to terminate a program. The File\Exit you are talking about is doing exactly the same, but is not present in every Windows program (in the case of Audirvana the developers have chosen for a different GUI design), but functionally there is no difference. Even Microsoft themselves do not use the ‘File\Exit’ menu anymore in a lot of newer Windows programs (see Edge, Windows file explorer, Windows Mail, Windows task manager etc. etc.). You only can close those with the ‘X’ or ‘Alt-F4’ as well.

Here is a screenshot how you can send your debug(system)/info. Click on the Debug info button and the info will be automatically copied to the clipboard. You only have to paste that in a new post in this thread).

Some general tips. If you use a DAC check that you have installed the latest Windows drivers installed from your DAC manufacturer. In Windows: check your sound settings. If your music library is installed on a network drive: check your network connection (and use a cabled connection instead of Wifi). Check your sound buffer in Audirvana\settings (if it is too large your computer may crash because of too little memory) Etc. Etc.
This is all guessing from my part, but probably this forum can help more if you send your debug info and of course Antoine can help you better with your crash dump file.
To avoid confusion: I am just a forum member and not Audirvana support (@Antoine is Audirvana support).

1 Like

Hi AndyLubke - thanks for the reply.

A couple of thoughts

“I don’t know if you ever did, but then you can see they all behave the same as Audirvana.”

I have kept ‘Store installs’ to a minimum over the years as pretty much universally I have found Store installs to be much more buggy and unpredictable compared to ‘traditional installs’ for things like iTunes, for example. So I avoid - store installs wherever possible. The other thing is most ‘Store’ installs let you know whether they are ‘Store’ installs

“What is the difference between ‘File\Exit’ or the ‘X’ in the upper right corner? They both do exactly the same ‘graceful’ thing. There is no difference (in any Windows program) in using one over the other (both options trigger the same windows ‘close’ message internally in a program).”

This may indeed be the case and what I have figured with a bit of investigation is that pretty much 95% of the ‘Traditional installs’ on my machine have the option to close or exit the program as well as the X - whereas the one or two ‘Store Installs’ I have, do not have a close or exit option - just the X. TBH if there weren’t the crashes I probably wouldn’t have paid so much attention. BTW that behavior was seen both on my previous Windows 10 build and this basically brand new Windows 11 build (new PC, new OS)

“I use Audirvana in Windows 11 and I don’t have your experience with crashes. Maybe there is something with your specific system (ASIO driver, sound driver problem, settings in Audirvana etc. etc.).”

My setup is fairly simple - I have an iFI Zen V2 DAC connected as my output so have the iFI driver installed for the ASIO as well as having ASIO4All and the Realtek ASIO that came with the MB installed (but use the iFi driver predominantly). For some context this driver / device setup is used with Foobar2000 happily with no crashes or issues on the same Windows 11 build

Do you have some settings specifically in Audirvana that you feel might be creating issues that I should check?

"Some general tips. If you use a DAC check that you have installed the latest Windows drivers installed from your DAC manufacturer. In Windows: check your sound settings.

Latest iFI Drivers installed.

“If your music library is installed on a network drive: check your network connection (and use a cabled connection instead of Wifi).”

Music Drive is local on SATA SSD and my machine is ethernet connected as is the Zen Stream and most other devices in my network that Audirvana feeds to

“Check your sound buffer in Audirvana\settings (if it is too large your computer may crash because of too little memory) Etc. Etc.”

Sound buffer is not at the maximum by any means and the system has 64GB of RAM - so should be good

Many thanks

________________________________Debug

Audirvana Studio 2.6.3 (20603)

Windows 11 (22621) with 64GB physical RAM

Connected account of :

NETWORK
Status: available
Available network interfaces:
Ethernet ({c5581ad3-8f83-4bf3-8803-59a690da895b}) is private
Windows Defender Firewall status for this instance of Audirvana Studio
Active profile types: all
Private profile:
Firewall: enabled
Inbound: allowed
Outbound: allowed
Notifications: enabled
Public profile:
Firewall: enabled
Inbound: blocked
Outbound: allowed
Notifications: enabled

SIGNAL PROCESSING:

Polarity Inversion:
	Globally: OFF
	Per track: ON
Effects plugins NOT ACTIVE

UPSAMPLING:
r8brain not in use
r8brain filter parameters
Bandwidth = 99.5%
Stop band attenuation 218dB
Phase linear

AUDIO VOLUME:
Max allowed volume: 100
Replay Gain: None
SW volume control: OFF

LIBRARY SETTINGS:
Sync list: 0 folders
Library database path: C:\Users\blade\AppData\Local\Packages\Audirvana.Audirvana-4118-9684-d80dbb7827cd_q3nymrkmej12j\LocalCache\Local\Audirvana\Audirvana\AudirvanaDatabase.sqlite

Local audio files fingerprinting
Tracks with no MBID: 1244

Remote Control server:
Listening on 192.168.x.x on port 54235

ACTIVE STREAMING SERVICES

=================== AUDIO DEVICE ========================

Active method: UPnP

Preferred device: [UPnP] iFi zen stream Model UID:iFi audio iFi audio UID:uuid:ca3f1797-449f-3de3-5db8-42a10b471455

Selected device:iFi zen stream
Manufacturer: iFi audio
Model name: iFi audio
Model UID: iFi audio iFi audio
UID: uuid:ca3f1797-449f-3de3-5db8-42a10b471455
UPnP device at http://192.168.x.x:49153/description.xml

10 available sample rates up to 768000Hz
44100
48000
88200
96000
176400
192000
352800
384000
705600
768000

Volume control: No
Max volume alert: Enabled

MQA capability
Auto-detect MQA devices: Yes
Not a MQA device, user set to MQA Decoder
DSD capability: Raw DSD (msb)

Device audio channels
Preferred stereo channels L:0 R:1
Channel bitmap: Ox3, layout:
Channel 0 mapped to 0
Channel 1 mapped to 1

UPnP set capabilities
Maximum PCM frequency set: 768000Hz
Maximum PCM bitdepth set: 24
Maximum DSD rate set: DSD512
Avoid RAW PCM streams: No
Unwanted playback stop workaround: No

UPnP / DLNA supported protocols :
http-get::application/flac:
http-get::audio/flac:
http-get::audio/x-flac:
http-get::audio/aac:
http-get::audio/x-aiff:
http-get::audio/dff:
http-get::audio/x-dff:
http-get::audio/dsd:
http-get::audio/x-dsd:
http-get::audio/dsf:
http-get::audio/x-dsf:
http-get::audio/m4a:
http-get::audio/x-m4a:
http-get::audio/mp1:
http-get::audio/mp4:
http-get::audio/mpeg:
http-get::audio/x-mpeg:
http-get::audio/ogg:
http-get::audio/vorbis:
http-get::audio/wav:
http-get::audio/x-wav:
http-get::audio/wave:
http-get::audio/x-ms-wma:
http-get::audio/x-ogg:
http-get::audio/x-scpls:
http-get::audio/x-vorbis+ogg:
http-get::audio/x-vorbis:
http-get::video/mp4:
DLNA 1.5: No
Native Gapless playback: Yes
Universal Gapless playback active: No
Missing events workaround: No
Can play native DSD: Yes
Volume Control: None
Number of channels: 2
Use as stereo device only: No

1 output streams:
Number of active channels: 2, in 1 stream(s)
Channel #0 :Stream 0 channel 0
Channel #1 :Stream 0 channel 1
2 ch Integer PCM 16bit little endian 44.1kHz finite length
2 ch Integer PCM 24bit little endian 44.1kHz finite length
2 ch Integer PCM 16bit little endian 88.2kHz finite length
2 ch Integer PCM 24bit little endian 88.2kHz finite length
2 ch Integer PCM 16bit little endian 176.4kHz finite length
2 ch Integer PCM 24bit little endian 176.4kHz finite length
2 ch Integer PCM 16bit little endian 352.8kHz finite length
2 ch Integer PCM 24bit little endian 352.8kHz finite length
2 ch Integer PCM 16bit little endian 705.6kHz finite length
2 ch Integer PCM 24bit little endian 705.6kHz finite length
2 ch Integer PCM 16bit little endian 48kHz finite length
2 ch Integer PCM 24bit little endian 48kHz finite length
2 ch Integer PCM 16bit little endian 96kHz finite length
2 ch Integer PCM 24bit little endian 96kHz finite length
2 ch Integer PCM 16bit little endian 192kHz finite length
2 ch Integer PCM 24bit little endian 192kHz finite length
2 ch Integer PCM 16bit little endian 384kHz finite length
2 ch Integer PCM 24bit little endian 384kHz finite length
2 ch Integer PCM 16bit little endian 768kHz finite length
2 ch Integer PCM 24bit little endian 768kHz finite length
2 ch DSD 8bit little endian in 8bit chunk 2822.4kHz finite length
2 ch DSD 8bit little endian in 8bit chunk 5644.8kHz finite length
2 ch DSD 8bit little endian in 8bit chunk 11289.6kHz finite length
2 ch DSD 8bit little endian in 8bit chunk 22579.2kHz finite length

Current device transportInfo:
CurrentTransportState: STOPPED
CurrentTransportStatus: OK
CurrentSpeed: 1

Current device MediaInfo:
NrTracks: 1
MediaDuration: 00:00:00
CurrentURI:
CurrentURIMetadata:
nextURI: http://192.168.x.x:49152/audirvana/audio_f_77.wav
nextURIMetadata:
PlayMedium: NONE
RecordMedium: NOT_IMPLEMENTED
WriteStatus: NOT_IMPLEMENTED

Current transport actions:
Next,Previous,Play

Current device AVT service description:

<?xml version="1.0"?> 1 0 urn:schemas-upnp-org:device:MediaRenderer:1 iFi zen stream iFi audio https://ifi-audio.com The Audiophile Music Player iFi audio 1.0 https://ifi-audio.com 42 uuid:ca3f1797-449f-3de3-5db8-42a10b471455 image/png 64 64 32 /upmpd/icon.png urn:schemas-upnp-org:service:RenderingControl:1 urn:upnp-org:serviceId:RenderingControl /upmpd/RenderingControl.xml /ctl/RenderingControl /evt/RenderingControl urn:schemas-upnp-org:service:AVTransport:1 urn:upnp-org:serviceId:AVTransport /upmpd/AVTransport.xml /ctl/AVTransport /evt/AVTransport urn:schemas-upnp-org:service:ConnectionManager:1 urn:upnp-org:serviceId:ConnectionManager /upmpd/ConnectionManager.xml /ctl/ConnectionManager /evt/ConnectionManager urn:av-openhome-org:service:Product:1 urn:av-openhome-org:serviceId:Product /upmpd/OHProduct.xml /ctl/OHProduct /evt/OHProduct urn:av-openhome-org:service:Info:1 urn:av-openhome-org:serviceId:Info /upmpd/OHInfo.xml /ctl/OHInfo /evt/OHInfo urn:av-openhome-org:service:Time:1 urn:av-openhome-org:serviceId:Time /upmpd/OHTime.xml /ctl/OHTime /evt/OHTime urn:av-openhome-org:service:Volume:1 urn:av-openhome-org:serviceId:Volume /upmpd/OHVolume.xml /ctl/OHVolume /evt/OHVolume urn:av-openhome-org:service:Playlist:1 urn:av-openhome-org:serviceId:Playlist /upmpd/OHPlaylist.xml /ctl/OHPlaylist /evt/OHPlaylist urn:av-openhome-org:service:Radio:1 urn:av-openhome-org:serviceId:Radio /upmpd/OHRadio.xml /ctl/OHRadio /evt/OHRadio /upmpd/presentation.html http://192.168.x.x:49153/

Current device RootDevice description:

<?xml version="1.0"?> 1 0 urn:schemas-upnp-org:device:MediaRenderer:1 iFi zen stream iFi audio https://ifi-audio.com The Audiophile Music Player iFi audio 1.0 https://ifi-audio.com 42 uuid:ca3f1797-449f-3de3-5db8-42a10b471455 image/png 64 64 32 /upmpd/icon.png urn:schemas-upnp-org:service:RenderingControl:1 urn:upnp-org:serviceId:RenderingControl /upmpd/RenderingControl.xml /ctl/RenderingControl /evt/RenderingControl urn:schemas-upnp-org:service:AVTransport:1 urn:upnp-org:serviceId:AVTransport /upmpd/AVTransport.xml /ctl/AVTransport /evt/AVTransport urn:schemas-upnp-org:service:ConnectionManager:1 urn:upnp-org:serviceId:ConnectionManager /upmpd/ConnectionManager.xml /ctl/ConnectionManager /evt/ConnectionManager urn:av-openhome-org:service:Product:1 urn:av-openhome-org:serviceId:Product /upmpd/OHProduct.xml /ctl/OHProduct /evt/OHProduct urn:av-openhome-org:service:Info:1 urn:av-openhome-org:serviceId:Info /upmpd/OHInfo.xml /ctl/OHInfo /evt/OHInfo urn:av-openhome-org:service:Time:1 urn:av-openhome-org:serviceId:Time /upmpd/OHTime.xml /ctl/OHTime /evt/OHTime urn:av-openhome-org:service:Volume:1 urn:av-openhome-org:serviceId:Volume /upmpd/OHVolume.xml /ctl/OHVolume /evt/OHVolume urn:av-openhome-org:service:Playlist:1 urn:av-openhome-org:serviceId:Playlist /upmpd/OHPlaylist.xml /ctl/OHPlaylist /evt/OHPlaylist urn:av-openhome-org:service:Radio:1 urn:av-openhome-org:serviceId:Radio /upmpd/OHRadio.xml /ctl/OHRadio /evt/OHRadio /upmpd/presentation.html http://192.168.x.x:49153/

UPnP devices found : 4
Device #0: iFi zen stream
UID: uuid:ca3f1797-449f-3de3-5db8-42a10b471455
Location: http://192.168.x.x:49153/description.xml
Manufacturer: iFi audio
Model name: iFi audio
Device #1: Kitchen Zipp
UID: uuid:7bc7a8f1-bd8b-462e-b25a-fa463b4f2f79
Location: http://192.168.x.x:49152/description.xml
Manufacturer: Libratone
Model name: LTH
Device #2: AFTGAZL-15[DLNA]
UID: uuid:beab1ea7-2a98-4056-9dc8-7223a545d38d
Location: http://192.168.x.x:3500/
Manufacturer: SoftMedia Inc.
Model name: AirReceiver
Device #3: Lounge-AMP
UID: uuid:5F9EC1B3-ED59-79BB-4530-745e1c56518f
Location: http://192.168.x.x:8080/description.xml
Manufacturer: PIONEER CORPORATION
Model name: SC-LX87/SYXJ8

Local

Max. memory for audio buffers: 44146MB

Local Audio Engine: ASIO 0
Driver version 0
Use max I/O buffer size: ON

Local devices found : 4
Device #0: ASIO4ALL v2
Manufacturer:
Model UID: ASIO4ALL v2
UID: ASIO4ALL v2
Model name: ASIO4ALL v2
Device #1: foo_dsd_asio
Manufacturer:
Model UID: foo_dsd_asio
UID: foo_dsd_asio
Model name: foo_dsd_asio
Device #2: iFi USB Audio Device
Manufacturer:
Model UID: iFi USB Audio Device
UID: iFi USB Audio Device
Model name: iFi USB Audio Device
Device #3: Realtek ASIO
Manufacturer:
Model UID: Realtek ASIO
UID: Realtek ASIO
Model name: Realtek ASIO

Chromecast

Chromecast devices found : 1
Device #0: AFTGAZL-15[Cast]
ID: DnsSd#AFTGAZL-15[Cast]._googlecast._tcp.local#0
Model name: AirReceiver

UPnP can cause problems. Just for troubleshooting: have you tried a direct USB connection to your DAC?

Also check the settings of your DAC here:

Latest Plāys With Audirvāna topics - Audirvana

Hi AndyLubke

The Zen V2 DAC is USB connected to my desktop

The Zen Streamer and all other devices are connected via the ethernet / Wi-Fi network

With regard to the DAC settings for the Zen V2 I use the IFI Asio locally with as I have a lot of DSD files up to and including 256 and some options seem to disappear when using kernel mode

Best regards

ASIO Drivers in Windows can do the full DSD rate available in your DAC.

WASAPI (Windows Audio System Application Programming Interface) and Kernel Streaming do ‘DSD over PCM’ (DoP) which lowers the maximum DSD rate you can sent to your DAC. The term DoP can be confusing, but it still is pure DSD send to your DAC (packaged in a PCM container).

DoP open Standard | DSD-Guide.com

@AndyLubke - thanks for the update - I am aware of that but would prefer to push it without the additional overhead and not clear on the benefits balanced against the limitations of using the Kernel Streaming

@bladeraptor,

I received your dmp files, will review them as soon as possible and come back to you by email.

@Antoine - thank you very much for your reply and help - very much appreciated

The DAC supports up-to 768kHz and Audirvana is capable of transferring DSD256 via DoP 1.1 …

You have more than 50% of your System RAM allocated for playback pre-load memory… There is no good reason to apply 44GB of preload memory… Try bringing this down to 8GB… *No good reason to impinge on System operations by allocating a huge chunk of memory for pre-load, as the CPU is also working in the background loading the play queue while playing a track, in concert with packetizing the track via UPnP protocol for transmission on the output buses…

:notes: :eye: :headphones: :eye: :notes:

Are you playing the Zen V2 DAC simultaneously with the UPnP devices…? If so, how are you doing this?

Maybe @AndyLubke or @Antoine can explain if this ASIO4ALL v2 driver is the culprit.

:notes: :eye: :headphones: :eye: :notes:

@Agoldnear - thanks for the update and observation. One of those tweaks must have been done at some point. In systems typically running GBs of RAM, its less helpful to have the allocation in the UI in MB - I had wrongly assumed when doing the configuration that the available MB scale was a factor of 10 less than what can actually be configured in the UI and there would also be in the UI a headline max as a fixed upper % of the installed RAM. In some respects its great one can take all the RAM there is in the system - but as you suggest no reason to. It would be good to know if the 8 odd GB figure you mention is some sort of best practice ratio with effective minimum and maximums for optimum performance / lag or stutter offset

@Agoldnear - no not playing simultaneously through the local DAC and then the networked devices at all. As you assume Audirvana does not allow for that. For that type of wider scale audio broadcast I use something like Tuneblade. Best Regards

If a driver is the culprit, @Antoine can probably see it in the crash dump file he received. ASIO4ALL is mainly used as a real time interface between DAW’s and virtual instrument/effects plugins to reduce latency. As far as I know it does not do DSD at all. Also the max. PCM rate is not higher than 48 or 96 KHz I believe. But it is a time ago I had ASIO4ALL installed so I can be wrong.

In general the ASIO drivers provided by DAC manufacturers (mostly from Thesycon) are better suited for DSD and high PCM rates.

Generally the trade-off here is, how the concurrent background loading of track files affects Audirvana functions and the sound-quality of the track being played,… All operational functions will be intrinsically tied to bus speed/throughput and CPU power and the symbiotic availability of System RAM… There will be a functional balance that works for your playback scenario and you will need to experiment to find the playback sweet-spot in regard to pre-load RAM allocation… However, fewer background CPU operations, translates into less inducted noise on the digital-audio code signal, that will impact the final qualitative assessment of the playback signal.

:notes: :eye: :headphones: :eye: :notes: