PDA

View Full Version : Install problem with bad unidentified driver


Mike Weigandt
December 11th 03, 07:17 AM
After upgrading a recent P4 PC with Windows 2K Pro to
Windows XP Pro, all applications appeared to work and the
upgrade appeared to be successful. About a week later,
without installing anything new, the system crashed upon
boot up with a message that the error may be submitted to
Microsoft for an online analysis. This analysis simply
stated that there was a driver problem without identifying
the driver or the device involved. Then this happened
again and again usually on booting the system but sometimes
abruptly while already in Windows. I checked that all
drivers were digitally signed and found those for the
video card were not, so I replaced the video card with an
ATI RADEON 7000 with signed drivers. Also for some reason
the Promise RAID Controller was still using the 2K driver
and I replaced it with the XP version. Still these random
crashes continued sometimes a day apart but sometimes a
week apart. I then decided to do a repair reinstall of XP
and during the install I got a message that an untested
driver (but without naming it) was encountered giving me
the option to continue installing it or not. Of course, I
chose not to install it. I figured that at last the
problem driver was found and everything should be fine
without it having been installed. That was last Saturday
and that day everything seemed to work fine. Yesterday I
was informed that a crash occurred again but perhaps with
a different message (I haven't seen it) saying that a
driver was installed improperly. I don't know if refusing
installation of the untested driver resulted in that. How
in the world can I identify the problem driver and/or
device involved in these crashes? I am left struggling
with this like a blind man. If I don't solve this very
soon I will suffer severe financial loss as the client is
beginning to ask for a refund of the purchase price of
this PC which was built by us for him. He no longer wants
a PC that can not be successfully upgraded to Windows XP.
Please try to help.

Rick \Nutcase\ Rogers
December 11th 03, 07:17 AM
Hi Mike,

Start/run eventvwr.msc, what do the system and application logs show?

Also, start/run sigverif.exe to check for any other unsigned drivers. Please
note that just because a driver is signed is no guarantee of 100%
compatibility. It may be a conflict with another installed driver.

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Win9x
Windows isn't rocket science! That's my other hobby!
http://mvp.support.microsoft.com/
Associate Expert - WinXP - Expert Zone
www.microsoft.com/windowsxp/expertzone
Win98 Help - www.rickrogers.org

"Mike Weigandt" > wrote in message
...
> After upgrading a recent P4 PC with Windows 2K Pro to
> Windows XP Pro, all applications appeared to work and the
> upgrade appeared to be successful. About a week later,
> without installing anything new, the system crashed upon
> boot up with a message that the error may be submitted to
> Microsoft for an online analysis. This analysis simply
> stated that there was a driver problem without identifying
> the driver or the device involved. Then this happened
> again and again usually on booting the system but sometimes
> abruptly while already in Windows. I checked that all
> drivers were digitally signed and found those for the
> video card were not, so I replaced the video card with an
> ATI RADEON 7000 with signed drivers. Also for some reason
> the Promise RAID Controller was still using the 2K driver
> and I replaced it with the XP version. Still these random
> crashes continued sometimes a day apart but sometimes a
> week apart. I then decided to do a repair reinstall of XP
> and during the install I got a message that an untested
> driver (but without naming it) was encountered giving me
> the option to continue installing it or not. Of course, I
> chose not to install it. I figured that at last the
> problem driver was found and everything should be fine
> without it having been installed. That was last Saturday
> and that day everything seemed to work fine. Yesterday I
> was informed that a crash occurred again but perhaps with
> a different message (I haven't seen it) saying that a
> driver was installed improperly. I don't know if refusing
> installation of the untested driver resulted in that. How
> in the world can I identify the problem driver and/or
> device involved in these crashes? I am left struggling
> with this like a blind man. If I don't solve this very
> soon I will suffer severe financial loss as the client is
> beginning to ask for a refund of the purchase price of
> this PC which was built by us for him. He no longer wants
> a PC that can not be successfully upgraded to Windows XP.
> Please try to help.

Google