175 pts.
 OCS and AutoLogon BSOD Issues
Hi all, Recently, one of my clients has been experiencing issues with a BSOD (I'll enter the stop error details below). The first referenced communicator.exe, and the second referenced Autologon.exe as being the culprits. Has anyone had any experience with these two programs causing driver faults? If so, did a reinstall of both solve the issue, or was there something deeper occurring?

Stop Error Info: BugCheck 1000008E, {c0000047, 804fcf44, a8f7f94c, 0} Arg1: c0000047, The exception code that was not handled Arg2: 804fcf44, The address that the exception occurred at Arg3: a8f7f94c, Trap Frame Arg4: 00000000 PROCESS_NAME: Autologon.exe

BugCheck 1000008E, {c0000047, 804fcf44, a9b2c3a4, 0} Arguments: Arg1: c0000047, The exception code that was not handled Arg2: 804fcf44, The address that the exception occurred at Arg3: a9b2c3a4, Trap Frame Arg4: 00000000 PROCESS_NAME: communicator.exe

Thanks,

Lordhowe



Software/Hardware used:
Dell Optiplex 755
ASKED: January 31, 2011  4:31 PM
UPDATED: February 17, 2011  11:01 PM

Answer Wiki:
My first advice is verify your computer for virus/malware. Temporarily disable autologon. Update OCS client to the latest version to your environment. Next, test if the computer boots without problem after disabling autologon. If it boots correctly, manually lunch Outlook and see what happens. Please keep us posted
Last Wiki Answer Submitted:  January 31, 2011  7:46 pm  by  saturno   4,570 pts.
All Answer Wiki Contributors:  saturno   4,570 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

Malware/Spyware was not an issue here.

I ended up reinstalling both Autologon and Communicator. So far, so good. I’ve asked the user to leave his machine running for the next week (along with Outlook 2010) to make sure there are no further issues.

Thanks,
Lordhowe

 175 pts.