The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
I need to scan memory occupied by ntoskrnl.exe to find some specific data based on some pattern. It mostly works, but fails with 'paged fault in non-paged area'
if verifier is enabled or if amount of memory on test environment is less than 2GB. Do I understand correctly this is because windows unloads some of ntoskrnl.exe pages
or the root cause if different? I thought ntoskrnl.exe is one of most important components which should never be unloaded, no?
Anyway, I've made an experiment and wrapped all the access to ntoskrnl memory with MmIsAddressValid so that if memory is invalid - code just skips this particular byte
and searches starting from the next one. And... It stopped crashing but also stopped finding what I need under verifier.
The question: what is the right way of scanning all the memory occupied by ntoskrnl.exe ? If this is not possible at all, I probably could get what I need via loading another instance of ntoskrnl.exe and searching it. But in this case, do I understand correctly that I have to load it to non-paged memory? Or lock memory somehow? Is there any links which could help me?
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Writing WDF Drivers||7 Dec 2020||LIVE ONLINE|
|Internals & Software Drivers||25 Jan 2021||LIVE ONLINE|
|Developing Minifilters||8 March 2021||LIVE ONLINE|