[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 952
  • Last Modified:

PFN_LIST_CORRUPT (4e)

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: 00000099, A PTE or PFN is corrupt
Arg2: 00000000, page frame number
Arg3: 00000000, current page state
Arg4: 00000000, 0

Debugging Details:
------------------


DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x4E

PROCESS_NAME:  AgentSrv.exe

LAST_CONTROL_TRANSFER:  from 80501d05 to 804f8a51

STACK_TEXT:  
a9ca5a78 80501d05 0000004e 00000099 00000000 nt!KeBugCheckEx+0x1b
a9ca5ab0 805021ca 01000014 c07e4808 00000000 nt!MiEliminateWorkingSetEntry+0x27d
a9ca5ad8 80502694 00000014 c0883cfc c07e4808 nt!MiFreeWsle+0x4e
a9ca5b08 80640b75 81b924f8 00000001 81b92300 nt!MiEmptyWorkingSet+0x132
a9ca5b38 805c2781 ffffffff ffffffff 00000000 nt!MmAdjustWorkingSetSizeEx+0x5f
a9ca5bf8 805c2b61 ffffffff 00000001 00edff30 nt!PspSetQuotaLimits+0x1f5
a9ca5d4c 8053c958 ffffffff 00000001 00edff30 nt!NtSetInformationProcess+0x393
a9ca5d4c 7c90eb94 ffffffff 00000001 00edff30 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
00edff50 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MiEliminateWorkingSetEntry+27d
80501d05 8b4708          mov     eax,dword ptr [edi+8]

SYMBOL_STACK_INDEX:  1
Hello

I've been having some strange problems with one of my computers, it keeps crashing, I got one BSOD, I have some Master Browser error in my Event Viewer and cant seems to find the problem, any ideas?

this is the log from Microsft windb.exe memory dump debugger from last crash


FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  433b28b7

SYMBOL_NAME:  nt!MiEliminateWorkingSetEntry+27d

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x4E_nt!MiEliminateWorkingSetEntry+27d

BUCKET_ID:  0x4E_nt!MiEliminateWorkingSetEntry+27d

Followup: MachineOwner
0
piotrmikula108
Asked:
piotrmikula108
  • 2
1 Solution
 
jkrCommented:
Looks like a classic case of defective RAM. Can you rult that out by using a memory test utility like 'MemTest' (http://www.hcidesign.com/memtest/) or exchanging it?
0
 
piotrmikula108Author Commented:
Hello

thank you for that tool, how long does it take to run it for 512RAM? I typed in 512 for memory size and it did only 0.5% in 2 hours, veeeeeery slooooooooow ;-)

Peter
0
 
jkrCommented:
It has to be slow to reliably test that. Take you time and be happy about not testing 2GB ;o)
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now