|
Home > Archive > 70-210 > April 2003 > Full of Errors
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| prezbedard 2003-04-03, 11:31 am |
| I was looking at this system log. It is from a computer that was having problems a bit ago but now it is chaulk full of errors that were not there before.
I have been examining it and been able to
pick things out here and there but I am having a lot of trouble understanding many of the files that the errors are indicating. Espcially the Windows File Protection errors.
Any help would be apprecited.
Thanks | |
| Carl660 2003-04-04, 3:20 pm |
| prezbedard,
I am relatively new in this arena, but I do know that if you look in the Event Viewer and get the Event ID and Source ID you can go to the Microsoft Technet website and find out what it means (in most cases anyway).
Just by looking at this file and the other attachment you posted, I would venture to guess that a program (or 2) got loaded that had numerous files that were not signed by Microsoft. This means that Microsoft has not verified that it will work with the operating system. In this case, it looks as if your Windows OS doesn't like the program and is rebelling.
NOTE: I am assuming that this computer and the computer you discussed in your other post are the same machine.
This could also be causing the other problem you posted; if it is also the same computer.
Hope this helps,
Carl | |
| prezbedard 2003-04-04, 4:38 pm |
| quote:
Originally posted by Carl660
prezbedard,
I am relatively new in this arena, but I do know that if you look in the Event Viewer and get the Event ID and Source ID you can go to the Microsoft Technet website and find out what it means (in most cases anyway).
Just by looking at this file and the other attachment you posted, I would venture to guess that a program (or 2) got loaded that had numerous files that were not signed by Microsoft. This means that Microsoft has not verified that it will work with the operating system. In this case, it looks as if your Windows OS doesn't like the program and is rebelling.
NOTE: I am assuming that this computer and the computer you discussed in your other post are the same machine.
This could also be causing the other problem you posted; if it is also the same computer.
Hope this helps,
Carl
Yes it is the same computer.
I have used technet many times to look up event IDs's but sometimes the search yields result that are not realtive to my particular problem and the solution does not help. I did look some of these last ones up.
Thanks |
|
|
|
|