Announcement

Collapse
No announcement yet.

ImageUSB Crashes on Windows 10

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    ImageUSB Crashes on Windows 10

    On Windows 10 x64, Immediately after I click "OK" to confirm that ImageUSB will write the file on the USB drive (Sandisk Ultra 16GB), it crashes. Log file:

    11-Dec-2015 - 21:10:30:149 - PassMark Software - imageUSB v1.2.1004
    11-Dec-2015 - 21:10:30:149 - Getting list of available removable USB drives...
    11-Dec-2015 - 21:10:30:149 - Inspecting Drive C:\...
    11-Dec-2015 - 21:10:30:149 - Drive String \\.\C:
    11-Dec-2015 - 21:10:30:165 - Drive C:\: Not of USB Type Skipping. (DriveType 11)
    11-Dec-2015 - 21:10:30:165 - Inspecting Drive D:\...
    11-Dec-2015 - 21:10:30:165 - Drive String \\.\D:
    11-Dec-2015 - 21:10:30:165 - Drive D:\: Not of USB Type Skipping. (DriveType 11)
    11-Dec-2015 - 21:10:30:165 - Inspecting Drive E:\...
    11-Dec-2015 - 21:10:30:165 - Drive String \\.\E:
    11-Dec-2015 - 21:10:30:165 - Drive E:\: Not of USB Type Skipping. (DriveType 11)
    11-Dec-2015 - 21:10:30:165 - Inspecting Drive F:\...
    11-Dec-2015 - 21:10:30:165 - Drive String \\.\F:
    11-Dec-2015 - 21:10:30:165 - Failed to get Drive Info for F:\: Error No. 21
    11-Dec-2015 - 21:10:30:165 - Failed with error 21: The device is not ready.


    11-Dec-2015 - 21:10:30:165 - Inspecting Drive G:\...
    11-Dec-2015 - 21:10:30:165 - Drive String \\.\G:
    11-Dec-2015 - 21:10:30:165 - Drive G:\ Size: 16008577024 Bytes Volume: Other: NTFS
    11-Dec-2015 - 21:10:30:165 - Ready...
    11-Dec-2015 - 21:10:57:212 - Error - Unable to determine disk number of Drive G:\.


    From the event log:
    Faulting application name: imageUSB.exe, version: 1.2.1004.0, time stamp: 0x55b921fe
    Faulting module name: imageUSB.exe, version: 1.2.1004.0, time stamp: 0x55b921fe
    Exception code: 0xc0000094
    Fault offset: 0x0000a4bf
    Faulting process id: 0x568
    Faulting application start time: 0x01d1348aa81d3172
    Faulting application path: C:\<path>\imageUSB.exe
    Faulting module path: C:\<path>\imageusb\imageUSB.exe
    Report Id: 422b3be1-a701-4b4b-b88b-72abd808ed18
    Faulting package full name:
    Faulting package-relative application ID:
    Tags: None
  • #2
    We have tested the software on Win10 and didn't find any problems.

    Is it consistent and reproducible all the time?

    If you can run the software in debug mode and email in the log we can take a look at where the crash might be occurring. A debug information can be generated by starting imageUSB with the "-d" command line argument. The filename for the logfile is "imageUSB.log" and can be found in the same directory as the executable.

    Comment

    • #3
      Originally posted by vr335 View Post
      On Windows 10 x64, Immediately after I click "OK" to confirm that ImageUSB will write the file on the USB drive (Sandisk Ultra 16GB), it crashes. Log file:

      11-Dec-2015 - 21:10:30:149 - PassMark Software - imageUSB v1.2.1004
      11-Dec-2015 - 21:10:30:149 - Getting list of available removable USB drives...
      11-Dec-2015 - 21:10:30:149 - Inspecting Drive C:\...
      11-Dec-2015 - 21:10:30:149 - Drive String \\.\C:
      11-Dec-2015 - 21:10:30:165 - Drive C:\: Not of USB Type Skipping. (DriveType 11)
      11-Dec-2015 - 21:10:30:165 - Inspecting Drive D:\...
      11-Dec-2015 - 21:10:30:165 - Drive String \\.\D:
      11-Dec-2015 - 21:10:30:165 - Drive D:\: Not of USB Type Skipping. (DriveType 11)
      11-Dec-2015 - 21:10:30:165 - Inspecting Drive E:\...
      11-Dec-2015 - 21:10:30:165 - Drive String \\.\E:
      11-Dec-2015 - 21:10:30:165 - Drive E:\: Not of USB Type Skipping. (DriveType 11)
      11-Dec-2015 - 21:10:30:165 - Inspecting Drive F:\...
      11-Dec-2015 - 21:10:30:165 - Drive String \\.\F:
      11-Dec-2015 - 21:10:30:165 - Failed to get Drive Info for F:\: Error No. 21
      11-Dec-2015 - 21:10:30:165 - Failed with error 21: The device is not ready.


      11-Dec-2015 - 21:10:30:165 - Inspecting Drive G:\...
      11-Dec-2015 - 21:10:30:165 - Drive String \\.\G:
      11-Dec-2015 - 21:10:30:165 - Drive G:\ Size: 16008577024 Bytes Volume: Other: NTFS
      11-Dec-2015 - 21:10:30:165 - Ready...
      11-Dec-2015 - 21:10:57:212 - Error - Unable to determine disk number of Drive G:\.


      From the event log:
      Faulting application name: imageUSB.exe, version: 1.2.1004.0, time stamp: 0x55b921fe
      Faulting module name: imageUSB.exe, version: 1.2.1004.0, time stamp: 0x55b921fe
      Exception code: 0xc0000094
      Fault offset: 0x0000a4bf
      Faulting process id: 0x568
      Faulting application start time: 0x01d1348aa81d3172
      Faulting application path: C:\<path>\imageUSB.exe
      Faulting module path: C:\<path>\imageusb\imageUSB.exe
      Report Id: 422b3be1-a701-4b4b-b88b-72abd808ed18
      Faulting package full name:
      Faulting package-relative application ID:
      Hi vr335, I just upgraded to Windows 10 from Windows 7 and I'm getting crashes with error logs like this too. Did you find out what the problem was and how to fix it?

      Comment

      • #4
        We did not hear back from the original poster about the issue. If you are experiencing the same issue, perhaps you can shed some light.

        Is it consistent and reproducible all the time?

        If you can run the software in debug mode and email in the log we can take a look at where the crash might be occurring. A debug information can be generated by starting imageUSB with the "-d" command line argument. The filename for the logfile is "imageUSB.log" and can be found in the same directory as the executable.

        Comment

        Previous template Next
        Working...
        X