Parents' computer having fatal errors

[Reloadron]

Personally I like to see the Page File about 1.5 times the system memory, however, per Hitman twice the system memory is fine also. The size is not what I was overly concerned with, I wanted you to note the size so it could easily be returned to that size. The idea behind removing it was that if the PF had somehow become corrupt we would blow it away then let Windows create a new PF. Letting Windows manage it is fine. I "think" Windows will manage it at 1.5 times system memory.

OK, cool as you did use the event viewer. The "Warnings" you see are not a big concern. The big concern are those little red X's that are errors. Those need to be looked into. They are not necessarily a bad, bad thing all the time. The trick is knowing whay they are there and if they would cause a BSOD.

Let's see what happens and if need be we can look at memory dumps.

Ron

[screwballl]

blues screens can be caused by soon to fail hardware including memory, hard drive, power supply or sometimes it is MS engineering at its finest

try this and get the actual error message:

go to System properties
Advanced tab
startup and Recovery -> Settings button
uncheck "Automatically Restart" under system Failure

this will give you the BSOD instead of automatically restarting and will give you the specific error codes when it happens

[Dread]

Originally Posted by WhiteEagle

It was 1.5 times the size. Now it's set to system managed, so it should fix itself...I hope.

Last time it crashed, I sent the created error report to Microsoft. According to web page that popped up afterwards, it's something they haven't found a cure for yet.

I've noticed that most of the errors that MS hasn't found a solution for yet are driver related.

also, when was the last time that system had a fresh install?

[WhiteEagle]

Good question, Dread. I think it last got wiped clean about 3 or four months ago. Apparently they've been taking it in to the local repair shop, and those people can't pin down the problem, either.

[WhiteEagle]

Hey all,

When I booted up my parents' PC today (Saturday, May 18th), I got the blue screen with the following error: PFN_LIST_CORRUPT. What does this particular error mean, and how can I solve it?

TIA,
Nathan P. (WhiteEagle)

[stinger608]

Originally Posted by WhiteEagle

Hey all,

When I booted up my parents' PC today (Saturday, May 18th), I got the blue screen with the following error: PFN_LIST_CORRUPT. What does this particular error mean, and how can I solve it?

TIA,
Nathan P. (WhiteEagle)

According to what I have found about that error, it is a bad Ram chip!!!

If you have more than one chip in the rig, pull all but one and boot until you find the bad one!

[WhiteEagle]

Well, looks like my brother James will have to pay for new RAM and its installation, as my mom isn't paying anymore for that PC. Glad I don't use it that much anymore.

[stinger608]

Originally Posted by WhiteEagle

Well, looks like my brother James will have to pay for new RAM and its installation, as my mom isn't paying anymore for that PC. Glad I don't use it that much anymore.

You should still test it though with memtest86!!! Just to find out which chip is bad.

[WhiteEagle]

My parents computer just came back from the fix-it repair shop. I ran memtest86 on it and before I stopped it, there was over 40,000 errors, scanning all memory and only on the 3rd test. Yet when they tested the memory individually in another rig, it was fine What's going on

BTW, the motherboard is as old as the PC (5 years old). I'm wondering if that's part of the problem.

[stinger608]

Originally Posted by WhiteEagle

My parents computer just came back from the fix-it repair shop. I ran memtest86 on it and before I stopped it, there was over 40,000 errors, scanning all memory and only on the 3rd test. Yet when they tested the memory individually in another rig, it was fine What's going on

BTW, the motherboard is as old as the PC (5 years old). I'm wondering if that's part of the problem.

Again, just like another thread that Zambini started, there is a strong possibility that it could be a power supply taking a dump also! This would give tons of errors in something like memtest! If you can come up with an extra psu, say from the computer shop, (see if you can borrow one maybe), toss it in and check again!