Is there a newer reference for bugcheck codes than windbg helpfile?
I'm getting Driver Verifier error (C4) with P1=60, it is not listed in windbg helpfile.

Thanks,
-- PA

Re: Driver Verifier error 60 by Nick

Nick
Tue Sep 02 18:07:21 CDT 2003

It's there...

"The following parameters are used only when the Memory Pool Tracking
option of Driver Verifier is active:

0x60 - Bytes allocated from paged pool - Bytes allocated from nonpaged
pool - Total number of unfreed allocations - The driver is unloading
without first freeing all its memory pools."

Pavel A. wrote:

> Is there a newer reference for bugcheck codes than windbg helpfile?
> I'm getting Driver Verifier error (C4) with P1=60, it is not listed in windbg helpfile.
>
> Thanks,
> -- PA
>
>

--
Nick Ryan (MVP for DDK)


Re: Driver Verifier error 60 by Pavel

Pavel
Tue Sep 02 19:43:05 CDT 2003

Sorry... my damn old eyes :(


"Nick Ryan" <nryan@nryan.com> wrote in message news:vla8lb3a3336ec@corp.supernews.com...
> It's there...
>
> "The following parameters are used only when the Memory Pool Tracking
> option of Driver Verifier is active:
>
> 0x60 - Bytes allocated from paged pool - Bytes allocated from nonpaged
> pool - Total number of unfreed allocations - The driver is unloading
> without first freeing all its memory pools."
>
> Pavel A. wrote:
>
> > Is there a newer reference for bugcheck codes than windbg helpfile?
> > I'm getting Driver Verifier error (C4) with P1=60, it is not listed in windbg helpfile.
> >
> > Thanks,
> > -- PA
> >
> >
>
> --
> Nick Ryan (MVP for DDK)
>