Verifier useless on XP

[Gil Baron]

HOW am I to find out which driver is giving a BSOD on my system. In the past you could use verifier.exe and it would intercept the failure and give the name of the driver, I cannot use it because even verifying only unsigned drivers the reboot goes to a loop. It gets to the Windows logo and then starts the boot process again. This repeats forever,
Is there a new toil? if not, what do I do. I just have too many drivers to tryremoving a few at a time or a binary search strategy.A total rebuild would be faster but I am not abiut to do that until I get a new computer.

 

[Guest]

Try reading article #816071 At microsoft.com

 

[Gil Baron]

Try reading article #816071 At microsoft.com

I read it and it has nothing to do with verifier.exe nor does it say anything about loop in bootup. You must have misunderstood my post. I still need suggestions here,

 

[Gil Baron]

HOW am I to find out which driver is giving a BSOD on my system. In the past you could use verifier.exe and it would intercept the failure and give the name of the driver, I cannot use it because even verifying only unsigned drivers thereboot goes to a loop. It gets to the Windows logo and then starts the boot process again. This repeats forever,
Is there a new toil? if not, what do I do. I just have too many drivers to try removing a few at a time or a binary search strategy.A total rebuild would befaster but I am not abiut to do that until I get a new computer.

PLEASE SOMEBODYM HELP ME
TIA

 

[AJR]

Modify the Boot.ini file by including the "/sos" switch - results in drivers
being listed as they are loaded.
Also have you considered checking - F8 select "enable boot logging" and
checking the ntbtlog.txt (C:|Windows)
to determine what is being loaded and filing.

 

[Gil Baron]

Modify the Boot.ini file by including the "/sos" switch - results in drivers
being listed as they are loaded.
Also have you considered checking - F8 select "enable boot logging" and
checking the ntbtlog.txt (C:|Windows)
to determine what is being loaded and filing.

I will try that as it ay show why boot faiks but may not, It us unlikeky to tell me which gives the BSOD since that hapens much later tan boot, It can run fordays first,