Memory could not be written

[kptkill]

Hello,

I'm getting the following Error message when I try to start any VM. If I start the VMs headless, they launch correctly. This problem existed prior to the newest release.

The instruction at 0x060812a0 referenced memory at 0x060812a0. The memory could not be written. Click on OK to terminate the program.

[Perryg]

Code: Select all

00:00:05.310611 OpenGL Info: Render SPU: GL_VENDOR:   Microsoft Corporation
00:00:05.310623 OpenGL Info: Render SPU: GL_RENDERER: GDI Generic

This usually means that you do not have specific drivers for you graphics card installed ( on host ) and that has caused issues. If you turn off 3D acceleration in the guest settings does this still fail.

[kptkill]

I was RDP'd into my laptop when I tried to run that VM. That explains the lack of 3d drivers. Here is an attempt while sitting at my laptop. (with 3d accl disabled).
The hypervisor does run, but always dies about 20 seconds in. even if I start the hypervisor and then pause it immediately.

[Perryg]

The log file does not show any critical error or that the guest had aborted or even shut down. This points to the guest. Seeing that you have snapshots would indicate that the guest had worked at one time. What changed between the time it worked and now?

[kptkill]

one day (admittedly awhile ago) a new version was released and visualization stopped working at all on this host.
I've created a brand new VM, no OS, all defaults and immediately was presented w/ the same error:

(we can ignore the fact there is no bootable OS/Disk/CD etc, it didn't even make it that far.)

I can't seem to find any way to troubleshoot. All of the debugging options I've found require the hypervisor to start.
This started with the new versions of Vbox. If I go back (old enough) the VMs will start working again. I haven't experimented with exactly what version, though I reported the problem back in Nov 2014.
Is there any way to open an official support ticket?

[Perryg]

Try 4.3.12
http://download.virtualbox.org/virtualbox/4.3.12/

You also need to post the VBoxStartup.log
Please read the following link as well viewtopic.php?f=6&t=66071

[kptkill]

Yes, 4.3.12 does appear to be working correctly. Do you need VBoxStartup.log from 4.3.12 or the latest?

things potential significance:
Win7 pro, 64bit
Symantec Endpoint Protection (11.0.6300.803)
Cisco AnyConnect
Cisco VPN adapter
Intel HD Graphics 3000
Nvidia NVS 4200M
Checkpoint VPN

[Perryg]

The startup log would need to come from a non-working version.

[kptkill]

Please find the requested logfile attached.
I've noticed a few supR3HardNtViCallWinVerifyTrust related to some nvidia drivers.

[Perryg]

The new hardened version of VirtualBox requires signed drivers for Windows. You might need to find why they are not signed.

Also see viewtopic.php?f=6&t=66071

[kptkill]

This was an official driver from the nvidia website. I was under the impression that windows would not allow unsigned drivers to be installed without taking "steps" to disable the security checks. The driver does appear to be signed to me:

[Perryg]

In that case you should post a ticket at bugtracker

[kptkill]

Ahh, I do see this...

Whos problem is this? Nvidia's? What is the next course of action here? I'm sure its been already asked... Is there any way to disable the enhanced security in the mean time?

[Perryg]

Only way to get around the security on Windows is to revert to version 4.3.12 but you really should see what nVidia has to say about it and if it is self signed you may need to contact bugtracker

[kptkill]

I've opened Ticket #13882 on this issue. Thank you for taking the time to point me in the correct direction!