Blue screen PFN_list_corrupt

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My computer shows a blue screen and dumps memory. The Stop info is
"PFN-list-corrupt. What is the simple way to repair this? Do I need to put
it in the shop?
 
DocMemory Diagnostic, an advanced self-bootable PC Memory
Diagnostic Software is a user friendly software designed to capture
all possible memory failures in PC.
http://www.simmtester.com/PAGE/products/doc/docinfo.asp

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

Get Windows XP Service Pack 2 with Advanced Security Technologies:
http://www.microsoft.com/athome/security/protect/windowsxp/choose.mspx

-------------------------------------------------------------------------------------------

:

| My computer shows a blue screen and dumps memory. The Stop info is
| "PFN-list-corrupt. What is the simple way to repair this? Do I need to put
| it in the shop?
 
Cause
This error is typically caused by drivers passing bad memory descriptor lists. For example, a driver might have called MmUnlockPages twice with the same list.

Bug Check 0x4E: PFN_LIST_CORRUPT
The PFN_LIST_CORRUPT bug check has a value of 0x0000004E. This indicates that the page frame number (PFN) list is corrupt.

Parameters
The following parameters are displayed on the blue screen. Parameter 1 indicates the type of violation. The meaning of the other parameters depends on the value of Parameter 1.

Parameter 1 Parameter 2 Parameter 3 Parameter 4 Cause of Error
0x01 The ListHead value which was corrupt The number of pages available 0 The list head was corrupt
0x02 The entry in the list being removed The highest physical page number The reference count of the entry being removed A list entry was corrupt
0x07 The page frame number The current share count 0 A driver has unlocked a page more times than it locked it
0x8F New page number Old page number 0 The free or zeroed page listhead is corrupt
0x99 Page frame number Current page state 0 A PTE or PFN is corrupt
 
I have service pack 2. Actually, I didn't have this problem untill
installing it. On the blue screen, it references uninstallint recently
installed software.
 
Always provide the exact text of any error message.

Type verifier in Start - Run and follow the wizard. This will make all drivers slower but error messages should contain the driver's name and all drivers get checked as they work. The error code may change as Windows is strict with drivers.

If errors stop you from booting then choose Last Known Good Configuration on the Startup menu that will appear.

Create a minidump. Type in Help, Small Memory Dump. Type
minidump
in Start Run to view any you may have created.

I would suggest that you get windows to display the blue screen rather than restart. It tells you how on the same page as how to make mini dumps.The reason you should display blue screens is if you blue screen while booting. Then you won't be able to boot to read event viewer.
 
This blue screen has an entire page of stuff. It doesn't stay up long enough
to write it all down. I get these messages asking if I want to report this
problem to Microsoft. No matter what I say, it shuts down and up comes this
blue screen.

Sorry, but this reply is a little over my head. I don't even know what
dumps are! Sorry..
 
Type in Help, Small Memory Dump. Type minidump
in Start Run to view any you may have created.

No minidump (small memory dump) no solution. The instructions in help are click this then that. Even a girl can do it. See http://groups.google.com.au/groups?...%3A+BSOD+constantly!&hl=en&btnG=Google+Search for an actual girl doing it.

But I require a modicum of common sense from you to solve your problem.

The page that will appear in help is titled "To specify what Windows does if the system stops unexpectedly". It will help set your blue screen of death (Stop error in MS terminology) options. Type event viewer in help to see how to start event viewer.
 
Linda K said:
OK Smart................. We'll see if I can do it.. I'll
take the challange.


Windows does if the system stops unexpectedly". It will help
set your blue screen of death (Stop error in MS terminology)
options. Type event viewer in help to see how to start event
viewer. > > This blue screen has an entire page of stuff. It
doesn't stay up long enough
 > > to write it all down. I get these messages asking
if I want to report this
 > > problem to Microsoft. No matter what I say, it
shuts down and up comes this
 > > blue screen.
 > >
 > > Sorry, but this reply is a little over my head. I
don't even know what
 > > dumps are! Sorry..
 > >
 > >
 > >
 > > "David Candy" wrote:
 > >
  > >> Always provide the exact text of any error
message.
  > >>
  > >> Type verifier in Start - Run and follow the
wizard. This will make all drivers slower but error messages
should contain the driver's name and all drivers get checked
as they work. The error code may change as Windows is strict
with drivers.
  > >>
  > >> If errors stop you from booting then choose
Last Known Good Configuration on the Startup menu that will
appear.
  > >>
  > >> Create a minidump. Type in Help, Small Memory
Dump. Type
  > >> minidump
  > >> in Start Run to view any you may have
created.
  > >>
  > >> I would suggest that you get windows to
display the blue screen rather than restart. It tells you how
on the same page as how to make mini dumps.The reason you
should display blue screens is if you blue screen while
booting. Then you won't be able to boot to read event viewer.
  > >>
  > >> --
  > >>
----------------------------------------------------------
  > >>
  > >> "Linda K"
<[email protected]> wrote in message
  > >> >I have service pack 2. Actually, I didn't
have this problem untill
  > >> > installing it. On the blue screen, it
references uninstallint recently
  > >> > installed software.
  > >> >
  > >> >
  > >> >
  > >> > "David Candy" wrote:
  > >> >
  > >> >> Cause
  > >> >> This error is typically caused by drivers
passing bad memory descriptor lists. For example, a driver
might have called MmUnlockPages twice with the same list.
  > >> >>
  > >> >> Bug Check 0x4E: PFN_LIST_CORRUPT
  > >> >> The PFN_LIST_CORRUPT bug check has a value
of 0x0000004E. This indicates that the page frame number (PFN)
list is corrupt.
  > >> >>
  > >> >> Parameters
  > >> >> The following parameters are displayed on
the blue screen. Parameter 1 indicates the type of violation.
The meaning of the other parameters depends on the value of
Parameter 1.
  > >> >>
  > >> >> Parameter 1 Parameter 2 Parameter 3
Parameter 4 Cause of Error
  > >> >> 0x01 The ListHead value which was
corrupt The number of pages available 0 The list head was
corrupt
  > >> >> 0x02 The entry in the list being
removed The highest physical page number The reference count
of the entry being removed A list entry was corrupt
  > >> >> 0x07 The page frame number The
current share count 0 A driver has unlocked a page more times
than it locked it
  > >> >> 0x8F New page number Old page number
0 The free or zeroed page listhead is corrupt
  > >> >> 0x99 Page frame number Current page
state 0 A PTE or PFN is corrupt
  > >> >>
  > >> >>
  > >> >> --
  > >> >>
----------------------------------------------------------
  > >> >>
  > >> >> "Carey Frisch [MVP]"
<[email protected]> wrote in message
  > >> >> > DocMemory Diagnostic, an advanced
self-bootable PC Memory
  > >> >> > Diagnostic Software is a user friendly
software designed to capture
  > >> >> > all possible memory failures in PC.
  > >> >> >
http://www.simmtester.com/PAGE/products/doc/docinfo.asp
  > >> >> >
  > >> >> > --
  > >> >> > Carey Frisch
  > >> >> > Microsoft MVP
  > >> >> > Windows XP - Shell/User
  > >> >> > Microsoft Newsgroups
  > >> >> >
  > >> >> > Get Windows XP Service Pack 2 with
Advanced Security Technologies:
  > >> >> >
http://www.microsoft.com/athome/security/protect/windowsxp/choose.mspx

  > >> >> >
  > >> >> >
--------------------------------------------------------------
-----------------------------
  > >> >> >
  > >> >> > "Linda K" wrote:
  > >> >> >
  > >> >> > | My computer shows a blue screen and
dumps memory. The Stop info is
  > >> >> > | "PFN-list-corrupt. What is the
simple way to repair this? Do I need to put
  > >> >> > | it in the shop?
  > >> >>
  > >>

Maybe this will work? Please let me know what happens.
I may have to go over to a co workers house tomorrow and try to fix
there computer. Please let me know what you all think.

1. Press F8 as the computer starts up.
2. Advanced Startup Options screen will come up.
3. Select Safe mode.
4. The computer should start up normally.
5. Click Start then All Programs then Accessories the System Tools.
6. Click System Restore.
7. Then Restore your computer to an earlier point.
 
Back
Top