Driver caused 'crashes'

[Clavin Schwindt]

Periodically my XP-Pro system recovers from a "serious error." MS tells me it was caused by an unidentified driver- hardware or software. Is there a way to produce a list of all the drivers employed by my system? Any suggestion for finding the offender? Thanks. CGS

 

[Rick \Nutcase\ Rogers]

Hi Clavin,

Producing a list is easy, but it may not help you identify the problem.

To produce the list, start/run sigverif.exe. Use the options to create a
log, this you can view after it completes the run (takes a few minutes). It
will also give you a list of unsigned drivers, though these may not
necessarily be the problem, it only indicates that they were not run through
logo testing before release. This does not mean they are bad, or that they
are not compatible.

Your better bet is to start/run eventvwr.msc and check the system logs for
clues. The details of the errors may hold clues as to which driver is
causing the problem.

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Win9x
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone



Periodically my XP-Pro system recovers from a "serious error." MS tells me
it was caused by an unidentified driver- hardware or software. Is there a
way to produce a list of all the drivers employed by my system? Any
suggestion for finding the offender? Thanks. CGS

 

[Clavin Schwindt]

Rick: Thanks for the info. I'll let you know 'how it goes.' CGS

 

[Clavin Schwindt]

Rick: I found the following: 5 "Warning" entries one after the other with
"source"='cdrom' and "event" noted as "51." Then a few minutes later there
are two "Error" entries 2 minutes apart with "Source" = 'cdrom' and "Event"
= '11.' What is the significance of the "51" and "11" entries?
In addition to the built in CDROM, I have an external 'burner.' Which of
these are the entries directed toward?
There was no "blue" or "black" screen crash, the "recovered from a serious
error" message came up the next time I booted up, totally unexpected.
Additional advice will be greatly appreciated. CGS

 

[Rick \Nutcase\ Rogers]

Hi Clavin,

Not sure what it means, but I did find this:

Information About Event ID 51
http://support.microsoft.com/?kbid=244780

It may be that your drive requires a firmware update.

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Win9x
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone

 

[Clavin Schwindt]

Rick: I followed the links on your initial reference, and I came to this
http://support.microsoft.com/default.aspx?scid=kb;EN-US;159865 which tells
how to ID a drive from an 'event' #. However, the XP "OS" is not referenced;
"2000" and "NT" are. Would it be safe to proceed as this article outlines,
despite no direct reference to "XP?" I am using "XP-Pro." I recognize the
need to backup my Registry, if I go into this, as noted in the initial KB
article. I may have to defer to someone with more experience in these
matters, but I am sure the help you have provided will facilitate finding
the "culprit." Many thanks! CGS

 

[Rick \Nutcase\ Rogers]

Hi Clavin,

The registry instructions in that article are only for identifying the
problem, there is no actual work done on it. You can extract the same
information from the disk manager (start/run diskmgmt.msc), without taking
any chances.

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Win9x
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone

 

[Clavin Schwindt]

Rick: Thanks for the added info. I will go that easier route. CGS