I believe it's trying to display information which has been paged out to disk, which isn't available in a minidump.
Not particularly, as it would just show as invalid, pagefile: 0, and what offset in memory it's located at (as far as !pte goes). Here's my terrible one minute diagram:
Code:
proc # here: kd> !pte blah blah
VA blah blah
PDE at blah blah PTE at blah blah
contains blah blah contains blah blah
pfn blah blah ------------ not valid
PageFile: 0 < -- means we're off on the page file
Offset: <-- location in memory on pagefile here
Protect: blah blah
Rarely do you actually get !pte to dump anything in a small dump though as we know, you gotta get lucky.
@John, if you do a
!pte 3cab6f, if the PXE and PPE are available, you'll be able to see the output + the fact that the page directory and page table are missing. If PEB is in fact missing, this implies that the debugger is trying to access the user portion of the address space, which obviously isn't in anything but a complete dump, so it 's displaying in text form that the page it's trying to access isn't present.