Corrupt Event logs
 

I've got a client with Windows Server 2K3(with SP1) and their System Event Log keeps recorrupting. I can remove the corrupt log and things work fine, but once I reboot, it recorrupts. I found this knowledge base article that seems to be what's happening:
http://support.microsoft.com/default...b;en-us;899416
but the upshot is Microsoft wants you to call them, pay them money, and then if this is the issue they MIGHT refund your money. Just give me the fucking hotfix, jackasses!

Has anyone else run across this problem? I know replacing the network adaptors (or using different drivers) might be the proper course of action but I don't have a lot of spare time to work on this issue; it's pretty outside the scope of my support but it's holding up my actual work.

They just want to keep track of who's using it with what. I agree it can be painful, but from their perspective it can help testing and lmiit problems of pre-release versions floating around.

Call and tell them your mutual customer needs eventlog.dll version blah. Have the kb article number, NIC info, and driver version handy. Maybe throw in they're a mixed shop of Linux and Windows. :)

Well, it turns out that setting the offending NIC to full duplex mode solves the issue. I am done with that job, and thank the Lord.