Check Error Log In Winxp
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the windows xp event viewer command line company Business Learn more about hiring developers or posting ads with us Super User Questions windows xp event log Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; windows xp event log location it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Where are the results of the XP windows xp event viewer log file location Disk Error Checking utility logged? up vote 3 down vote favorite Last Friday, before I left work, I started a disk error check using the GUI found on the Tools tab of the disk properties. I checked the boxes for "Automatically fix file system errors" and "Scan for and attempt recovery of bad sectors." It hadn't finished by the time I left. When I came in this morning, there was a message box saying
Event Viewer Windows 7
that the check had completed successfully, but I haven't been able to find the results (i.e. if there were any corrupt files or other errors). A subsequent run of chkdsk (in the console with no switches) informs me that there are no bad sectors and that the indexes check out and there are no errors. Usually I run chkdsk on the command line and am able to look over the results. When its run on the OS drive, it logs an event in Application section that shows the same result text as the console prints. Are the results of the Disk Error Checking utility logged anywhere so I can review them? EDIT TO ADD: This was not the OS drive and was connected via USB. windows-xp chkdsk share|improve this question edited Aug 9 '10 at 21:26 asked Aug 9 '10 at 17:49 yhw42 2,01611727 add a comment| 2 Answers 2 active oldest votes up vote 7 down vote They are logged in event viewer. Start -> Run -> type "eventvwr.msc" (no quotes) -> ENTER. Click on Application and select the most recent winlogon entry. share|improve this answer answered Aug 9 '10 at 18:24 Moab 46k776128 add a comment| up vote 3 down vote accepted Here's what I've found researching my question: 1) Running chkdsk.exe (or using the XP Disk Error Check G
Appearance Subscribe l l FOLLOW US TWITTER GOOGLE+ FACEBOOK GET UPDATES BY EMAIL Enter your email below to get exclusive access to our best articles and http://www.howtogeek.com/howto/windows/fixing-the-event-log-is-full-error-on-windows-xp/ tips before everybody else. RSS ALL ARTICLES FEATURES ONLY TRIVIA Search How-To Geek Fixing "The Event Log is Full" Error on Windows XP I was working on a project for work when I suddenly http://www.pcreview.co.uk/threads/windows-xp-chkdsk-log-location.328554/ got the strangest error: "The Event Log is Full". Seriously? What I didn't remember is that Windows XP doesn't automatically overwrite events less than 7 days old from the event log, so when it's full, windows xp most applications that try and write to the event log are going to break. You can easily fix this problem by changing the event logs to overwrite old events regardless of the date, or just increase the size that the log is allowed to grow to. Note: If your event log is so huge within 7 days that you are getting this error, there's probably something seriously wrong. You should windows xp event inspect your event log to understand what is causing all of the errors… more on that in a future article. Increasing Event Log Size Open up Event Viewer by typing in eventvwr into the Start \ Run box, or you can find it under Administrative tools section of Control Panel. You'll notice over on the right-hand side of the window that the current size of my Application and System Event Logs are 512 KB… Now you can right-click on one of the Event Logs in the list, and choose Properties from the menu. In this dialog you can do a number of things… you could clear the log, increase the size, or just set the system to overwrite events as needed. I chose to increase the maximum size of the event log, and then also to overwrite events as needed. For those of you using Windows Vista, you'll notice that the default settings in Vista are to overwrite as needed, and the maximum size is way bigger. Guess my setting choices make sense then… Again, if your Application or System event logs are growing so gigantic that you are getting this error, you should really look into the root cause by carefully examining the entries in the logs. J
in various news groups where the log or logfile is for Windows XP or Windows 2000 for chkdsk (or scandisk, but it is technically chkdsk). They ask this because when you go into "My Computer" (or whatever), select a disk, right click, select "properties", click the "tools" tab, and select "Check Now" for error checking the disk, it usually makes reference to starting the check on the next reboot and looking in the log file for information on how the check did. The problem is that the damned user interface doesn't tell you where to find that log, and searching on the Web, on Microsoft's own site, and in Usenet newsgroups also generally isn't very clear on the topic. To find the results of a previous chkdisk, go into "Start->Control Panel" and doubleclick on "Administrative Tools". Then doubleclick on "Event Viewer", then select "Application". (This much the newsgroups say, but then what?) Now you will see a list of Application events. Look for the most recent "Winlogon" event. You can tell the date and time of the Winlogon event to see if that corresponds with the particular chkdsk you are interested in seeing the results for. Double click on it, and you will see the results of your chkdsk. By the way, don't worry if you see something like: Cleaning up 3 unused index entries from index $SII of file 0x9. Cleaning up 3 unused index entries from index $SDH of file 0x9. Cleaning up 3 unused security descriptors. Unused index entries and security descriptors supposedly accumulate whenever you delete a folder or file that had any custom settings on it and is not a sign of hard disk trouble and is to be expected. See the following excellent reference for details: http://www.jsiinc.com/SUBE/tip2200/rh2217.htm -- Brooke P. Anderson Brooke P. Anderson, Jan 10, 2004 #1 Advertisements Show Ignored Content Want to reply to this thread or ask your own question? It t