More > JRiver Media Center 19 for Windows

How to "Fix" MC if it is Hanging or Crashing

<< < (2/7) > >>

JimH:
I love glynor when he goes verbose.   ;D :D

Thanks, Ed!

mwillems:
Really excellent stuff here; this will save folks a lot of heartache  :)

nwboater:
Glynor - Great thread!!!

A couple of months ago I needed to reinstall Win7 on our HTPC. (This had nothing to do with MC - it was a corrupted OS.) Prior to the OS reinstall we would get several hangs and crashes a week. Since the reinstall I don't think we have had one. A wonderful improvement obviously!

Really don't have a clue what had been causing all the grief before the reinstall but there were a few versions of MC and lots of unneeded stuff on the system. There had also been many installs/uninstalls of a variety of software. I am now trying to keep our HTPC as lean as possible.

I find a periodic OS reinstall very beneficial on any system. It can be a good bit of work but I am usually rewarded with much better performance. In this case it made a tremendous improvement.

Cheers,
Rod

jmone:
Just sat down with a cup of coffee to read through - great stuff.

glynor:

--- Quote from: jmone on January 15, 2014, 02:36:33 pm ---Just sat down with a cup of coffee to read through - great stuff.

--- End quote ---

I'm actively modifying it and adding to it now.


--- Quote from: nwboater on January 15, 2014, 08:26:51 am ---I find a periodic OS reinstall very beneficial on any system. It can be a good bit of work but I am usually rewarded with much better performance. In this case it made a tremendous improvement.

--- End quote ---

I prefer to save this as a solution of last resort.  If you are careful with your installation, you can usually get years (and even multiple physical hardware platforms) of life out of a single Windows installation.  But, sometimes, a good old Nuke and Pave is certainly the easiest solution.

Before you proceed with this, I'd certainly verify hardware stability.  Nothing is more frustrating than blowing away a working copy of Windows, and everything that goes with it, only to discover that it was a bad RAM stick or flaky motherboard that caused the issue (when it recurs with a brand-new build).

Navigation

[0] Message Index

[#] Next page

[*] Previous page