How does a Windows Kernel mode Driver, access paged memory?
1) A usermode process has its own "address context", which maps the user-mode virtual addresses to a unique collection of physical page frames. That is, the meaning of any particular virtual address changes from one moment to the next as the Windows XP scheduler switches threads. Part of work of "switching threads" is to change the page tables so that they refer to the incoming thread’s process context. _ 2) A Windows Kernel-mode Driver executes in "arbitrary thread context". A driver may create a system thread and work in its context...but I am talking about the situation when one doesn't