When I start my app I get a lot of information like this:
System.Windows.Data Information: 10 : Cannot retrieve value using the binding and
no valid fallbac
Yes, you should. It is safest to treat binding feedback (information, errors, etc) just like compiler warning and errors. Binding issues tend to slow the execution of the application down since it forces bindings to be re-evaluated, and in my experience, sometimes breaks them to where you need to recreate the binding in code.
The simplest workaround, if you can, is to set the FallbackValue on your binding to a value which can be treated as default. For example, if you have a class which has a "Count" property, but said class can be null at some point in time when your view is created, your binding might look like which would display a "0" in the text block, or pass the fallback value to the converter if there is one in use.