I have another question for the group regarding the use of Windbg. When
performing a post mortem analysis on a memory.dmp file, or even in a
live kernel debug session, is it possible to determine in Windbg if the
Driver Verifier is in use?
For example, I recently came across a SAP application server that was
running low on PTE’s, causing application failures to occur. In the end
it was discovered the Driver Verifier had previously been enabled, but
forgotten by the server administrators. This server was already running
low on PTE’s due to the application load and /3gb memory tuning, but
Driver Verifier consumed enough PTE’s to push the server over the edge
resource wise. In this circumstance, Driver Verifier wasn’t throwing an
exception, but the fact that it was running was causing significant
performance issues. If I’m looking at a LiveKD session in Windbg, or
if I’m analyzing a kernel memory dump, how would I determine if Driver
Verifier was enabled from within Windbg?
!verifier
At 09:56 AM 6/22/2005 -0500, you wrote:
I have another question for the group regarding the use of Windbg. When
performing a post mortem analysis on a memory.dmp file, or even in a live
kernel debug session, is it possible to determine in Windbg if the Driver
Verifier is in use?
For example, I recently came across a SAP application server that was
running low on PTE’s, causing application failures to occur. In the end
it was discovered the Driver Verifier had previously been enabled, but
forgotten by the server administrators. This server was already running
low on PTE’s due to the application load and /3gb memory tuning, but
Driver Verifier consumed enough PTE’s to push the server over the edge
resource wise. In this circumstance, Driver Verifier wasn’t throwing an
exception, but the fact that it was running was causing significant
performance issues. If I’m looking at a LiveKD session in Windbg, or if
I’m analyzing a kernel memory dump, how would I determine if Driver
Verifier was enabled from within Windbg?
You are currently subscribed to windbg as: xxxxx@privtek.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Look at the top of the command window when you load the crash dump file.
There should be some banners/splash/brag printing from DV.
–
The personal opinion of
Gary G. Little
–
The personal opinion of
Gary G. Little
“Kurt Congdon” wrote in message news:xxxxx@windbg…
>I have another question for the group regarding the use of Windbg. When
>performing a post mortem analysis on a memory.dmp file, or even in a live
>kernel debug session, is it possible to determine in Windbg if the Driver
>Verifier is in use?
> For example, I recently came across a SAP application server that was
> running low on PTE’s, causing application failures to occur. In the end
> it was discovered the Driver Verifier had previously been enabled, but
> forgotten by the server administrators. This server was already running
> low on PTE’s due to the application load and /3gb memory tuning, but
> Driver Verifier consumed enough PTE’s to push the server over the edge
> resource wise. In this circumstance, Driver Verifier wasn’t throwing an
> exception, but the fact that it was running was causing significant
> performance issues. If I’m looking at a LiveKD session in Windbg, or if
> I’m analyzing a kernel memory dump, how would I determine if Driver
> Verifier was enabled from within Windbg?
>
>
>
!duh. Yeah … !verifier is of course the best.
–
The personal opinion of
Gary G. Little
“Gary G. Little” wrote in message news:xxxxx@windbg…
> Look at the top of the command window when you load the crash dump file.
> There should be some banners/splash/brag printing from DV.
>
> –
> The personal opinion of
> Gary G. Little
>
> –
> The personal opinion of
> Gary G. Little
>
> “Kurt Congdon” wrote in message news:xxxxx@windbg…
>>I have another question for the group regarding the use of Windbg. When
>>performing a post mortem analysis on a memory.dmp file, or even in a live
>>kernel debug session, is it possible to determine in Windbg if the Driver
>>Verifier is in use?
>> For example, I recently came across a SAP application server that was
>> running low on PTE’s, causing application failures to occur. In the end
>> it was discovered the Driver Verifier had previously been enabled, but
>> forgotten by the server administrators. This server was already running
>> low on PTE’s due to the application load and /3gb memory tuning, but
>> Driver Verifier consumed enough PTE’s to push the server over the edge
>> resource wise. In this circumstance, Driver Verifier wasn’t throwing an
>> exception, but the fact that it was running was causing significant
>> performance issues. If I’m looking at a LiveKD session in Windbg, or if
>> I’m analyzing a kernel memory dump, how would I determine if Driver
>> Verifier was enabled from within Windbg?
>>
>>
>>
>
>
>
> !duh
What does that command do? I can’t find it in the docs. Is it a private
extension?
At 10:37 AM 6/22/2005 -0500, you wrote:
!duh. Yeah … !verifier is of course the best.
–
The personal opinion of
Gary G. Little
“Gary G. Little” wrote in message news:xxxxx@windbg…
> > Look at the top of the command window when you load the crash dump file.
> > There should be some banners/splash/brag printing from DV.
> >
> > –
> > The personal opinion of
> > Gary G. Little
> >
> > –
> > The personal opinion of
> > Gary G. Little
> >
> > “Kurt Congdon” wrote in message news:xxxxx@windbg…
> >>I have another question for the group regarding the use of Windbg. When
> >>performing a post mortem analysis on a memory.dmp file, or even in a live
> >>kernel debug session, is it possible to determine in Windbg if the Driver
> >>Verifier is in use?
> >> For example, I recently came across a SAP application server that was
> >> running low on PTE’s, causing application failures to occur. In the end
> >> it was discovered the Driver Verifier had previously been enabled, but
> >> forgotten by the server administrators. This server was already running
> >> low on PTE’s due to the application load and /3gb memory tuning, but
> >> Driver Verifier consumed enough PTE’s to push the server over the edge
> >> resource wise. In this circumstance, Driver Verifier wasn’t throwing an
> >> exception, but the fact that it was running was causing significant
> >> performance issues. If I’m looking at a LiveKD session in Windbg, or if
> >> I’m analyzing a kernel memory dump, how would I determine if Driver
> >> Verifier was enabled from within Windbg?
> >>
> >>
> >>
> >
> >
> >
>
>
>
>—
>You are currently subscribed to windbg as: xxxxx@privtek.com
>To unsubscribe send a blank email to xxxxx@lists.osr.com
When you enter this command, an arm reaches out from your PC/Laptop, smacks
you up the back to the head and as it goes back you hear a voice that sadly
says “Think before you type …”
–
The personal opinion of
Gary G. Little
“Dan Kyler” wrote in message news:xxxxx@windbg…
> > !duh
>
> What does that command do? I can’t find it in the docs. Is it a private
> extension?
>
>
> At 10:37 AM 6/22/2005 -0500, you wrote:
>>!duh. Yeah … !verifier is of course the best.
>>
>>–
>>The personal opinion of
>>Gary G. Little
>>
>>“Gary G. Little” wrote in message news:xxxxx@windbg…
>> > Look at the top of the command window when you load the crash dump
>> > file.
>> > There should be some banners/splash/brag printing from DV.
>> >
>> > –
>> > The personal opinion of
>> > Gary G. Little
>> >
>> > –
>> > The personal opinion of
>> > Gary G. Little
>> >
>> > “Kurt Congdon” wrote in message news:xxxxx@windbg…
>> >>I have another question for the group regarding the use of Windbg.
>> >>When
>> >>performing a post mortem analysis on a memory.dmp file, or even in a
>> >>live
>> >>kernel debug session, is it possible to determine in Windbg if the
>> >>Driver
>> >>Verifier is in use?
>> >> For example, I recently came across a SAP application server that was
>> >> running low on PTE’s, causing application failures to occur. In the
>> >> end
>> >> it was discovered the Driver Verifier had previously been enabled, but
>> >> forgotten by the server administrators. This server was already
>> >> running
>> >> low on PTE’s due to the application load and /3gb memory tuning, but
>> >> Driver Verifier consumed enough PTE’s to push the server over the edge
>> >> resource wise. In this circumstance, Driver Verifier wasn’t throwing
>> >> an
>> >> exception, but the fact that it was running was causing significant
>> >> performance issues. If I’m looking at a LiveKD session in Windbg, or
>> >> if
>> >> I’m analyzing a kernel memory dump, how would I determine if Driver
>> >> Verifier was enabled from within Windbg?
>> >>
>> >>
>> >>
>> >
>> >
>> >
>>
>>
>>
>>—
>>You are currently subscribed to windbg as: xxxxx@privtek.com
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>