There's nothing weird about that. There are times when a reboot will fix a multitude of sins. Remember the Dilbert cartoons? Dogbert is sitting at the helpdesk, and his choice phrase to anyone that called is "Shutup and Reboot!"
In reality, as you've seen, bits of program code can get scrambled in memory (RAM not permenant storage), and then all hell breaks loose from annoyances such as this (it's all relative of course to the problem), to complete failures of programs where they need to send a message to Microsoft or some other unknown entity.
What happens in many cases is that the code gets stomped on by some other errant program that forgets what memory-space has been allocated to it. The errant program overwrites a little bit of some other program's code, usually the more important one that you are running, and then the program that was innocently being over written gets confused when it reads someone else's bits.
Anyway, rebooting a system often is one of the ways of getting around this problem especially with Windows, where many applications are known to suffer from memory leaks as well, and use up space that is needed by other applications.
John