If the driver reads or writes to the buffer after freeing it, Driver Verifier will issue Bug Check 0xCC. When the buffer is freed, Driver Verifier will detect the alteration and issue Bug Check 0xC1. If the driver writes in the memory prior to the beginning of the buffer, this will (presumably) alter the patterns. If the driver attempts to access memory after the end of the allocation, Driver Verifier will detect this immediately, and will issue Bug Check 0xCD. The previous page and the next page are marked inaccessible. The previous portion of the page is written with special patterns. The highest possible address that allows the allocation to fit on the page is returned, so that the memory is aligned with the end of the page. When the Special Pool feature is active and Verify End has been selected, each memory allocation requested by the driver is placed on a separate page. Note that the vast majority of memory corruptions are due to overruns, not underruns.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |