Guru meditation at start - rc=VERR_PGM_INVALID_GC_PHYSICAL_ADDRESS GCAddr

[hocho]

I have used Virtulbox for years and recently recieved an unknow error where any off my VMs goes straight to Guru meditation mode. This appears when trying to boot any OS. I dont know if this have to do anything with any of the Windows Guards but I have tried disabling them but does not seem to work.

I have also tried Enable/disable PAE/NX, different accelarators, enabling hyper-v, running as Admin etc but still get the same error

Massive and multiple log files are generated in vbox.log with the following message:
00:00:18.790945 0000 - read error rc=VERR_PGM_INVALID_GC_PHYSICAL_ADDRESS GCAddr=f000eef3f000eef3.

Attached parts of the vbox.log since its repeats above and haredninglog.

Anyone have any idea what the issue is?

[scottgus1]

Your hardening log has an exit code of 1. See Diagnosing VirtualBox Hardening Issues. Per the recommended solution in the tutorial, look through your host PC for any extra antivirus, nanny-style 'web-safe-security' software, Trusteer Rapport, HP ProtrectTools, etc., which often cause trouble.

Also re-install Virtualbox using right-click-Run-As-Administrator, even if you already are an admin.

enabling hyper-v,

At the moment, Hyper-V is disabled. Don't enable it, it will cause more trouble.

[hocho]

Thanks for the adivce.
I tried:
sfc /scannow
DISM.exe /Online /Cleanup-image /Restorehealth - didnt find any critical errors in the CSB log
Updated Windows to the latest patch
Followed the Hardening issues guide but still the same issue
Enable intel vt in bios
Removed the drivers from device manager after installation and installed VB again

When VB goes into Guru mode it loops writing "00:00:11.322772 f8c574 - read error rc=VERR_PGM_INVALID_GC_PHYSICAL_ADDRESS GCAddr=f000ff53f0f9c3de" to the VBox.log file and easily get 1gb+ if I dont kill the process.

I am out of ideas, could it be Windows10 restricting virtualization and there is no solution?

[scottgus1]

Followed the Hardening issues guide

What exactly did you do, besides the things reported so far?


Did you hunt for anything like these:

extra antivirus, nanny-style 'web-safe-security' software, Trusteer Rapport, HP ProtectTools, etc.,

installed VB again

using right-click-Run-As-Administrator?

could it be Windows10 restricting virtualization and there is no solution?

I have two Windows 10 hosts, Pro & Home, and I run Virtualbox any day of the week. Windows 10 itself with Windows 10's built-in AV and Hyper-V disabled does not block Virtualbox.