Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ssands]

This happened recently, I think perhaps before the latest build. Happened on Win 7 and now Win 10 (reinstalled for Win 10).
Running the latest stable MC 20 version: 20.0.131

Anyone know how to fix this?

[glynor]

This can sometimes happen when your Audio Device is misconfigured (event style versus non for WASAPI, perhaps) or your driver is angry. I've seen it before caused by the audio device, anyway.

Otherwise, post a shutdown log. Turn on Logging, close MC, let it hang for a good long time (minutes, not seconds). Then force quit if you must, re-launch, and immediately generate the Log zip file.  It might include a clue.

[ssands]

Thanks, Glynor. Don't really know how to interpret the log, but I do see messages:
Handheld: CMSCDeviceEnumerator::GetMSCDevices: Device interface invalid
Handheld: CAnalyzeDevices::EnumerateDevices: Computer metering didn't work!  (but I don't have an portable (handheld?) device attached.

Your help is appreciated.

[glynor]

How are you outputting audio?

The Nvidia HDMI, the Intel HDMI, the RealTek onboard, or something else?

[ssands]

realtek
screen clip attached.

[ssands]

Bump

[JimH]

Disconnect any devices you can.

[ssands]

Disconnect any devices you can.

I've got nothing connected directly. No MP3 player. There are DLNA devices on the network, but nothing directly connected. This may have started when I transfered some files to an MP3 player that I had not previously used with MC. (Hadn't used it in years and years).

But it doesn't show up in my device list. All I see is the internal CD/DVD/blu-ray player. (Snapshot attached).

[JimH]

No USB devices?  Hubs?

[ssands]

No USB devices?  Hubs?

Nothing. There's is nothing plugged into this machine. Not even a mouse (I use the built-in trackpad).

Is it possible that there is a setting somewhere indicating that the handheld should still be there? I saw handheld error messages in the log I posted above. And I did use a handheld for the first time ever about a month ago, so it could be related.

Is there someway that MC has to "eject" a handheld?
(I've rebooted numerous times since I used that handheld.)

[adamt]

Do you have any DLNA devices or other things on the network?  Try disabling Media Network. Sometimes they can cause slow shutdowns.

[ssands]

Do you have any DLNA devices or other things on the network?  Try disabling Media Network. Sometimes they can cause slow shutdowns.

There are DLNA devices on the network, but that hasn't changed in years. Also, it's not slow, it just doesn't shut down.
I have seen slow shutdowns (and thought they might be network-related), but this is not that.
It does not shut down at all. No matter how long I wait.

[glynor]

I hadn't gotten a chance to come back yet, but I did see two things in your Log package.

1. The Realtek drivers aren't up to date. I've seen this with Realtek drivers.  Try updating them. If it is a laptop, you might need the ones from your OEM instead of Realtek, but it's pretty much equally likely that the Realtek ones will work fine.

2. You have all sorts of audio outputs enabled, which MC is enumerating, including HDMI audio for the Intel onboard and Nvidia GPU.  If you're only using one, disable the rest.  Usually you can just do this in the Windows Sound Control Panel, but it can help in other ways if you disable the GPU entirely if it isn't being used (in the BIOS).

[ssands]

I hadn't gotten a chance to come back yet, but I did see two things in your Log package.

1. The Realtek drivers aren't up to date. I've seen this with Realtek drivers.  Try updating them. If it is a laptop, you might need the ones from your OEM instead of Realtek, but it's pretty much equally likely that the Realtek ones will work fine.

2. You have all sorts of audio outputs enabled, which MC is enumerating, including HDMI audio for the Intel onboard and Nvidia GPU.  If you're only using one, disable the rest.  Usually you can just do this in the Windows Sound Control Panel, but it can help in other ways if you disable the GPU entirely if it isn't being used (in the BIOS).

Thanks, I did in fact update the RealTek drivers last night, but that didn't seem to help. The weird thing is nothing has changed on the HDMI audio settings, it's perhaps been years. I rarely use them, but have before.

So, I will try that, but not sure why that would cause the hang (as opposed to a slow shut down).

Do you think the Handheld errors are not a concern?

[ssands]

Windows Sound Dialog is only showing RealTek, and as I mentioned, I updated the drivers yesterday. And the problem is still occurring.

Side question: why would having the HDMI on the intel and nvidia chips impact JRiver? I can understand that it might make for a longer shutdown, but I'm experiencing a complete hang.

[ssands]

Turned off the Intel and Nvidia audio.

Had no effect.

Still hangs forever on shutdown.

[JimH]

Did this start recently?

Other than MC, what else changed?  I notice you say Win10, but that it happened with Win7.

Do you have iTunes installed?

Antivirus?

Does MC 20.0.115 work?

[ssands]

Did this start recently?

Other than MC, what else changed?  I notice you say Win10, but that it happened with Win7.

Do you have iTunes installed?

Antivirus?

Does MC 20.0.115 work?

It did start recently, when I was still running Win 7.
I'm using Kaspersky, but have been for over a year and running MC longer than that.

I will try 115 and see what happens.

Did just notice another pattern. If I open MC, and even leave it open without using it to listen to audio, it will close. If I listen to audio, then it does not.

[JimH]

The fact that you were using the AV program before the problem began doesn't eliminate the possibility that it is the cause.  The only way to be sure is to uninstall it.

Even using an older build that works can't eliminate the possibility.

Here is a thread on antivirus problems.

[glynor]

Did just notice another pattern. If I open MC, and even leave it open without using it to listen to audio, it will close. If I listen to audio, then it does not.

Then it is almost certainly the audio device or drivers.

Try the uninstall/reinstall method described in the wiki:
http://wiki.jriver.com/index.php/Audio_Troubleshooting_Guide#Checking_for_Misbehaving_Audio_Devices

If that doesn't work, then it could be Kapersky interfering. OS patches and definitions updates can wildly alter the way AV applications behave. The only way to be sure and rule it in or out completely is to uninstall, reboot, test.

[ssands]

Well, I just checked V 115.

And it worked fine. I played some audio, stopped it, and then clicked the red X in the upper right.

And it closed.

So, while it is possibly an issue with AV and drivers, it sure seems like something changed in MC.

[ssands]

Forgot to address your other question:
I do NOT have iTunes installed. Never did, never will.

I can check about the AV later on, but it is interesting that it works fine in 20.0.115, but not the latest stable release.

[glynor]

Well, I just checked V 115.

That's interesting, but doesn't necessarily rule in or out the drivers, nor the Anti-Virus (in fact, it actually makes me more suspicious of the AV). But, Realtek's drivers are often troublesome. I've had to go back to earlier ones before and hunt around to find ones that work right (though usually the latest work fine).

For the record, I'm using Realtek onboard audio on 3 different machines right now, with no issues, including the one I'm typing this on (ALC898). I'm using Realtek 6.0.1.7083 from November 2013 on this machine.

But, before anything else, I'd still recommend this process:

Try the uninstall/reinstall method described in the wiki:
http://wiki.jriver.com/index.php/Audio_Troubleshooting_Guide#Checking_for_Misbehaving_Audio_Devices

[ssands]

[SOLVED]
It was the anti-Virus (Kaspersky Internet Security 2016).

For some reason, it impacted V131, but not the previous versions. I made sure to exclude the scanning of the MC files, and now it closes properly.

I did not have to make any changes to the RealTek drivers.

Thanks for you attention and help.
Weird how the same tools, with the same settings didn't bother earlier versions of MC, but did with the latest (of V20) and only after playing audio.

[JimH]

[SOLVED]
For some reason, it impacted V131, but not the previous versions. I made sure to exclude the scanning of the MC files, and now it closes properly.

Because they stupidly look for patterns in software.  It's impossible to do this and not cause problems with legitimate software that happens to have the same pattern.

I believe that Kaspersky supplies the "engine" for a lot of other antivirus programs, and that's probably why Norton and a few others have caused problems recently, starting after build 115 of MC. 

These problems should be reported to the antivirus makers.

The antivirus problem thread would be a lot longer if we had started it earlier.
http://yabb.jriver.com/interact/index.php?topic=86096.msg588759#msg588759

Thanks for posting the solution.

[ssands]

Reported.

[ssands]

So, I hate to bring this up, but it happened even after I turned off Kaspersky, but played audio for awhile.

So, that possibly points to Glynor's conjecture of a Realtek driver issue. (I am using the latest version of the Realtek audio driver).

Got fed up and tried MC 21.

And, it works fine w/Kaspersky and the latest Realtek driver.

So this was the only version I tried of MC that had that problem.

Just wanted to provide the update.

[JimH]

Turning "off" Kaspersky might not work.  Antivirus programs are embedded in the OS, so uninstalling them is the only way to know whether they are causing the problem.

They also might not like some sequence of characters or some process in just one build of MC.

Thanks for reporting in any case.