Nookz
asked on
Application popup: Winlogon generic control dialog: winlogon.exe - Application Error
Having deployed the lastest security fixes on our test group, we have had several machines rebooting during the day with no indication. I assume, machines that had their screensaver activated received the message :
Application popup: Winlogon generic control dialog: winlogon.exe - Application Error : The instruction at "0x77f585c0" referenced memory at "0x00000001". The memory could not be "written".
when they clicked ok, the machine then bounced. Other instances, the machine has rebooted whilst the user was working. Any idea what could be going on? Nothing much in the event log to go by.
Application popup: Winlogon generic control dialog: winlogon.exe - Application Error : The instruction at "0x77f585c0" referenced memory at "0x00000001". The memory could not be "written".
when they clicked ok, the machine then bounced. Other instances, the machine has rebooted whilst the user was working. Any idea what could be going on? Nothing much in the event log to go by.
When Windows crashes with blue screen, it writes a system event 1001 and a minidump to the folder windows\minidump.
Check system event 1001 and it has the content of the blue screen
Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001. Copy the content and paste it back here
If you do not find the system event 1001, the reboot is triggered by faulty hardware or virus reboot. Make sure your windows does not trojan or virus.
Check system event 1001 and it has the content of the blue screen
Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001. Copy the content and paste it back here
If you do not find the system event 1001, the reboot is triggered by faulty hardware or virus reboot. Make sure your windows does not trojan or virus.
Do you want to find out why the system reboot or the appiication error at winlogon.exe?
ASKER
need to find out why the machineS rebooted. Event ID 1001 is :
The SNMP Service has started successfully.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
We have up to date virus definitions, definately not a virus, and this has happened on various machines, so that rules out faulty hardware.
the machine does not blue screen, it reboots straight away (black screen) i.e. no dump.
The SNMP Service has started successfully.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
We have up to date virus definitions, definately not a virus, and this has happened on various machines, so that rules out faulty hardware.
the machine does not blue screen, it reboots straight away (black screen) i.e. no dump.
Reboot without blue screen is usually hardware problem unless it is reboot wth reboot command which may be triggered by a new virus. Up to date virus defiition does not mean your windows does not new virus.
ASKER
I've checked with Symantec, Sophos etc.. they have not seen this before, they do not think it is a virus that is causing it :S
I think it is hardware error
Run memtest to stress test the ram. www.memtest86.com
or
Windows diagnostic http://oca.microsoft.com/en/windiag.asp
Run memtest to stress test the ram. www.memtest86.com
or
Windows diagnostic http://oca.microsoft.com/en/windiag.asp
ASKER
this has happened on over 15 machines, dont think all machines hardware failed at the same sort of time
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Microsoft advised to upgrade to SP2 to fix the issue!
Upgrade to SP2 is a standard reply from microsoft. Maybe the culprit is the anti-virus or firewall. Btw what anti-virus and firewall utility are you using. If you can attach the Dr Watson log here, maybe I can find out the culprit.
ASKER
Machines are XP SP1.