One issue that you might notice after upgrading to Windows 10 is that the vMix interface appears slightly out of ficus or blurry. The way to resolve this is to right click over the vMix desktop item. Select "Properties". Select the "Compatibilty" tab and check the "Disable display scaling on high DPI settings".

This will need to to be done for a number of applications, not just vMix.

Martin, if you want to test this, try using your older Lenovo laptop with the thunderbolt port. It was on that machine/model I picked up the issue.

I just upgraded to Windows 10 but vMix will not play MP3 Audio now. Any help appreciated!

Nick, I have tested on a number of machines and cannot replicate this. Can you play mp3's with other programs?

For those found on Windows 10 and Vmix a Blue screen in dxgmms1.sys with an nvidia card, you must return to the 350.12 driver for Windows 8.1.
indeed any drivers for Windows 10 like the nvidia 359.02 trigger a BOD on some middle and high end cards.

Jean Michel

Just got a D3DStartup error as well vMix 108

ASUS Laptop 880M Running Win 10

Just went back to 8.1 and all ok

Just got the D3DStartup error on my Asus UX302LG Laptop (Nvidia GT 730M).

For testing purposes I recently switched over to Win10 on this machine. Initially the Nvidia card was not recognized (driver error in Windows), but after a few days (and Windows updates I guess), fibbling with drivers from Nvidia, it started to both being recognized and used by vMix.

After some thinking and testing it seems to me that I got/get the D3DStartup error when I switch over form 720@50p to 1080@50p. The only way to get vMix running again was to right-click start vMix(x64).exe with Integrated graphics (Intel HD), go back to 720p, restart vMix, and exit. After that vMix(x64) with Nvidia works again (trying with 1080p will repeat the error).

As I said earlier, it will be quite a while before we switch over to Win10 on our production machines.

(and I am pretty fed up with how Microsoft PUSH/FORCE out Win10).

Be careful out there ;)

Was able to switch from C530 to GTX 960M card before, but today I got D3DStartup-error... Only thing I changed were sme settings in Vmix; changed display size from 720x480 to 1920x1280. Changed it back and was able to switch grahicscard again!

Win 10
Lenovo Ideapad Y700
Intel HD Graphics C530
Nvidia GTX960M

I'm with Tom!
Windows 10 isn't ready for Prime time on a video production system, primarily because they've screwed up the video system when they added DX12.

If I update my GTX 970 drivers, it works great with 3-4ms render times until I restart the machine, and my render times increase to greater than 48ms, and 30FPS 720P video output has trouble maintaining 20FPS. The only way to rectify this sluggish performance is to re install the drivers, and reboot again, but then it's only good for that one boot.

I'm finishing up installing 8.1 on that system for vMix. It's on a separate HDD, so I can still play with it on 10 on the same system, but for now, I've given up on 10 for video production.

I might add as well, it doesn't really seem to affect my CPU performance.

I resolved all my windows 10 issues!

I reverted to Windows 8.1!
;)

I've recovered the performance windows 10 lost.

Hi guys,

There appears to be a recent update called the Windows 10 November Update
that is causing blue screen crashes to occur on systems with NVIDIA graphics when running graphically intensive software such as vMix.
(A lot of reports of games having the same issue as well)

For many users this update has only been installed in the past month or so causing an increase in problems being reported.

I initially though this bug was caused by vMix 17 as that is when I started seeing it for myself.
(For what its worth Windows 10 has actually been pretty smooth sailing on our own systems up until now..).

We have submitted an emergency support request with both Microsoft and NVIDIA to hopefully get this issue resolved very soon.

If you are seeing high CPU, that is an unrelated issue that you can narrow down the source for in Task Manager.
If it is "System and compressed memory" that means it could be a driver, possibly a capture card driver that does not like the November update either.
Since we aren't seeing this issue internally, if you are able to email us to setup TeamViewer I have some diagnostic tools to find the specific driver at fault.

Regards,

Martin
vMix