Using Classic Outlook on Windows for personal email, calendar, and contact management
Outlook 2000 OUTLLIB.DLL
Subject: Outlook 2000 OUTLLIB.DLL
I am investigating repeated Outlook 2000 crashes on Windows 10.
The original OUTLLIB.DLL is version 9.0.0.2711, 5,275,698 bytes.
Windows Application events repeatedly identify:
Exception: 0xC0000005
Fault offset: 0x002D2FF3
Calculated fault address: 0x3A6F2FF3
The corresponding x86 code is:
3A6F2FEE 83 C9 FF OR ECX,-1
3A6F2FF1 33 C0 XOR EAX,EAX
3A6F2FF3 F2 AE REPNE SCASB
Two callers reach the same scanning helper:
Caller 1: 0x3A6F318F, using a local buffer at [EBP-0xD8]. An earlier call passes 0x3F (63 decimal) as an argument.
Caller 2: 0x3A6F31DC, using a pointer stored at [EBP-0x34], previously derived from a local buffer at [EBP-0x118].
My question: How can we establish the actual readable capacity of each buffer, determine whether 63 bytes is the appropriate scan bound for either or both callers, and safely replace the effectively unbounded REPNE SCASB operation without changing the function's return semantics?
I would appreciate instruction-level guidance on the correct x86 repair strategy, including handling an invalid input pointer or an unterminated string.
Outlook | Windows | Classic Outlook for Windows | For home
1 answer
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more