You are currently offline, waiting for your internet to reconnect

"Buffer Overrun Detected" error after you install Office 2003 Service Pack 3 for Hebrew

Support for Office 2003 has ended

Microsoft ended support for Office 2003 on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article describes the Microsoft Office Word 2003 issue that is fixed in the hotfix package that is dated March 20, 2008.

This article describes the following items about the hotfix package:
  • The issues that the hotfix package fixes.
  • The prerequisites for installing the hotfix package.
  • Whether you must restart the computer after you install the hotfix package.
  • Whether the hotfix package is replaced by any other hotfix package.
  • Whether you must make any registry changes.
  • The files that the hotfix package contains.

Issue that the hotfix package fixes

This hotfix fixes the following issue that was not previously documented in a Microsoft Knowledge Base article:

The Hebrew version of Microsoft Office Word 2003 Service Pack 3 may stop responding when you run a spelling and grammar check or when you use a custom dictionary that was created before Service Pack 3. You may receive the following error message:
Microsoft Visual C ++ Runtime library
buffer overrun detected! Program: C:\Program Files\Microsoft Office\Office11\Winword.exe
A buffer overrun has been detected which has corrupted the program's internal state.
the program cannot safely continue execution and must now be terminated.

Note This problem occurs if the version of the MSSP3HE.dll file is
More information

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


Word 2003 must be installed before you apply this hotfix. Additionally, Office 2003 Service Pack 3 must be installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
870924 How to obtain the latest service pack for Office 2003

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

Installation instructions

When you install this hotfix, follow these guidelines:
  • Run Ptk.msp if you have the Hebrew Proofing Tools installed.
  • Run Hbrmui.msp if you have the Hebrew Language Pack installed
  • Run Mssp3he.msp if you have the Hebrew localized version installed.

Post-installation instructions

After you install this hotfix, the CUSTOM.DIC file must be renamed.

To have us rename it for you, go to the "Fix it for me" section. If you prefer to fix this problem yourself, go to the "Let me fix it myself" section.

Fix it for me

To rename the CUSTOM.DIC file automatically, click the Fix this problemlink. Click Runin the File Downloaddialog box, and follow the steps in the Fix it wizard.

Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.

Next, go to the "Did this fix the problem?" section.

Let me fix it myself

To rename the CUSTOM.DIC file, follow these steps:
  1. Click Start, click Run, type %appdata%, and then press ENTER.
  2. Open the Microsoft folder.
  3. Open the Proof folder.
  4. For every file that has a .DIC extension, change the extension to .OLD.
To copy the contents of the old CUSTOM.DIC to the new file, follow these steps:
  1. Open Microsoft Word.
  2. Add a new word to the dictionary.
  3. Exit Word.
  4. Open CUSTOM.OLD in Notepad.
  5. Copy the contents.
  6. Open CUSTOM.DIC in Notepad, paste in the content, and save the file.

Did this fix the problem?

Check whether the CUSTOM.DIC file is renamed. If the CUSTOM.DIC file is renamed, you are finished with this section. If the problem is not fixed, you can contact support.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The Hebrew version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information
File nameFile versionFile sizeDateTimePlatform
Hbrmui.cabNot applicable6,296,82419-Mar-200808:37Not applicable
Mssp3he.cabNot applicable572,62719-Mar-200808:37Not applicable
Ptk.cabNot applicable20,864,12319-Mar-200808:39Not applicable
Microsoft Windows Installer .msp file information
File nameFile versionFile sizeDateTimePlatform
Hbrmui.mspNot applicable6,340,09619-Mar-200808:39Not applicable
Mssp3he.mspNot applicable828,92819-Mar-200808:39Not applicable
Ptk.mspNot applicable21,045,76019-Mar-200808:39Not applicable

Contents of the Hbrmui.msp file

File nameFile versionFile sizeDateTimePlatform
Mssp3en.lex_1037Not applicable2,515,85512-Sep-200615:52Not applicable
OutlookNot applicable476,56212-Sep-200612:40Not applicable

Contents of the Mssp3he.msp file

File nameFile versionFile sizeDateTimePlatform
Mssp3en.lex_1037Not applicable2,515,85512-Sep-200615:52Not applicable

Contents of the Ptk.msp file

File nameFile versionFile sizeDateTimePlatform
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
fixit fix it

Article ID: 950009 - Last Review: 05/23/2014 07:26:00 - Revision: 8.0

Microsoft Office Word 2003

  • kbmsifixme kbfixme kbautohotfix kboffice2003presp4fix kbhotfixrollup kbexpertiseinter kbfix kbqfe kbhotfixserver KB950009