Win10 VirtualBox Guest seems like sudden disk corruption, but restored .ova does too

[NginUS]

I've originally posted for help in the Linux Mint forums, but was referred here from there.

I'm on Linux Mint 18.3 with VirtualBox 5.1.38_Ubuntu r122592.

This is the second time I've seen this occur. The Windows VM starts randomly jumbling & omitting text from everything, just borking the whole desktop in general. It looks like disk corruption, so I restored from an exported .ova I had created before the problem began.

But the restored VM continues to have the same problem. I've tried changing the VMs disk location on the host from my SSD where it originally resided, to a spindle drive. Also tried changing the VM's disk imported from the .ova using a .vdi or a .vmdk, but no help.

Last time this happened I had to reinstall the whole Win10 from scratch. But that takes forever, so I'd sure like to fix what's wrong & move forward from there.

In case it matters the last time I saw this happen was after changing the VM from 2 to 1 CPU thread- changing back didn't help. This time it happened after I opened several high-load apps all at once.

Screenshot of the mess: https://files.catbox.moe/7byhej.png

Thanks in advance.

EDIT:

Corruption.jpg (127.01 KiB) Viewed 618 times

[socratis]

Please attach the image locally in your response (see the "Upload attachment" tab below the reply form). Not a lot of people will go to 3rd party sites. Plus, it's more convenient if the image goes along with the message...

Edit: I see you took care of that part, while I was replying...

I restored from an exported .ova I had created before the problem began. But the restored VM continues to have the same problem.

Which means that the problem might have been there before you did the export, it may have simply not manifested itself.

Why do you think that this is VirtualBox related? What's your evidence for that? Just because an OS/program that runs in the context of VirtualBox has a problem, it doesn't make it a VirtualBox problem necessarily. You're having an issue that has most probably nothing to do with VirtualBox, so my suggestion would be to treat it as such, as a native problem with the OS or the application of the guest.

If you strongly believe that to be a VirtualBox problem, we need to see a complete VBox.log, from a complete VM run, where the problem actually occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.