-
[Pro] PFN_LIST_CORRUPT
PFN_LIST_CORRUPT
stop 0x0000004e (0x00000099, 0x00000000, 0x00000000, 0x00000000)
On a colleague's desktop who claims that it usually happens when using Internet Explorer.The PC is on a network.
Found it in Microsoft KB
http://support.microsoft.com/kb/291806/en
However I can't determine what the parameters stand for.
Any ideas to do that?
-
It's a page frame database error, and can get very complicated, try the MS Driver Verifier first: http://support.microsoft.com/?kbid=244617
Liam
-
Thanx Liam, will try ASAP and report
-
Is it true that if you use the Driver Verifier all the drivers that are not digitally signed will be gone?(And they might be quite a few)
P.S. The company's technician is looking after his 6 days old daughter...
-
I don't think it will remove them without user input, it will probably display them and may blame one, but it is good for helping diagnose driver problems, check out this review: http://www.edbott.com/weblog/?p=576
Liam
-
That particular Stop error is often caused by bad RAM. Try testing the RAM, you can run either or both of these from a floppy, without needing to boot into Windows:
Memtest86
Windows Memory Diagnostic
-
Grrrr, I wanted to run the memory tests yesterday to let it check overnight but I forgot it...The problem is, I can't get hold of the machine on my desk because the colleague has to work on it, even under these conditions...
Anyway, I'll leave it to the technician because I don't want to mess any more with it(I could fix it of course :cool: - under your guidance that is)since it's not my responsibility.
Thanx for the help, if I am informed on what the cause is, I'll let you know otherwise I'll just mark it "resolved"...
-
Ok sorted it out.Windows Memory Diagnostic showed some errors.The only problem is, it didn't show which memory stick(out of 2)was the faulty one.I went through the interface but I couldn't locate it.So I changed both of them...
If the day goes by without any BSOD's I guess we figerred it out.
Thanx
-
The way to pick out the stick that is faulty is to remove one, run the diag, and if it has errors, then it is faulty, you might aswell test the other stick seperately too though to rule that out.
Liam
-
Yeah, I was too bored to do that...Thanx anyway liam
-
No probs, fingers crossed that was the problem. :)
Liam
-
Just a note here some times the fault isnt either stick.. rather Both of them and neither of them.. That is together they are faulty, apart they will be good..
As the components change certain aspects of the components specifications will change, each will be different.. so what works today wont in 3 or 6 even 36 months time.. some times the cure is as simple as reseating the memory sticks or swapping slots...
Just a FYI..