I have been using driver verifier for a while but never encountered
any issue until I saw one today. I recieved a crash dump of a bugcheck
on a remote system... The remote system has driver verifier turned on
and it gets a verifier induced bugcheck related to memory leak that I
need to debug.

after loading the crash dump, when I check for verifier...it gives
some errors and I am not able to debug any further..

Fyi, the verifier works fine if I debug through a local session when
debugging the target..however the problem isnt reproduced here.

Here is the error when I use !verifier 1( or other options)...It does
output part of the spew but doesnt output the last important
information....

Current paged pool allocations 0x0 for 00000000 bytes
Peak paged pool allocations 0x52 for 0017C058 bytes
Current nonpaged pool allocations 0x1 for 00000020 bytes
Peak nonpaged pool allocations 0x4c2b for 0452BB80 bytes

GetPointerFromAddress: unable to read from 81b39868
Unable to read MiSystemVaType memory at 81b19420

any help appreciated!

Thanks

what is the output of !analyze -v?

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


<amparikh@gmail.com> wrote in message
news:01094657-4f28-4b3b-842b-58360d19a78c@q27g2000prf.googlegroups.com...

Why do you need running verifier on a dump?

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

<amparikh@gmail.com> wrote in message
news:01094657-4f28-4b3b-842b-58360d19a78c@q27g2000prf.googlegroups.com...