This problem occurs if the fully qualified domain name ( FQDN) of your computer is exactly 200 bytes long. During logon, one character more than the 200-byte allocation is written and heap corruption occurs.
Of course, the suggested workaround is just as entertaining:
To work around this problem, rename the computer so that it is one character shorter. If you do so, the FQDN is less than 200 characters long and the heap corruption does not occur.
Yes, this is old and was fixed in a service pack years ago.