BlueScreen accessing Remote Desktop

  • Thread starter Thread starter Frank Jacobs
  • Start date Start date
F

Frank Jacobs

I need to administer a new company. Right now, temporary, there is a clone
Server with a GIGABYTE Motherboard Model 8KNXP with a SCSI CARD Adaptec
ASC-29320 Ultra320 SCSI Controller.
Server is running Windows Server Standard 2003 SP 1.

Remote Desktop was disabled when I arrived.
Now I enabled and when accessing, the server gives me blue screen with error
msg "STOP: 0x0000004E PFN_LIST_CORRUPT"
KB291806 tells me it is related to hardware.

Does anyone know a way to fix this?

Thanks;
Frank Jacobs
Small Business Specialist
 
"Frank Jacobs" <FrankJacobs@discussions.microsoft.com> wrote in message
news:0BDECD61-4C9E-4686-9A01-7F9431B45085@microsoft.com...
>I need to administer a new company. Right now, temporary, there is a clone
> Server with a GIGABYTE Motherboard Model 8KNXP with a SCSI CARD Adaptec
> ASC-29320 Ultra320 SCSI Controller.
> Server is running Windows Server Standard 2003 SP 1.
>
> Remote Desktop was disabled when I arrived.
> Now I enabled and when accessing, the server gives me blue screen with
> error
> msg "STOP: 0x0000004E PFN_LIST_CORRUPT"
> KB291806 tells me it is related to hardware.
>
> Does anyone know a way to fix this?


Start with the items suggested in that article (but I presume you did
these):

1. Run hardware diagnostic tools that are provided by your computer
manufacturer.

2. Disable all file system filter drivers, such as backup utilities,
virus scanners, or firewall software.

3.View the following Microsoft Web site to verify that the hardware and
the drivers for the hardware are compatible with Windows 2000:
http://www.microsoft.com/whdc/hcl/default.mspx
(http://www.microsoft.com/whdc/hcl/default.mspx)
For information about the hardware on your computer, contact the
manufacturer.

4.If you receive this error message randomly, or when you try to start a
program, remove extra memory or have the random access memory (RAM) in your
computer tested. This behavior may occur if you have bad RAM.

(5) For more information about the parameters of the PFN_LIST_CORRUPT
function, visit the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/library/ms793247.aspx


This last explains that this is typically going to be due to bad drivers --
and probably
not those built by Microsoft.

I would consider strongly looking at any "unusual" hardware and its drivers,
upgrading to the latest (production) versions of those drivers and perhaps
the latest (production) version of your motherboard or other
"BIOS/firmware".

Another possibility is to remove all non-essential drivers (virus scanners
and
backup might be included here) and either run without them or replace them
with drivers/services from other manufacturers.

You might spend on time looking especially at your VIDEO since it seems
related to Remote Desktop which gets involved with video drivers.

Also, consider upgrading to the LATEST Service Pack and all possible
HotFixes.

After that, I might also consider a REPAIR INSTALL using the latest (or
last Service Pack ready) OS Installation CDROM.

This last (Repair Install) has solve many problems for me and causes no
real problems other than the need to re-apply subsequent Service packs
and hotfixes after the Repair is complete.

After that you are pretty much left with removing EVERY hardware device
that is NOT on the "Hardware Compatibility List" (HCL.)


--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
 
Back
Top