Topic: Crash issues (Read 1654 times)

Denti · « **on:** April 04, 2022, 05:32:10 pm »

I started the thread with JRMC28 but am using 29 now, so I’m posting here for better visibility and more immediate help. Maybe mods can move the thread here?

https://yabb.jriver.com/interact/index.php/topic,132318.msg919326.html#msg919326

Denti · « **Reply #1 on:** April 05, 2022, 05:55:51 pm »

Alright, here are the issues and logs. I’m consolidating it all here from the other thread.

When I play a music file (any, though most are FLAC or DSD) and I pause it for longer than a minute or so, when I unpause it often crashes. When I start it up again and try to play the same file it crashes every time until I restart. Any idea how I could get to the bottom of this?

The first crash dump log is from the day before yesterday when I was trying unsuccessfully to replicate the problem. While waiting with the music on pause I was looking around in the settings and at one point I selected Audio and it crashed. Not the usual problem, but a problem nonetheless. I tried over and over to replicate the problem by pausing the music, waiting different lengths of time and the restarting. The issue did not replicate, sadly.

The other log is from yesterday. I wasn't planning on testing it, but had paused the music and taken the dog out. When I returned I hit play to restart and it crashed. This is what has been happening pretty regularly these past few weeks.

The last two logs are me trying to to play a file after the crash.

JimH · « **Reply #2 on:** April 05, 2022, 06:32:22 pm »

Crashes are hard to find, but they are usually related to antivirus problems or drivers.

One way to find them is to narrow down the cause by eliminating variables. Machine, OS, drives, and so on.

Denti · « **Reply #3 on:** April 05, 2022, 06:40:27 pm »

I was told to get crash logs. Do these not reveal the source of the problem? This is not an isolated event.

Matt · « **Reply #4 on:** April 06, 2022, 09:50:28 am »

I looked at one of your crash dumps and it was crashing enumerating Kernel Streaming pins. It's not obvious why, but Kernel Streaming is not the preferred output.

Could you try WASAPI or DirectSound instead?

Thanks.

AndreaT · « **Reply #5 on:** April 06, 2022, 10:50:45 am »

Hello Matt and JimH,
I am having similar crash after long pause with MC29 and in my case it looks related to the HDD wake-up process taking somehow longer than expected.
However, as Matt should know checking my crash logs, this is not reported. I mean, it looks that any HDD related error or timeout is not reported in your logs.
If you confirm that (I didn't get any reply about from Matt), it might be worth to improve a bit your diagnostic capability and add such a kind of issues as well.
Regards, Andrea

Denti · « **Reply #6 on:** April 06, 2022, 11:22:36 am »

Quote from: Matt on April 06, 2022, 09:50:28 am

I looked at one of your crash dumps and it was crashing enumerating Kernel Streaming pins. It's not obvious why, but Kernel Streaming is not the preferred output.

Could you try WASAPI or DirectSound instead?

Thanks.

Thanks, Matt. What is kernel streaming? I can't use WASAPI or DirectSound with my DAC. I have the drivers for that DAC selected as output. Anything I can do or do I have to live with it?

Awesome Donkey · « **Reply #7 on:** April 06, 2022, 12:31:41 pm »

Kernel streaming is an old XP-era legacy audio output that's been long depreciated since Windows 7 was released. WASAPI is the modern equivalent, which kinda surprises me that WASPAI can't be used in your case. Maybe you need to check the Disable event style in MC's Settings > Audio > Device settings after selecting WASAPI (if available for your DAC). Actually, what DAC are you using?

If you're using ASIO4ALL, this is also just a kernel streaming wrapper and should be avoided if possible. More info about kernel streaming here: https://wiki.jriver.com/index.php/Audio_Output_Modes#Kernel_Streaming

Denti · « **Reply #8 on:** April 06, 2022, 06:25:28 pm »

Driver is for a Gustard X20: Diynhk USB driver. It appears as ASIO.

I’m outputting 4xDSD, which requires ASIO. That’s not kernel streaming, is it?

Matt · « **Reply #9 on:** April 06, 2022, 06:38:15 pm »

If you're using ASIO I'm riddled by the crash. Let me look at a couple more crashes tomorrow and I'll let you know if I find anything.

Denti · « **Reply #10 on:** April 06, 2022, 06:47:18 pm »

Do you need me to gather more crash reports?

JimH · « **Reply #11 on:** April 06, 2022, 09:38:04 pm »

Your crash is because of kernel streaming. Not an MC problem.

Quote from: Matt on April 06, 2022, 09:50:28 am

I looked at one of your crash dumps and it was crashing enumerating Kernel Streaming pins. It's not obvious why, but Kernel Streaming is not the preferred output.

Could you try WASAPI or DirectSound instead?

Denti · « **Reply #12 on:** April 07, 2022, 06:46:42 am »

Quote from: JimH on April 06, 2022, 09:38:04 pm

Your crash is because of kernel streaming. Not an MC problem.

As noted above, I’m not using kernel streaming but ASIO.

JimH · « **Reply #13 on:** April 07, 2022, 07:34:12 am »

Then the ASIO driver isn't working. It may be AISO4All, which uses Kernel Streaming, as AwesomeDonkey said above.

You could try the 32 bit version of MC. It's possible it would work.

But this isn't an MC problem.

Denti · « **Reply #14 on:** April 07, 2022, 08:14:27 am »

Quote from: JimH on April 07, 2022, 07:34:12 am

Then the ASIO driver isn't working. It may be AISO4All, which uses Kernel Streaming, as AwesomeDonkey said above.

You could try the 32 bit version of MC. It's possible it would work.

But this isn't an MC problem.

So basically you can’t guarantee that otherwise stable drivers will work with MC?

Matt · « **Reply #15 on:** April 07, 2022, 08:21:26 am »

I sent you an email with something to try. Please follow up there. Thanks.

dtc · « **Reply #16 on:** April 07, 2022, 09:58:26 am »

According to their website, the DIYINHK USB Audio Driver is based on Thesycon's driver. Unlikely that a Thesycon driver is using ASIO4ALL or kernel streaming. Most ASIO drivers are based on Thesycon. Seems like something funny is going on. The current version is 3.38. Are you using the current version and is it properly signed by Thesycon? You can use sigverif.exe from Windows Search in the toolbar to check your drivers' signatures. Advanced View Log will show you signed it. Is that driver that Gustard recommends? It looks like they may have their own driver.

From the DIYINHK website

"The driver is complied and signed by the original software manufacturer Thesycon"

kr4 · « **Reply #17 on:** April 07, 2022, 03:30:00 pm »

Quote from: dtc on April 07, 2022, 09:58:26 am

According to their website, the DIYINHK USB Audio Driver is based on Thesycon's driver. Unlikely that a Thesycon driver is using ASIO4ALL or kernel streaming. Most ASIO drivers are based on Thesycon. Seems like something funny is going on. The current version is 3.38.

I am using a DIYINHK USB Driver in Win10 and Win11 without an issue. However, I have different DAC (Okto DAC8 Pro) and the version I use is v4.59. Mebbe you want to try that one.

dtc · « **Reply #18 on:** April 07, 2022, 04:09:20 pm »

There are two different versions of this driver on the website. One is V4.67 the other is V3.88. Not sure what the difference is.

Denti · « **Reply #19 on:** April 09, 2022, 08:36:08 am »

I have driver version 3.34. Is there a newer version? I think it’s signature verified. Can’t find sigverif.exe on my system.

According to this post https://www.head-fi.org/threads/gustard-x20-dac.780385/page-71#post-13026960
the 3.38 version is only for use with a different USB card.

JimH · « **Reply #20 on:** April 09, 2022, 09:50:59 am »

Quote from: dtc on April 07, 2022, 04:09:20 pm

There are two different versions of this driver on the website. One is V4.67 the other is V3.88. Not sure what the difference is.

Did you try the 4.67 driver?

INTERACT FORUM

Author Topic: Crash issues (Read 1654 times)