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 use a UEFI boot-loader to deposit some data in a region of physical memory.
I would like to retrieve said data using a driver.
And with MmMapIoSpace that works great.
That is until I enable this driver verifier contraption of MSFT
With it it bugchecks 0x83 "The driver called MmMapIoSpace without having locked down the MDL pages. The physical pages represented by the physical address range being mapped must have been locked down prior to making this call."
How do I locked down the pages?
I saw many users here asking questions about MmMapIoSpace and driver verifier but it did not seam anyone of them got an answer, one suggestion was to use MmAllocateContiguousMemorySpecifyCache but that does not work probably because the UEFI allocates the region properly so that windows does not overwrite it.
So what I need is a foll prof way to read physical memory such that driver verifier does not complain.
Any help would be greatly appreciated.
|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!|
|Developing Minifilters||24 May 2021||Live, Online|
|Writing WDF Drivers||14 June 2021||Live, Online|
|Internals & Software Drivers||27 September 2021||Live, Online|
|Kernel Debugging||15 November 2021||Live, Online|