From this old threads, it seems to be a old bug from cam350, there are a couple of workarounds that you could try: