Actually an unmapped page will cause a #PF - Page Fault. If you’re running
at an IRQL < DISPATCH_LEVEL and the physical frame corresponding to the
virtual address is swapped out to disk and a #PF occurs then the exception
will be handled and execution will continue as no exception occurred.
However, if you’re running at IRQL >= DISPATCH_LEVEL or the virtual address
has no corresponding physical frame a #PF will trigger a BSOD.
In the context of accessing invalid memory regions a GP is only generated
when using non-canonical memory addresses, i.e. bits 63 to 47 must all have
the same value (all 1’s or all 0’s) - this is not something you should
worry about.
On 29 July 2015 at 02:18, wrote:
> A page in the virtual address space is either mapped to an actual physical
> page, and thus accessible, or not mapped, and thus any access will cause a
> GPF - General Protection Fault.
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>