Crash converting from vCenter 6.7U3 to Proxmox 9

VM image converter (VMDK, VHD, VHDX, IMG, RAW, QCOW and QCOW2), P2V migrator
Post Reply
DavidYerger
Posts: 1
Joined: Mon Nov 03, 2025 8:14 pm

Mon Nov 03, 2025 8:26 pm

Tried two different VMs, it will run a while and then crash, latest example got Event ID Application Error 1000:

Faulting application name: V2V_Converter.exe, version: 9.0.1.772, time stamp: 0x68b55074
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000204ae647060
Faulting process id: 0x1b60
Faulting application start time: 0x01dc4cf1a78155e5
Faulting application path: C:\Program Files\StarWind Software\StarWind V2V Converter\V2V_Converter.exe
Faulting module path: unknown
Report Id: a525be9a-5149-40c7-addc-2ac83fae6faf
Faulting package full name:
Faulting package-relative application ID:

Followed by Event ID 1001, Windows Error Reporting:

Fault bucket 1367585323191676131, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: V2V_Converter.exe
P2: 9.0.1.772
P3: 68b55074
P4: StackHash_f26e
P5: 0.0.0.0
P6: 00000000
P7: PCH_4F_FROM_ntdll+0x00000000000A0E74
P8: c0000005
P9: 0000000000000008
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.77d01081-63a1-4de4-a75f-d95468d429ae.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ab328d14-b0c7-4671-9b75-e29856db4afb.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.59093f08-21f9-48fa-a9b7-81e9982268e0.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2311e384-35cd-49ce-bb98-087f380aa42d.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5c51b838-155a-4ebc-bfb4-f66bd7e65d2c.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_V2V_Converter.ex_703dce829c81c9bfb0e7a9fa5cf1d2cccea5c21_4d6675c0_6c45e078-9964-496e-8924-8c050f7dc67c

Analysis symbol:
Rechecking for solution: 0
Report Id: a525be9a-5149-40c7-addc-2ac83fae6faf
Report Status: 268435456
Hashed bucket: 8256da480ea05dc672faa39b0ce0ace3
Cab Guid: 0

There was about 16 GB of RAM on the destination Proxmox node at the time of the crash.

Thank you!
yaroslav (staff)
Staff
Posts: 4309
Joined: Mon Nov 18, 2019 11:11 am

Mon Nov 03, 2025 11:45 pm

Hi,

Welcome to StarWind Forum. I have forwarded the logs to R&D.
For now, as a workaround, I think you can copy the VMDKs to Proxmox and recreate the VM there. It is not live conversion, but it should do the trick. See this KB too https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE.
Good luck with your project.
yaroslav (staff)
Staff
Posts: 4309
Joined: Mon Nov 18, 2019 11:11 am

Mon Nov 03, 2025 11:55 pm

Update: the fix should be in the future build.
Can I please have the conversion logs anyway?
LillianaVolkman
Posts: 1
Joined: Tue Jan 06, 2026 9:18 am

Tue Jan 06, 2026 9:20 am

yaroslav (staff) wrote:
Mon Nov 03, 2025 11:45 pm
Hi,

Welcome to StarWind Forum. I have forwarded the logs to R&D.
For now, as a workaround, I think you can copy the VMDKs to Proxmox and recreate the VM there. It is not live conversion, but it should do the trick. See this KB too https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE/Geometry Dash Bloodbath.
Good luck with your project.
The information you shared is very useful, thank you.
Last edited by LillianaVolkman on Mon Jan 12, 2026 1:42 am, edited 1 time in total.
yaroslav (staff)
Staff
Posts: 4309
Joined: Mon Nov 18, 2019 11:11 am

Tue Jan 06, 2026 9:33 am

Good luck with your project.
Post Reply