4 Answers
No. Bootex.log is a file created by chkdsk.exe when it is run; its results are rolled into the main log after the system finished booting. If chkdsk.exe is interrupted, bootex.log can become corrupted. When chkdsk.exe runs again, it tries to write to bootex.log, which is, unfortunately, now corrupt. It doesn’t know this until after the check; so even though it was deleted by chkdsk.exe, it was written to in the mean time and is therefore still corrupt. The fix is to run under the Recovery console by either booting from the Windows XP CD or running i386winnt32.exe on the Windows XP CD with the argument /cmdcons. When in the console, run chkdsk.exe /p to fix the file. Then type del c:bootex.log to remove the offending file. Reboot, and all is taken care of.
Dear,
No. Bootex.log is a file created by chkdsk.exe when it is run; its results are rolled into the main log after the system finished booting. If chkdsk.exe is interrupted, bootex.log can become corrupted. When chkdsk.exe runs again, it tries to write to bootex.log, which is, unfortunately, now corrupt. It doesn’t know this until after the check; so even though it was deleted by chkdsk.exe, it was written to in the mean time and is therefore still corrupt. The fix is to run under the Recovery console by either booting from the Windows XP CD or running i386winnt32.exe on the Windows XP CD with the argument /cmdcons. When in the console, run chkdsk.exe /p to fix the file. Then type del c:bootex.log to remove the offending file. Reboot, and all is taken care of.
In case of further issues regarding computers & internet dont forget to contact via…
Yahoo! Groups
vijaysomanath – Customer Support Knowledge Database,
http://tech.groups.yahoo.com/group/vijaysomanath
¤ Regards, vijaysomanath
¤ http://www.spaces.msn.com/vijaysomanath
¤ Copyright © 1999-2006 vijaysomanath. All rights reserved.
Its associated with ChkDsk.exe (a disk checking utility that comes with Windows XP, and previous versions). ChkDsk.exe is also the file that sometimes runs automatically during boot up, that checks for disk errors.
Apparently ChkDsk.exe logs its progress and results to bootex.log while it is running. Then the next time Windows loads, it adds that information to the eventlog and deletes the bootex.log file. Sometimes, such as ChkDsk.exe being interrupted in the middle of a scan, the bootex.log can become corrupt. Windows can’t add it to the eventlog since it cant read the corrupt file, and therefor it is not deleted. One of my listed sources explains how to fix this.
I hope this helps.
Edit: Oh well. Sc©©ttY beat me with their cut-n-paste response from the annoyances site I list in my sources. Their response is the same as (and copied from) the sites I listed. In fact, it seems everyone is giving valid answers. Refer to software like HiJackThis (www.spywareinfo.com/~merijn/), adaware (www.lavasoftusa.com/), and Spybot Search and Destroy (http://www.safer-networking.org/) when you have suspect files in the future.
Sources:
http://discussions.hardwarecentral.com/showthread….
nope not a virus….. but you could have a virus attached to that file— so be carefull.