Strange blue screen error in Windows XP Pro

Discussion in 'Operating Systems' started by Fardringle, Jan 17, 2013.

  1. Fardringle

    Fardringle Diamond Member

    Joined:
    Oct 23, 2000
    Messages:
    7,991
    Likes Received:
    4
    This one has me stumped so I hope that someone out there can figure out what I am missing. This will be kind of long since I want to be thorough.

    I recently reinstalled Windows XP Pro on a Dell Dimension 330 for a small office client because it was replaced and they were passing the machine down to someone that had been using a very old computer and they wanted it to have a clean install for the new user.

    So I reinstalled XP and all drivers and software that they normally use with no apparent problems. Then I copied the user's profile from the old computer to the replacement as I normally do when moving people so that everything shows up the same way it did on their old computer. Again, no apparent problems. Everything runs fine, nothing missing, and no errors.

    That is, until the user tries to log off, restart, or shut down Windows. Then it gets a blue screen error "STOP: 0x0000004E (0x00000099....) PFN_LIST_CORRUPT". Searching on Google seems to indicate that this is either a virus or a device driver error. I knew it couldn't be a virus, but I scanned the system with Stinger, Malwarebytes, and ComboFix just to be sure and nothing was found.

    I installed WhoCrashed and it says that the crashes were most likely caused by NTOSKRNL.EXE. I checked the Event Viewer and it doesn't even have a reference to the crashes at all, which is pretty surprising to me because I've never seen a blue screen that didn't have at least one error entry in the Event Viewer.

    I verified that all device drivers are current (reinstalled all of them), ran SFC /SCANNOW to check for missing Windows files, and when that didn't work, did a full repair installation of Windows from the XP CD. The computer is still getting the same blue screen error, and still only when shutting down, rebooting, or logging off. This happens when I create a completely new user account and try to shut down or reboot with that account as well so it doesn't appear to be a problem specific to the user.

    I also ran MEMTEST and Prime95 (separately) for about 8 hours each and SeaTools (Seagate hard drive) as well as the built in Dell diagnostic tools and none of them found any errors.


    Cliff Notes: Fresh install of Windows XP runs normally while being used, except when it is logged off, rebooted, or shut down, and then it gets a PFN_LIST_CORRUPT blue screen error. Any suggestions?
     
  2. VirtualLarry

    VirtualLarry Lifer

    Joined:
    Aug 25, 2001
    Messages:
    33,366
    Likes Received:
    33
    This can be caused by bad RAM too.
     
  3. JackMDS

    JackMDS Super Moderator<BR>Elite Member
    Super Moderator

    Joined:
    Oct 25, 1999
    Messages:
    27,767
    Likes Received:
    5
  4. Fardringle

    Fardringle Diamond Member

    Joined:
    Oct 23, 2000
    Messages:
    7,991
    Likes Received:
    4
    I ran MEMTEST over night. It didn't find any errors.

    I'll try that when she isn't using the machine so I can log in remotely and see what it says. Thanks.
     
  5. jolancer

    jolancer Senior member

    Joined:
    Sep 6, 2004
    Messages:
    469
    Likes Received:
    0
    never tried that, when iv type of thing on my own comp i transfered files and settings, not the entire profile so not sure but....

    maybe the permission settings on the profile you transfered? asuming there not a conflict or something from doing that cause it was a different service pack version or something?

    couldnt u test it just by creating a new profile and logoff/shutdown ?
     
  6. Fardringle

    Fardringle Diamond Member

    Joined:
    Oct 23, 2000
    Messages:
    7,991
    Likes Received:
    4
    I copy user profiles like that frequently (log in to the new machine to create the profile folder, then replace everything inside with the contents of the profile folder on the old machine) so I don't think it's related. It does the same thing with a completely new user account/profile.
     
  7. lxskllr

    lxskllr Lifer

    Joined:
    Nov 30, 2004
    Messages:
    44,406
    Likes Received:
    38
    Was the machine being actively used before it was repurposed? I'm wondering if it could have something to do with the psu, or mb parts relating to power distribution.
     
  8. Fardringle

    Fardringle Diamond Member

    Joined:
    Oct 23, 2000
    Messages:
    7,991
    Likes Received:
    4
    Yes, it was actively used and had no issues at all. It's certainly possible that the PSU or some other component is failing, but it worked just fine before I reinstalled Windows, and still works perfectly fine except when logging off or restarting/shutting down. If it it only happened while restarting/shutting down, that would make a power issue more likely, but simply logging off causes the same blue screen error.
     
  9. styrafoam

    styrafoam Platinum Member

    Joined:
    Jun 18, 2002
    Messages:
    2,685
    Likes Received:
    0
    What sort of computer was the profile pulled from? Mismatched bios or Windows power management settings or the Dell doesn't supported the same features?
     
  10. Fardringle

    Fardringle Diamond Member

    Joined:
    Oct 23, 2000
    Messages:
    7,991
    Likes Received:
    4
    Both computers are Dells. The old one was a Dimension 4500, but it really doesn't matter for the user profile as long as the operating system is the same (which it is). And this really doesn't seem to be a profile problem since, as I mentioned earlier, it happens even with a completely different new user profile for a different user account.
     
  11. styrafoam

    styrafoam Platinum Member

    Joined:
    Jun 18, 2002
    Messages:
    2,685
    Likes Received:
    0
    Sorry, seems i skimmed a bit. I would probably try disabling the sound and then the nic in the bios and seeing if the bsod persists after each. If that isn't an option then doing so in the device manager is second best. The computer is old enough that i wouldn't be surprised if the motherboard is dying from bad caps.