Opened 5 years ago
Last modified 4 years ago
#19243 new defect
VMSVGA 3d get Crash while guest try to reboot
Reported by: | Aridu68 | Owned by: | |
---|---|---|---|
Component: | 3D support | Version: | VirtualBox 6.1.2 |
Keywords: | VMSVGA | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description
Graphic Controller VMSVGA get Problem while 3d Acceleration Enabled. Error Message show while Guest do reboot procedure.
Attachments (3)
Change History (6)
by , 5 years ago
Attachment: | VBox.log.2 added |
---|
by , 5 years ago
comment:1 by , 5 years ago
In hardening log showing nvd3dumx.dll has (CERT_E_CHAINING) error while WinVerifyTrust then failed loading the link library.
this
... 24f0.26a4: supR3HardNtViCallWinVerifyTrust: WinVerifyTrust failed with 0x800b010a (CERT_E_CHAINING) on '\Device\HarddiskVolume2\Windows\System32\nvd3dumx.dll' .... 24f0.26a4: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\nvd3dumx.dll': rcNt=0xc0000190 ...
and other dump show dump of the VMSVGA3d.
... 00:00:21.140533 VMSVGA3d: cap[0]=0x00000001 {3D} 00:00:21.140533 VMSVGA3d: cap[1]=0x00000000 {MAX_LIGHTS} 00:00:21.140533 VMSVGA3d: cap[2]=0x00000000 {MAX_TEXTURES} 00:00:21.140533 VMSVGA3d: cap[3]=0x00000000 {MAX_CLIP_PLANES} 00:00:21.140533 VMSVGA: Unsupported vertex shader version 0 00:00:21.140533 VMSVGA3d: cap[4]=0x00000000 {VERTEX_SHADER_VERSION} 00:00:21.140533 VMSVGA3d: cap[5]=0x00000001 {VERTEX_SHADER} 00:00:21.140533 VMSVGA: Unsupported pixel shader version 0 .... 00:00:21.140533 00:00:21.140533 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 00000000000026a4!!! 00:00:21.140533 00:00:21.140533 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ff8edf6ed1c ...
comment:3 by , 4 years ago
Not sure if this is the same problem I'm having but I am running Linux Mint with the latest 6.1.18 guest additions installed and I'm experiencing a crash on most reboots.
It seems to mainly happen with VMSVGA enabled VMs running with the EFI BIOS option on VirtualBox. It's super annoying as it happens so frequently!
I am includeing Hardening log in archive.