Link to home
Start Free TrialLog in
Avatar of esenn
esenn

asked on

winlogon.exe - Application Error when shutting down machine, not always but most times

Have a two month old Sony Vaio and getting the following error message when shutting down (occasionlly - not always):

winlogon.exe - Application Error : The instruction at "0x7c910f29" referenced memory at "0x00000006". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program


I have had Norton Antivirus on it with regular updates since it was purchased.  I have run a complete system scan, nothing found.

I just downloaded AdAware personal edition and updated it library files, ran it, found 40 objects, one being the virus Mircosoft Winlogon Trojan, removed it, rebooted same problem, running ad aware again now in the background.  

Prior to AdAware scan I unchecked all but essential items in MSCONFIG and still had this problem.

Thoughts/Suggestions?

Thanks,
Eric
Avatar of g127404
g127404

Chkdsk /r
from a command line (Start ->Run->cmd.exe)

It's probably a bad sector on your harddrive.  Running chkdsk should repair this.

This thread also has a similar error message:
https://www.experts-exchange.com/questions/21238499/Winlogon-exe.html
Avatar of younghv
Hi Eric,
If you browse through the Security and Anti-virus forums here, you will see that most Experts recommend against Norton/Symantec products.
Very processor intensive and many conflicts within the OS.
Plus it has not been doing a very good job lately.

I recommend the following - you can do all of it with Norton still installed, but you may find even more that Norton has missed.
Good Luck,
Vic

On-Line Anti-virus Scan
http://www.trendmicro.com/hc_intro/default.asp

Then, I would load MS Defender (http://www.microsoft.com/athome/security/spyware/software/default.mspx) PLUS at least one of the following.

SpyBot S&D searches your harddisk for so-called spy- or adbots;
http://security.kolla.de/
or
Adaware
http://www.lavasoftusa.com/software/adaware/

Make sure that your Definition files are updated for all the security apps.
Re-boot into Safe Mode and do a complete system scan with all applications.
Try running the System File Checker (SFC):
      SFC /SCANNOW

      Description of the Windows System File Checker Tool
      http://support.microsoft.com/default.aspx?scid=kb;en-us;310747
Hello

If you boot the system in safemode, then boot there and run sfc /scannow from Start>Run>cmd and after that run Chkdsk /r and then restart and check if same problem ??
if you cannot start the system in safemode even, then try this,

HOW TO: Start the System Restore Tool from a Command Prompt in Windows XP:
http://support.microsoft.com/?kbid=304449
Avatar of esenn

ASKER

I have tried all of the above to no avail.   I watched the screen and noticed a blue screen appearing briefly if I tried debugging rather than just hitting cancel.  the screen was disappearing to fast because the machine was set to restart on halt.  I disabled this and was able to capture the following blue screen message:

STOP: c000021a {Fatal System Error}

The windows logon process terminated unexpectedly with a status of 0xc0000005 (0x0000000 0x0000000)
The system has been shut down.


Again, this is the blue screen I get after pressing debug when I get the application error as described in the initial problem section.  

I have replaced the RAM, run ad aware, spybot, defender, online virus scan, and sfc /scannow in both standard and safe modes.  All yielding just your standard threats (cookies, etc) that I have removed and still continue to have this problem.

Are there any other suggestions?
ASKER CERTIFIED SOLUTION
Avatar of g127404
g127404

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Try Changing the Ram
Try installing in a new hard drive
if you have 2 RAM Installed in your system try instaling in one Ram Check one by one if they have fault
Avatar of esenn

ASKER

well rinstalling windows fixed it eventhough that was what I had hoped to avoid.  Must have been something in the registry gone amuk.