Microsoft KB Archive/111263

= PRB: Causes of DX1020 or R6915 Unhandled Exception Error =

Article ID: 111263

Article Last Modified on 12/1/2003

-

APPLIES TO


 * Microsoft C Professional Development System 6.0a
 * Microsoft C/C++ Professional Development System 7.0
 * Microsoft Visual C++ 1.0 Professional Edition
 * Microsoft Visual C++ 1.5 Professional Edition
 * Microsoft Visual C++ 1.51
 * Microsoft Visual C++ 1.52 Professional Edition
 * Microsoft FORTRAN Compiler 5.1
 * Microsoft FORTRAN PowerStation 1.0 Standard Edition
 * Microsoft Fortran PowerStation 1.0a for MS-DOS
 * Microsoft Macro Assembler 6.11 Standard Edition

-



This article was previously published under Q111263







SYMPTOMS
When you build an application in Microsoft C, Microsoft Visual C++, Microsoft FORTRAN, Microsoft FORTRAN PowerStation, or Microsoft Macro Assembler (MASM), one of the MS-DOS-extended development tools returns an unhandled exception error message such as:

run-time error R6915 -

DOSX16: unhandled exception

-or-

DOSXNT : fatal error DX1020: unhandled exception:

Stack fault;

contact Microsoft Support Services

-or-

DOSXNT : fatal error DX1020: unhandled exception:

General protection fault;

contact Microsoft Support Services

-or-

DOSXNT : fatal error DX1020: unhandled exception:

Page fault;

contact Microsoft Support Services



CAUSE
Unhandled exception errors can be caused by a system configuration problem such as an ill-behaved device driver, a terminate-and-stay-resident (TSR) program, or a memory manager that is not configured correctly for the hardware in a particular machine.



RESOLUTION
Make backups of both the CONFIG.SYS and the AUTOEXEC.BAT files. Edit your CONFIG.SYS and AUTOEXEC.BAT files to remove all unnecessary device drivers and TSRs. You can typically get by with a CONFIG.SYS file that contains only a FILES= statement and a DEVICE=path\HIMEM.SYS. Depending on the hardware or configuration of a particular machine, other device drivers might be required. The AUTOEXEC.BAT file can contain a PATH statement and any required SET statements, but should not invoke any programs.

After creating clean CONFIG.SYS and AUTOEXEC.BAT files, shut down and restart your system. Try running the development tool that generated the unhandled exception error from the MS-DOS prompt, without starting Windows or any other programs. If at this point the problem goes away, substitute items back into your CONFIG.SYS and AUTOEXEC.BAT files until you can isolate which device driver or TSR caused the problem. If the problem occurs under Windows but not MS-DOS, try cleaning out your SYSTEM.INI file. If the problem does not go away, you will want to consult the Microsoft knowledge base for other causes of the error.

Additional query words: 1.00 1.50 DOSXNT

Keywords: kbprb KB111263

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.