Re: HCT 11.2 Driver Verifier and Blue Screen

searching on msdn.microsoft.com for "DRIVER_VERIFIER_DETECTED_VIOLATION" one
of the first hits was:

http://msdn.microsoft.com/library/d...ccodes_7r1j.asp

param 1 2 3
4 explanation
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


you leaked 0xcfd0 # of bytes in non paged pool from 0x5f allocations.
!verifier 3 <drivername.sys> should dump out the address of the function
that made the allocation.

d

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sherwin Lim" <sherwinlim@avermedia.com.tw> wrote in message
news:u6Ev8RfQDHA.1560@TK2MSFTNGP12.phx.gbl...
>
> Hi,
>
> Since I dont know where the following questions should go, I am
> cross-posting this message on:
> microsoft.public.development.device.drivers
> microsoft.public.windowsxp.winlogo
>
> I ran Driver Verifier on a USB TV capture card device driver, and
> encountered blue screen.
>
> I need to find the root of the problem. When I used DumpChk on the
mememory
> dump, I found the following info:
>
> BugCheck Code = 0x000000C4
> BugCheck Param1 = 0x00000060
> BugCheck Param2 = 0x00000000
> BugCheck Param3 = 0x0000CFD0
> BugCheck Param4 = 0x0000005F
>
> After searching through MSDN, I know the bugcheck code means
> DRIVER_VERIFIER_DETECTED_VIOLATION. However, I need to know what the
> parameters mean, if anything at all.
>
> Also, what is the best way to start debugging blue screens? I've looked
> through Oney's Programming the MS WDM, but only found how to throw
> bugchecks, but not how to decipher a blue screen.
>
> Any help would be great.
>
> peace,
> sherwin
> sherwinlim@avermedia.com.tw
>
>