Outlook 2003 SP3 Appcrash ntdll.dll c0000374 Windows 7 pro 64bit

I have a problem that shows up when closing Outlook 2003 after I have received an email that had a read request response. It does not matter whether I click on yes or no. I do not have any items checked in app add-ins or com add ins.
Here is a typical system log entry of the failure.
Log Name: Application
Source: Application Error
Date: 3/13/2012 4:54:40 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Michael-PC
Description:
Faulting application name: OUTLOOK.EXE, version: 11.0.8326.0, time stamp: 0x4c1c2372
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0x137c
Faulting application start time: 0x01cd016c33b8ec10
Faulting application path: C:\Program Files (x86)\Microsoft Office\OFFICE11\OUTLOOK.EXE
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 83637da2-6d5f-11e1-8314-0026b90eee78
Event Xml:
<Event xmlns="Error">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-03-13T22:54:40.000000000Z" />
<EventRecordID>30723</EventRecordID>
<Channel>Application</Channel>
<Computer>Michael-PC</Computer>
<Security />
</System>
<EventData>
<Data>OUTLOOK.EXE</Data>
<Data>11.0.8326.0</Data>
<Data>4c1c2372</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.17725</Data>
<Data>4ec49b8f</Data>
<Data>c0000374</Data>
<Data>000ce6c3</Data>
<Data>137c</Data>
<Data>01cd016c33b8ec10</Data>
<Data>C:\Program Files (x86)\Microsoft Office\OFFICE11\OUTLOOK.EXE</Data>
<Data>C:\Windows\SysWOW64\ntdll.dll</Data>
<Data>83637da2-6d5f-11e1-8314-0026b90eee78</Data>
</EventData>
</Event>

Outlook itself indicates Stachhash_4e4b errors but all the system log entries are like those above.

W7 has all the latest updates as does Outlook 2003.

Anyone got any idea what is happening?

Thank you JMH. There are so many restore points I would not know which one to choose to start the scan for affected programs. I don't know when this problem started happening except to say that I started doing some mainframe consulting and my client used the read reply request for emails sent to me and that is when I noticed the problem.

* Had you made any major Software / Hardware changes before the issue occurred?

* Is Office Outlook 2003 up to date with patches etc?

* The issues with crashes are often difficult to troubleshoot.
Crash issues are often caused by add-ins, corruption in the profile, and sometimes print drivers among others.

* As the error message indicated that the “ntdll.dll” is faulting module, please run the command SFC to check if there is a corruption.

The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.

Thank you for looking into this. As I mentioned in my original post both Outlook 2003 and W7 are at the latest Microsoft update levels. I have not done any major install recently. The read request feature is not one that I normally use but when I started consulting for my mainframe client the paymaster started sending me emails with the request being used. You mention that printer drivers can cause problems. I checked back though my notes for what I have done on my Laptop and found that I had allowed Microsoft Update to install a driver for what is a network printer here at home on 02/19/2012. There is no provision for driver roll back that I can find for this Brother printer so I will uninstall their software and try the Outlook thing from my home pc to my laptop.

What was the message received at the end of the SFC scan?

Good luck.

Uninstalling the Brother Printer driver and retesting after booting did not solve the problem. The sfc /scannow did not find any errors. The final message was "Windows Resource Protection did not find any integrity violations."

I read an incident on the internet where people with Dell laptops and an internal Bluetooth adapter removed the software and their problem like mine disappeared. My laptop is a Dell but it did not come with an internal Bluetooth adapter. Late last year I purchased a usb Bluetooth dongel and its software is installed but most of the time I don't have it plugged in. I will do some retesting and possibly uninstall the software.

Have you tried a System Restore point PRIOR to when your problem started?

A system restore point might work if I only knew when this all started. I have now ruled out the Bluetooth adapter and its software. Yesterday I tested it many times while trying different things. My system log has lots of funny things and I am going to work on those and see if it makes any difference. I found a Microsoft fix it for my CAPI2 code 4107 errors so I will do that stuff but I don't think that has anything to do with the Outlook problem. Thank you for advising. I will retry stuff after I have the CAPI2 things chased away.

Re the Cap 12 problem there...

The Cap 12 drama has been around for quite a few years.
Many threads have been written about the issue.

Have had the same problem on & off on all computers here.

Curiousity seeks answers always but there comes a time when one notices the sky hasn't fallen in.

Monitor what happens whilst moving on.