Windows 10 / Nvidia / 3D Video Playback - Windows Feedback Need Your Upvotes Please

[Nullack]

Hi folks

Are you on Windows 10 and use Nvidia GPUs? Are you sick and tired of the crashing experienced in 3d video playback with 3d stereoscopic enabled? Do you want to enjoy Madshi's madVR and Hendriks Lav Filters MVC playback and have it just work without hassles?

Well help me pressure the windows insider feedback system by upvoting my bug here:

Windows-Feedback:?contextid=70&feedbackid=63f74739-1fb0-4cad-a119-738b24b50ba8&form=1&src=2

In Windows 10 go into the feedback app, search for "3d video htpc" and you'll see the feedback titled "Serious Problem for HTPC Enthusiasts on Windows 10 and Nvidia with 3D Stereoscopic Playback."

Microsoft are generally working in this area now with build 11102 on the fast ring for windows insiders so nows the time to slip this one into that work and pressure Microsoft a bit.

Thanks

[huhn]

and the bug would be?

[FDisk80]

yea, what is the bug? And what is up with that link?

[Nullack]

The bug is the BSODs / Nvidia crashes / Media player crashes / madVR crashes that occur when 3d stereoscopic mode is enabled in the Nvidia control panel on Windows 10 builds (since beta, into RTM, then ongoing builds including windows insider builds post threshold 2 release Nov 2015) with madVR and playing back 2D content, or during mode shifts between 2d and 3d desktops for 3D MVC MKV content. Madshi has indicated its not something he can resolve and all the crash reports from madvr / mpcbe / BSOD crash analysis point to problems in WDDM and device drivers.

The bug also occurs with Cyberlink PowerDVD under the same circumstances. Cyberlink have also indicated they cant resolve the issue themselves.

Its not an app level problem, its lower down the abstraction stack.

EDIT: Its a link for the windows insider hub windows feedback app its not a URL.

[huhn]

if you want help you need to be way more precisely in your bug report.

a step by step way to reproduce the issue.

the bug reports from the event viewer.

links to other people with the issue.

BSODs / Nvidia crashes / Media player crashes / madVR crashes

so everything crushes randomly? sometimes the player sometimes the driver, sometimes the system and sometimes madVR?

if so link all available information to microsoft too. where the creator of these crashing software say that the issue is in WDDM.

and remove anything unnecessary a wall of text doesn't help.

[Nullack]

Normally what you say would be relevant, but this isnt a normal bug report situation. There's a bunch of stuff that's happened in the past months your not aware of. Like, me sending nvidia EDIDs , BSOD kernel memory dumps etcetc. Theyve got all the replication steps and the test results. Nvidia have been dealing with OS changes in the wddm / other areas as new windows builds fix bugs and so on. Windows 10 is now a service model not a waterfall style release model. The windows feedback isnt about supplying what their partner ihv already told them - its about demonstrating people are concerned about the issue and getting them to focus on it.

Another example is Intel and how weve waited over six months for teaming support in windows 10 for link aggregation. Its not just a matter of an ihv giving technical details in a normal bug report - its about applying heat from users so Microsoft pay attention to it. Intel gave them all the detailed bug report info before the windows 10 beta in one of the tech previews.

Getting MS to do stuff is about community pressure

[FDisk80]

Originally Posted by Nullack

The bug is the BSODs / Nvidia crashes / Media player crashes / madVR crashes that occur when 3d stereoscopic mode is enabled in the Nvidia control panel on Windows 10 builds (since beta, into RTM, then ongoing builds including windows insider builds post threshold 2 release Nov 2015) with madVR and playing back 2D content, or during mode shifts between 2d and 3d desktops for 3D MVC MKV content. Madshi has indicated its not something he can resolve and all the crash reports from madvr / mpcbe / BSOD crash analysis point to problems in WDDM and device drivers.

The bug also occurs with Cyberlink PowerDVD under the same circumstances. Cyberlink have also indicated they cant resolve the issue themselves.

Its not an app level problem, its lower down the abstraction stack.

EDIT: Its a link for the windows insider hub windows feedback app its not a URL.

You right, I noticed the crashes when using madVR with stereoscopic mode is enabled. Doesn't have to be anything 3D going on. MPC-BE will sometimes show a low memory warning or just crash while opening a 2D content.
With stereoscopic mode is disabled the problem doesn't occur.


Another issue that started with Windows 10 Version 10.0.10586 update "ArcCtrl.sys" driver that belongs to "Arcsoft Total Media Theatre". Total Media Theatre is no longer supported or developed. With the latest Windows 10 update OS will BSOD randomly.

"ArcCtrl.sys" driver needs to be removed manually. For some reason uninstalling "Total Media Theatre" doesn't remove it.

So yea, Windows 10 messed up stereoscopic mode real good.