virtualbox.org

I have windows 7 Ultimate x64 installed on my ASUS F2A85-M PRO as the host operating system and I keep on getting this error with several guests installed.

Windows Server 2019 Standard x64 ,Windows 10 x64 and windows 7 Ultimate x64

Instruction at 0x000000 referenced memory the memory could not be written
at random times with all of the guest system and I cant figure out why.

Please right-click the guest in the main Virtualbox window's guest list, choose Show Log.

Search the far left tab's log for this text:

Attempting fall back to NEM

If you find it, Hyper-V is enabled and needs to be disabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active). (The new test builds might have a fix for this problem. If you try a test build and it works, report here: viewtopic.php?f=6&t=90853, and save the installer file.)

If you don't find that text, save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.

[quote="scottgus1"]Please right-click the guest in the main Virtualbox window's guest list, choose Show Log.

Okay I will try to get all of that done tomorrow afternoon is my bedtime here now.

I have looked through the logs for the issues indicated but I have seen nothing here is the log >> Win 7 Multibrand X64-2020-09-29-15-40-41.zip.

You're using a software called Actual Multiple Monitors, which is rejected by the VirtualBox hardening code. For a test, uninstall that software and see if the issue persists.

fth0 wrote:You're using a software called Actual Multiple Monitors, which is rejected by the VirtualBox hardening code. For a test, uninstall that software and see if the issue persists.

Okay I see that I will give it a try here in a while., thanks for the info I didn't know that

I did as suggested and uninstalled actual multiple monitors and restarted my computer and installed the newest test build >> 6.1.15.140592 and it is still doing the error.I am not sure where to look now here are the logs and image.

Any help and ideas would be appreciated.

Win 7 Multibrand X64-2020-10-02-18-24-41.log wrote:

00:10:27.673594 Potential code addresses on the stack:
00:10:27.673599 00000000002a97e8: 000000006c33494d - 0x000c494d bytes into C:\Program Files\Oracle\VirtualBox\Qt5WidgetsVBox.dll
00:10:27.673609 00000000002a9818: 000007fee0c90349 - 0x00160349 bytes into C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll
00:10:27.673633 00000000002a9828: 0000000074378d17 - 0x00068d17 bytes into C:\Program Files\Oracle\VirtualBox\MSVCR100.dll

Win 7 Multibrand X64-2020-10-02-18-24-41.log wrote:

00:00:02.139653 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume6\Windows\System32\uxtheme.dll
00:00:02.139848 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\UxTheme.dll': rcNt=0xc0000190

Well, the crash happens somewhere in the VirtualBox code where the graphical elements of the VM's window are handled (QT5). This also matches your new screenshot, where you've just opened the USB status icon menu. Additionally, the Windows UxTheme.dll is still patched, which I attributed to the Actual Multiple Monitors software. The latter is just an educated guess and could be wrong of course. It could also be a malware responsible for that. Please post a zipped VBoxHardening.log file.

I did notice this too when I go to open the USB status icon menu it crashes every time without fail I do believe, on all V.M.'s too.

here is the VBoxHardening.log file >> Hardening Log_Win Server 2012 R2-2020-10-04-01-20-49.zip

In the VirtualBox Hardening log file, the patched Windows DLL UxTheme.dll is rejected three times, and immediately after the third rejection the crash takes place. So my first suggestion should be obvious: Replace the UxTheme.dll by the original version.

Additionally, you could try if uninstalling Malwarebytes Anti-Malware makes a difference.

After researching all possible options I reinstalled Windows 7 ultimate and everything works fine now all Virtual machines operate as expected.Thanks to everyone for all their help on this one it was very much appreciated.

Great! Glad you're up and running.