|
| |||||||||
| Tags: bsod, pfn_list_corrupt |
![]() |
| | Thread Tools | Search this Thread |
|
#1
| |||
| |||
| PFN_LIST_CORRUPT bsod
I woke up this morning to a blue screen. I have run dumpchk.exe on the minidump log, and have a text file of my pstat.exe data. I have run memtest for hours and no memory errors have been found. How can I further troubleshoot this error? Can anyone read the dumpchk and pstat files and help me determine how to fix this error? TIA, Leef |
|
#2
| |||
| |||
| Re: PFN_LIST_CORRUPT bsod
Information on STOP 0x4E: PFN_LIST_CORRUPT http://www.aumha.org/win5/kbestop.php#0x4e -- Ted Zieglar "You can do it if you try." "Leef" <leef1@texoma.net> wrote in message news:eKGk7msFGHA.2212@TK2MSFTNGP15.phx.gbl... > I woke up this morning to a blue screen. I have run dumpchk.exe on the > minidump log, and have a text file of my pstat.exe data. I have run memtest > for hours and no memory errors have been found. How can I further > troubleshoot this error? Can anyone read the dumpchk and pstat files and > help me determine how to fix this error? > > TIA, > Leef > > > |
|
#3
| |||
| |||
| Re: PFN_LIST_CORRUPT bsod
I have run memtest for hours and it finds 0 errors in the memory. I have run dumpchk on the minidump and it dies not give a faulting driver. Anything else that can cause this? "Ted Zieglar" <teddy.z@notmail.com> wrote in message news:%23FnE6ssFGHA.3200@tk2msftngp13.phx.gbl... > Information on STOP 0x4E: PFN_LIST_CORRUPT > http://www.aumha.org/win5/kbestop.php#0x4e > > > -- > Ted Zieglar > "You can do it if you try." > > "Leef" <leef1@texoma.net> wrote in message > news:eKGk7msFGHA.2212@TK2MSFTNGP15.phx.gbl... >> I woke up this morning to a blue screen. I have run dumpchk.exe on the >> minidump log, and have a text file of my pstat.exe data. I have run > memtest >> for hours and no memory errors have been found. How can I further >> troubleshoot this error? Can anyone read the dumpchk and pstat files and >> help me determine how to fix this error? >> >> TIA, >> Leef >> >> >> > |
|
#4
| |||
| |||
| Re: PFN_LIST_CORRUPT bsod
Leef How about posting the full text of the Stop Error message. I suggest you Disable automatic restart on system failure. This should help by allowing time to write down the STOP code properly. Right click on the My Computer icon on the Desktop and select Properties, Advanced, StartUp and Recovery, System Failure and uncheck box before Automatically Restart. Enable automatic restart on system failure after you have captured / copied and pasted the message in a further post here. There will also be Error Reports in Event Viewer. Please post copies. What you posted would be much easier to understand if you followed the advice in the last paragraph of this message. You can access Event Viewer by selecting Start, Administrative Tools, Event Viewer. When researching the meaning of the error, information regarding Event ID, Source and Description are important. HOW TO: View and Manage Event Logs in Event Viewer in Windows XP http://support.microsoft.com/default...&Product=winxp A tip for posting copies of Error Reports! Run Event Viewer and double click on the error you want to copy. In the window, which appears is a button resembling two pages. Double click the button and close Event Viewer. Now start your message (email) and do a paste into the body of the message. This will paste the info from the Event Viewer Error Report complete with links into the message. Make sure this is the first paste after exiting from Event Viewer. -- Hope this helps. Gerry ~~~~ FCA Stourport, England Enquire, plan and execute ~~~~~~~~~~~~~~~~~~~ "Leef" <leef1@texoma.net> wrote in message news:uAAvfHvFGHA.1180@TK2MSFTNGP09.phx.gbl... >I have run memtest for hours and it finds 0 errors in the memory. I have >run dumpchk on the minidump and it dies not give a faulting driver. >Anything else that can cause this? > > "Ted Zieglar" <teddy.z@notmail.com> wrote in message > news:%23FnE6ssFGHA.3200@tk2msftngp13.phx.gbl... >> Information on STOP 0x4E: PFN_LIST_CORRUPT >> http://www.aumha.org/win5/kbestop.php#0x4e >> >> >> -- >> Ted Zieglar >> "You can do it if you try." >> >> "Leef" <leef1@texoma.net> wrote in message >> news:eKGk7msFGHA.2212@TK2MSFTNGP15.phx.gbl... >>> I woke up this morning to a blue screen. I have run dumpchk.exe on the >>> minidump log, and have a text file of my pstat.exe data. I have run >> memtest >>> for hours and no memory errors have been found. How can I further >>> troubleshoot this error? Can anyone read the dumpchk and pstat files >>> and >>> help me determine how to fix this error? >>> >>> TIA, >>> Leef >>> >>> >>> >> > > |
|
#5
| |||
| |||
| Re: PFN_LIST_CORRUPT bsod
Here are the two related events from the Event Viewer. I did have "restart on error" turned off and the blue screen gave the same error code and parameters as below but the top of the error code had: PFN_LIST_CORRUPT. I ran pstat.exe after rebooting, but could find no offfending driver from the dumpcheck to check against it. And, I ran memtest overnight with NO memory errors. Event Type: Error Event Source: System Error Event Category: (102) Event ID: 1003 Date: 1/11/2006 Time: 7:22:51 AM User: N/A Computer: ALF Description: Error code 0000004e, parameter1 0000008f, parameter2 00011168, parameter3 ffffffff, parameter4 00000000. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 53 79 73 74 65 6d 20 45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64 65 ror code 0018: 20 30 30 30 30 30 30 34 0000004 0020: 65 20 20 50 61 72 61 6d e Param 0028: 65 74 65 72 73 20 30 30 eters 00 0030: 30 30 30 30 38 66 2c 20 00008f, 0038: 30 30 30 31 31 31 36 38 00011168 0040: 2c 20 66 66 66 66 66 66 , ffffff 0048: 66 66 2c 20 30 30 30 30 ff, 0000 0050: 30 30 30 30 0000 ============================================= Event Type: Information Event Source: Save Dump Event Category: None Event ID: 1001 Date: 1/11/2006 Time: 7:22:12 AM User: N/A Computer: ALF Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000008f, 0x00011168, 0xffffffff, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini011106-01.dmp. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Here is the content of the dumpchk which was run on the minidump from this error: ----- 32 bit Kernel Mini Dump Analysis DUMP_HEADER32: MajorVersion 0000000f MinorVersion 00000a28 DirectoryTableBase 06fe0000 PfnDataBase 81b13000 PsLoadedModuleList 805624a0 PsActiveProcessHead 80568558 MachineImageType 0000014c NumberProcessors 00000002 BugCheckCode 0000004e BugCheckParameter1 0000008f BugCheckParameter2 00011168 BugCheckParameter3 ffffffff BugCheckParameter4 00000000 PaeEnabled 00000000 KdDebuggerDataBlock 805522e0 MiniDumpFields 00000dff TRIAGE_DUMP32: ServicePackBuild 00000200 SizeOfDump 00010000 ValidOffset 0000fffc ContextOffset 00000320 ExceptionOffset 000007d0 MmOffset 00001068 UnloadedDriversOffset 000010a0 PrcbOffset 00001878 ProcessOffset 000024c8 ThreadOffset 00002728 CallStackOffset 00002980 SizeOfCallStack 0000087c DriverListOffset 00003490 DriverCount 00000095 StringPoolOffset 000060d0 StringPoolSize 000014c8 BrokenDriverOffset 00000000 TriageOptions 00000041 TopOfStack f79ba784 DebuggerDataOffset 00003200 DebuggerDataSize 00000290 DataBlocksOffset 00007598 DataBlocksCount 00000005 Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0 Debug session time: Wed Jan 11 03:26:40 2006 System Uptime: 0 days 18:47:32 start end module name 804d7000 806fd000 nt Checksum: 0020D6EC Timestamp: Tue Mar 01 18:57:27 2005 (42250F77) Unloaded modules: b4e0f000 b4e39000 kmixer.sys Timestamp: unavailable (00000000) b4e0f000 b4e39000 kmixer.sys Timestamp: unavailable (00000000) b4e0f000 b4e39000 kmixer.sys Timestamp: unavailable (00000000) b4e0f000 b4e39000 kmixer.sys Timestamp: unavailable (00000000) b4e89000 b4eb3000 kmixer.sys Timestamp: unavailable (00000000) b4e89000 b4eb3000 kmixer.sys Timestamp: unavailable (00000000) b4e89000 b4eb3000 kmixer.sys Timestamp: unavailable (00000000) b4e89000 b4eb3000 kmixer.sys Timestamp: unavailable (00000000) b4e89000 b4eb3000 kmixer.sys Timestamp: unavailable (00000000) b4e89000 b4eb3000 kmixer.sys Timestamp: unavailable (00000000) b4e89000 b4eb3000 kmixer.sys Timestamp: unavailable (00000000) b4e89000 b4eb3000 kmixer.sys Timestamp: unavailable (00000000) b50bb000 b50e5000 kmixer.sys Timestamp: unavailable (00000000) b6619000 b662b000 NAVENG.Sys Timestamp: unavailable (00000000) b662b000 b66e1000 NavEx15.Sys Timestamp: unavailable (00000000) b5c48000 b5c72000 kmixer.sys Timestamp: unavailable (00000000) f7cf7000 f7cf8000 drmkaud.sys Timestamp: unavailable (00000000) b5d8a000 b5d97000 DMusic.sys Timestamp: unavailable (00000000) b5c72000 b5c95000 aec.sys Timestamp: unavailable (00000000) b5f3a000 b5f48000 swmidi.sys Timestamp: unavailable (00000000) f7b4d000 f7b4f000 splitter.sys Timestamp: unavailable (00000000) f7803000 f780c000 processr.sys Timestamp: unavailable (00000000) f7883000 f7888000 Cdaudio.SYS Timestamp: unavailable (00000000) f7a47000 f7a4a000 Sfloppy.SYS Timestamp: unavailable (00000000) Finished dump check "Gerry Cornell" <gcjc@tenretnitb.com> wrote in message news:eacRY9vFGHA.2472@TK2MSFTNGP10.phx.gbl... > Leef > > How about posting the full text of the Stop Error message. > > I suggest you Disable automatic restart on system failure. This should > help by allowing time to write down the STOP code properly. Right click > on the My Computer icon on the Desktop and select Properties, Advanced, > StartUp and Recovery, System Failure and uncheck box before > Automatically Restart. > > Enable automatic restart on system failure after you have captured / > copied and pasted the message in a further post here. > > There will also be Error Reports in Event Viewer. Please post copies. > What you posted would be much easier to understand if you followed the > advice in the last paragraph of this message. > > You can access Event Viewer by selecting Start, Administrative Tools, > Event Viewer. When researching the meaning of the error, information > regarding Event ID, Source and Description are important. > > HOW TO: View and Manage Event Logs in Event Viewer in Windows XP > http://support.microsoft.com/default...&Product=winxp > > A tip for posting copies of Error Reports! Run Event Viewer and double > click on the error you want to copy. In the window, which appears is a > button resembling two pages. Double click the button and close Event > Viewer. Now start your message (email) and do a paste into the body of > the message. This will paste the info from the Event Viewer Error Report > complete with links into the message. Make sure this is the first paste > after exiting from Event Viewer. > > > > -- > > Hope this helps. > > Gerry > ~~~~ > FCA > Stourport, England > > Enquire, plan and execute > ~~~~~~~~~~~~~~~~~~~ > > > > > "Leef" <leef1@texoma.net> wrote in message > news:uAAvfHvFGHA.1180@TK2MSFTNGP09.phx.gbl... >>I have run memtest for hours and it finds 0 errors in the memory. I have >>run dumpchk on the minidump and it dies not give a faulting driver. >>Anything else that can cause this? >> >> "Ted Zieglar" <teddy.z@notmail.com> wrote in message >> news:%23FnE6ssFGHA.3200@tk2msftngp13.phx.gbl... >>> Information on STOP 0x4E: PFN_LIST_CORRUPT >>> http://www.aumha.org/win5/kbestop.php#0x4e >>> >>> >>> -- >>> Ted Zieglar >>> "You can do it if you try." >>> >>> "Leef" <leef1@texoma.net> wrote in message >>> news:eKGk7msFGHA.2212@TK2MSFTNGP15.phx.gbl... >>>> I woke up this morning to a blue screen. I have run dumpchk.exe on the >>>> minidump log, and have a text file of my pstat.exe data. I have run >>> memtest >>>> for hours and no memory errors have been found. How can I further >>>> troubleshoot this error? Can anyone read the dumpchk and pstat files >>>> and >>>> help me determine how to fix this error? >>>> >>>> TIA, >>>> Leef >>>> >>>> >>>> >>> >> >> > > |
![]() |
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "PFN_LIST_CORRUPT bsod" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| ‘Pfn_list_corrupt’ BSOD on Windows 7 x64 | Aerona | Windows x64 Edition | 6 | 22-06-2011 11:57 AM |
| Blue screen PFN_list_corrupt | Chain-SmokeR | Operating Systems | 4 | 23-07-2009 12:42 AM |
| BSOD - PFN_LIST_CORRUPT error | Halina | Operating Systems | 4 | 19-02-2009 07:40 PM |
| Error PFN_LIST_Corrupt with Blue Screen | goatape | Operating Systems | 2 | 18-02-2009 06:14 PM |
| Vista BSOD, am unable to shutdown without BSOD, logoff OK | Edward Ray | Vista Help | 4 | 29-01-2007 08:59 AM |