PassMark Software

Announcement

Collapse
No announcement yet.

imageUSB Exiting after fatal event

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • imageUSB Exiting after fatal event

    I'm using Windows 8.1 ENT, Toshiba TransMemory 8GB usb 2.0, ImageUSB v1.4 build 1000.
    When trying write an image to usb drive imageusb exits after fatal event.

    Code:
    2019/02/07 10:15:37 890319 DEBUG [imageusb.cpp->UpdateDriveStructure:1377] Inspecting Volume G:\
    2019/02/07 10:15:37 890614 DEBUG [imageusb.cpp->UpdateDriveStructure:1393] Calling IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS...
    2019/02/07 10:15:37 892523 DEBUG [imageusb.cpp->IsBitLocked:7604] WMI: Connect server failed (-2147217394)
    
    ]
    2019/02/07 10:15:50 493343 DEBUG [imageusb.cpp->OnRun:1806] INFO: OnRun() - Current imageUSB status: 0. Requested Action: Write
    2019/02/07 10:15:54 504915 DEBUG [imageusb.cpp->PreRunCheck:6099] Selected - Disk TOSHIBA TransMemory (Serial: 0 Disk: 3, Part. Type: MBR, Size: 7.21 GB, Volumes: G)
    2019/02/07 10:15:56 016125 DEBUG [imageusb.cpp->OnRun:1822] 1 Drives selected for Imaging.
    2019/02/07 10:15:56 023618 DEBUG [imageusb.cpp->Write:1911] Successfully opened image file [D:\\memtest86-usb\memtest86-usb.img] (524288000 bytes) for read access.
    2019/02/07 10:15:56 025683 DEBUG [imageusb.cpp->Write:1914] Checking for imageUSB image header...
    2019/02/07 10:15:56 027535 DEBUG [imageusb.cpp->Write:1933] Image file was not created with imageUSB.
    2019/02/07 10:15:56 029468 DEBUG [imageusb.cpp->Write:2007] Created 1 Write Threads. Imaging Starting Soon...
    2019/02/07 10:15:56 543701 DEBUG [imageusb.cpp->WriteImageThread:2040] Write Image Thread started on [TOSHIBA TransMemory ] (Disk 3)
    2019/02/07 10:15:56 606345 DEBUG [imageusb.cpp->LockAndDismountAllVolumes:2560] Attempting to LOCK and UNMOUNT G:\ [Volume \\?\Volume{065a6b12-3711-11e8-8256-c8d3a3ac3e54}] on Disk No 3.
    2019/02/07 10:15:57 444521 DEBUG [imageusb.cpp->LockAndDismountAllVolumes:2570] Volume \\?\Volume{065a6b12-3711-11e8-8256-c8d3a3ac3e54} on Disk No 3 LOCKED.
    2019/02/07 10:15:57 447961 DEBUG [imageusb.cpp->LockAndDismountAllVolumes:2580] Volume \\?\Volume{065a6b12-3711-11e8-8256-c8d3a3ac3e54} on Disk No 3 UNMOUNTED.
    2019/02/07 10:15:57 452799 DEBUG [imageusb.cpp->IsBitLocked:7604] WMI: Connect server failed (-2147217394)
    2019/02/07 10:15:57 455789 DEBUG [imageusb.cpp->LockAndDismountAllVolumes:2594] Volume \\?\Volume{065a6b12-3711-11e8-8256-c8d3a3ac3e54} on Disk No 3 OFFLINE.
    2019/02/07 10:15:57 458630 DEBUG [imageusb.cpp->ObliterateBitLocker:7697] INFO: Attempting to clear Drive Layout Information on BitLocked Drive \\.\PhysicalDrive3.
    2019/02/07 10:15:57 621496
    
    ***** FATAL EXCEPTION RECEIVED *******
    
    ***** Vectored Exception Handler: Received fatal exception EXCEPTION_ACCESS_VIOLATION PID: 4920
    
    ******* STACKDUMP *******
    stack dump [0]
    stack dump [1]
    stack dump [2]
    stack dump [3]
    stack dump [4]
    stack dump [5]
    stack dump [6]
    stack dump [7]
    stack dump [8]
    stack dump [9]
    stack dump [10] BaseThreadInitThunk
    stack dump [11] RtlInitializeExceptionChain
    stack dump [12] RtlInitializeExceptionChain
    
    Exiting after fatal event (FATAL_EXCEPTION). Fatal type: EXCEPTION_ACCESS_VIOLATION
    Log content flushed sucessfully to sink
    
    
    g3log g3FileSink shutdown at: 10:15:57 621911

  • #2
    Thank you for the report. This might be related to another issue we have been made aware of. We have a fix in progress and hope to have a new release shortly.

    Comment


    • #3
      Update: We ran into an issue with overwriting BitLocked drives that we are currently investigating and testing a solution on that will be included in the next release. We need to do some additional testing before we make it public. Hopefully a new release with the commutative fixes will be ready sometime next week.

      Comment


      • #4
        A new build release of ImageUSB, V1.4 Build 1001, was uploaded that should address the crash and issues with overwriting BitLocker drives. Let us know if you run into any issues with the new update.

        Comment


        • #5
          With ImageUSB, V1.4 Build 1001 I run into another issue. When trying to write an image I get a message “Failed to lock&dismount volume”

          Code:
          g3log created log at: Tue Feb 19 15:06:24 2019
                  LOG format: [YYYY/MM/DD hh:mm:ss uuu* LEVEL FILE->FUNCTION:LINE] message        (uuu*: microseconds fractions of the seconds value)
          
          2019/02/19 15:06:25 403718    DEBUG [imageusb.cpp->wWinMain:358]    Starting...  imageUSB v1.4  Build 1001
          2019/02/19 15:06:25 403730    DEBUG [imageusb.cpp->wWinMain:359]    Command line: "D:\imageusb\imageUSB.exe" -d
          2019/02/19 15:06:25 403744    DEBUG [imageusb.cpp->wWinMain:360]    Program Path: D:\imageusb
          2019/02/19 15:06:25 403750    DEBUG [imageusb.cpp->wWinMain:365]    Date: 02/19/19 02/19/19
          2019/02/19 15:06:25 485192    DEBUG [imageusb.cpp->UpdateDriveStructure:1129]    Getting list of eligible removable USB drives...
          2019/02/19 15:06:25 485578    DEBUG [imageusb.cpp->UpdateDriveStructure:1156]    Opening handle to \\.\PhysicalDrive0
          2019/02/19 15:06:25 487324    DEBUG [imageusb.cpp->UpdateDriveStructure:1165]    Calling IOCTL_STORAGE_QUERY_PROPERTY X1...
          2019/02/19 15:06:25 487562    DEBUG [imageusb.cpp->UpdateDriveStructure:1194]    Calling IOCTL_STORAGE_QUERY_PROPERTY X2...
          2019/02/19 15:06:25 487802    DEBUG [imageusb.cpp->UpdateDriveStructure:1215]    \\.\PhysicalDrive0 Not Added. Not of USB Device Type. Device Type 3
          2019/02/19 15:06:25 488089    DEBUG [imageusb.cpp->UpdateDriveStructure:1156]    Opening handle to \\.\PhysicalDrive1
          2019/02/19 15:06:25 491379    DEBUG [imageusb.cpp->UpdateDriveStructure:1165]    Calling IOCTL_STORAGE_QUERY_PROPERTY X1...
          2019/02/19 15:06:25 491606    DEBUG [imageusb.cpp->UpdateDriveStructure:1194]    Calling IOCTL_STORAGE_QUERY_PROPERTY X2...
          2019/02/19 15:06:25 491830    DEBUG [imageusb.cpp->UpdateDriveStructure:1215]    \\.\PhysicalDrive1 Not Added. Not of USB Device Type. Device Type 11
          2019/02/19 15:06:25 492164    DEBUG [imageusb.cpp->UpdateDriveStructure:1156]    Opening handle to \\.\PhysicalDrive2
          2019/02/19 15:06:25 492771    DEBUG [imageusb.cpp->UpdateDriveStructure:1165]    Calling IOCTL_STORAGE_QUERY_PROPERTY X1...
          2019/02/19 15:06:25 492985    DEBUG [imageusb.cpp->UpdateDriveStructure:1194]    Calling IOCTL_STORAGE_QUERY_PROPERTY X2...
          2019/02/19 15:06:25 493182    DEBUG [imageusb.cpp->UpdateDriveStructure:1264]    Calling IOCTL_DISK_GET_DRIVE_LAYOUT_EX...
          2019/02/19 15:06:25 493429    DEBUG [imageusb.cpp->UpdateDriveStructure:1300]    INFO: [\\.\PhysicalDrive2] Found 1 partitions total.
          2019/02/19 15:06:25 493622    DEBUG [imageusb.cpp->UpdateDriveStructure:1301]    INFO: [\\.\PhysicalDrive2] 1 partitions in use.
          2019/02/19 15:06:25 493815    DEBUG [imageusb.cpp->UpdateDriveStructure:1313]    Getting Info on Partition \\.\PhysicalDrive2(0)
          2019/02/19 15:06:25 494025    DEBUG [imageusb.cpp->UpdateDriveStructure:1326]    Calling IOCTL_DISK_GET_DRIVE_GEOMETRY_EX...
          2019/02/19 15:06:25 494756    DEBUG [imageusb.cpp->UpdateDriveStructure:1357]       Adding eligible USB Drive [TOSHIBA  TransMemory     ] to list.
          2019/02/19 15:06:25 495071    DEBUG [imageusb.cpp->UpdateDriveStructure:1156]    Opening handle to \\.\PhysicalDrive3
          2019/02/19 15:06:25 496203    DEBUG [imageusb.cpp->UpdateDriveStructure:1160]    ERROR: Failed to Open Handle: \\.\PhysicalDrive3.
              Error No. 5 [Отказано в доступе.]
          
              Error No. 5 [Отказано в доступе.]
          2019/02/19 15:06:25 518041    DEBUG [imageusb.cpp->UpdateDriveStructure:1370]    Mapping Volumes to Drives/Partitions.
          2019/02/19 15:06:25 518231    DEBUG [imageusb.cpp->UpdateDriveStructure:1387]    Inspecting Volume C:\
          2019/02/19 15:06:25 518436    DEBUG [imageusb.cpp->UpdateDriveStructure:1403]    Calling IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS...
          2019/02/19 15:06:25 518636    DEBUG [imageusb.cpp->UpdateDriveStructure:1387]    Inspecting Volume D:\
          2019/02/19 15:06:25 518839    DEBUG [imageusb.cpp->UpdateDriveStructure:1403]    Calling IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS...
          2019/02/19 15:06:25 519037    DEBUG [imageusb.cpp->UpdateDriveStructure:1387]    Inspecting Volume E:\
          2019/02/19 15:06:25 519263    DEBUG [imageusb.cpp->UpdateDriveStructure:1403]    Calling IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS...
          2019/02/19 15:06:25 519483    DEBUG [imageusb.cpp->UpdateDriveStructure:1415]    Error 5 [Отказано в доступе.
          ]
          2019/02/19 15:06:25 519670    DEBUG [imageusb.cpp->UpdateDriveStructure:1387]    Inspecting Volume G:\
          2019/02/19 15:06:25 520078    DEBUG [imageusb.cpp->UpdateDriveStructure:1403]    Calling IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS...
          2019/02/19 15:06:25 534099    DEBUG [imageusb.cpp->UpdateDriveStructure:1451]    Error 5 [Отказано в доступе.
          ]
          
          2019/02/19 15:06:41 680765    DEBUG [imageusb.cpp->OnRun:1816]    INFO: OnRun() - Current imageUSB status: 0. Requested Action: Write
          2019/02/19 15:06:42 965389    DEBUG [imageusb.cpp->PreRunCheck:6054]    Selected - Disk TOSHIBA TransMemory (Serial: 0 Disk: 2, Part. Type: MBR, Size: 7.21 GB, Volumes: G)
          2019/02/19 15:06:44 083812    DEBUG [imageusb.cpp->OnRun:1832]    1 Drives selected for Imaging.
          2019/02/19 15:06:44 090444    DEBUG [imageusb.cpp->Write:1921]    Successfully opened image file [D:\imageusb\memtest86-usb.img] (524288000 bytes) for read access.
          2019/02/19 15:06:44 092148    DEBUG [imageusb.cpp->Write:1924]    Checking for imageUSB image header...
          2019/02/19 15:06:44 093949    DEBUG [imageusb.cpp->Write:1943]       Image file was not created with imageUSB.
          2019/02/19 15:06:44 095771    DEBUG [imageusb.cpp->Write:2017]    Created 1 Write Threads. Imaging Starting Soon...
          2019/02/19 15:06:44 601207    DEBUG [imageusb.cpp->WriteImageThread:2050]    Write Image Thread started on [TOSHIBA  TransMemory     ] (Disk 2)
          2019/02/19 15:06:44 731701    DEBUG [imageusb.cpp->IsBitLocked:7575]    WMI: Connect server failed (-2147217394)
          2019/02/19 15:06:44 734413    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8106]    INFO: Attempting to clear BitLocked Volume \\?\Volume{065a6b12-3711-11e8-8256-c8d3a3ac3e54} on Drive 2.
          2019/02/19 15:06:44 736438    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8123]    INFO: Loading VDS Service
          2019/02/19 15:06:46 800022    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8175]    INFO: Querying VDS Software Providers
          2019/02/19 15:06:46 802045    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8184]    INFO: Looping through VDS Software Providers
          2019/02/19 15:06:46 804038    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8205]    INFO: Querying Packs for VDS Software Provider
          2019/02/19 15:06:46 805787    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8215]    INFO: Looping through Packs for VDS Software Provider
          2019/02/19 15:06:46 807701    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8236]    INFO: Querying Disks in Pack
          2019/02/19 15:06:46 809407    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8246]    INFO: Looping through Disks for VDS Pack
          2019/02/19 15:06:46 811253    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8261]    WARNING: No more Disks found for this VDS Pack.
          2019/02/19 15:06:46 813290    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8230]    WARNING: No more IID_IVdsPack found for this VDS Software Provider.
          2019/02/19 15:06:46 815112    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8205]    INFO: Querying Packs for VDS Software Provider
          2019/02/19 15:06:46 817379    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8215]    INFO: Looping through Packs for VDS Software Provider
          2019/02/19 15:06:46 820025    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8236]    INFO: Querying Disks in Pack
          2019/02/19 15:06:46 823556    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8246]    INFO: Looping through Disks for VDS Pack
          2019/02/19 15:06:46 825461    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8268]    INFO: Getting Identification Data for VDS Disk
          2019/02/19 15:06:46 842606    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8261]    WARNING: No more Disks found for this VDS Pack.
          2019/02/19 15:06:46 846415    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8236]    INFO: Querying Disks in Pack
          2019/02/19 15:06:46 848881    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8246]    INFO: Looping through Disks for VDS Pack
          2019/02/19 15:06:46 850640    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8268]    INFO: Getting Identification Data for VDS Disk
          2019/02/19 15:06:46 855983    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8261]    WARNING: No more Disks found for this VDS Pack.
          2019/02/19 15:06:46 859408    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8236]    INFO: Querying Disks in Pack
          2019/02/19 15:06:46 861256    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8246]    INFO: Looping through Disks for VDS Pack
          2019/02/19 15:06:46 863355    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8268]    INFO: Getting Identification Data for VDS Disk
          2019/02/19 15:06:46 866823    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8261]    WARNING: No more Disks found for this VDS Pack.
          2019/02/19 15:06:46 870141    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8236]    INFO: Querying Disks in Pack
          2019/02/19 15:06:46 872756    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8246]    INFO: Looping through Disks for VDS Pack
          2019/02/19 15:06:46 874734    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8268]    INFO: Getting Identification Data for VDS Disk
          2019/02/19 15:06:46 879072    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8311]    INFO: Disk Serials Match: 0 vs 0
          2019/02/19 15:06:46 880873    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8316]    INFO: Getting Properties for VDS Disk
          2019/02/19 15:06:46 884832    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8329]    INFO:    Disk Address: Port0Path0Target0Lun0
          2019/02/19 15:06:46 887094    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8334]    INFO:    Friendly Name: TOSHIBA TransMemory USB Device
          2019/02/19 15:06:46 889493    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8339]    INFO:    Adapter Name: USB Mass Storage Device
          2019/02/19 15:06:46 892574    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8344]    INFO:    Device Path : \\?\usbstor#disk&ven_toshiba&prod_transmemory&rev_1.00#00e6d39b491dcd81c43d1bcb&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
          2019/02/19 15:06:46 895175    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8353]    INFO:    Name: \\?\PhysicalDrive2
          2019/02/19 15:06:46 897602    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8385]    INFO: Getting Pack associated with this VDS Disk
          2019/02/19 15:06:46 900139    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8394]    INFO: Querying Volumes on this VDS Disk Pack
          2019/02/19 15:06:46 902545    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8403]    INFO: Looping through Volumes for VDS Disk Pack
          2019/02/19 15:06:46 904989    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8429]    INFO: Querying Volumes Properties for VDS Volume
          2019/02/19 15:06:46 907891    DEBUG [imageusb.cpp->RemoveBitLockerOnVolume:8518]    ERROR: No more volumes found on Disk.
          2019/02/19 15:06:49 835451    DEBUG [imageusb.cpp->wWinMain:394]    Exiting with Return Code 0.
          g3log g3FileSink shutdown at: 15:06:49 836052
          Last edited by AlexS; 02-19-2019, 11:13 AM.

          Comment


          • #6
            In order to overwrite an existing drive, ImageUSB requires that all volumes on the drive to be Locked and Dismounted for exclusive access to the drive. To do so for BitLocker enabled drives, imageUSB will try to do force format on the BitLocked volume to clear the BitLocker status, but it can fail if something else is holding access to the drive or if the volume is not being reported (therefore a format is not able to preformed). It seems that in your case that the volume is not being reported when we are querying for volumes on your disk.

            However, I believe the BitLocker status is being incorrect reported for your drive, and that it might not be BitLocked at all. The following line in the log seems to lead me to believe so, "...IsBitLocked:7575] WMI: Connect server failed (-2147217394)". Which is the error code 0x8004100E WBEM_E_INVALID_NAMESPACE, which means our mechanism to detect BitLocker is not available on your system.

            Is your drive BitLocker enabled?
            What Windows OS Version are you running?
            Are you running as admin or elevated permissions when launching imageUSB?


            Comment


            • #7
              We've released a new build, V1.4 Build 1002. This should address the issue where the software will try to clear incorrectly detected BitLocker volumes during imaging.

              Comment


              • #8
                No errors with build, V1.4 Build 1002.
                I`ve erased drive with imgUSB and wrote an image.

                Comment

                Working...
                X