Nvidia geforce driver 417.01 break mp1 (2 Viewers)

[daWooky]

pretty weird, but (un)luckily not everyone seems to be affected. i tried it briefly on my game pc with the latest win 1803 updates and nv 417.01 - still worked as before

 

[grabi_2001]

with 417.21 I also have the boot loop, I had already said.

 

[Sebastiii]

I have installed 417.21 and all is working here on my side but I'm on insider lol

 

[catavolt]

I'm on insider

As you can see from my specs me too

 

[HomeY]

I'm on a non-insider build, tested 417.21 and that still gives me the bootloop, so back to 416.94 for me

[2018-12-01 09:32:40,114] [Log ] [MPMain ] [INFO ] - Main: GPU_HUNG - Error in the application.
-2005530508 (Unknown)
at Microsoft.DirectX.Direct3D.Device.PresentInternal(tagRECT* sourceRectangle, tagRECT* destRectangle, IntPtr overrideWindow)
at Microsoft.DirectX.Direct3D.Device.Present()
at MediaPortalApp.Render(Single timePassed) in D:\GITsource\Sebastiii\mediaportal\MediaPortal.Application\MediaPortal.cs:line 3874
[2018-12-01 09:32:40,114] [Log ] [MPMain ] [INFO ] - Restarting - saving settings...
[2018-12-01 09:32:40,130] [Log ] [MPMain ] [DEBUG] - Restarting - executing script C:\Program Files (x86)\Team MediaPortal\MediaPortal\restart.vbs

** EDIT **
Windows updated itself again (KB4467682) and with Nvidia driver 416.94 i don't have a bootloop and ambilight is still working fine.
So it looks like Nvidia driver is causing the problems (although i had D3D errors yesterday after rolling back Nvidia update).

 

[Requiem]

I can confirm this with mit 950 on my HTPC. Broken with 417.01 (bootloop).
I reinstalled my HTP this week and went back to the version before, everything fine so far. Win10 Pro x64 v1809, non-insider build, current windows patchlevel.
Hope this gets fixed soon.

 

[mironicus]

The problem does not appear if you start Mediaportal in windowed mode (disable "Start Mediaportal in fullscreen mode").

 

[grabi_2001]

Thanks for the workaround ...
But that is not a solution for a living room and wife and child .... unfortunately ... can already hear the discussions
The new version 417.22 has the error as well.
Then stop back to the older driver

 

[HomeY]

The new version 417.22 has the error as well.

+1 on that, got the same bootloop with 417.22 here (back to 416.94)

 

[Sebastiii]

Thanks, too bad that I wasn't able to reproduce it but maybe I will soon and will be able to debug that but I'm little busy for now