[solved] WARNING: NVidia driver issue since 358.87 (5 Viewers)

[killer8]

Not sure yet, I reverted to 359.00 now first, as I thought this was stable for me. Atleast it didn't crash straight away when I use your steps from the first post to reproduce it.

Will keep you updated.

 

[killer8]

I just had a crash with 359.0(included watchdog zip). I will revert to the drivers from the first post 358.50

 

[powermarcel10]

I have still the same problem, also after a fresh windows 10 installation. Latest driver that is working fine is 358.50 indeed...

 

[Remoteglen]

Hi guys

So I rolled back to 358.50 and everything seemed fine.

I the thought I would try the latest version 359.06 and it was ok for a few days then mp started freezing again so I rolled back to 358.50 and it is still freezing!

I have attached logs in case something else is going on.

Can someone let me know please

 

[Sebastiii]

Can you tell us when it freeze ?
It seems that it's a different issue but i'm not 100% sure, i didn't see GPU drivers error in log.

 

[Remoteglen]

While watching recorded tv

 

[Stéphane Lenclud]

Yeah, sounds like a different issue. Also my issue does not cause a crash. Instead it hangs for while and the UI renders are broken. However somehow MP is still responding to commands even though you only get garbadge on the screen amd thus can't see what you are doing.

 

[Remoteglen]

I was watching a show it would just freeze and none of the buttons on the remote would do anything.

Sometimes if I press the button to launch mp on the remote it would go back to the home screen.

I would then go back to the file and it would be as if I hadn't watched it.

 

[mm1352000]

It seems that it's a different issue but i'm not 100% sure, i didn't see GPU drivers error in log.

Look in MediaPortal.1.log rather than MediaPortal.log.

[2015-12-08 13:50:19,497] [Log ] [MPMain ] [INFO ] - Planescene caught GPU_HUNG in InternalPresentImage

...and then lots of D3DERR_NOTAVAILABLE etc. as usual.

 

[mm1352000]

BTW, I was just looking at the code and this seems odd to me:
https://github.com/MediaPortal/Medi...iaportal/MediaPortal.Application/D3D.cs#L1290

@Scythe42
Why is the Windowed property hard-coded as "true"? Surely that should be set based on the "windowed" parameter (as it was in the old code before your rework)?