Using VMSVGA crashes VirtualBoxVM.exe

[Paul A Sand]

Using VirtualBox on a Windows 10 host. Guest is Fedora 31 running Cinnamon UI.

After booting up guest, logging in, things work fine for a few minutes. But eventually, the guest crashes with an alert, title "VirtualBoxVM.exe - Application Error".

Message is: "The instruction at 0x00007FF95B82489D referenced memory at 0x0000000000000010. The memory could not be read. Click on OK to terminate the program."

This is using the suggested VMSVGA Graphics Controller for 3D Acceleration. Backing off to VBoxSVGA causes things to not crash, but I lose 3D.

I have had this problem in the past with previous VirtualBox versions, but it persists in 6.1.0

[sunlover]

Fedora 31 guest with Cinnamon UI works for me.

There is nothing more to say without a VBox.log and a step by step instructions on how to reproduce the crash (no one knows what you do in the guest during these few minutes).

[dnd]

I've had a crash as well, using Fedora 31 and XFCE. I can reasonably reliably trigger it by opening Google Chrome (eg and then Youtube) and then closing the chrome window.

[sunlover]

dnd, thanks for the log. the crash seems to be somewhere in the host graphics driver.

I still could not reproduce it on a Windows 10 host here (AMD graphics card). How often does the crash happen? I.e. how many times do you usually have to start/close Chrome before it crashes?

[Klaus Espenlaub]

Deleting the attachment on dnd's request, who will provide a new attachment.

[Paul A Sand]

VBox.log for crash

[Paul A Sand]

I have attached a recent VBox.log that I think shows a crash. I am only running Gnome Terminal and google-chrome. Unlike dnd, I do not close the google-chrome window, but I do open (maybe) 4-5 tabs.

[dnd]

Windows crash logs

[facboy]

Basically I open Chrome, and close it, and it crashes. It always wants to restore multiple tabs (extensions claiming they are updated) so I'm not sure if it's linked to the tab behaviour. I notice that the extension icons are sometimes corrupted (in the top right).

[wojtasjd]

Thanks for reporting this bug (I've upgraded VB 6.0.14 to 6.1 lately and about the same time increased RAM in machine so I've had suspicion about new RAM).

Host: Windows 7 SP1 x64, nVidia GPU, earlier was installed VB 6.0.14 without this problem.

Now with VB 6.1 - if in VM settings: as graphics controller is VMSVGA with 3D enabled, I'm getting during guest machine restart (Mint 18.3 Cinnamon x64; KDE neon 5.17.4 x64) this error:
"VirtualBoxVM.exe - Application Error.
The instruction at 0xda1dd31c referenced memory at 0x00000000. The memory could not be read. Click on OK to terminate the program."

If I uncheck 3D option then VM is restarting fine, without "VirtualBoxVM.exe" crash.

fragment of Vbox.log:

00:06:34.676485 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000222c!!!
00:06:34.676488 
00:06:34.676488 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=000007feda1dd31c
00:06:34.676494 ExceptionInformation[0]=0000000000000000
00:06:34.676495 ExceptionInformation[1]=0000000000000000

[gazal]

I get the exact same issue. I can reproduce the issue by opening certain chrome tabs; like when using Google Sheets. The screen get all 'block'y and then the VM crashes. Happens with VMSVGA and 3D enabled. I'm running Fedora 31 with Gnome.

I don't know if this has anything to do with it, but my laptop has 2 GPUs; an intel embedded GPU and an nVidia discrete GPU.

[flipkick]

I also have this issue using 6.1 with a Windows host (nVidia GPU) and a Xubuntu 16.04 guest using 3D acceleration with VMSVGA.

For me the easiest way to reproduce it, is by starting two instances of Visual Studio Code in the guest system and moving the window of the second instance around. It won't render its content anyway.

[mkharkov]

rtR3WinUnhandledXcptFilter exception

[mkharkov]

Same error. Host system version: Windows 10 1909, build 18363.628. VirtualBox version: 6.1.2 r135662. VBox OS: Ubuntu 19.10, GNOME. Crashes with:

• 6 and 8 GB of RAM.
• 1, 2, 3 processor cores.
• VMSVGA graphics controller, 128mb of video memory, with 3D acceleration enabled

Logs attached VBoxLogs.zip

[Maff]

I'm having the same issue; Windows 10 Enterprise v1803 (17134.1246), VirtualBox 6.0.12 (r133076), nVidia DGPU, Intel IGPU, guest OS is PCLinuxOS 2020 (Linux 5.4.18-pclos1), configuration:

• Linux, Other Linux (64-bit)
• Bidirectional Clipboard, Drag&Drop
• 3072MB RAM
• Hard Disk, Optical boot order
• PIIX3 chipset
• USB Tablet pointing device
• I/O APIC
• UTC Hardware Clock
• 2 CPUs @ 100%
• PAE/NX enabled
• Default paravirtualisation, VT-x, Nested Paging
• 128MB video memory, 1 monitor, VMSVGA, 3D Acceleration
• IDE controller, PIIX4, I/O cache enabled
• 1x VHD on IDE Primary Master, marked SSD
• DirectSound host audio driver, Intel HD Audio virtualised controller, Audio Output only
• Adapter 1 enabled, NAT, Intel PRO/1000 MT Desktop (82540EM), Deny Promisc, No port forwarding
• USB enabled, EHCI, no filters
• No shared folders

Relevant snippet from VBox.log:

00:18:56.501532 
00:18:56.501534 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000002d98!!!
00:18:56.501563 
00:18:56.501564 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007fff6948081a
00:18:56.501569 ExceptionInformation[0]=0000000000000000
00:18:56.501574 ExceptionInformation[1]=0000000000000010
00:18:56.501579 
00:18:56.501579 cs:rip=0033:00007fff6948081a
00:18:56.501585 ss:rsp=002b:00000000142bf260 rbp=0000000000000000
00:18:56.501589 rax=0000000000000000 rcx=00007fff9fe337f0 rdx=0000000000c00000 rbx=0000000073292b00
00:18:56.501594 rsi=0000000000000000 rdi=00007fff9fe337f0 rsp=00000000142bf260 rbp=0000000000000000
00:18:56.501599 r8 =0000000000703b40 r9 =0000000000008000 r10=0000000000000000 r11=0000000000000246
00:18:56.501604 r12=0000000000000000 r13=0000000001cd3c90 r14=0000000005e1c0d0 r15=00000000142bf660
00:18:56.501609 ds=002b es=002b fs=0053 gs=002b eflags=00010246
00:18:56.501613 p1home=0000000000000000 p2home=0000000000000000 pe3home=0000000073292b00
00:18:56.501618 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
00:18:56.501622    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
00:18:56.501626 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
00:18:56.501632 
00:18:56.501632 Stack 00000000142be170, dumping 0x1e90 bytes (low=00000000141c0000, high=00000000142c0000)

[Nabil Kanzari]

Got same error here (VM 6.1 latest version to date) in Centos 7 guest on a Windows 10 host. The VM got 64Mb video memory, 2 CPU out of 4, 16Gb ram and a 60Gb SSD. When I enable 3D Acceleration, the VM crashes after a couple of minutes. When the 3D acceleration is off, the display lag whenever I switch from window mode to full-screen or the other way around.

[ethomaz]

Same error here and not fixed in the last three 6.1 updates (I tried every but have to back to 6.0 after the crash).

Using Windows 10 host and Windows 7 guest. The same VM on 6.0 works fine that means the issue is 6.1 related.

No option fix the issue even with 3D disabled or another graphic controller.

PS. I need to test the last version 6.1.8.

[giliev]

Attached 2 more logs. Host is Windows 10, guest is Ubuntu 20.04. I was having issues with Ubuntu 19.10 before the upgrade as well.

Seems to be related to VMSVGA driver.

Frequency is about once a day to once a couple of days. I can collect more logs if needed.

[giliev]

Still the same issue with 6.1.10 and the latest Intel graphics drivers.

[ulkesh]

8 months and no movement on this. It occurs on my brand new setup of Ubuntu 20.04 on VirtualBox 6.1.12 r139181 (Windows 10 Host). Easy to reproduce when simply shutting down or rebooting the VM.

[wfouche]

Seeing the same crash rather often, a few times a day. VMSVGA with or without 3D acceleration crashes the guest Linux VM (Linux Mint 20 or Kubuntu 20.04)

[Dmitrii Grigorev]

Hello all. The crash with "rtR3WinUnhandledXcptFilter caught an exception" message was fixed in 6.1.12 r139181, please recheck it. Could you again attach VBox.log if the crash persists on your side.

[Paul A Sand]

Original reporter here. I no longer use VirtualBox, so can't check the fix. Appreciate the effort, though.

[MartySweet]

I can confirm this is still an issue on v6.1.12 r129181 where VMSVGA and 3D acceleration is enabled with Ubuntu 20.04. I can reliably reproduce the issue performing a "Restart" from within a freshly installed Ubuntu guest.

[Bill Peckham]

I see a similar issue on Version 6.1.12 r139181 (Qt5.6.2). In my case, I'm using VBoxVGA (because for my setup it's more functional that VMSVGA). The host is Windows 10. The guest is XUbuntu 20.04 LTS (xfce).

The crash occurs when I undock. While docked, I have two monitors connected. When I undock, the laptop lid is closed.

21:39:33.845526 Audio: Device configuration of driver 'DSoundAudio' has changed
21:39:33.847432 Audio: Device configuration of driver 'DSoundAudio' has changed
21:39:33.847756 Audio: Device configuration of driver 'DSoundAudio' has changed
21:39:33.854752 GUI: UIMachineLogicFullscreen: Host-screen count changed
21:39:33.854787 GUI: UIMultiScreenLayout::update: GUI/AutomountGuestScreens is disabled
21:39:33.854810 GUI: UIMachineLogic: Host-screen count changed
21:39:33.856914 TM: Not bothering to attempt catching up a 314 826 682 962 ns lag; new total: 314 826 682 962
21:39:33.856937 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 316 seconds ago
21:39:33.857083 VMMDev: GuestHeartBeat: Guest is alive (gone 316 065 128 253 ns)
21:39:33.895192 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenResized: Screen 1 is formally resized to: 0x0 x 1920x1080
21:39:33.895227 GUI: UIMachineLogic: Host-screen geometry changed
21:39:33.962612 GUI: UIMachineViewFullscreen::adjustGuestScreenSize: Adjust guest-screen size if necessary.
21:39:33.963319 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: 0x0 x 1920x1080
21:39:33.968347 GUI: UIMachineLogicFullscreen: Host-screen count changed
21:39:33.968380 GUI: UIMultiScreenLayout::update: GUI/AutomountGuestScreens is disabled
21:39:33.968426 GUI: UIMachineLogic: Host-screen count changed
21:39:33.969129 GUI: UIMachineViewFullscreen::adjustGuestScreenSize: Adjust guest-screen size if necessary.
21:39:34.023772 GUI: UIMachineViewFullscreen::adjustGuestScreenSize: Adjust guest-screen size if necessary.
21:39:34.024020 
21:39:34.024020 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000000b60!!!
21:39:34.024030 
21:39:34.024030 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffb827a0594
21:39:34.024036 ExceptionInformation[0]=0000000000000000
21:39:34.024041 ExceptionInformation[1]=0000000e00000000
21:39:34.024119 
21:39:34.024119 cs:rip=0033:00007ffb827a0594
21:39:34.024126 ss:rsp=002b:00000000012fb6b8 rbp=00000000012fb729
21:39:34.024132 rax=0000000006b9c7a0 rcx=0000000007701d40 rdx=0000000e00000000 rbx=0000000000000001
21:39:34.024137 rsi=0000000002741868 rdi=0000000000000001 rsp=00000000012fb6b8 rbp=00000000012fb729
21:39:34.024143 r8 =000000000000000c r9 =0000000007806810 r10=0000000000008000 r11=00000000012fb690
21:39:34.024148 r12=0000000000000001 r13=0000000002741868 r14=0000000000000001 r15=0000000000000001
21:39:34.024153 ds=002b es=002b fs=0053 gs=002b eflags=00010202
21:39:34.024158 p1home=0000000000000000 p2home=000000000000006d pe3home=0000000000000001
21:39:34.024162 p4home=00007ffb96f1f045 p5home=0000000000000030 pe6home=000000000000006d
21:39:34.024167    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
21:39:34.024172 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
21:39:34.024180 

[Aren Cambre]

Same problem here. Windows 10 20H2 host, Ubuntu 20.10 Desktop guest, VirtualBox 6.1.16.

In my case, I can cause this b y simply going through the Ubuntu installation in full. At the end, it instructs you to press enter after removing the installation media. The guest OS crashes, and a dialog comes up with a message like this (cannot guarantee I got every bit correct):

The instruction at 0x00007FFADE30f59C referenced memory at 0x000000000000000.

The VM's configuration is all default except:

• Shared Clipboard and Drag'n'Drop both set to Bidirectional. (May be meaningless. I think this has no effect until VirtualBox Extensions is installed?)
• Base Memory: 8000 MB
• Processor(s): 4
• In Storage, I set the optical drive to use the Ubuntu installation ISO.

I just got a Dell XPS 13 9310. I never had this problem with my prior computer, an HP Elitebook 1040 G4. I wonder if a difference in Windows graphics systems is related to this?

While I didn't change these, I see that the Graphics Controller is VMSVGA, and Enable 3D Acceleration is checked. Those were the default settings.

[Dmitrii Grigorev]

Hello Aren. Thank you for report. Could you attach the VBox.log file (to make further analysis possible).

Replying to Aren Cambre:

Same problem here. Windows 10 20H2 host, Ubuntu 20.10 Desktop guest, VirtualBox 6.1.16.

In my case, I can cause this b y simply going through the Ubuntu installation in full. At the end, it instructs you to press enter after removing the installation media. The guest OS crashes, and a dialog comes up with a message like this (cannot guarantee I got every bit correct):

The instruction at 0x00007FFADE30f59C referenced memory at 0x000000000000000.

The VM's configuration is all default except:

• Shared Clipboard and Drag'n'Drop both set to Bidirectional. (May be meaningless. I think this has no effect until VirtualBox Extensions is installed?)
• Base Memory: 8000 MB
• Processor(s): 4
• In Storage, I set the optical drive to use the Ubuntu installation ISO.

I just got a Dell XPS 13 9310. I never had this problem with my prior computer, an HP Elitebook 1040 G4. I wonder if a difference in Windows graphics systems is related to this?

While I didn't change these, I see that the Graphics Controller is VMSVGA, and Enable 3D Acceleration is checked. Those were the default settings.

[Piotr Dobrogost]

I have the same issue with version 6.1.2 r135662 (Qt5.6.2) What is the current status?

[kfehrenbach]

Same here! Version 6.1.18 r142142 (Qt5.6.2)

Running Windows 10 and a Kubuntu 20.04 Guest! Crash is immediately after startup as the desktop initializes. VBoxLog and VBoxHardening telle me it's in the VMSVGA FIFO and the ExceptionAddress tells me it has no do with the Intel HD Grapshics (igdumdim64.dll)

Therefor i updated the Intel Driver to the latest version but the issues is still the same!

[wojtasjd]

I had https://www.virtualbox.org/ticket/19154#comment:7 problem for a long time but after upgrading VB to ver. 6.1.20 guest crashes (with VMSVGA and 3D option enabled) are gone.

(also - as a test - I've downgraded from ver. 6.1.20 to ver. 6.1.18 and again "VirtualBoxVM.exe - Application Error ...".)

[Paul A Sand]

Replying to wojtasjd:

I had https://www.virtualbox.org/ticket/19154#comment:7 problem for a long time but after upgrading VB to ver. 6.1.20 guest crashes (with VMSVGA and 3D option enabled) are gone.

(also - as a test - I've downgraded from ver. 6.1.20 to ver. 6.1.18 and again "VirtualBoxVM.exe - Application Error ...".)

Original reporter here (17 months ago). I switched over to VMWare Player in late 2019, mostly due to the reported problem. But wojtasjd's note (thanks!) got me to try VBox again.

My current setup is Windows 10 host, Fedora 34 (Beta, almost released) guest, Cinnamon spin. Using 6.1.20.:

Good news: It may not crash anymore.

Bad news: The Cinnamon environment is unusable with VMSVGA/3D Acceleration. No windows appear (total gray screen); task bar shows up with characters replaced with white blocks. It's not a pretty picture. (So I haven't actually used it enough to verify it doesn't crash.)

Good news: turning off 3D acceleration results in a normal-appearing system, stable so far, except...

Bad news: I get that annoying "Check Your Video Drivers" message at login.

I will try to stay with VBox for a while; VMWare has its own problems.

[Klaus Espenlaub]

No immediate idea why it suddenly works for you... there were just some additional sanity checks added between 6.1.18 and 6.1.20. Nothing which is expected to make any difference with a usual VM.

[ethomaz]

I just tested the 6.1.22 and it is fixed. Thanks.

[Paul A Sand]

Replying to ethomaz:

I just tested the 6.1.22 and it is fixed.

Original reporter here. I'm using 6.1.22 and the usability issue (actually: unusability issue) I described in comment 27 above, five weeks ago, still exists.

[Mikhail Kovalev]

We can also reproduce the crash with VirtualBox 6.1.22/6.1.26 on Windows 10 (VMSVGA + 3d acceleration + Debian 9 VM). The crash happens in a few minutes after we start a video conferencing app in the browser (with a webcam enabled). With 3d acceleration disabled there is no crash.

[Dmitrii Grigorev]

Hi MikhaliK. Could you describe steps to reproduce your crash and attach VBox.log here?

Replying to MikhailK:

We can also reproduce the crash with VirtualBox 6.1.22/6.1.26 on Windows 10 (VMSVGA + 3d acceleration + Debian 9 VM). The crash happens in a few minutes after we start a video conferencing app in the browser (with a webcam enabled). With 3d acceleration disabled there is no crash.

[Mikhail Kovalev]

Hi DmitrG,

The steps to reproduce:

1. Start a VM
2. Forward the webcam to the VM (via VBox UI, Devices->Webcams)
3. Open Google Chrome or Chromium browser. We tried various versions, e.g. Chrome 78.0.3904.108, 64-bit and Chromium 90.0.4430.212, 64-bit. The checkbox "Use hardware acceleration when available" needs to be enabled in the browser settings (it is enabled by default).
4. Navigate to zoom.us and login (a free account is enough).
5. Host a meeting with a webcam enabled. The meeting needs to be started in the browser, not in the native linux app. There is no need for others to join the meeting.
6. If it doesn't hang or crash immediately - give it a few minutes to run. And if it doesn't crash now - close the browser. I tried it now on Chromium 90 and the crash only happened after the browser was closed. But usually it crashes or hangs while the browser is running.

I will attach VBox.log from the last crash with Chromium 90. This time it was not a hang, but a crash with the error message "The instruction at .... referenced memory at 0x0000000000000010...".

While trying to reproduce the issue today, I also got a hang by just going to "zoom.us" in chromium 83. The hang has happened when the "Cookies" window was loading: it turned out to be completely corrupted and the VM hang occurred. I will attach VBox.log.1 from this hang as well. The error in the log is VMSVGA related but is different to what I see in case of crash.

Note: in the attached logs Hyper-V is enabled. But this doesn't make a difference and we can reproduce this issues with Hyper-V disabled as well.

Replying to DmitrG:

Hi MikhaliK. Could you describe steps to reproduce your crash and attach VBox.log here?

[Mikhail Kovalev]

VBox.log with a crash when running zoom.us in chrome/chromium

[Mikhail Kovalev]

VBox.log with a hang when navigating to zoom.us in chrome/chromium

[Dmitrii Grigorev]

Hi MikhailK. Thank you for the description.

One can see in your VBox.log that the crash happens on a laptop with Intel GPU. Could you check if it also happens on AMD or NVidia GPU? Host GPU really matters here, that is why I'm asking.

In fact, it will be great to have a separate ticket for your issue.

Replying to MikhailK:

Hi DmitrG,

The steps to reproduce:

1. Start a VM
2. Forward the webcam to the VM (via VBox UI, Devices->Webcams)
3. Open Google Chrome or Chromium browser. We tried various versions, e.g. Chrome 78.0.3904.108, 64-bit and Chromium 90.0.4430.212, 64-bit. The checkbox "Use hardware acceleration when available" needs to be enabled in the browser settings (it is enabled by default).
4. Navigate to zoom.us and login (a free account is enough).
5. Host a meeting with a webcam enabled. The meeting needs to be started in the browser, not in the native linux app. There is no need for others to join the meeting.
6. If it doesn't hang or crash immediately - give it a few minutes to run. And if it doesn't crash now - close the browser. I tried it now on Chromium 90 and the crash only happened after the browser was closed. But usually it crashes or hangs while the browser is running.

I will attach VBox.log from the last crash with Chromium 90. This time it was not a hang, but a crash with the error message "The instruction at .... referenced memory at 0x0000000000000010...".

While trying to reproduce the issue today, I also got a hang by just going to "zoom.us" in chromium 83. The hang has happened when the "Cookies" window was loading: it turned out to be completely corrupted and the VM hang occurred. I will attach VBox.log.1 from this hang as well. The error in the log is VMSVGA related but is different to what I see in case of crash.

Note: in the attached logs Hyper-V is enabled. But this doesn't make a difference and we can reproduce this issues with Hyper-V disabled as well.

Replying to DmitrG:

Hi MikhaliK. Could you describe steps to reproduce your crash and attach VBox.log here?

[Paul A Sand]

Replying to DmitrG:

In fact, it will be great to have a separate ticket for your issue.

As the originator of this ticket, that would be a great idea. I still have issues with 3D acceleration (as described four months back, see above). But the original crashing behavior I described 21 months ago (!) has long been resolved.

[Mikhail Kovalev]

Sure, I will create a new ticket as soon as I get some time to test it again with Nvidia and/or AMD GPU.

Replying to Pun Salad:

Replying to DmitrG:

In fact, it will be great to have a separate ticket for your issue.

As the originator of this ticket, that would be a great idea. I still have issues with 3D acceleration (as described four months back, see above). But the original crashing behavior I described 21 months ago (!) has long been resolved.

[Mikhail Kovalev]

https://www.virtualbox.org/ticket/20528

Replying to MikhailK:

Sure, I will create a new ticket as soon as I get some time to test it again with Nvidia and/or AMD GPU.

[Dmitrii Grigorev]

Hello Pun Salad. Could you check your VM with Cinnamon Desktop using the recent test build as described here https://www.virtualbox.org/ticket/20513#comment:4.

[Paul A Sand]

Replying to DmitrG:

Hello Pun Salad. Could you check your VM with Cinnamon Desktop using the recent test build as described here https://www.virtualbox.org/ticket/20513#comment:4.

Yes! Enabling 3D acceleration under VMSVGA on Cinnamon now works for me. (My guest is not-quite-beta Fedora 35 with a 5.14.0 kernel. As a bonus, the Guest Additions now compile cleanly.

Thanks very much for pointing out the availability of the recent test build.

[tb4jc]

Crash with 6.1.28 after window resizing and starting Chrome

[tb4jc]

Running Mint. Same issue as above in comment 21 after a screen resizing, crash occurred after clicking on Chromium 51:46:01.374563 GUI: UIMachineLogic: Host-screen count changed 51:46:01.385393 GUI: UIMachineLogic: Host-screen count changed 51:46:01.392475 GUI: UIMachineLogic: Host-screen count changed 51:46:01.392525 GUI: UIMachineLogic: Host-screen count changed 51:46:01.392651 GUI: UIMachineLogic: Host-screen count changed 51:46:02.850354 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 0x0 x 1920x1170 51:46:02.850383 GUI: UIMachineLogic: Host-screen available-area changed 51:46:02.853035 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: 1920x0 x 1920x1050 51:46:02.853066 GUI: UIMachineLogic: Host-screen available-area changed 52:38:05.963748 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 1920x1105 if necessary 52:38:08.972902 VMMDev: SetVideoModeHint: Got a video mode hint (1920x1105x32)@(0x0),(1;0) at 0 52:38:08.974513 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=1920 h=985 bpp=0 cbLine=0x0 flags=0x2 origin=0,0 52:38:08.980323 GUI: UIMediumEnumerator: Medium-enumeration finished! 52:38:08.997712 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000010f20000 w=1920 h=1105 bpp=32 cbLine=0x1E00 flags=0x1 origin=0,0 52:38:09.005232 GUI: UIMachineLogic: Guest-screen count changed 52:38:11.469218 52:38:11.469220 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000832c!!! 52:38:11.469236 52:38:11.469236 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffee88e2dd2 52:38:11.469243 ExceptionInformation[0]=0000000000000000 52:38:11.469250 ExceptionInformation[1]=0000000000000000 52:38:11.469256

[vipiish]

Similar problem on Windows 7 64-bit host with FreeBSD guest (VirtualBox version 6.1.30). Tried both FreeBSD 12.2 and FreeBSD 13.0. It crashes with the same exact message for both OS versions (yes, same addresses even).

"The instruction at 0xdd3ace16 referenced memory at 0x00000000. The memory could not be read. Click on OK to terminate the program."

I've tried disabling as many features/optimizations as I possibly can (even disabled hardware such as network adapters, USB support, etc.) and just let the machine sit there idling for some hours after a clean install of the guest, while doing some very casual web-browsing on the host machine. It's a randomly occurring bug, at least in my case it seems.. And it doesn't appear to be an out-of-memory issue. Sometimes it takes a couple of hours before it crashes, other times it can take more than a day (24h+).

For the record, the host machine has 32 GB RAM, but it rarely ever exceeds 20 GB in use, and I allocate 2 GB RAM for FreeBSD.