Wednesday 27 August 2008

Vista - Stop 0x0000004e - PFN List Corrupt

We were putting together a new Vista x64 box for some VMs to run on Virtual PC.

We went to install Vista Ultimate SP1 x64 and received a strange BSOD:

Stop 0x0000004e PFN_List_Corrupt
Now, this box has been used once or twice in the past couple of months. However, it was behaving quite strange. So, yesterday we put in a new set of drives for the RAID 1 array and went to reinstall the OS.

Thinking that the problem may have been with having too much RAM, even though SP1 is not supposed to have that problem, we pulled the two 2GB sticks leaving 2GB in the machine.

Sure enough, the OS installed.

After a shutdown and reinstall of the 2GB sticks we started seeing the system behave strangely to the point where it would not function at all.

We rebooted, hit the F8 key to get into the boot selection key, then it ESC to get to the Memory Diagnostic Tool.

This is what we were greeted with:

Windows Memory Diagnostics Tool

Yes, we have a hardware problem. At least it is now confirmed.

Once the system had rebooted as indicated it would when the test was finished we saw:

Bad Memory

Too bad the DQ35JO doesn't light up the slot the bad memory is in like the server systems do.

After a little bit of troubleshooting, we had the culprit and put in to Kingston for an RMA.

Philip Elder
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

No comments: