I have a problem with Outlook (2003, full patched). This morning when I
arrived at the office, Outlook had crashed.

Tried to start it; it crashed again. Tried to start in Safe Mode
(outlook /safe); it still crashed.

Event Log has two entries for each crash:
- Faulting application outlook.exe, version 11.0.8118.0, faulting module
ntdll.dll, version 5.1.2600.2180, fault address 0x000114b6.
- Fault bucket 403357038.

I have never had any problem with Outlook, and I don't know why it
started now. The last thing I newly installed was last week; VSE80P15
on McAfee VirusScan Enterprise 8.0, plus the new scan engine 5200.

I also tried to start Outlook with VirusScan disabled, but it still
crashes. Any ideas or suggestions?

I have done the following since the message below
- deleted and recreated mail profile;
- System Restore to the day before;
- uninstalled all add-ins;
- uninstalled McAfee VirusScan;
- created a new mail profile with only Exchange server access;
- created a new mail profile with only PST file access;
- ran Detect and Repair;
- ran scanpst on all PST files;
- uninstalled and reinstalled Outlook completely;

None of these steps did anything to prevent the crash in ntdll.dll

Unfortunately I do not have a recent backup - the last if of March this
year. But unless someone has a better idea, this will be my last hope.

Pat Willener wrote:
> I have a problem with Outlook (2003, full patched). This morning when I
> arrived at the office, Outlook had crashed.
>
> Tried to start it; it crashed again. Tried to start in Safe Mode
> (outlook /safe); it still crashed.
>
> Event Log has two entries for each crash:
> - Faulting application outlook.exe, version 11.0.8118.0, faulting module
> ntdll.dll, version 5.1.2600.2180, fault address 0x000114b6.
> - Fault bucket 403357038.
>
> I have never had any problem with Outlook, and I don't know why it
> started now. The last thing I newly installed was last week; VSE80P15
> on McAfee VirusScan Enterprise 8.0, plus the new scan engine 5200.
>
> I also tried to start Outlook with VirusScan disabled, but it still
> crashes. Any ideas or suggestions?

It seems that there are a number of similar problems posted here today;
I wonder what this means? I think I am going to do some serious malware
scanning...

In the meantime I have requested hotfix 922617 to be delivered to me
(http://support.microsoft.com/kb/922617/)

Pat Willener wrote:
> I have done the following since the message below
> - deleted and recreated mail profile;
> - System Restore to the day before;
> - uninstalled all add-ins;
> - uninstalled McAfee VirusScan;
> - created a new mail profile with only Exchange server access;
> - created a new mail profile with only PST file access;
> - ran Detect and Repair;
> - ran scanpst on all PST files;
> - uninstalled and reinstalled Outlook completely;
>
> None of these steps did anything to prevent the crash in ntdll.dll
>
> Unfortunately I do not have a recent backup - the last if of March this
> year. But unless someone has a better idea, this will be my last hope.
>
> Pat Willener wrote:
>> I have a problem with Outlook (2003, full patched). This morning when I
>> arrived at the office, Outlook had crashed.
>>
>> Tried to start it; it crashed again. Tried to start in Safe Mode
>> (outlook /safe); it still crashed.
>>
>> Event Log has two entries for each crash:
>> - Faulting application outlook.exe, version 11.0.8118.0, faulting module
>> ntdll.dll, version 5.1.2600.2180, fault address 0x000114b6.
>> - Fault bucket 403357038.
>>
>> I have never had any problem with Outlook, and I don't know why it
>> started now. The last thing I newly installed was last week; VSE80P15
>> on McAfee VirusScan Enterprise 8.0, plus the new scan engine 5200.
>>
>> I also tried to start Outlook with VirusScan disabled, but it still
>> crashes. Any ideas or suggestions?

It turned out to be an add-in (Cloudmark Desktop). Although I
uninstalled it, it seemed to remain active until I removed the install
folder from my drive.

Pat Willener wrote:
> It seems that there are a number of similar problems posted here today;
> I wonder what this means? I think I am going to do some serious malware
> scanning...
>
> In the meantime I have requested hotfix 922617 to be delivered to me
> (http://support.microsoft.com/kb/922617/)
>
> Pat Willener wrote:
>> I have done the following since the message below
>> - deleted and recreated mail profile;
>> - System Restore to the day before;
>> - uninstalled all add-ins;
>> - uninstalled McAfee VirusScan;
>> - created a new mail profile with only Exchange server access;
>> - created a new mail profile with only PST file access;
>> - ran Detect and Repair;
>> - ran scanpst on all PST files;
>> - uninstalled and reinstalled Outlook completely;
>>
>> None of these steps did anything to prevent the crash in ntdll.dll
>>
>> Unfortunately I do not have a recent backup - the last if of March this
>> year. But unless someone has a better idea, this will be my last hope.
>>
>> Pat Willener wrote:
>>> I have a problem with Outlook (2003, full patched). This morning when I
>>> arrived at the office, Outlook had crashed.
>>>
>>> Tried to start it; it crashed again. Tried to start in Safe Mode
>>> (outlook /safe); it still crashed.
>>>
>>> Event Log has two entries for each crash:
>>> - Faulting application outlook.exe, version 11.0.8118.0, faulting module
>>> ntdll.dll, version 5.1.2600.2180, fault address 0x000114b6.
>>> - Fault bucket 403357038.
>>>
>>> I have never had any problem with Outlook, and I don't know why it
>>> started now. The last thing I newly installed was last week; VSE80P15
>>> on McAfee VirusScan Enterprise 8.0, plus the new scan engine 5200.
>>>
>>> I also tried to start Outlook with VirusScan disabled, but it still
>>> crashes. Any ideas or suggestions?

Hi Pat,

I experienced an itdentical problem on all of my office PCs last night. It
did in fact turn out to be Cloudmark's SPAMNET. We rely on that program to
catch our SPAM. Now that it is diabled, I have contacted Cloudmark for
further instructions.

Anyone else gotten burned by Cloudmark recently?

Kevin Siegel

"Pat Willener" wrote:

> It turned out to be an add-in (Cloudmark Desktop). Although I
> uninstalled it, it seemed to remain active until I removed the install
> folder from my drive.
>
> Pat Willener wrote:
> > It seems that there are a number of similar problems posted here today;
> > I wonder what this means? I think I am going to do some serious malware
> > scanning...
> >
> > In the meantime I have requested hotfix 922617 to be delivered to me
> > (http://support.microsoft.com/kb/922617/)
> >
> > Pat Willener wrote:
> >> I have done the following since the message below
> >> - deleted and recreated mail profile;
> >> - System Restore to the day before;
> >> - uninstalled all add-ins;
> >> - uninstalled McAfee VirusScan;
> >> - created a new mail profile with only Exchange server access;
> >> - created a new mail profile with only PST file access;
> >> - ran Detect and Repair;
> >> - ran scanpst on all PST files;
> >> - uninstalled and reinstalled Outlook completely;
> >>
> >> None of these steps did anything to prevent the crash in ntdll.dll
> >>
> >> Unfortunately I do not have a recent backup - the last if of March this
> >> year. But unless someone has a better idea, this will be my last hope.
> >>
> >> Pat Willener wrote:
> >>> I have a problem with Outlook (2003, full patched). This morning when I
> >>> arrived at the office, Outlook had crashed.
> >>>
> >>> Tried to start it; it crashed again. Tried to start in Safe Mode
> >>> (outlook /safe); it still crashed.
> >>>
> >>> Event Log has two entries for each crash:
> >>> - Faulting application outlook.exe, version 11.0.8118.0, faulting module
> >>> ntdll.dll, version 5.1.2600.2180, fault address 0x000114b6.
> >>> - Fault bucket 403357038.
> >>>
> >>> I have never had any problem with Outlook, and I don't know why it
> >>> started now. The last thing I newly installed was last week; VSE80P15
> >>> on McAfee VirusScan Enterprise 8.0, plus the new scan engine 5200.
> >>>
> >>> I also tried to start Outlook with VirusScan disabled, but it still
> >>> crashes. Any ideas or suggestions?
>

Kevin,
Yes we had it also - just by chance checked this newsgroup as last resort.
Cloudmark have an easy fix posted on their website.

On Aug 9, 2:10 pm, Rick <R...@discussions.microsoft.com> wrote:
> Kevin,
> Yes we had it also - just by chance checked this newsgroup as last resort.
> Cloudmark have an easy fix posted on their website.

This, from the Cloudmark Website:

Glenn

If you are experiencing a crash, the problem was caused by a corrupted
file that was part of an automatic Cloudmark update. We have isolated
and resolved the issue. Please perform the following steps to remove
the corrupted file which will resolve the issue on your computer:
For Windows 2000/XP

1. Right click on your Start button and select Windows Explorer
2. Select Tools > Folder Options an click on the View tab
3. Click on the radio button that says 'Show hidden files and
folders' and then click OK.
4. Navigate to C:\Documents and Settings\{insert your username here}
\Local Settings\Application Data\Cloudmark\SpamNet\
5. Delete all of the files in this folder
6. Restart your computer

For Windows Vista

1. Right click on your Start button and select Explore
2. Select Organize > Folder and Search Options and click on the
View tab
3. Click on the radio button that says 'Show hidden files and
folders' and then click OK
4. Navigate to C:\Users\{insert your username here}\AppData\Local
\Cloudmark\SpamNet Data\Cloudmark\SpamNet\
5. Delete all of the files in this folder
6. Restart your computer

We're very sorry for any inconvenience this issue has caused you.

If this does not solve your problem, please submit a request for help
and we will assist you further.

Interesting...currently (8/11/07) the fix on the Cloudmark site calls for
simply downloading and running a new installer. But, it doesn't work. In my
case, the earlier fix did work.

This just wiped out several years accumulation of "attaboys" for Cloudmark.

Bill

"(E-Mail Removed)" wrote:

> On Aug 9, 2:10 pm, Rick <R...@discussions.microsoft.com> wrote:
> > Kevin,
> > Yes we had it also - just by chance checked this newsgroup as last resort.
> > Cloudmark have an easy fix posted on their website.
>
> This, from the Cloudmark Website:
>
> Glenn
>
> If you are experiencing a crash, the problem was caused by a corrupted
> file that was part of an automatic Cloudmark update. We have isolated
> and resolved the issue. Please perform the following steps to remove
>the corrupted file which will resolve the issue on your computer:
> For Windows 2000/XP
>
> 1. Right click on your Start button and select Windows Explorer
> 2. Select Tools > Folder Options an click on the View tab
> 3. Click on the radio button that says 'Show hidden files and
> folders' and then click OK.
> 4. Navigate to C:\Documents and Settings\{insert your username here}
> \Local Settings\Application Data\Cloudmark\SpamNet\
> 5. Delete all of the files in this folder
> 6. Restart your computer
>
> For Windows Vista
>
> 1. Right click on your Start button and select Explore
> 2. Select Organize > Folder and Search Options and click on the
> View tab
> 3. Click on the radio button that says 'Show hidden files and
> folders' and then click OK
> 4. Navigate to C:\Users\{insert your username here}\AppData\Local
> \Cloudmark\SpamNet Data\Cloudmark\SpamNet\
> 5. Delete all of the files in this folder
> 6. Restart your computer
>
> We're very sorry for any inconvenience this issue has caused you.
>
> If this does not solve your problem, please submit a request for help
> and we will assist you further.
>
>