I just went through a series of having to kill and restart MC 24.0.45...
After a reboot of the Win7 desktop, I kept trying to use JRemote to start up some music. While it was able to connect and allow browsing of the library, JRemote's list of zones/devices was incomplete -- it never seemed to populate correctly. Walking over to the desktop and trying the GUI, it had frozen. Killing that process and trying again, with JRemote as the "first point" of contact, the same behavior happened again.
Letting Windows stop the MC process and re-starting again, I used the GUI on the desktop to start playback on the device I was interested in (an ODroid running Kodi that has been quite stable). After verifying that playback had started, then I was able to stop playing (on a new instance of JRemote, running on iOS) and perform my usual library browsing.
So, the above is seemingly separate from the sleep problem I first replied with, but I thought worth capturing. After all of this, playback has been nice and stable and MC (and JRemote) seem happy to get along (presumably until the next reboot).
With recent MC releases, it really seems like it takes some patience to get things "settled" and working following a reboot of the desktop!