Alright, so I was able to reproduce a similar crash log by putting invalid characters in the file name for the font registry entries. Unfortunately it's not exactly the same, and none of your fonts appear to have illegal characters in the registry, so it is probably an issue related to .NET 3.5...