Dear all!
After update to VB 6.1.10 r138449 I started to encounter "The memory could not be written" error. Last time it happened during VM restart (reboot).
Host: Windows 10 Enterprise
Guest: Ubuntu 16.04.1
VirualBox: 6.1.10 r138449
VirtualVoxVM.exe - Application Error. The memory could not be written
-
gamebox.arty
- Posts: 3
- Joined: 21. May 2020, 14:19
VirtualVoxVM.exe - Application Error. The memory could not be written
- Attachments
-
- Ubuntu 16.04 LTS-2020-06-14-16-48-46.log.zip
- VM log
- (33.3 KiB) Downloaded 5 times
-
- Error dialog
- image_2020-06-14_16-50-29.png (13.43 KiB) Viewed 806 times
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: VirtualVoxVM.exe - Application Error. The memory could not be written
Looks like this guest ran for 30 hours, with a host sleep/hibernate at 21 hours, and finally crashed on a sound problem:
Does this happen all the time?21:26:49.580438 Pausing VM execution, reason 'host suspend'
.....
24:40:23.139287 Resuming VM execution, reason 'host resume'
.....
30:21:40.785352 Changing the VM state from 'RUNNING' to 'RESETTING'
.....
30:21:52.376021 Audio: Disabling input for driver 'DSoundAudio'
30:21:52.380695 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000553c!!!
30:21:52.382783 Xcpt PC : 00007ffe6f4c8201 - 0x00028201 bytes into C:\WINDOWS\System32\dsound.dll
-
gamebox.arty
- Posts: 3
- Joined: 21. May 2020, 14:19
Re: VirtualVoxVM.exe - Application Error. The memory could not be written
I believe it might have something to do with sleep / hibernate of the host. It happened 4-5 times during the past week. Not able to reproduce it on purpose. I will try to disable audio in guest settings to see if problem persists.