Page 1 of 1
Error when I use a vdi on new VM
Posted: 25. Jul 2014, 18:34
by calancheur
Hi,
I have uninstall and re install VirtualBox on my computer for differents reasons.
I saved the .vdi file to use it on the new install
But I got this error message when I launch the VM.
If anyone could help me, it would be perfect.
Thanks a lot
Sorry for my English
Échec de l'ouverture de session pour la machine virtuelle SSL.
The virtual machine 'XXXXXX' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\xxxxx\VirtualBox VMs\SSL\Logs\VBoxStartup.log'.
Code d'erreur : E_FAIL (0x80004005)
Composant : Machine
Re: Error when I use a vdi on new VM
Posted: 25. Jul 2014, 19:02
by socratis
calancheur wrote:More details may be available in 'C:\Users\xxxxx\VirtualBox VMs\SSL\Logs\VBoxStartup.log'.
Could you share with us the log file?
Re: Error when I use a vdi on new VM
Posted: 26. Jul 2014, 09:01
by calancheur
Yes of course.
Thanks.
Hope it can help you to help me

This vdi is really important for me.
Code: Select all
1374.eb4: Log file opened: 4.3.15r95226 g_hStartupLog=000000000000015c g_uNtVerCombined=0x63258000
1374.eb4: Calling main()
1374.eb4: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x0
1374.eb4: SUPR3HardenedMain: Respawn #1
1374.eb4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\virtual box\VirtualBox.exe)
1374.eb4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\virtual box\VirtualBox.dll)
1374.eb4: supR3HardenedWinDoReSpawn(1): New child 1bf4.1bfc [kernel32].
1374.eb4: supR3HardenedWinPurifyChild: PebBaseAddress=00007ff79b529000 cbPeb=0x388
1374.eb4: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ffceb790000 uNtDllChildAddr=00007ffceb790000
1374.eb4: supR3HardNtPuChTriggerInitialImageEvents: pvLdrInitThunk=00007ffceb7e6a4c pvNtTerminateThread=00007ffceb82b0b0
1374.eb4: supR3HardNtPuChSanitizeImage: 00007ff79bd60000 '\Device\HarddiskVolume3\virtual box\VirtualBox.exe'
1374.eb4: supR3HardNtPuChSanitizeMemory: Freeing exec mem at 00007ffc6b950000 (00007ffc6b950000 LB 0x2000)
1374.eb4: supR3HardNtPuChSanitizeImage: 00007ffceb790000 '\Device\HarddiskVolume1\Windows\System32\ntdll.dll'
1374.eb4: supR3HardNtPuChSanitizeMemory: Freeing exec mem at 00007ffceb940000 (00007ffceb940000 LB 0x1000)
1374.eb4: supR3HardenedWinDoReSpawn(1): Quitting: ExitCode=0xc0000005 rcNt=0x0
Re: Error when I use a vdi on new VM
Posted: 26. Jul 2014, 09:45
by calancheur
I don't have the same error message at each time:
Code: Select all
ef4.1020: Log file opened: 4.3.15r95226 g_hStartupLog=00000000000001e4 g_uNtVerCombined=0x63258000
ef4.1020: Calling main()
ef4.1020: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x0
ef4.1020: SUPR3HardenedMain: Respawn #1
ef4.1020: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume6\VB\VirtualBox.exe)
ef4.1020: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume6\VB\VirtualBox.dll)
ef4.1020: supR3HardenedWinDoReSpawn(1): New child 1920.1094 [kernel32].
ef4.1020: supR3HardenedWinPurifyChild: PebBaseAddress=00007ff7520f3000 cbPeb=0x388
ef4.1020: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ffceb790000 uNtDllChildAddr=00007ffceb790000
ef4.1020: supR3HardNtPuChTriggerInitialImageEvents: pvLdrInitThunk=00007ffceb7e6a4c pvNtTerminateThread=00007ffcebe60000
ef4.1020: Fatal error:
ef4.1020: NtWriteVirtualMemory/LdrInitializeThunk[restore] failed: 0xc0000005
Re: Error when I use a vdi on new VM
Posted: 26. Jul 2014, 12:05
by socratis
Can you see if downgrading to
4.3.12 fixes the problem? There have been some
issues with 4.3.14 and the 4.3.15 build that you have is a test build.
Re: Error when I use a vdi on new VM
Posted: 26. Jul 2014, 12:59
by calancheur
Yes, downgrade to 4.3.12 fixes this problem!!!
Thank you
Re: Error when I use a vdi on new VM
Posted: 26. Jul 2014, 14:06
by mpack
See the "anti-virus conflicts with 4.3.14" sticky topic at the top of this forum.