Prev: error: IE unable to update RSS feed and will try again later
Next: istaling windows
From: mynick on 4 Jan 2010 14:30
if you point it to win\sys32\drivers can it detect corruption of the
driver that causes boot stop(at volsnap.sys so bootlog is not
written)?
how about verifier.exe tool in the same situation?
From: MowGreen on 5 Jan 2010 13:17
mynick wrote:

> if you point it to win\sys32\drivers can it detect corruption of the
> driver that causes boot stop(at volsnap.sys so bootlog is not
> written)?
> how about verifier.exe tool in the same situation?



sigverif.exe determines if a driver is digitally signed:
http://support.microsoft.com/kb/308514

Driver Verifier (verifier.exe) provides the following capabilities -
Pool Allocations
Provide Extreme Memory Pressure
Parameter Validation
Pool Allocation Injection Failure
Pool Being Freed
Pool Leakage Detection
Driver Unload Checking
I/O Verifier

Using Driver Verifier to identify issues with Windows drivers for
advanced users
http://support.microsoft.com/kb/244617



MowGreen
===============
*-343-* FDNY
Never Forgotten
===============

banthecheck.com
"Security updates should *never* have *non-security content* prechecked"
From: mynick on 6 Jan 2010 09:03
On Jan 5, 7:17 pm, MowGreen <mowgr...(a)nowandzen.com> wrote:
> mynick wrote:
> > if you point it to win\sys32\drivers can it detect  corruption of the
> > driver that causes boot stop(at volsnap.sys so bootlog is not
> > written)?
> > how about verifier.exe tool in the same situation?
>
> sigverif.exe determines if a driver is digitally signed:http://support.microsoft.com/kb/308514
>
> Driver Verifier (verifier.exe) provides the following capabilities -
> Pool Allocations
> Provide Extreme Memory Pressure
> Parameter Validation
> Pool Allocation Injection Failure
> Pool Being Freed
> Pool Leakage Detection
> Driver Unload Checking
> I/O Verifier
>
> Using Driver Verifier to identify issues with Windows drivers for
> advanced usershttp://support.microsoft.com/kb/244617
>
> MowGreen
> ===============
>   *-343-*  FDNY
> Never Forgotten
> ===============
>
> banthecheck.com
> "Security updates should *never* have *non-security content* prechecked"

is it possbile use Verifier from recovery xp/cd recovery console
because system cannot boot due to driver error?
From: John John - MVP on 6 Jan 2010 09:23
mynick wrote:
> On Jan 5, 7:17 pm, MowGreen <mowgr...(a)nowandzen.com> wrote:
>> mynick wrote:
>>> if you point it to win\sys32\drivers can it detect corruption of the
>>> driver that causes boot stop(at volsnap.sys so bootlog is not
>>> written)?
>>> how about verifier.exe tool in the same situation?
>> sigverif.exe determines if a driver is digitally signed:http://support.microsoft.com/kb/308514
>>
>> Driver Verifier (verifier.exe) provides the following capabilities -
>> Pool Allocations
>> Provide Extreme Memory Pressure
>> Parameter Validation
>> Pool Allocation Injection Failure
>> Pool Being Freed
>> Pool Leakage Detection
>> Driver Unload Checking
>> I/O Verifier
>>
>> Using Driver Verifier to identify issues with Windows drivers for
>> advanced usershttp://support.microsoft.com/kb/244617
>>
>> MowGreen
>> ===============
>> *-343-* FDNY
>> Never Forgotten
>> ===============
>>
>> banthecheck.com
>> "Security updates should *never* have *non-security content* prechecked"
>
> is it possbile use Verifier from recovery xp/cd recovery console
> because system cannot boot due to driver error?

No, but you can disable the driver from the Recovery Console, use the
DISABLE command. For help on the command do: HELP DISABLE for help on
the command. For a list of services that can be disabled do LISTSVC.

http://support.microsoft.com/kb/314058
Description of the Windows XP Recovery Console for advanced users

John
From: mynick on 6 Jan 2010 10:31
On Jan 6, 3:23 pm, John John - MVP <audetw...(a)nbnot.nb.ca> wrote:
> mynick wrote:
> > On Jan 5, 7:17 pm, MowGreen <mowgr...(a)nowandzen.com> wrote:
> >> mynick wrote:
> >>> if you point it to win\sys32\drivers can it detect  corruption of the
> >>> driver that causes boot stop(at volsnap.sys so bootlog is not
> >>> written)?
> >>> how about verifier.exe tool in the same situation?
> >> sigverif.exe determines if a driver is digitally signed:http://support..microsoft.com/kb/308514
>
> >> Driver Verifier (verifier.exe) provides the following capabilities -
> >> Pool Allocations
> >> Provide Extreme Memory Pressure
> >> Parameter Validation
> >> Pool Allocation Injection Failure
> >> Pool Being Freed
> >> Pool Leakage Detection
> >> Driver Unload Checking
> >> I/O Verifier
>
> >> Using Driver Verifier to identify issues with Windows drivers for
> >> advanced usershttp://support.microsoft.com/kb/244617
>
> >> MowGreen
> >> ===============
> >>   *-343-*  FDNY
> >> Never Forgotten
> >> ===============
>
> >> banthecheck.com
> >> "Security updates should *never* have *non-security content* prechecked"
>
> > is it possbile use Verifier from recovery xp/cd recovery console
> > because system cannot boot due to driver error?
>
> No, but you can disable the driver from the Recovery Console, use the
> DISABLE command.  For help on the command do:  HELP DISABLE for help on
> the command.  For a list of services that can be disabled do LISTSVC.
>
> http://support.microsoft.com/kb/314058
> Description of the Windows XP Recovery Console for advanced users
>
> John

ok thanks
where can one find the order of loading the drivers during boot
I guess all drivers are noted in registry but is there a predetermined
load list
 |  Next  |  Last
Pages: 1 2
Prev: error: IE unable to update RSS feed and will try again later
Next: istaling windows