Hello
I've created a new Ubuntu 64bit VM to run on my Windows 7 host. When I start it, I pointed it to the Ubuntu ISO and click Next. It then indicates that it is starting and a few seconds later it fails with the following error:
"The instruction at 0x0f675b60 referenced memory at 0x0f675b60. The memory could not be written. Click on OK to terminate the program."
Here are the details of my environment:
1. Using VirtualBox 5.0.6 r103037. I have installed the Guest Additions.
2. Host is Windows 7 Enterprise SP1 - 64-bit with 8Gb RAM running on Lenovo Thinkpad (graphics card is Intel HD Graphics Family)
3. Guest is ubuntu-14.04.3-desktop-amd64 - I've provided it with 4Gb RAM.
3. VBox.log attached.
My colleague is experiencing the exact same behavior on his laptop (exact same model as mine). He has indicated that it he did not experience any problems in the past and that it just stopped to work one day. Even his working VMs from the past does not launch anymore. We are thinking that it must be IT update rollouts which are causing the problems, but can't pinpoint it to something specific. His thoughts are that it might be anti-virus related (we are now using McAfee v4.8.0.1923 and there is also something called Avecto Defendpoint running in the background).
Any help would be much appreciated.
Thanks,
Jaco
The instruction at 0x0f675b60 referenced memory at 0x0f675b6
The instruction at 0x0f675b60 referenced memory at 0x0f675b6
- Attachments
-
VBox.log- (65.2 KiB) Downloaded 7 times
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: The instruction at 0x0f675b60 referenced memory at 0x0f6
Can you please ZIP and attach the file "VBoxHardening.log" located in the same folder as your "VBox.log"?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: The instruction at 0x0f675b60 referenced memory at 0x0f6
Thanks for the response.
Requested file attached.
Requested file attached.
- Attachments
-
- VBoxHardening.zip
- (26.83 KiB) Downloaded 9 times
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: The instruction at 0x0f675b60 referenced memory at 0x0f6
You have a lot of messages about "lacks WinVerifyTrust". I would suggest that you run "sfc /scannow" from an elevated privileged command prompt. A second step would be to search for "lacks WinVerifyTrust site:forums.virtualbox.org" to see what other have been dealing with...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: The instruction at 0x0f675b60 referenced memory at 0x0f6
Hi Scoratis
It seems there are conflicts between the VirtualBox Hardened Security and either McAfee or Avecto Defendpoint as we have been reading in the following forum thread:
viewtopic.php?f=6&t=67840&start=165
We have rolled back VirtualBox to version 4.3.12 which is apparently the last version without the hardening feature.
The only issue we found was that USB 3.0 XHCI support is not available in 4.3.12, so we needed to hand modify the *.vbox file, removing the <Controllers> section below:
<USB>
<Controllers>
<Controller name="xHCI" type="XHCI"/>
</Controllers>
<DeviceFilters/>
</USB>
With this change both the Ubuntu 14.04 and CentOS7 images work OK.
It seems there are conflicts between the VirtualBox Hardened Security and either McAfee or Avecto Defendpoint as we have been reading in the following forum thread:
viewtopic.php?f=6&t=67840&start=165
We have rolled back VirtualBox to version 4.3.12 which is apparently the last version without the hardening feature.
The only issue we found was that USB 3.0 XHCI support is not available in 4.3.12, so we needed to hand modify the *.vbox file, removing the <Controllers> section below:
<USB>
<Controllers>
<Controller name="xHCI" type="XHCI"/>
</Controllers>
<DeviceFilters/>
</USB>
With this change both the Ubuntu 14.04 and CentOS7 images work OK.