Clonevdi still results in crashing VirtualBox (version 1.6.2)

Btw: I also tried to copy a VDI file where the filenames do not contain <spaces>, and I did a reinstallation of both Windows and VirtualBox.

We can't reproduce this here. Are you running out of disk space perhaps?

No absolutely not (> 20 GB disk space left where the VDI file is approximately 2 GB).

Are there maybe any prerequisites w.r.t. 3rd party software that needs to be installed in order for VirtualBox to run properly, such as the latest version of .NET, or the latest version of DirectX etc.

None. Which windows version are you using?

XP with SP3. Patch level of Windows is up-to-date (so all patches after SP3 are also installed)

This weekend, I run some additional tests: I did a reinstallation of VirtualBox on a different partition and afterwards I did a reinstallation of Windows XP within the Virtual Machine. Unfortunately, I had the same error message as stated above.

Can it be that I have some kind of physical memory error, which results in e.g. a CRC checksum error which is not being correctly handled by VirtualBox?

Btw, VirtualBox is able to process the copied harddisk...

Hi,

I have exactly the same error.
VirtualBox 1.6.2
Host system: WindowsXP Pro SP1 (50GB free space for 1.3GB vdi file)
Guest System: WindowsXP Pro SP0
Error Signature:
AppName? : vboxsvc.exe AppVer? : 1.0.0.1 ModName?: unknown ModVer? : 0.0.0.0 Offset : 00001214

But my copied file crashes always, which is my main concern, because I just want to backup some configurations.

I did some CloneVDI several months ago with earlier VirtualBox version(s) without any problems.

I have the same effect with VirtualBox 1.6.2 and 1.6.4 on WinXP SP2. It copies up to 100% and then crashes. Some months ago it worked.

The Windows event log contains the following error message: Faulting application vboxsvc.exe, version 1.0.0.1, faulting module unknown, version 0.0.0.0, fault address 0x000005b4.

The copied VDI file has the same size as the original file.

Can you provide a minidump? See http://www.virtualbox.org/wiki/User_FAQ

We have produced two different minidump files and stored them at:

http://source-code.biz/temp/virtualbox

The error occurs in different variations. Sometimes it does not occur at all (on the same computer and with the same VDI file which is copied). Sometimes the DEP (data execution prevention) is triggered.

The stack trace for the first dump file is:

774ff2a6 ole32CoInitialize+0x9c 774fee98 ole32CoInitializeEx+0x32b 00436916 ole32CoUninitialize+0x52 004356ad VBoxManage+0x36916 7c816fd7 VBoxManage+0x356ad

The error occurred within CoUnitialize?, which is called when VboxManage? terminates. There is probably some memory corruption.

This error still occurs with Virtualbox 2.0.0.