Remote Desktop Error

[Jeff Zander]

When attempting to connect to my WinXP Pro SP2 machine, the session begins
but errors out with this dialog box on the remote session:

User Interface Failure: winlogon.exe - Application Error

The instruction at "0x10039bfe" referenced memory at "0x10039bfe". The
memory could not be "read".

Click on OK to terminal the program
Click on CANCEL to debut the program


Clicking on either OK or CANCEL produces the same result...the session is
terminated. Anyone have any ideas?

TIA,

--jeff

 

[Jeffrey Randow (MVP)]

We've seen this error in the past. It seemed that it was caused by an
incomplete SP install (in that case, SP1). Try either re-running the
SP2 install or run "sfc /scannow" to see if the winlogon application
may be corrupted.

Jeffrey Randow (Windows Networking & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

 

[Jeff Zander]

Thanks, Jeffrey. I've tried running sfc but it keeps yelling at me that I
don't have the correct Windows XP CD in the tray.

I assume that my install path is correct (where is that in regedit?) and
I've tried both WinXP RTM cd and the WinXP SP2 Slipstream.

Do you think perhaps it's because my build was done with XP SP1 and I
applied SP2 later? I do not have a copy of the XP SP1 cd image.

 

[Jeff Zander]

I reapplied SP2. Now, Windows starts up okay but I get a "winlogon.exe"
error:

There was a problem with this program and it must close.

An "appcompat.txt" file was created and it's contents follow:

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="983552" CHECKSUM="0x4CE79457"
BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180"
PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="Windows NT BASE API Client
DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows®
Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="©
Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0"
VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2"
MODULE_TYPE="WIN32" PE_CHECKSUM="0xFF848" LINKER_VERSION="0x50001"
UPTO_BIN_FILE_VERSION="5.1.2600.2180"
UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:56:36"
UPTO_LINK_DATE="08/04/2004 07:56:36" VER_LANGUAGE="English (United States)
[0x409]" />
</EXE>
</DATABASE>

Is this any help?

Regards,
--jeff

 

[Jeffrey Randow (MVP)]

No... Something is still wrong...

I have been researching this and the normal conclusion (after you
check for corruption, which you have done) is to troubleshoot the
programs you are running and to run a memory test. I would recommend
the memory test first - you can get one at http://memtest86.com

To troubleshoot applications loading at startup, take a look at
http://www.microsoft.com/resources/...Windows/XP/all/reskit/en-us/prmb_tol_dxth.asp

Jeffrey Randow (Windows Networking & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

 

[Jeffrey Randow (MVP)]

You should have only needed the RTM and the SP2 CD...

Jeffrey Randow (Windows Networking & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

 

[Guest]

I agree with Rainbow; this sounds like a memory module or chip flaking out.
If this is the case you need to get on it quickly, as it will take down your
XP install by corrupting system files. If you have jacked up your memory
settings in BIOS, try restting them to normal before running memtest for a
more accurate result.

Vince