Ajuda por favor Error a memória não pode ser written

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Chapolim
Posts: 3
Joined: 12. Apr 2020, 04:41

Ajuda por favor Error a memória não pode ser written

Post by Chapolim »

Estou tendo frequentemente esse erro na minha máquina virtual box.
Tenho o Windows 10 como maquina principal
E uso o linux mint na máquina virtual
Quando estou com minha máquina virtual box linux mint em execução aparece a msg da foto e dps fecha o programa e a maquina fica como abortada, quando vou salvar o estado da máquina também ocorre o mesmo erro dps de carregar.
Attachments
Error
Error
errrrrto.jpg (117.82 KiB) Viewed 4996 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Ajuda por favor Error a memória não pode ser written

Post by mpack »

That will be a hardening error. Read the FAQ: FAQ: Diagnosing VirtualBox Hardening Issues.

NVidia have a habit of forgetting to digitally sign some DLLs in their file set. You might want to look at that.

If you want to continue the discussion then I'll need a ZIPPED VBoxHardening.log from the VM folder, attached here. You can confirm it's the problem if disabling 3D acceleration in the guest stops the error from happening.

p.s. You Windows host has a lovely little app called "Snipping Tool" which is excellent for taking screenshots of much better quality than you can manage with a JPEG photograph. Search for it in the start menu.
Chapolim
Posts: 3
Joined: 12. Apr 2020, 04:41

Re: Ajuda por favor Error a memória não pode ser written

Post by Chapolim »

Sim desativei a aceleração 3D e sim o pobrema foi resolvido, ja fiz sfc scannow no Windows e nao resolveu
Reinstalei o virtualbox porém ainda continua o erro.

Aqui deixarei a pasta de log
Attachments
VIRTUAL BOX LOGGSS Logs.zip
(159.78 KiB) Downloaded 75 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Ajuda por favor Error a memória não pode ser written

Post by mpack »

You should read the hardening FAQ again, because you still have Kaspersky antivirus installed. Windows 10 does not need help from third party AV products, and multiple suits of armour does not make a warrior extra safe, it just makes him slow and easily toppled.

The only relevant log here is the VBoxHardening.log. Around 80 lines down you'll see a line :
3f44.ff8: supR3HardenedWinFindAdversaries: 0x840
The hexadecimal number after the colon ':' is the number of third party AV modules found. That number should ideally be 0x000.
fth0
Volunteer
Posts: 5690
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Ajuda por favor Error a memória não pode ser written

Post by fth0 »

mpack wrote:The hexadecimal number after the colon ':' is the number of third party AV modules found.
More specifically, it's the number of bits in the hexadecimal number that corresponds to the number of AV products found. In this case, the two set bits indicate Kaspersky and COMODO.
Chapolim
Posts: 3
Joined: 12. Apr 2020, 04:41

Re: Ajuda por favor Error a memória não pode ser written

Post by Chapolim »

Sim uso COMODO e Kaspersky.
Nao gostaria de desistalar,
Será que existe outra forma de corrigir o erro
Eu uso outras maquinas virtual e nao dao nenhum erro somente essa que uso com o linux mint.
Esse erro comecou recentemente antes nao acontecia.
Desde ja muito obrigado por responderem.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Ajuda por favor Error a memória não pode ser written

Post by mpack »

I do wonder why you think that Windows in 2020 still needs the kind of help it needed in 1998, as if Microsoft are somehow capable of writing the rest of a complex OS, but not capable of making it secure without help - from people with no access to OS source code.

Still, that's your choice.

However. Even if only for temporary test purposes, you do need to disable all third party AV. That will at least establish that your problem is with the AV. And since you have two third party AV packages installed, you should ideally pinpoint which one (if not both) conflicts with VirtualBox.

After identifying the culprit then it's up to you what you do about it. E.g. configure it to allow VirtualBox as an exception, update it or delete it, or uninstall VirtualBox and choose something else.
Post Reply