Page 1 of 1

Windows 10: VBoxOGLpackspu.dll causes BSOD

Posted: 15. Nov 2017, 21:05
by AndreaL
VirtualBox_Windows 10 DEV_30_10_2017_19_40_27.png
VirtualBox_Windows 10 DEV_30_10_2017_19_40_27.png (16.63 KiB) Viewed 1535 times
I'm getting lots of BSOD when using my Windows 10 hosts.
Faulting application name: dwm.exe, version: 10.0.14393.0, time stamp: 0x578999ab
Faulting module name: VBoxOGLpackspu.dll, version: 5.1.30.18389, time stamp: 0x59e4836f
Exception code: 0xc0000005
Fault offset: 0x0000000000003a41
Faulting process id: 0x2740
Faulting application start time: 0x01d351cf64167a10
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\system32\VBoxOGLpackspu.dll
Report Id: b3a08867-26c9-4475-8103-2d62d68b75ec
Faulting package full name:
Faulting package-relative application ID:
I can provide more logs if needed.

Current version: Version 5.1.30 r118389 (Qt5.6.2)

Re: Windows 10: VBoxOGLpackspu.dll causes BSOD

Posted: 16. Nov 2017, 10:27
by mpack
That's a crash in an OpenGL driver, try turning off 3D acceleration.

Re: Windows 10: VBoxOGLpackspu.dll causes BSOD

Posted: 16. Nov 2017, 15:53
by dgrigorev
This is a known and already fixed problem, see https://www.virtualbox.org/ticket/17082 .
Please update your Guest Additions to a recent version.

Re: Windows 10: VBoxOGLpackspu.dll causes BSOD

Posted: 16. Nov 2017, 16:09
by mpack
Hmm. I must admit I don't personally see how that ticket is applicable. Plus the ticket says that the problem was fixed in 5.1.30, which is what the OP is using, unless you mean he needs to update the GAs?

Re: Windows 10: VBoxOGLpackspu.dll causes BSOD

Posted: 16. Nov 2017, 17:31
by dgrigorev
Hi AndreaL.
The ticket 17082 is in fact unrelated, I agree with Mpack.
Could you attach compressed VBog.log here?
Guest OS kernel memory dump is required also, please use the instructions
https://docs.microsoft.com/en-us/window ... -dump-file

Re: Windows 10: VBoxOGLpackspu.dll causes BSOD

Posted: 17. Nov 2017, 16:57
by quizerti
Seems like there is an issue with graphics on the current stable release of VirtualBox. In my thread ( here: viewtopic.php?f=2&t=85331 ), mpack also suggested that OpenGL is throwing up a lot of errors in my logs. I have also pointed another user to my thread, who is having similar issues to myself - this is their thread: viewtopic.php?f=2&t=85456
mpack wrote:Hmm. Someone else getting the "resolution xxx not accepted by the frontend" warning in the log. In the UI (not the VM) what setting do you have for File|Preferences|Display|Max Guest DIsplay Size?

I see several occurrences of OpenGL errors such as this :-
VBox.log wrote: 00:04:00.524920 OpenGL Warning: cleaning gl error (0x502), ignoring.. (3 out of 5) ..
00:04:00.554905 OpenGL Warning: cleaning gl error (0x502), ignoring.. (4 out of 5) ..
0x502 is GL_INVALID_OPERATION, not much help since I don't know what the operation is.

The session only seems to last 4 minutes, so I don't know if the OpenGL errors would have continued.