avidemux is conflicting with windows 10

[nick4avi]

The conflict seems to occur at least At least withcumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3194496)  and possibly earlier.

After doing between 5 and 10 files conversions - the display goes completely dead on the computer, and while the system appears to be running - there is no alternative but to reboot the system.  I have 16 gb of RAM and many spare terabytes of disk space.  It is a very strange bug  and of course it may also be an issue caused by microsoft.  However, it occurs only when I am using avidemux.  It is quite possible that other applications exhibit the same behavior - but right now the only culprit I see is avidemux.  I hope that some developer with an intimate knowledge of avidemux internals can correct this - I use it very frequently.

The tasks that I am doing when it happens is always converting a video file to H264  and avi  - a facility that I see has been made much more complicated in the latest version of avidemux.

If by some misperception it is avidemux at fault then please let me know how I can make it functional;

[mm0359]

Please provide more (technical) details!
For example,

Which version of Avidemux are you using?
Does it happen with an earlier/later version?

Which codecs/settings are you using?
Anything interesting in Avidemux log (after reboot)?

What about the Avidemux process while you use it? CPU/RAM usage (increase), ...
Anything interesting in Windows (event) logs (after reboot)?

...

[zakk]

I would run a stress test if I where you. Possibly a hardware problem of power supply, heat, etc...

[fish]

I would guess your video card is in terminal decline. My last video card, which had more than paid it's way, began it's slow death by giving a screen full garbage intermittently, only when playing 1080p video in full screen. I was able to keep using it but when I finally junked it, it was showing garbage every time I played a few seconds of 1080p video in full screen.