Excel Err Msg: "Excel Has Caused a Segment Load Failure..."

 Last reviewed: April 21, 1997
Article ID: Q94676

The information in this article applies to:
  • Microsoft Excel for Windows, versions 4.0, 4.0a, 5.0, 5.0c

SUMMARY

If Microsoft Excel for Windows is unable to read from your hard disk, you will receive the following error message: 

   Application Error: Excel has caused a segment load failure in
   module EXCEL.EXE at xxxx:yyyy
This error may indicate one of the following:
  • The EXCEL.EXE file did not expand properly during setup

    -or-

  • A memory conflict exists

    -or-

  • A hardware problem has occurred

MORE INFORMATION

The EXCEL.EXE File Did Not Expand Properly During Setup

If you received the error message the first time you tried to run Microsoft Excel after installing it, the EXCEL.EXE file may not have been expanded properly. You will find this file in the directory in which you installed Microsoft Excel. Use Windows File Manager to ensure that the file date and size match one of the following: 

   Microsoft Excel version 4.0:

       4/1/92  2740736
      11/1/92  2766592

   Microsoft Excel version 5.0:

     12/14/93  4185600

   Microsoft Excel version 5.0c:

       7/8/94  4246784
If the file date and size do not match any of the above dates and sizes, delete EXCEL.EXE and reinstall Microsoft Excel. When you reinstall, you can avoid installing all of the other Microsoft Excel files by choosing Custom Installation and selecting the Microsoft Excel only option.

A Memory Conflict Exists

If your EXCEL.EXE file appears to have the right date and file size, clean boot your machine. For more information on clean booting, see pages 99-100 of the "Getting Started with Microsoft Windows" version 3.1 manual, and pages 528-531 of the version 3.1 "Microsoft Windows Users Guide."

In Microsoft Windows, try closing down all other applications. In addition, clear the 32-Bit Access check box. To do this:

  1. In the Windows Control Panel, choose the 386 Enhanced icon.

  2. Choose the Virtual Memory button.

  3. Choose the Change button, and clear the 32-bit Access check box.

If you are using a third-party disk-compression utility, verify that your Microsoft Windows swapfile, whether temporary or permanent, is on your non-compressed drive. For more information about checking and changing your swapfile settings, see pages 533-537 of the "Microsoft Windows Users Guide."

CAUTION: Quit Windows before you try the following procedure.

If you still receive the error, type "CHKDSK /f" (without the quotation marks) at the MS-DOS command prompt. This will fix your file allocation table. If there are many lost clusters reported, your hard drive may be fragmented and in need of optimization. You can use a hard drive utilities application to optimize your drive.

A Hardware Problem Has Occurred

If the error persists, you may also need to run diagnostic tests on your hard drive and hard drive controller.

NOTE: There are a variety of utility products on the market that you can use to run diagnostic tests and optimize your drive. For more information about these utility products, consult your computer dealer or service representative.

REFERENCES

"Microsoft Windows User's Guide," version 3.1, pages 528-531, 533-537 "Getting Started with Microsoft Windows," version 3.1, pages 99-100

Additional Query Words: 4.00 4.00a fat UAE XL 

Version             : 4.00 4.00a 5.00 5.00c
Platform            : WINDOWS
Issue type          : kbprb

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 21, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.