Invalid Page Faults
A page fault isn't really a fault; it's part of the operation of the "memory manager", which during its turn is part of Windows' Virtual Machine Manager (Vmm32.vxd). Vmm32.vxd controls and incorporates all of the Virtual Machines in Windows, so there is no separate memory manager file.
The VMM allows applications to address more memory space than your RAM actually has, and it uses paging to accomplish this. For example: if you have 32 Mb of RAM, the VMM can make your applications believe that there is 80 Mb of memory, or even more, depending on what is necessary. It creates a Swap File on your hard disk (Win386.swp, in the Windows folder and variable in size) in which it stores pieces of memory that would normally reside in the RAM. Those pieces of data or code, 4 Kb each, are called pages.
Code and date are loaded in the virtual memory, i.e. RAM and Swap File. If a page that is on disk is needed by a process, the processor generates a page fault and the page will be paged into physical memory (RAM).
In other words: whenever a page in the Swap File is needed in physical RAM, the Virtual Memory Manager swaps the page for another page that was in the physical RAM and will now be "paged" to the Swap File on disk.
When an application causes an invalid page fault in a module, it means that it tried to load a page into an address space that was occupied by the module, which should run in a protected memory space anyway. If the module belongs to the Windows Kernel, it is likely that not only the application, but the operating system will crash.
The real question is: How and why does the application cause the invalid page fault? It could be a bug, or just a badly written application, or even a corrupted Vmm32.vxd.
In any case it should be clear that is it necessarily not the module itself. Kernel32.dll takes care of memory management, handling input/output operations and interrupts etc. For every action taken in a Windows application, Kernel32.dll is involved.