winlogon.exe Application Error

[Guest]

I am getting an error at the logon screen before I get a chance to login.

winlogon.exe - Application Error

The instruction at "0x77f581bf" referenced memory at "0x00708040". The
memory could not be "written".

Click on OK to terminate the program


If I press OK, it just reboots the pc, and the problem happens over and over
again. I have tried booting in safe mode, same error. I have gone into the
recovery console and

expand d:\i386\winlogon.ex_ c:\windows\system32

I get same error on boot up. I havn't installed any new programs in weeks.
Any help would be much appreciated.

 

[da_test]

I am getting an error at the logon screen before I get a chance to login.

winlogon.exe - Application Error

The instruction at "0x77f581bf" referenced memory at "0x00708040". The
memory could not be "written".

Click on OK to terminate the program


If I press OK, it just reboots the pc, and the problem happens over and over
again. I have tried booting in safe mode, same error. I have gone into the
recovery console and

expand d:\i386\winlogon.ex_ c:\windows\system32

I get same error on boot up. I havn't installed any new programs in weeks.
Any help would be much appreciated.

I hope this helps.
Logon to the safemode COMMAND PROMPT.
Execute system restore from the command line.

Revert the system to a time before the problem
started.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q304449


DAve

 

[Guest]

I cannot boot into safe mode, or safe mode with command prompt, I get the
same error. Can you think of anything else that might be the problem?
Thanks for the help.

 

[da_test]

I cannot boot into safe mode, or safe mode with command prompt, I get the
same error. Can you think of anything else that might be the problem?
Thanks for the help.

"da_test" wrote:

Try logging on as Administrator.
Safemode if you have to .

If you can successfully LOGON
Run chkdsk /F
retry using your normal ID.

If it still fails, possible corruption in the profile,
or even a virus or other malware.
I even read somewhere that the AV product
itself (mcafee in this case) caused the problem.

Dave