DWM.exe and Next PVR Issues since W10 Anniversary Update

[Barry10]

Anyone try the new release 3.8.3 and see if it fixed the memory issue?

[sub]

Anyone try the new release 3.8.3 and see if it fixed the memory issue?

I don't think it's anything directly related to NextPVR, so I doubt it'll make any difference. ie, it sounds like some bug with the Windows EVR video renderer affecting some systems.

[2leftfeet]

Sub,

I believe you are right, everything else being the same - DWM.exe was behaving itself with NPVR in fullscreen before AE, but going crazy after AE.

Question: I have been running the Kodi client all day without dwm.exe behavioral issues - what possible differences between the two clients (Windows interface) that would cause dwm.exe to expand its memory consumption in one case, but not the other?

[sub]

what possible differences between the two clients (Windows interface) that would cause dwm.exe to expand its memory consumption in one case, but not the other?

NextPVR uses the directshow, and the Windows video renders. Kodi doesn't use either of those, so probably a bug in one of those. Like EVR video renderer etc.

[Lofty]

I have had the same issue with dwm using up to 6gb of memory and bringing my system to a complete standstill. I ran the directx file on the previous page and changed to the VMR7 renderer and so far all appears to be running better.

[Lofty]

Update:

I spoke too soon. Have not even had NextPVR running today and dwm.exe is currently using 2,242mb of memory. Back to the drawing board...

[SoupSatchel]

I've got this issue too and was thinking of using this http://www.pcwintech.com/cleanmem. If anyone wants to be a guinea pig and try it first I won't stop them.

[jwh7]

Good news so far; I was fed up with this dwm memory issue, and since the Insider "Slow Ring" recently had a build update (14931), I decided to try it. Been watching football (fullscreen) for an hour, and dwm.exe is currently at 10.4 MB. Looks like something was actually fixed for a change. One out of 10 ain't bad I guess...

Note you have to log in with a MSN/Live account to enable Insider Builds.

[Trocadile]

Good news so far; I was fed up with this dwm memory issue, and since the Insider "Slow Ring" recently had a build update (14931), I decided to try it. Been watching football (fullscreen) for an hour, and dwm.exe is currently at 10.4 MB. Looks like something was actually fixed for a change. One out of 10 ain't bad I guess...

Note you have to log in with a MSN/Live account to enable Insider Builds.

Yes! At last this fix has made it to the "Release Preview" level (KB3201845). After updating, I've been able to switch back to EVR Video Renderer from VMR7 and DWM memory usage is now stable. For anyone still having this problem, I assume the regular Windows Update will soon have the fix included.

[griffy]

downloaded KB3201845 and so far all good, finally able to update to Anniversary update (just don't get me started about AMD drivers and preventing them from updating to broken HDMI switching one, somehow sorted that too)