Corrupt Event Log File

One reader shares his tips for troubleshooting a corrupt event-log file in Windows 2000.

Readers

June 12, 2001

1 Min Read
ITPro Today logo in a gray background | ITPro Today

After my Windows 2000 system reached the logon screen, the system was displaying the message NT AuthoritySystem server.exe status code 128, then rebooting. I determined that the cause was a corrupt file in the event logs. To solve the problem, I booted to the Recovery Console (RC) and renamed the Application, Security, and System event-log files C:winntsystem32configappevent.evt, C:winntsystem32configsecevent.evt, and C:winntsystem32configsysevent.evt, respectively.

—Patrick Gliniecki
[email protected]

Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.

You May Also Like