MP Home Screen Freezes After System Has Been Idle (1 Viewer)

chrisworkman

Portal Pro
February 9, 2009
92
7
Ohio
Home Country
United States of America United States of America
I seem to have a problem similar to some others here, but I believe my issue is different becuase the known solutions haven't worked.

After my htpc has been idle or even suspended for a long period of time, upon resume MP is frozen at the home screen. Sometimes it will revive after a few minutes, sometimes if you let it sit it will "awake" after a few minutes to 30-40 miutes. Obviously, I'm not willing to wait so I normally have to hit the reset button and reboot. AFAIK tell, the OS is still functioning. When MP is frozen on the home screen I can still access hard drives, etc. via my network. If there's recordings occurring during this "frozen time", they'll playback without interruption later on when I've got it back working; so I believe the OS and the TVserver are still functioning. Sometimes hitting ctrl+alt+del will get it unfrozen, other times it won't.

What happens exactly is I'll turn on the TV and my htpc will wake up (if sleeping, even when it's not sleeping I'll usually get the same result) and the home screen will be frozen. The clock will say 3:00am (or whatever time in the past when it actually froze). When it does resume the current time will come up and the menus are then responsive.

I found a solution in another thread about using a MS loopback connection for the TV server but that didn't help.

Since I'm not sure it's the same issue, here I am.

BTW, I was recording to my NAS and then switched back to my internal drive and it's still doing it. It was doing it before I switched to the NAS also.

Thanks in advance.
 
Last edited:

mm1352000

Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,578
    8,228
    Home Country
    New Zealand New Zealand
    Looking at the log files now.
    PS: it helps to explicitly state the time when the latest problem occurred. I guess you grabbed the log files shortly after it happened?
     

    chrisworkman

    Portal Pro
    February 9, 2009
    92
    7
    Ohio
    Home Country
    United States of America United States of America
    Yes I did. And it happened the next morning also. Lately I've been closing MP so I can still record, etc. without having to manually force a restart due to the freezing.

    I can pull more logs if needed, just let me know.
    Chris
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,578
    8,228
    Home Country
    New Zealand New Zealand
    Yes I did. And it happened the next morning also. Lately I've been closing MP so I can still record, etc. without having to manually force a restart due to the freezing.
    What I see is that Windows thinks MP is hanging:

    "10/10/2012 11:10:15 PM";"Application Hang";"(101)";"Error";"The program MediaPortal.exe version 1.2.3.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 9a4 Start Time: 01cda75dd81304e2 Termination Time: 9 Application Path: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Report Id: ";"1002"

    So that happened at 11pm.
    I'm not sure if that means that you had this problem after attempting to wake the computer or whether the fact that it is hanging is what caused the problem the following morning.
    Unfortunately the MP and MP error logs don't go back this far so I can't tell what might have caused this.

    Note: looks like you have a runaway recording?
     

    chrisworkman

    Portal Pro
    February 9, 2009
    92
    7
    Ohio
    Home Country
    United States of America United States of America
    How could I determine that? Recordings seem to be starting and finishing as intended.

    And would Windows thinking MP is hanging be any diff than MP actually hanging? I mean the screen is frozen, etc.

    Would additional logs help?
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,578
    8,228
    Home Country
    New Zealand New Zealand
    How could I determine that? Recordings seem to be starting and finishing as intended.
    I was mistaken. :)

    And would Windows thinking MP is hanging be any diff than MP actually hanging? I mean the screen is frozen, etc.
    That would depend on what MP thinks it is doing, and that is what I'm struggling to ascertain at this point.

    Would additional logs help?
    Yes, absolutely. Please specify times and dates as well if possible.
    For example, turned on TV at 6pm on the 14th and MP was frozen.

    mm
     

    chrisworkman

    Portal Pro
    February 9, 2009
    92
    7
    Ohio
    Home Country
    United States of America United States of America
    Got home tonight and the system was frozen up. Here's the logs I immediately pulled. I noticed that last log entry was at 01:45 this morning so I'm assuming that is when it froze.

    The error log has the following which I noticed before:

    Code:
    2012-10-15 01:45:00.430589 [ERROR][MPMain(1)]: HTPC Info: Speedfan Shared Memory Initialization Error. (Error Code: HTPCInfo.Core.SharedMemoryException: Error accessing shared memory area. (2)
      at HTPCInfo.Core.SpeedfanSharedMemory..ctor()
      at HTPCInfo.Core.SpeedfanHandler..ctor(Boolean filterZeroValues)
      at HTPCInfo.Core.SpeedfanHandler..ctor()
      at HTPCInfoPlugin.HTPCInfo.InitConnectors(), Error accessing shared memory area. (2))

    What's happening here? Could this be the cause? It's a heck of a coincidence that the system appeared to freeze at the same exact time.

    Thanks again in advance.
     

    chrisworkman

    Portal Pro
    February 9, 2009
    92
    7
    Ohio
    Home Country
    United States of America United States of America
    Here's more logs. Turned the TV on about 1am (10/16) and the MP Home Screen/clock was frozen at 11:01pm (10/15).

    I'm only assuming that's when it froze.
     

    Users who are viewing this thread

    Top Bottom