INTERACT FORUM
More => Old Versions => JRiver Media Center 21 for Windows => Topic started by: Blueshound24 on March 30, 2016, 05:36:35 am
-
I have MC 21 with Windows 7 and for whatever reason every once in a while it will freeze up and it will not shut down. To end the program I have to either go to Task Manager to "end process" or if that doesn't work reboot the computer. Never had any issues with MC 20. I think I have the latest build and will check to see and will post what version of MC 21 I have when I get it unfrozen. I am using Kaspersky AV. Thanks in advance for any solutions.
-
Hi if this persists you really should post your log after a crash/freeze like that. Almost impossible to guess what could cause this otherwise.
If you don't know how to do this here you go => https://wiki.jriver.com/index.php/Logging (https://wiki.jriver.com/index.php/Logging) Make sure you have the most recent version installed, not what is called the "stable" build which you might have installed so everyone ison the same page to help you. Check to see that all of your drivers are up to date especially Video drivers (even if you are only using audio for playback) and any drivers you might be using for your dac before posting the log. Often drivers are responsible
-
Please uninstall the AV to test. Disabling it may not be enough.
-
My build is 21.0.50, it appears that is the most recent?
I checked all my drivers they are all up to date.
I will uninstall Kaspersky and try to reproduce the issue.
Thanks
Log attached
-
There is a more recent build at the top of this board.
-
Ok, I installed 21.0.66
Thanks.
-
I am curious if anything deleterious showed up in my log. Would someone be able to decipher it?
-
I am curious if anything deleterious showed up in my log. Would someone be able to decipher it?
Hi
Sorry I'm not a real expert on logs and haven't the time to go through it totally. But it appears that you have a loop going on with an Amazon lookup. A duke Ellington record?? You also have a bunch of podcasts that are trying to update themselves, but they are not causing the freeze.
I'd clear the request or temporarily disable Amazon under Services=>Stores shown in the Tree too see if my guess is right. You can re-enable ti later. Warning you though I'm just fishing ... :) worse case I bump your post ;)
-
Hi
Sorry I'm not a real expert on logs and haven't the time to go through it totally. But it appears that you have a loop going on with an Amazon lookup. A duke Ellington record?? You also have a bunch of podcasts that are trying to update themselves, but they are not causing the freeze.
I'd clear the request or temporarily disable Amazon under Services=>Stores shown in the Tree too see if my guess is right. You can re-enable ti later. Warning you though I'm just fishing ... :) worse case I bump your post ;)
Ok, I do not even use podcasts, I'll try to disable them? As for Amazon, not sure what that is. I do not use an Amazon app and the only Amazon I use is when I go to the web page, (which I do a lot :-). So not sure how to: clear the request or temporarily disable Amazon under Services=>Stores shown in the Tree
But thanks for the bump ;)
After updating to 21.0.66 MC has crashed a couple of times, that is, it shut itself down. But has not locked up or gone unresponsive, to the point of not being able to shut it down manually.
-
@Blueshound the amazon I'm referring to is not an app per se it is a feature in JRiver itself. Why its looking up a Duke Ellington album I don't know. I told you how to disable this. Open Options then as I said Services=>"Stores Shown in the Tree" and uncheck "Amazon". Of course this might not have anything do do with it :D
If you don't use podcasts you can turn them off too, btw. Just type in te search box of the Opitions window. Its a good way to find stuff as there are so many options and configurations possible in JRiver
-
@Blueshound the amazon I'm referring to is not an app per se it is a feature in JRiver itself. Why its looking up a Duke Ellington album I don't know. I told you how to disable this. Open Options then as I said Services=>"Stores Shown in the Tree" and uncheck "Amazon". Of course this might not have anything do do with it :D
If you don't use podcasts you can turn them off too, btw. Just type in te search box of the Opitions window. Its a good way to find stuff as there are so many options and configurations possible in JRiver
:-[ face palm. Ok, I disabled Amazon via Services, and right clicked on podcasts in the tree and disabled auto download as well. Thanks for the search box in the Options window tip!
-
:-[ face palm. Ok, I disabled Amazon via Services, and right clicked on podcasts in the tree and disabled auto download as well. Thanks for the search box in the Options window tip!
not to worry its not obvious at all :) Hope this sorts you out. You shoudl trunoff the logging feature if this is all it was. The log file can get pretty big after awhile.
-
not to worry its not obvious at all :) Hope this sorts you out. You shoudl trunoff the logging feature if this is all it was. The log file can get pretty big after awhile.
Thanks!
The logging must have been on by default? I don't think I have ever turned it on?
Shouldn't it be left on in case something undesirable happens so there would be a record of it to diagnose?
-
Thanks!
The logging must have been on by default? I don't think I have ever turned it on?
Shouldn't it be left on in case something undesirable happens so there would be a record of it to diagnose?
not sure if it on by default actually :)
but the log can get really long (the size is not a real issue as much), just makes it easier to isolate the issues when trying to read them, IMO. Most glitches in MC have to do with drivers being out of date, or AVs not allowing an update to complete (once it has been set up and running well that is). Crashes are rare, but freezes where you have to wait on the program can happen for a lot of reasons unrelated to JRiver - network issues etc. I keep it off. If I have a problem and it recurs more than once, then its time to turn it on and try to provoke the problem by repeating what you just did when it crashed/freezed.
-
not sure if it on by default actually :)
but the log can get really long (the size is not a real issue as much), just makes it easier to isolate the issues when trying to read them, IMO. Most glitches in MC have to do with drivers being out of date, or AVs not allowing an update to complete (once it has been set up and running well that is). Crashes are rare, but freezes where you have to wait on the program can happen for a lot of reasons unrelated to JRiver - network issues etc. I keep it off. If I have a problem and it recurs more than once, then its time to turn it on and try to provoke the problem by repeating what you just did when it crashed/freezed.
That makes sense, I'll keep it off until needed.