The Unknown P
January 5th 04, 11:40 PM
It's now known as the "event viewer" and is found in your
administrative tools in the control panel or under the
start button if you enable aministrative tools by right
clicking the start button then click properties\start menu
tab\customize button\advanced tab then scroll to the
bottom and you can put your admin tools in one of two
places. I use the "display on all programs and start menu"
selection. The event viewer contains three logs.
Applications,System,and Security. Double click on the
applications log to start and look for any red Xs in the
right panel. Double click them to open the details window.
This will not only tell you the application that caused
your problem but sometimes the very module as well. If you
have too many red Xs to figure out which one corresponds
to your BSOD then clear all events in all logs and then
start with an empty log and the next time you BSOD get up
and running and look at the event viewer to see what event
corresponds to the time you BSOD. 90% of BSOD's in XP are
caused by the failure to update the drivers from each
manufacturers site of your hardware. This includes mother
boards, sound cards, video cards, mouse, keyboard,
monitor, printer, camera and so on. The generic drivers
provided by Microsoft only allow minimal functionality and
when a piece of hardware calls for a higher function that
just isn't there then lockup and BSODs occur. Have fun.
administrative tools in the control panel or under the
start button if you enable aministrative tools by right
clicking the start button then click properties\start menu
tab\customize button\advanced tab then scroll to the
bottom and you can put your admin tools in one of two
places. I use the "display on all programs and start menu"
selection. The event viewer contains three logs.
Applications,System,and Security. Double click on the
applications log to start and look for any red Xs in the
right panel. Double click them to open the details window.
This will not only tell you the application that caused
your problem but sometimes the very module as well. If you
have too many red Xs to figure out which one corresponds
to your BSOD then clear all events in all logs and then
start with an empty log and the next time you BSOD get up
and running and look at the event viewer to see what event
corresponds to the time you BSOD. 90% of BSOD's in XP are
caused by the failure to update the drivers from each
manufacturers site of your hardware. This includes mother
boards, sound cards, video cards, mouse, keyboard,
monitor, printer, camera and so on. The generic drivers
provided by Microsoft only allow minimal functionality and
when a piece of hardware calls for a higher function that
just isn't there then lockup and BSODs occur. Have fun.