Opened 10 years ago
Closed 10 years ago
#14562 closed defect (fixed)
VirtualBox-4.3.30-101610-Win and VirtualBox-5.0.4-102546 doesn't run in Windows 10.0.10240
| Reported by: | Leonardo Lira | Owned by: | |
|---|---|---|---|
| Component: | installer | Version: | VirtualBox 5.0.4 |
| Keywords: | Windows 10, Install, Setup, boot, start | Cc: | lvlira@… |
| Guest type: | Windows | Host type: | Windows |
Description
Notebook ACER Aspire VS-471 serie with i7 processor - 6GB Ram - 500Gb harddisk O.S. Windows 10 build 10240.
After updated of Windows 10, VirtualBox (4.3.30-101610) didn't started. Only shown me a error message 'Failed to load VMMR0.r0'
I downloaded the last version (5.0.4-102546) and a blue screen was shown during the instalation. The Windows was restarted with no virtualbox instaled.
The folder 'C:\Program Files\Oracle\VirtualBox' has all files and I clicked 'VirtualBox.exe' the aplication started but didint boot any virtual machines. The error message 'RTR3InitEx failed with rc=-1912 (rc=-1912)' is shown.
Attachments (3)
Change History (11)
by , 10 years ago
by , 10 years ago
| Attachment: | VBoxStartup.log added |
|---|
After the blue screen, start VirtualBox and force a virtual machine to boot
follow-up: 2 comment:1 by , 10 years ago
VBox 4.3.30 is not expected to work on Windows 10. Though VBox 5.0.4. For helping sorting the BSOD, please go here and scroll down to Creating a kernel dump when a Bluescreen (BSOD) occurred.
comment:2 by , 10 years ago
Hi frank,
I did what you asked and the zip file of memory kernel dump has over 100Mb. Can you give me a link or some FTP server for sending that file?
Replying to frank:
VBox 4.3.30 is not expected to work on Windows 10. Though VBox 5.0.4. For helping sorting the BSOD, please go here and scroll down to Creating a kernel dump when a Bluescreen (BSOD) occurred.
comment:3 by , 10 years ago
Unfortunately not. Could you upload the file to some server and provide me the URL? You can do this also via private email to frank _dot_ mehnert _at_ oracle _dot_ com. Thank you!
comment:4 by , 10 years ago
Looking at the dump it seems that you have the driver verifier enabled. The verifier found a small memory leak. We fixed this leak in our latest Windows test build which you can download here. Can you confirm the fix? Later you might also want to disable the driver verifier, see here. The driver is 'VBoxNetAdp'.
comment:5 by , 10 years ago
Please, disable diver verifier and upgrade the VBox after that. After upgrading you may switch on verifier again. It will allow us to install fixed version.
comment:6 by , 10 years ago
Perfect!!! The installation was a success !
I disabled the driver verifier using the "Verifier" tool of Windows 10, I did the instalation and after a boot I did run the Verifier tools again to put all settings to default value.
The VirtualBox is running fine. Thanks a lot!
First First attempt to start