Migrate OS to SSD - Crashes at Copying Partition

Discussion in 'Other Paragon Disk Utilities' started by pirivan, Jan 8, 2013.

Thread Status:
Not open for further replies.
  1. pirivan

    pirivan Registered Member

    Joined:
    Jan 8, 2013
    Posts:
    2
    I am running Paragon migrate OS to SSD (Paragon-198-PEE_WinInstallSNU_10.0.17.13028_000) and I am experiencing an odd crash bug.

    The process gets to: Copy Partition '2 minutes 38 seconds remaining' and then crashes with the following error message:

    Faulting application name: migrateos.exe, version: 10.0.17.13028, time stamp: 0x4d6c4ba6
    Faulting module name: hdm.dll, version: 10.0.17.13028, time stamp: 0x4d6c41d0
    Exception code: 0xc0000005
    Fault offset: 0x001bed81
    Faulting process id: 0x1250
    Faulting application start time: 0x01cdee1f786d2b37
    Faulting application path: C:\Program Files (x86)\Paragon Software\Migrate OS to SSD\program\migrateos.exe
    Faulting module path: C:\Program Files (x86)\Paragon Software\Migrate OS to SSD\program\hdm.dll
    Report Id: 018c7384-5a13-11e2-9efb-001fbc010988

    In the event log I have located the following error that does occur infrequently and does not coincide with trying to image the drive, however it does relate to the SSD (that is the SSD's volume ID) so I thought it was relevant:
    Encrypted volume check: Volume information on \\?\Volume{37bd2ebd-5a11-11e2-9efb-001fbc010988} cannot be read.

    The source volume is a Samsung HD501LJ (500GB SATA drive, the drive only has 150GB or so of data on it) and the destination is a 300GB Intel 320 Series SSD. Honestly I have no idea what this points to. I can copy data from the source volume to the destination without any issues. I have used the tool in the past without any issues.

    Any advice/feedback would be welcome; thanks!
     
    Last edited: Jan 9, 2013
  2. pirivan

    pirivan Registered Member

    Joined:
    Jan 8, 2013
    Posts:
    2
    In case someone sees this later, it turns out the issue was Paragon's software. I used another SSD imaging program I had that came with a Crucial M4 SSD and that worked without any issues.
     
Loading...
Thread Status:
Not open for further replies.