Printable View
pfn_file_corrupt; this the tail end of a blue screen dump with a stop bit error of 0x0000004E.
i know there is a KB article on a reg hack to fix it but it's a booger to find because there's no KB article associated with this stop bit, it was explained in a related KB article.
if anyone has a link to this needle i would appriciate it.
Do you really mean STOP: 0x0000004E (parameter, parameter, parameter, parameter) PFN_LIST_CORRUPT.
This is a Windows NT Executive character-mode STOP message. It indicates the memory management page file number (PFN) list is corrupt. Have you tried different memory chips?
I also found this:
PFN_LIST_CORRUPT (0x4E)
Caused by corrupting I/O driver structures. If the kernel debugger is available, get a stack trace.
Parameters
----------
1 - Value 1
2 - ListHead value that was corrupt
3 - Number of pages available
4 - 0
1 - Value 2
2 - Entry in list being removed
3 - Highest physical page number
4 - Reference count of entry being removed
This doesn't tell you much... https://forums.windrivers.com/
that was it! sorry for the mixup in wording.
yea, tried two different types of memory i'm currently running seimens 128 meg stick of pc100
Is the new memory working then? https://forums.windrivers.com/
[This message has been edited by StevePorter (edited January 08, 2001).]
no, i posted this the day it started with the seimens memory. it doesn't do it on a regular basis and has not done it in about a month(on shut down). i was thinking of trying micron but i get the feeling i might be chasing my tail.
your thoughts?
I don't think memory (RAM) is the problem here. In my experience, it's really rare to have a stick of memory take a dive. We need to do a little more sleuthing here. Did you install any new hardware and/or programs just before this error occurred? This kind of STOP error is usually associated with a device driver failure (it's trying to access a position in memory that's not available).
As tedious as it sounds, try yanking all non-essential hardware (i.e., NIC, sound card, SCSI card, etc.) and do a restart. See if the error repeats itself. In the meantime, I'll do some more checking to see if I can find some solution for this. https://forums.windrivers.com/
steve, first thanks for the responses. question for ya, the last time i reinstalled the OS i did with acpi disabled would it be better to reinstall with acpi enabled?
storm.
YES! Definitely, unless you have one of those odd motherboards that go apes**t when you enable ACPI. Enabling ACPI will allow W2K to perform PCI Steering. You'll see multiple devices sharing a single IRQ. This is normal and allows many more devices to be installed into your computer. (Some legacy devices can get screwed up under ACPI, but from what I've seen that doesn't seem to happen too often.) Without ACPI, you're back to the WinNT4 days of playing with the IRQs to get everything to work together.
You will need to re-install W2K once you've enabled ACPI in your BIOS. Oh, and flash your BIOS to the latest version before you change the setting... https://forums.windrivers.com/
thanks again steve, i though it would be better to have it with acpi then without and yes i do have a newer board that doesn't have a problem with acpi enabled.
i had it enabled the first time i installed was having various problems and reinstalled with it disabled as part of my troubleshooting...bad call...
anyway i'll reinstall this weekend with it enabled..and flash the bio before hand.
later, storm
Let me know if you're still having problems. We'll try another approach... https://forums.windrivers.com/