Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PFN_LIST_CORRUPT at logoff or shutdown 1

Status
Not open for further replies.

DonL2x

Programmer
Feb 6, 2003
9
I have started getting occasional NT 4.0 PFN_LIST_CORRUPT (0x0000004E) blue screen errors at logoff and/or shutdown. I have replaced my RDRAM which has not helped. No new drivers have been added for a long, long time. Only system software changes made have been Microsoft recommended updates.

Does anybody else have any ideas as to what else might be causing this problem ?

Thanks

don

 
Might be time to update your drivers...

Go looking on the manufacturers site and if thats no good, (username: drivers , password: all).

When was the last time you ran check disk?

Have you tried reapplying \ updating your service packs?

How often do you run maintenance on your computer (check disk, defrag, anti virus, clearing temp files etc)?
 
Don,

I have expierienced this as well as 3-4 other STOP errors on 6 different NT machines here at work. It all happened after I updated to the latest IE Service Pack as well as all the Hotfixes three weeks ago. I am still working on which one exactly it is but it is definately one of the patches we installed. Before that we had no problems at all, and with machines ranging from Pentium-2 350, Pentium-3 733, AMD XP 2100, I feel that the problem is not hardware or driver related. I will keep looking, and let me know if you find out anything as well.
 

Virus files are updated daily. Disk scan, defrag, temp file clearing, Microsoft updates, etc performed every 30 days as part of backup procedure. The system is well maintained and backed up.

Since I have had no hardware problems (RDRAM was not the problem) and no software changes or additions have been performed except Microsoft updates, I too have suspicions about recent Microsoft updates (recent VM update ?).

I did force recreation of my pagefile.sys. I did that 5 days ago and so far (fingers crossed) have had no problem. I'm not sure this is conclusive since my problems were not continual but very intermetitent. But I knew it could not hurt.

 
I have had the same problem here on 8 NT boxes after applying some MS Critical Updates, SP's and Security patches. I discovered after some digging that there was a problem with one of the published Sec.Patches from December '02 .. specifically Q328310 I believe. There was an article on it earlier last week but I can't seem to find the link right now. I removed it from all of these PC's and everything has been fine up until earlier today. I have had two of these 8 PC's blue screen on me again. If I come across the link I will post it.
 
Per SteelyMac's post I found this page on the Q328310 patch.


At the bottom of the page it lists the revisions:

V1.0 (December 11, 2002): Bulletin Created.
V1.1 (December 17, 2002): Updated information in Additional information section.
V1.2 (February 03, 2003): Subsequent to the release of this bulletin it was determined that the patch for Microsoft Windows NT 4.0 machines introduced an error that may, under certain configurations, cause NT 4.0 to fail. The bulletin has been updated to remove the download links for the NT 4.0 patch and will be revised again once the updated package is available.
V2.0 (February 07, 2003): Microsoft has investigated this issue and is releasing an updated patch for Windows NT 4.0. The bulletin has been modified to include the new download links for the revised NT 4.0 patch.

Notice the problem in V1.2 and the fix in V2.0.

I will uninstall these patches and reinstall the new version to see if it fixes the problems.
 

I also rooted around this morning and found the same tech note. The timing makes sense, I installed Hotfix Q328310 on 12/13 and my problems first occured on 12/29. I too will uninstall and reinstall 328310 today and see what happens.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top