Win10 Lync 2013 crashes on VBoxD3D9wddm-x86.dll 4.3.28.0

Discussions about using Windows guests in VirtualBox.
Post Reply
kjstech
Posts: 1
Joined: 6. Jul 2015, 21:35

Win10 Lync 2013 crashes on VBoxD3D9wddm-x86.dll 4.3.28.0

Post by kjstech »

Windows 7 Pro 64-bit guest running VirtualBox 4.3.28 and latest Windows 10 Pro technical preview build 10162 (clean install) cannot execute Microsoft Lync 2013 (Now called Skype for Business).

The error is "The program has stopped working". In Event Viewer there is more detail that states Faulting application name: lync.exe version 15.0.4701.1000 Faulting module name: VBoxD3D9wddm-x86.dll, version 4.3.28.0, exception code 0xc000005.

I know its running in Windows 10 along with Office 2016 Technical Preview, but its faulting in a VirtualBox display driver it looks like, so I figured I would post here. Tried running the app under various compatibility modes with no fix.
Carlos D.
Posts: 19
Joined: 29. Jun 2015, 14:11
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Win10 Lync 2013 crashes on VBoxD3D9wddm-x86.dll 4.3.28.0

Post by Carlos D. »

I also noticed that certain programs simply crash the VBox Direct3D driver if you start them while having 3D acceleration enabled. Turn 3D off, and those applications start fine, although slow. That's an issue even in the latest 5.x version. MS might have changed something in their Direct3D when they moved to 10.x kernels...
DFarmerTX
Posts: 8
Joined: 2. Aug 2015, 01:12

Re: Win10 Lync 2013 crashes on VBoxD3D9wddm-x86.dll 4.3.28.0

Post by DFarmerTX »

This happens to me to. If 3D acceleration is disabled, it works fine, but the entire display driver is disabled by Windows 10 when the host screen goes to sleep.
Greg_D
Posts: 1
Joined: 18. Aug 2015, 00:13

Re: Win10 Lync 2013 crashes on VBoxD3D9wddm-x86.dll 4.3.28.0

Post by Greg_D »

DFarmerTX wrote:This happens to me to. If 3D acceleration is disabled, it works fine, but the entire display driver is disabled by Windows 10 when the host screen goes to sleep.
This is happening to me as well. I'm hoping that the next version will fix it and will be released soon.
Post Reply