Outlook.exe appcrash in ntdll.dll, please help!

[bstonehill]

I just did a fresh install of microsoft office 2007 that I downloaded from microsoft's website on my new computer running Vista Business. I previously had this running on my old computer which was also Vista Business. I kept getting appcrash errors everytime I tried to launch outlook but other office programs seemed to run ok. I've found several forums pointing out a conflict with Cloudmark that causes this error but I do not have it installed and have never used it. I was going to try downloading ntdll.dll from dll-files.com and install it over the current one but I read that it was a critical windows file and am afraid of crashing windows. System Restore only goes back 2 days and I've only installed a handful of programs (AVG, Firefox, Adobe CS3, and UVNC(Viewer Only)). All of these programs were installed on the old computer and I had no problems.

The error message contains the following:
Problem Event Name: APPCRASH
Application Name: OUTLOOK.EXE
Application Version: 12.0.6300.5000
Application Timestamp: 4760725d
Fault Module Name: ntdll.dll
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bdc9
Exception Code: 80000003
Exception Offset: 00042ea8
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 1033
Additional Information 1: e51a
Additional Information 2: 4c0d4d78887f76d971d5d00f1f20a433
Additional Information 3: e51a
Additional Information 4: 4c0d4d78887f76d971d5d00f1f20a433

I would greatly appreciate any help with this.

Thanks!

 

[MMSMSD]

Of the additional software you've installed, AVG would be my guess as the culprit, since it needs to load it's add-in during the startup of Outlook in order to protect email. That would explain why the other Office apps are not affected.

I would check for a newer version of AVG (8.x is the latest but 7.5 is the latest FREE version.) If AVG was installed BEFORE Office 2007, that might introduce a problem as well. If your version of AVG is Office 2007 compatible, you may want to try uninstalling and the reinstalling it.

While not as much of a possibility, failing RAM and/or bad sectors on a drive would cause this type of situation. It can't hurt to run a thorough memory test and hard drive test.

Hope this helps.
Michael