no Windows updates have taken place during my 'font-installing spree.'
If an Update is involved, it would have happened before your font installing spree. Would you please investigate your Updates for the last 6 months to a year? You can look them up fairly easily. I don't know exactly how on Windows 10. But on Windows 7 it's Control Panel > Windows Updates. There, you can click a button to list all your updates, and search them by date (maybe even by keyword??). Read them and find out if there were any updates which affected fonts or font handling or font driver, etc. I know there's at least one, from a previous report I read.
If you can identify any Update which has something to do with fonts, will you please give me a link to it, so I can read about it?
Besidses that, all I could really do is refer you to my search results for the error message:
https://duckduckgo.com/?q=The+instruction+at+0x00007FF63263609A+referenced+memory+at+0x000000000000008.++The+memory+could+not+be+read.&t=seamonkey&ia=webNone of the results seem to focus on the anything in particular. They either say this is a generic kind of error which doesn't tell much by itself, or the answer instructs you to run several generic kind of troubleshooting steps (many of the same ones I suggested - Windows update, virus, malware, other programs, etc.). One answer I saw a few time was to open Windows in "clean boot" mode and find out if the problem still happens. But thhere really are only a few hits for it.
I also tried to search it in MS TechNet (
http://technet.microsoft.com/en-us/default.aspx) with more of the same.
I did look up fonthostdrv.exe, info here
https://www.file.net/process/fontdrvhost.exe.html. It's a Windows font driver, which you report crashed when you chose the debug option. But I'm still not sure what that option was connected to. Was that option connected to the error message?
It would probably be worth the time to see if there is any upgrade for that font driver. It's been a long time since I looked into upgrading a driver. I think you'd need to search your computer for fonthostdrv.exe. Then right-click > Properties. And I think on one of the tabs in that Properties dialog is a button to upgrade the driver. Again, at least that's for Windows 7. I'm not sure about Windows 10.
I know you said you uninstalled the font manager, so I guess you could double check that it was uninstalled successfully.
If none of this gives us any more helpful info, we'll need to bump this problem up to developers. I'll tell you how, after you've investigated the Updates. Because I really think an Update could be part of the problem. In any case, developers will want to know that info, so it will be good to be able to tell them.