.NET's Font.Initialize() error

I'v posted this several times now without any solution. Its an error that keeps occuring after a small amount of time of having a freashly formatted pc with the .NET framework on when trying to run most .NET apps. The 110% sure thing is that this error isn't caused due to an actually error like in the code because once the Font.Initialize error went away and all the apps started working again. I don't know what causes this but it makes .NET apps that don't even have anything in common bar, i suppose, what core .NET objects they are accessing, my guess is the problem lies in one of those. It also can't be just my computer because I have a laptop too and it happened on that with a freshly formatted laptop with nothing but the .NET framework installed, not connected to a network or anything. I also tryed reinstalling the framework and that doesn't do anything, so the problem may not lie in the .NET frameworks files that it copies over but in what they access or something, I don't really know that much about the dll's. I was wondering if anyone else has this error. This error also appears in different error messages depending on if you have VS.NET installed or not. The same error appears as "Application has generated an exception that could not be handled. Proccess id=0x580(1408), Thread id=0x414(1044)". Of course those exact numbers may not be the same on all machines but if you click cancel to debug and view the dissassembly you will see it still links back to the Font.Initialize() error. It also appears as an algorithm overflow/underflow error. PS One thing that was mentions is that someone said they had a similar error, and they have HP printers and think is is them. Now the curious thing is that yes I do have a HP printer, and didn't have the error for a while, then installed my printer and pretty much the next day I got this error, but the error was on my PC not laptop (I installed the printer on my laptop), but I never checked if I had it on my laptop at the time, then the next day I came to run a .NET app and found my laptop had this error too. The 2 computers are networked so I wonder if from having a printer on my laptop it may have been default shared and caused this problem to happen on my PC too?.