MusicBee freezing/locking up

[RejZoR]

Can someone tell me how to figure out what's causing MusicBee freezes (lockups)? It just stops responding when minimized and only way to get it working is to kill the process. This always seems to happen if I have it minimized and NOT playing any music.

This was never happening prior Windows 10 TH2 update, but I'm not sure if this is the reason as I've also change some other system things in the meanwhile (like the M.2 SSD cache drive instead of SATA SSD and also the caching software).

Funny thing is, the only other app behaving the same is eMule. Just these two programs are locking up and NOTHING else even though those programs are also resident. It's easier to figure out on crashes through Event Viewer, but with lockups I have no idea what to even try.

[phred]

Does it -only- happen when minimized without music playing?  If music is playing when minimized it's fine?  And when the music stops, MB locks up?
What version of MB are you using?  If not 2.5.5804, see my sig and update to the latest patch and try again.

You can also check the Error Log - Help > Support > View Error Log - and see if there are entries around the time of the lockup.  If so, copy those lines and paste them here in your reply.

[RejZoR]

Yeah, it ONLY happens when it's minimized and NOT playing any music. I have MP3's playing through entire night and it hasn't locked up so far. But if I forgot MusicBee running and not playing down in the treybar, it just refuses to respond. I can doubleclick or right click the trey icon and it just doesn't respond. Then I have to kill it through Task Manager.

I am using 2.5.5804 (one version back was also locking up, when I updated to this latest version). Have checked the error log and there is nothing recen in it. Last errors are from August when I wasn't experiencing these issues.

I think this all started happening after the big Windows 10 update (TH2)...

Forgot to write down my system specs:

Intel 5820k 4.5GHz (fully stable, no crashes anywhere with it)
32GB RAM DDR4 2400MHz (using XMP profile)
ASUS Sabertooth X99 (BIOS 2001)
ASUS Strix GTX980 4GB OC (with ForceWare 359.06 WHQL, did notice that Experience trey icon is not running hm)
WD Black 2TB + 128GB Samsung SM951 M.2 SSD cache (both connected together with PrimoCache)
Sound Blaster Z with latest Win10 drivers
Windows 10 64bit TH2 (fully updated)
System pagefile disabled entirely (0 MB)

[Steven]

i have no idea what the issue would be caused by but you could try v3 as its quite different to v2.x
http://getmusicbee.com/forum/index.php?topic=15050.0
you can still use v2.5 afterwards if you dont want to continue using it

[RejZoR]

Thx, I'll check it out. Hopefully problems will be gone.

[hiccup]

Maybe some antivirus tool performing some actions (which it can't perform while MusicBee is 'in use'?)

[pjwhams]

FYI, in case it helps other people:

I have just experienced a similar problem.  I was ripping to mp3 with Lame and the process created about 10 blank Lame console windows which just hung.

I found the problem was that I had installed Lame via Chocolatey, and I had configured the path to lame as:

    C:\ProgramData\Chocolatey\bin\lame.exe

rather than:

   C:\ProgramData\Chocolatey\lib\lame\tools\lame.exe

The first path is actually a shim that redirects to the second exe. When I set it to the second then it worked perfectly.