Page 1 of 1

The instruction at 0x00007FFF5C839B2C referenced memory at 0x00007FFF5C839B2C. The memory could not

Posted: 14. Apr 2021, 04:32
by TheCoolHackerBoio
Version 6.1.18 r142142 (Qt5.6.2)
64 bit.

VirtualBoxVM.exe : The instruction at 0x00007FFF5C839B2C referenced memory at 0x00007FFF5C839B2C. The memory could not be written.

Click on OK to terminate the program
Click on CANCEL to debug the program

These events happen when I simply power off a vm by closing the vm window top right & then selecting "power off the vm" in the vb menu that pops up

LMK if you need other logs or a dump. Please provide a link to appropriate guide for obtaining such additional files.

I looked at previous posts that have similar error message, but each solution seems unique or I didn't recognize the relevance for my problem, therefore, I am starting this new topic.

Many thanks for your help.
Logs.zip
(98.83 KiB) Downloaded 42 times

Re: The instruction at 0x00007FFF5C839B2C referenced memory at 0x00007FFF5C839B2C. The memory could

Posted: 14. Apr 2021, 14:52
by scottgus1
Logs starting the VM from full shutdown provide better diagnostics than a log from a saved-state VM.

Your host is showing a hardening problem, ExitCode=0xc0000005. See Diagnosing VirtualBox Hardening Issues.

Your host also has extra 3rd-party antivirus & firewall (Mcaffee) installed. Try uninstalling that as a test.

Re: The instruction at 0x00007FFF5C839B2C referenced memory at 0x00007FFF5C839B2C. The memory could

Posted: 14. Apr 2021, 15:34
by TheCoolHackerBoio
scottgus1 wrote:Your host also has extra 3rd-party antivirus & firewall (Mcaffee) installed. Try uninstalling that as a test.
I tried uninstalling my antivirus and the error was fixed.

Thanks a lot, scottgus1.

I was wondering if there is a way for me to fix the error without having to uninstall my antivirus?

Re: The instruction at 0x00007FFF5C839B2C referenced memory at 0x00007FFF5C839B2C. The memory could

Posted: 14. Apr 2021, 17:31
by scottgus1
You might be able to set scanning exceptions in the 3rd-party AV to not touch anything related to Virtualbox or the VM files.

Alternatively, roll with Windows 10's native AV & firewall. It works well and doesn't mess with Virtualbox.

Re: The instruction at 0x00007FFF5C839B2C referenced memory at 0x00007FFF5C839B2C. The memory could

Posted: 14. Apr 2021, 17:38
by TheCoolHackerBoio
scottgus1 wrote:You might be able to set scanning exceptions in the 3rd-party AV to not touch anything related to Virtualbox or the VM files.

Alternatively, roll with Windows 10's native AV & firewall. It works well and doesn't mess with Virtualbox.
Okay, thanks a lot, scottgus1.