Open the Event Viewer utility in your Administrative Tools control panel and look through your System and Application logs for entries flagged with "Error" or "Warning", especially those whose time-stamps coincide with the occurence of the problem(s). Double-clicking on such an entry will open a properties window with more detailed information on the error; post the details from a representative sample of some of the different error messages (please don't post duplicates of a given entry, or flood us with the entire contents of the logs).
To post the details:
In the Properties window of a given entry, click on the button with the graphic of two pieces of paper on it; the button is at the right of the window just below the up arrow/down arrow buttons. You won't see anything happen when you click the button, but it will copy all of the details to the Windows clipboard. You can then paste the details into your next post here.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
Unfortunately, "5.1.2600.2180" is the verison number associated with Windows XP itself, as well as many of the software components built for that OS. In other words, seeing that number listed as the AppVer in errors really doesn't tell us anything specific.
Can you give us more detail and background on the errors, please? How often they occur, whether or not they seem to be related to running a certain program or performing a certain task, and any other such clues would be helpful.
Also- have you scanned your system for malicious infections lately? Some virus/spyware infections can cause such errors.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
Next I will try to start deleting and uninstalling unused and barely used programs, then rolling back drivers of anything I can think of, I hear it could be any service or any driver causing this. I hate to disable start up programs and services one by one and rebooting every time, It seems like a lot of work, but it might ultimately be my only solution...
Unfortunately, having no more definitive clues, thatwould be the next procedure to try. It might also help you pinpoint the shutdown problem.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370