And additionally these are the runtime dlls from VS2008 while FreeCAD itself and all its 3rd party libraries were built with VS2013.As you can see, after the error happens there are two more .dll loaded:
To find the cause of the problem we have to figure out which other dll is loading the old runtime dll. I wonder whether your separate Python installation is responsible for it. Can you figure out which VS version it was built with? Therefore just double click the python.exe and then copy & paste the prompt.is the cause of the problem, and if so, what should I do about it?
E.g. for VS2013 it looks like this:
For testing purposes you can also rename C:\Python27. Then start FreeCAD and check if the problem is solved or not.Python 2.7.8 (default, Nov 17 2014, 20:37:05) [MSC v.1800 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>>