SBIG driver: Operating system error. Error = 30032.

Discussion in 'STX and STXL Series Cameras' started by Martin Pugh, Mar 3, 2021.

  1. Martin Pugh

    Martin Pugh Cyanogen Customer

    Joined:
    Oct 27, 2014
    Messages:
    262
    This STX16803 has just returned from repair. Its been back on the scope for a few days now, and I am seeing this error.

    advice?
     
  2. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    5,250
    Location:
    Earth
    Likely TheSky X is giving you that. Sometimes indicates operating system device driver problem, or other unknown low-level fault.
    Have you installed any OS updates lately? Check your machine is current. Run Windows Update a couple times.
    Then check this:
    https://forum.diffractionlimited.co...connects-turn-off-usb-selective-suspend.7848/

    Run the SBIG Driver Checker. Firmware tab - Get firmware version from camera to ensure it is able to talk to the camera.
    Sometimes doing the Driver - update drivers will re-install the drivers.
    Try testing the camera with CCDOps.
     
  3. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    5,250
    Location:
    Earth
    If you haven't resolved this, we would need debug logs from SBIG Driver Checker. This may impact system performance.
    Launch Driver Checker. Click [Debug Log] button. Click [All] button.
    Set the path for the log to a file on a fast local drive using [Set Path].
    [OK]
    Run your steps that result in OS Error 32.
    Then shutdown your software. Turn off all the log settings with [Clear All].
    Use Upload a File to send us the log.

    The OS Error 32 is indicating a Windows API failure of some kind. The Debug Log may capture the Windows Error Code and then we can see what Windows is unhappy about.
     
  4. Martin Pugh

    Martin Pugh Cyanogen Customer

    Joined:
    Oct 27, 2014
    Messages:
    262
    Some USB power saving features were enabled (again) by a Windows update which occurs with annoyimg regularity. I have also ran a new USB cable. Will see what happens now.
     

Share This Page