If you’re running Driver Verifier this is most probably memory overrun - the
address ending with 000 notes that next page was accessed.
So… don’t look for that address, but anything in the previous page, or a few
pages behind that (being that you do encryption filter, 64KB before this address
would probably be your allocated memory.)
Are you using pool tagging?
- Here is the -analyze -v, the memory address being accessed doesn`t appear
to have been allocated by me, but I am pretty sure that it was as it is only
on an encrypted file that this happens.
–
Kind regards, Dejan M. MVP for DDK
http://www.alfasp.com E-mail: xxxxx@alfasp.com
Alfa Transparent File Encryptor - Transparent file encryption services.
Alfa File Protector - File protection and hiding library for Win32 developers.
Alfa File Monitor - File monitoring library for Win32 developers.