OCS and AutoLogon BSOD Issues

175 pts.
Tags:
BSOD
Dell Optiplex
Microsoft Office Communications Server
Microsoft Office Communicator 2007 R2
Office Communication Server
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

Answer Wiki

Thanks. We'll let you know when a new response is added.

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

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Lordhowe
    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 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following