OK, I just tried something on my local machine.
I used Dependency Walker to see what jvm.dll from C:\Program Files\Java\jre1.8.0_121\bin\server depends on.
And it does indeed depend on msvcr100.dll -- a MS VC 2010 CRT DLL.
Since there is no msvcr100.dll next to JVM.dll, it loads the copy from c:\Windows\system32.
Now... What happens on your system might be that on Murmur uninstall, the MSVC2010 CRT is uninstalled, and thus no longer available in c:\Windows\system32.
That means jvm.dll is no longer loadable.
The easy fix would probably be to copy msvcr100.dll from C:\Program Files\Java\jre1.8.0_121\bin into C:\Program Files\Java\jre1.8.0_121\bin\server so JVM.dll has a local copy.
You can even do the above trick without uninstalling Murmur first.
Just do it, and reboot, to ensure SageTV's JVM uses its own local copy of msvcr100.dll.
I suppose SageTV is using jvm.dll directly, instead of using java.exe/javaw.exe? If it used those, I imagine the jvm.dll would in fact load the msvcr100.dll from C:\Program Files\Java\jre1.8.0_121\bin. (It would be required to, since java.exe/javaw.exe use that DLL.)
Finally, to ensure that that is actually the case, I'd recommend finding the SaveTV process via Process Explorer (https://technet.microsoft.com/en-us/sys ... lorer.aspx
) to check whether the correct msvcr100.dll is loaded into the proces. Try to find the process in Process Explorer, and use the module view at the bottom of the screen to see the loaded DLLs.
You should expect SageTV to be using the msvcr100.dll not from C:\Windows\system32, but instead from the JRE diretory, probably C:\Program Files\Java\jre1.8.0_121\bin\server\msvcr100.dll.
Once you have confirmed that SageTV is not using msvcr100.dll from c:\Windows\system32, you should be able to safely uninstall Murmur.
Hope it helps,