I am running Ubuntu 18.04.4 LTS 64-bit through VirtualBox on a Windows 10 host machine. I am running into an issue where randomly while using the VM an error throws up like the one below and the VM terminates.
"The instruction at 0x00007FFD26A0E812 referenced memory at 0x0000000000000000. The memory could not be written. Click OK to terminate the program."
Any help with this issue would be greatly appreciated. I have attached a VBox.log file and host systeminfo.
Memory could not be written error
Memory could not be written error
- Attachments
-
- systeminfo.txt
- Host system info
- (3.86 KiB) Downloaded 48 times
-
- VBox.zip
- Vbox log
- (31.05 KiB) Downloaded 38 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Memory could not be written error
Try turning off audio, and if that doesn't make a difference then try turning off 3D acceleration. These are tests, not long term suggestions.
Also, it would be nice to see the VBoxHardening.log, since it looks like a hardening error: it's either a driver being blocked by hardening, or you have a buggy host driver - and it looks audio related.
Also, it would be nice to see the VBoxHardening.log, since it looks like a hardening error: it's either a driver being blocked by hardening, or you have a buggy host driver - and it looks audio related.
Re: Memory could not be written error
Thank you for your swift reply.
I turned on the VM and replicated the error in about 10 minutes. This time it occured when attempting to shut the guest system down and it was a read error. I attached the regular log from this session and the hardening log as well.
I will try turning the audio and then 3D acceleration off and see if this helps.
I turned on the VM and replicated the error in about 10 minutes. This time it occured when attempting to shut the guest system down and it was a read error. I attached the regular log from this session and the hardening log as well.
I will try turning the audio and then 3D acceleration off and see if this helps.
- Attachments
-
- VBoxHardeningLog.zip
- Hardening log from another occurence of error
- (29.14 KiB) Downloaded 59 times
-
- VBoxLog2.zip
- Vbox.log from another occurence of error
- (36.48 KiB) Downloaded 18 times
-
- Volunteer
- Posts: 5678
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Memory could not be written error
Both crashes happen inside the Intel HD Graphics driver (igdumdim64.dll).