The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
“FATAL: Internal Stack Failure, System Halted” means different things on different computers. In historical MS-DOS, it signals that DOS ran out of internal stack frames used to handle interrupts—often because too many interrupts arrived too quickly. On the Control Data Cyber 930, similar wording refers to a console BIOS-detected stack overflow. Identify the operating system and hardware before applying a fix.
What does the error mean in MS-DOS?
For MS-DOS Version 3.20 or later, Microsoft Knowledge Base article Q41024, last modified May 16, 1989, describes the message as occurring when interrupts arrive too quickly and DOS exhausts its pool of internal stack frames. These frames support DOS interrupt handling. The error does not, by itself, show that a program’s own stack overflowed.
Interrupt sources can include devices such as network cards or laboratory instruments, according to the archived Microsoft article. The message indicates that DOS could not handle the interrupt activity with the available internal stack frames; it does not identify a particular faulty device on its own.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How is this different from an application stack overflow?
DOS interrupt stacks and an application’s own stack are distinct. Reproduced Microsoft technical material covering DOS 3.x–6.22 makes this distinction: changing the DOS STACKS setting may help when DOS interrupt stacks are exhausted, but it may not resolve an overflow in an application’s internal stack. The exact message and platform documentation matter before changing configuration.
#1 Best Overall
What does the error mean on a Cyber 930?
The Control Data Corporation Cyber 930 Maintenance Guide, revision H (November 1988), documents similar wording for a different failure: the console BIOS detects a stack overflow. In that case, the console halts, but NOS/VE is not affected. The guide directs the operator to power off the console, wait five seconds, and power it on again. This is system-specific historical guidance, not an MS-DOS repair.
What should you check before trying a fix?
- Record the exact error spelling, capitalization, and any messages immediately before or after it.
- Identify the operating system and version, and the computer or system model.
- Determine what halted: the whole machine, DOS, or only a separate console.
- Use documentation for that specific platform. Similar wording does not establish that the underlying failure or remedy is the same.
What does STACKS=n,s do in CONFIG.SYS?
In the historical MS-DOS context, STACKS=n,s configures DOS interrupt stack frames. Here, n is the number of stacks and s is the size of each stack in bytes. Microsoft Knowledge Base article Q41024 lists n as 8–64, with a default of 9, and s as 32–512 bytes, with a default of 128. It also gives a special default of 0,0 for MS-DOS 3.30 on IBM-PC, IBM-XT, and IBM-PC-Portable systems.
Rank #2
- Used Book in Good Condition
The same archived article says increasing the number of stacks usually corrects the DOS condition it describes. Those values and defaults are historical and version- and machine-dependent; they are not universal settings for every DOS release, emulator, or operating system. Check the documentation for the installation in question before editing CONFIG.SYS, and do not expect this setting to fix an application’s own stack overflow.
How to distinguish the two documented cases
| Clue | Historical MS-DOS case | Cyber 930 console case |
|---|---|---|
| Subsystem involved | DOS interrupt-handling stack-frame pool | Console BIOS stack |
| Documented trigger or detection | Too many interrupts arriving too quickly, exhausting the pool | Console BIOS detects a stack overflow |
| What halts | The DOS error reports that the system halted | The console halts; the guide says NOS/VE is unaffected |
| Documented response | Check the applicable DOS documentation and STACKS setting | Record the console message; power off the console, wait five seconds, then power it on |
The references describe historical systems and do not establish current support status or configurations. For an unidentified machine, the operating system/version, hardware, exact message, and surrounding output are needed to narrow down which meaning applies.
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
