Nvidia geforce driver 417.01 break mp1 (1 Viewer)

Stéphane Lenclud

Development Group
  • Team MediaPortal
  • April 29, 2013
    2,563
    1,288
    Germany Germany
    Country flag
    Reverting back to 416.94 fixed it.
    Error log was empty. Log themselves just stopped at some point.
    What was most annoying was that MP1 would keep restarting and crash in a loop.
    Do we have a watcher of some sort that's restarting MP1 after it crashes? That does not seem right.
     

    HomeY

    Test Group
  • Team MediaPortal
  • February 23, 2008
    6,466
    4,634
    45
    ::1
    Netherlands Netherlands
    Country flag
    GTX 1050i, 417.01 leaves MP in a bootloop while starting, showing a GPU_HUNG in the logs. Reverting back to 416.94 solves this, and makes MP usable again, but i'm not sure if there are more issues.
    My ambilight is broken on a D3DERR_INVALIDCALL, but not sure if this is from the Nvidia drivers or from the Windows update. I'll try to revert that update today for testing purposes.
     

    HomeY

    Test Group
  • Team MediaPortal
  • February 23, 2008
    6,466
    4,634
    45
    ::1
    Netherlands Netherlands
    Country flag
    OK, did some testing.

    Windows including latest update (KB4467682) and latest Nvidia driver (417.01) results in bootloop on startup of MP (GPU_HUNG) and broken ambilight (D3DERR_INVALIDCALL)

    Rolled back Nvidia driver to 416.94:
    - MP startup bootloop fixed, ambilight still broken

    Rolled back MS KB4467682:
    - So far everything works again, no bootloop and no D3D errors on ambilight. more testing to do
     

    Sebastiii

    Development Group
  • Team MediaPortal
  • November 12, 2007
    16,434
    10,256
    France
    France France
    Country flag
    It's possible that in code a restart it done even if this option is not checked (from memory) but its an error. So need to be investigated :)

    Tapatalk
     

    Users Who Are Viewing This Thread (Users: 0, Guests: 1)

    Top Bottom