virtualbox.org

Hi.

I have just updated to Windows 10 and VirtualBox 5.0.0 (on July, 29th 2015).

When I start VirtualBox, most of the time everything is okay.
But sometimes, let's say every third of fourth time, I need to start VirtualBox exactly three times before it starts.
When this is the case, I get the same following three error messages everytime in the exact same order.

I think these problems were already there when working with Windows 8 and VirtualBox 4.3.6.
But since I use VirtualBox on Windows 10 much more often (to start my good old Office 2000) it bothers me a lot more than before.

I have no Antivirus software installed except for the one that came with Windows 10. I left almost everything in Windows 10 at the default settings.

I have attached the last three error logs from the VM-Folder and screenshots of the error messages.

Can anyone help me with this issue?

Greetings,
ManicSorceress

Code: Select all

================================================================

[b]The first time I get the error message:[/b]
---------------------------------------
Failed to load VMMR0.r0
(VERR_LDR_MISMATCH_NATIVE).

Errorcode: E_FAIL (0x800004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

[b]The second time I get the error message:[/b]
----------------------------------------
Cannot load R0 module C:\Program Files\Oracle\VirtualBox/VBoxDDR0.r0: SUPR3LoadModule: supLoadModule returned
VERR_LDR_MISMATCH_NATIVE
(VERR_LDR_MISMATCH_NATIVE).

Failed to register ourselves as a PCI Bus (VERR_MODULE_NOT_FOUND).

Errorcode: E_FAIL (0x800004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

[b]And on the third try I get:[/b]
---------------------------
Cannot load R0 module C:\Program Files\Oracle\VirtualBox/VBoxDD2R0.r0: SUPR3LoadModule: supLoadModule returned
VERR_LDR_MISMATCH_NATIVE
(VERR_LDR_MISMATCH_NATIVE).

Errorcode: E_FAIL (0x800004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

[b]The fourth time VirtualBox just loads normal.[/b]
---------------------------------------------

When I look through the logs I notice that the problem always occurs near the end of the startup process.
And the first error is everytime

VERR_LDR_MISMATCH_NATIVE

What does that mean?
I've tried starting VirtualBox.exe in admin mode, but that does not help.

ManicSorceress wrote: VERR_LDR_MISMATCH_NATIVE

AFAIK, it means that you had a one or more machines in a saved (hibernated) state, and then you changed something fundamental about the system they were hibernated on. For example, a VirtualBox software upgrade, or moving the VM between hosts etc.

To fix, you right click the VM and choose "Discard saved state".

I never use any save states and I haven't changed anything on my system recently.
Thus, the option "Discard" for both my guests is greyed out.

And why does VirtualBox sometimes starts on the first try and sometimes when I launch it four times?

I tried launching it as administrator but this doesn't help also.

Any other ideas?

I also looked further into the logs.
It looks like a module called SUP either tries to load a file named

C:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0

or a file named

C:\Program Files\Oracle\VirtualBox\VBoxDD2R0.r0

and sometimes it perfectly works and sometimes the Return Code for this action is rc="VERR_LDR_MISMATCH_NATIVE".

What are these files good for? They're very small. DDR0.r0 is 152KB and DD2R0.r0 is 25KB.

Everything that folder is part of the executable. Don't mess with it.

As to what it is, going from the name I'd guess that is the low level ring 0 stuff that needs to be executed inside the VM.

Post the VM log file, as a zip attachment.

I have posted the last three log files and screenshots of the error messages in my first post.

Here is one of the tickets that address this error https://www.virtualbox.org/ticket/10872

Add to that the host is Windows 10 and you have a perfect mix for problems. W-10 is not fully supported yet.

What surprises me is that once a guest is started, it runs for hours and hours without a single problem.
The only downside at the moment is that sometimes I have to start the program four times before it works.

And that will be fixed as soon as a maintenance release addresses Windows 10 as host not being fully supported which they are working on.

I've written a Visual Basic Script which starts VirtualBox.exe and waits for it's return. Then it checks the actual log-file for an occurrence of "VERR_LDR_MISMATCH_NATIVE". If found it starts VirtualBox.exe again until there is no more occurrence of this string. I know, this is a crude emergency solution, but I think it works okay. For now. Maybe in the future I don't need it anymore when W10 is officially supported.

Code: Select all

' Dieses Skript startet VirtualBox und liest danach die Log-Datei.
' Wenn die Log-Datei die Zeichenfolge "VERR_LDR_MISMATCH" enthält, wird
' VirtualBox so lange neu gestartet bis die Zeichenfolge in der Log-Datei
' nicht mehr vorkommt.
' -----------------------------------------------

Option Explicit

Dim intRC
Dim wshShell
Dim strGast
Dim strBenutzer
Dim strPfadZuVB
Dim strPfadZuLog
Dim strLogInhalt

' Pfade und Name des Gastes festlegen (bei Gast Groß/Kleinschreibung beachten)
' --------------------------------------------------------------------------------------
strGast =     "Windows XP"
strBenutzer = "ManicSorceress"
' --------------------------------------------------------------------------------------
strPfadZuVB =  Chr(34) & "C:\Program Files\Oracle\VirtualBox\VirtualBox.exe" & Chr(34) & _
" --no-startvm-errormsgbox --startvm " & Chr(34) & strGast & Chr(34)
strPfadZuLog = "C:\Users\" & strBenutzer & "\VirtualBox VMs\" & strGast & "\Logs\VBox.log"
' --------------------------------------------------------------------------------------

' VirtualBox so lange neu starten, bis kein VERR_LDR_MISMATCH_NATIVE im Log vorkommt.
Set WSHShell = WScript.CreateObject("WScript.Shell")
Do
   intRC = WSHShell.Run (strPfadZuVB, 1, True)
   strLogInhalt = fktLogLesen(strPfadZuLog)
Loop Until Instr(strLogInhalt, "VERR_LDR_MISMATCH_NATIVE") = 0

Set wshShell = Nothing
WScript.Quit

' --------------------------------------------------------------------------------------

Function fktLogLesen(strPfad)

Dim objFSO
Dim objTS
Dim strText

Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objTS = objFSO.OpenTextFile(strPfad, 1)

Do Until objTS.AtEndOfStream
   strText = strText & objTS.ReadLine & vbCrLf
Loop
fktLogLesen = strText

objTS.Close
Set objFSO = Nothing

End Function

That error should be fixed with the latest Windows test build from here. Please confirm!

Frank Mehnert wrote:That error should be fixed with the latest Windows test build from here. Please confirm!

The latest test build (5.0.3) solved this issue for me.

virtualbox.org

VirtualBox starts after three failed attemps

VirtualBox starts after three failed attemps

Re: VirtualBox starts after three failed attemps

Re: VirtualBox starts after three failed attemps

Re: VirtualBox starts after three failed attemps

Re: VirtualBox starts after three failed attemps

Re: VirtualBox starts after three failed attemps

Re: VirtualBox starts after three failed attemps

Re: VirtualBox starts after three failed attemps

Re: VirtualBox starts after three failed attemps

Re: VirtualBox starts after three failed attemps

Re: VirtualBox starts after three failed attemps

Re: VirtualBox starts after three failed attemps

Re: VirtualBox starts after three failed attemps