Note that, as in the previous (4.3.14, 4.3.16) discussions, the purpose of this topic is to gather diagnostic data needed to solve the hardening issues, and nothing else. Wibble posts, opinion posts, and posts that don't include necessary diagnostics will most likely be deleted. If a test build is created then you'll be expected to have tried it before you post.

Please be explicit about errors. Don't say "same as xxxxx". See list above for what's required.

Latest version crashes when Qt Creator is launched with 3D accel on: "The instruction at 0xc562dc72 referenced memory at 0x00001680. The memory could not be read." I have a screenshot, but anti-spam protection does not let me post it.

This crash can be reliably reproduced. The second time it happened, VirtualBox corrupted part of my disk image. It doesn't happen if 3D acceleration is disabled, or with 4.3.16 on the exact same setup.

For the moment I'm downgrading VirtualBox to 4.3.12, which was the last version that wasn't laden with crashes. These crashes have already caused me data loss on two occasions. I appreciate the sentiment of trying to protect users from malicious software, but a hypervisor that crashes most of the time is all but useless.

Hello everbody I have tested the new 4.3.18 Build and I have the same problems with installing the new Windows 10 Preview. The Logs are in the Attachment.I hope there will be a fix soon. Thank you for you work.

@Doom Mortal, please be explicit about errors. I have no idea what you might mean by "same problems", though I suspect you have a problem with Windows 10, and not a problem related to hardening issues which is the sole reason for this discussion topic.

This problem has remained unchanged through all the 4.3.16 test builds. Although my test system remains basically the same (Win7 64-bit host w/ a FreeBSD 10-derived guest), I have taken the step of completely uninstalling my anti-virus software in an effort to further simplify the problem. One area in which I could use some advice is how to obtain better (i.e. more detailed?) debugging info while the guest is running. I have submitted the normal VBox logs (see posts referenced above) but they seem to basically end once the guest has booted up. Whether that is technically correct or not, I have never seen anything committed to those logs at the time the problem manifests itself on the guest (i.e. my USB NIC disconnects...). If anyone can advise me on how to collect more informative logs, I would be more than happy to provide them to aide the troubleshooting.

As it is now, I run this guest "day-to-day" under 4.3.12 with no problems. Because of the effort required to install VirtualBox test builds for troubleshooting and then rolling back to 4.3.12 in order to restore normal operations, I usually won't spend time on this during the week unless there is pretty compelling evidence that a fix might have been implemented. As always though, any effort from the VB devs or broader community is greatly appreciated in helping me to resolve this.

mpack wrote:@Doom Mortal, please be explicit about errors. I have no idea what you might mean by "same problems", though I suspect you have a problem with Windows 10, and not a problem related to hardening issues which is the sole reason for this discussion topic.

@mpackIm sorry I thought that my information that I provided weren´t enough to solve this problem.I have a problem in installing Windows 10. It apears the Loading-Screen of WIndows 10 and after a few seconds there will apear an error screen.The message of the error screen is in the .zip data as a picture file.

Before this thread started it only was said that it is a continuation of the old thread where i encountered the same descussion with Windows 10.Im sorry for that misunderstanding.

mpack wrote:@Doom Mortal, please be explicit about errors. I have no idea what you might mean by "same problems", though I suspect you have a problem with Windows 10, and not a problem related to hardening issues which is the sole reason for this discussion topic.

@mpackIm sorry I thought that my information that I provided weren´t enough to solve this problem.I have a problem in installing Windows 10. It apears the Loading-Screen of WIndows 10 and after a few seconds there will apear an error screen.The message of the error screen is in the .zip data as a picture file.

Before this thread started it only was said that it is a continuation of the old thread where i encountered the same descussion with Windows 10.Im sorry for that misunderstanding.

But the missing NX is going to stop the Win-10 guest from working IMHO and why you are getting the guru mediation message.Make sure that your bios has this feature and that it is enabled in your hosts bios.

other version which got the same error:VirtualBox-4.3.17-96342-Win.exeVirtualBox-4.3.17-96101-Win.exeVirtualBox-4.3.16-95972-Win.exeVirtualBox-4.3.14-95030-Win.exe

My host computer runs:Windows 7 ultimate sp1 64bits

Anti-virus Software:Microsoft Security Essentials

Turn on an existing VM show error:The virtual machine 'Funtoo' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'VBoxStartup.log'.code: E_FAIL (0x80004005)MachineIMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

I posted that VirtualBox-4.3.17-96342-Win.exe DOES work correctly in this environment.

I've now discovered the several test builds of 4.3.17 that occured AFTER 4.3.17.96342 (over at the Windows 4.3.16 specifically for errors due to security) thread.

Results are as follows:

Most/All builds of 4.3.17 after 96342 (I'ved tried 96426, 96468, 96495) cause the VM process to hang at startup and eventually timeout on the system with Symantec Endpoint Protection: Version 12.1.5 (12.1 RU5) build 5337 (12.1.5337.5000) as follows:

1) Select a virtual machine e.g. XP SP3 VM.2) Start it.3) There's a long pause (20-30 secs approx) before the Starting VM "Creating process for virtual machine ..... (GUI/Qt)" message appears.4) This message stays up, but stuck with progress bar at 0%, which doesn't progress.5) Then eventually a message is seen: "VirtualBox - Error in supR3HardNtChildWaitFor".Timed out after 60009 ms waiting for child request #1 (CloseEvents). (rc=258).with an Abort button.6) On clicking Abort, a Virtual Box error is shown:Failed to open a session for the virtual machine WS_XP.

The virtual machine 'WS_XP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\MDiack\VirtualBox VMs\WS_XP\Logs\VBoxStartup.log'.