Page 1 of 1
Reference Memory Could Not Be Written (#17526)
Posted: 5. Feb 2018, 18:05
by kpenrose
[ModEdit; related ticket: #17526: Memory exception]
Running an Ubuntu guest on a Windows 10 host, with VB 5.2.6, GAs 5.2.7. Everything will run fine for a while, and then suddenly an Application Error dialog will appear that states "The instruction at 0x00007FF8CD00E6C referenced memory at 0x0000000000000040. The memory could not be written. Click OK to terminate the program."
This happens repeatedly, so using the virtual machine is impossible.
I have added this bug to the bug tracker at Oracle, but I don't expect that it will get any immediate attention. Is anyone else experiencing the same problem?
Re: Reference Memory Could Not Be Written
Posted: 5. Feb 2018, 18:14
by socratis
kpenrose wrote:I have added this bug to the bug tracker at Oracle
Reference please.
Any antivirus running? Anything 3rd party installed that might interfere with the system?
Re: Reference Memory Could Not Be Written
Posted: 5. Feb 2018, 18:23
by kpenrose
The ticket in the bug tracker is
https://www.virtualbox.org/ticket/17526.
The Windows host is very stock, running windows defender security and outlook is about all I run. Perhaps a couple of explorer windows.
Re: Reference Memory Could Not Be Written (#17526)
Posted: 5. Feb 2018, 18:35
by socratis
OK, thanks for that. Two things: 1) what if you disable 3D acceleration, 2) ZIP and attach a copy of the VBoxHardening.log before you do change that setting, and one after.
Re: Reference Memory Could Not Be Written (#17526)
Posted: 5. Feb 2018, 18:51
by kpenrose
Okay - I'll probably have to do this in two different messages, since I'm not sure when I'll see the error again (but I know it will be soon).
Attached here is the hardening log prior to changing the 3D setting (but after an error was logged).
Re: Reference Memory Could Not Be Written (#17526)
Posted: 6. Feb 2018, 17:33
by kpenrose
Update:
Even though I am running the 5.2.27 GAs, which is supposed to have 3D acceleration fixes in place, I have not had this error occur when I run the guest system with 3D acceleration turned off.