I ran into a similar problem when moving to 2016 because of a bug in settings for hardware acceleration. See this post: