[Solved] 3d acceleration not working since 5.1.28 ?

[socratis]

Hello

I use Virtualbox on Windows 10 Host. My Guest is Windows XP.
Since I upgrade to Virtualbox 5.1.28, 3d acceleration (Direct 3D) no more working.
I installed Virtualbox addition in safe mode, 3D acceleration is enabled...

Upgrading to 5.1.30 / 5.2 RC1 don't change anything...

Any ideas ?
Thanks

[socratis]

I installed VirtualBox addition in safe mode

Safe mode is required only for Windows XP and Windows 7 with the Direct3D and not the WDDM drivers. In short if you install the WDDM drivers (like on Windows 10) you shouldn't be booting the VM into safe mode..

3d acceleration (Direct 3D) no more working.

What exactly was working and what exactly stopped working?

Edit: I misread your guest, I though that it was Win10, when that's your host and your guest is WinXP. You need to install the GAs in safe mode. Sorry for the confusion

[Ethancarter]

Thanks.

In fact Direct3D 8 and 9 are not working (Direct 3d 7 never works)
Tested with Dxdiag and a camera app using 3D.
When I run Dxdiag test, the screen becomes black.

I tried to reinstall Windows XP on Virtual Machine ... exactly the same problem.

I'm on VirtualBox 5.1.30 (Windows 10 hosts) :
- 2D and 3D acceleration ticked in config
- Additions (5.1.30) installed on safe Mode with "3d Mode"

I had any problem on previous versions (5.1.26...)

Thanks !

[socratis]

• Follow a "start the VM from cold-boot" / "observe error" / "shutdown the VM" cycle.
• With the VM shut down completely (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).

[Ethancarter]

Hello,

Here is the log (zipped). I read in this log :

00:00:08.059888 OpenGL Info: Host does not support OpenGL extension(s):
00:00:08.059894 OpenGL Info:   GL_ARB_shadow_ambient
00:00:08.059965 OpenGL Info:   GL_EXT_clip_volume_hint
00:00:08.059975 OpenGL Info:   GL_EXT_blend_logic_op
00:00:08.060084 OpenGL Info:   GL_EXT_texture_rectangle
00:00:08.060135 OpenGL Info:   GL_SGIS_texture_border_clamp
00:00:08.060159 OpenGL Info:   GL_SGIS_texture_edge_clamp
00:00:08.060193 OpenGL Info:   GL_GREMEDY_string_marker

In the Host (Windows 10) I have a Core i7-6700k + Nvidia Geforce GTX 970 and of course 3D is supported...

This is two screenshots on my Windows XP guest. Sorry, this is not an english Windows. Direct3d is enabled on Dxdiag and I run test: https://img15.hostingpics.net/thumbs/mini_851791ScreenShot001.jpg

Previously Direct3D8 and 9 works fine... But Now I get only this black screen: https://img15.hostingpics.net/thumbs/mini_301811ScreenShot002.jpg

And ANY apps using 3D works in the guest....

Thanks !

[socratis]

I read in this log :

00:00:08.059888 OpenGL Info: Host does not support OpenGL extension(s):

The smaller that list is, the better the support of your graphics card. For comparison, mine (AMD Radeon R9 M370X on a MacBookPro retina) has more non-supported extension compared to yours:

Code: Select all   Expand viewCollapse view

00:00:01.099578 OpenGL Info: Host does not support OpenGL extension(s):
00:00:01.099580 OpenGL Info:   GL_EXT_compiled_vertex_array
00:00:01.099595 OpenGL Info:   GL_EXT_texture_env_combine
00:00:01.099603 OpenGL Info:   GL_EXT_texture_env_dot3
00:00:01.099610 OpenGL Info:   GL_IBM_texture_mirrored_repeat
00:00:01.099632 OpenGL Info:   GL_EXT_blend_logic_op
00:00:01.099653 OpenGL Info:   GL_EXT_texture_cube_map
00:00:01.099658 OpenGL Info:   GL_EXT_texture_edge_clamp
00:00:01.099668 OpenGL Info:   GL_EXT_texture_object
00:00:01.099674 OpenGL Info:   GL_EXT_texture3D
00:00:01.099686 OpenGL Info:   GL_NV_fragment_program
00:00:01.099691 OpenGL Info:   GL_NV_fragment_program_option
00:00:01.099697 OpenGL Info:   GL_NV_fragment_program2
00:00:01.099702 OpenGL Info:   GL_NV_register_combiners
00:00:01.099708 OpenGL Info:   GL_NV_register_combiners2
00:00:01.099716 OpenGL Info:   GL_NV_texture_rectangle
00:00:01.099726 OpenGL Info:   GL_NV_vertex_program
00:00:01.099731 OpenGL Info:   GL_NV_vertex_program1_1
00:00:01.099736 OpenGL Info:   GL_NV_vertex_program2
00:00:01.099742 OpenGL Info:   GL_NV_vertex_program2_option
00:00:01.099747 OpenGL Info:   GL_NV_vertex_program3
00:00:01.099756 OpenGL Info:   GL_SGIS_texture_border_clamp
00:00:01.099777 OpenGL Info:   GL_GREMEDY_string_marker


However, your problem is not the non-supported OpenGL extensions, it's the fact that your whole Nvidia driver is rejected:

00:00:07.955660 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH
                fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\nvapi64.dll:
                WinVerifyTrust failed with hrc=CERT_E_CHAINING on '\Device\HarddiskVolume4\Windows\System32\nvapi64.dll'
00:00:07.955798 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\system32\nvapi64.dll'
                (C:\WINDOWS\system32\nvapi64.dll): rcNt=0xc0000190

The "VERR_CR_PKCS7_KEY_USAGE_MISMATCH" I believe refers to the fact that the Windows certificate database does not have the same certificate as the one presented by the DLL itself, forcing VirtualBox to outright reject the DLL. No DLL loaded, no 3D support.

You could/should try to install the latest graphics drivers for your graphics card, even if it's the same version. Sometimes the update mechanism either forgets to or fails to update the Windows certificate database and that can cause a mismatch. Someone would hope that a proper re-installation would remedy the situation.

Oh, and don't forget to run an "sfc /scannow" just for good measure. See "Diagnosing VirtualBox Hardening Issues" for more details.

[Ethancarter]

Thanks !

I update my Nvidia driver to the last version (387.92) and now it works...

Thanks for your advices !!

[socratis]

Great, thanks for the feedback. Marking as [Solved].

[batezip]

Hello,

I have same problem but graphic driver reinstall did not help.
3D support in safe mode installed.
Please can you look to my log?

Thank you
Martin

[scottgus1]

I have same problem

Batezip, if you were running Virtualbox 5.1.28 or .30 on Windows 10 build 16299 and an XP guest you might have the same problem. But you're running 10 build 18362 with Virtualbox 6.0.10 and a Windows 7 guest. And this thread is just shy of two years old. You do not have the same problem.

However, it's good you posted a zipped log!

So education-wise, if you have have the same issue as someone running the exact same version of host OS, guest OS & Virtualbox, then you might be OK adding to an existing thread. But not a thread that's old & resting peacefully, and not if you don't have the exact same software as the original poster.

Please see The Forum Posting Guide. And do please continue posting zipped logs using Upload Attachment when you start your new thread.