[QUESTION] Page States and Numbers

x BlueRobot · Sep 20, 2013

Code:

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000002bdd6e, page frame number
Arg3: 0000000000000000, current page state
Arg4: 00000000002bddee, 0

I've got a quick question, page states can be of three things: free, reserved and committed. So with a Stop 0x4E bugcheck, which numbers correspond to what page state? For example, what page state is 0?

Vir Gnarus · Sep 23, 2013

Sorry mate, couldn't tell you. However, the states for the page may be more like valid, modified, etc., and not the states you're thinking of, which are virtual memory states, not physical memory states.

x BlueRobot · Sep 30, 2013

Thanks for responding Vir, I'll keep searching and hopefully find a answer :)

Search

Search

[QUESTION] Page States and Numbers

x BlueRobot

Administrator

Vir Gnarus

BSOD Kernel Dump Expert

x BlueRobot

Administrator