How to fix the Runtime Code 28 Out of stack space
This article features error number Code 28, commonly known as Out of stack space described as The stack is a working area of memory that grows and shrinks dynamically with the demands of your executing program.
About Runtime Code 28
Runtime Code 28 happens when Windows fails or crashes whilst it’s running, hence its name. It doesn’t necessarily mean that the code was corrupt in some way, but just that it did not work during its run-time. This kind of error will appear as an annoying notification on your screen unless handled and corrected. Here are symptoms, causes and ways to troubleshoot the problem.
Definitions (Beta)
Here we list some definitions for the words contained in your error, in an attempt to help you understand your problem. This is a work in progress, so sometimes we might define the word incorrectly, so feel free to skip this section!
- Area — Area is a quantity that expresses the extent of a two-dimensional surface or shape, or planar lamina, in the plane.
- Memory — Use this tag for memory management or issues in programming
- Space — DO NOT USE THIS TAG! It is too ambigous, instead please use a more specific tag like letter-spacing separation between letters, whitespace between words, margin areas of a screen, layout or a platformlanguage-specific tag for non-web layouts etc.
- Stack — A stack is a last in, first out LIFO abstract data type and data structure
Symptoms of Code 28 — Out of stack space
Runtime errors happen without warning. The error message can come up the screen anytime Windows is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.
There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.
(For illustrative purposes only)
Causes of Out of stack space — Code 28
During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.
Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.
Repair Methods
Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.
If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.
Please note: Neither ErrorVault.com nor it’s writers claim responsibility for the results of the actions taken from employing any of the repair methods listed on this page — you complete these steps at your own risk.
Method 3 — Update your Virus protection program or download and install the latest Windows Update
Virus infection causing runtime error on your computer must immediately be prevented, quarantined or deleted. Make sure you update your virus program and run a thorough scan of the computer or, run Windows update so you can get the latest virus definition and fix.
Method 1 — Close Conflicting Programs
When you get a runtime error, keep in mind that it is happening due to programs that are conflicting with each other. The first thing you can do to resolve the problem is to stop these conflicting programs.
- Open Task Manager by clicking Ctrl-Alt-Del at the same time. This will let you see the list of programs currently running.
- Go to the Processes tab and stop the programs one by one by highlighting each program and clicking the End Process buttom.
- You will need to observe if the error message will reoccur each time you stop a process.
- Once you get to identify which program is causing the error, you may go ahead with the next troubleshooting step, reinstalling the application.
Method 2 — Update / Reinstall Conflicting Programs
Using Control Panel
- For Windows 7, click the Start Button, then click Control panel, then Uninstall a program
- For Windows 8, click the Start Button, then scroll down and click More Settings, then click Control panel > Uninstall a program.
- For Windows 10, just type Control Panel on the search box and click the result, then click Uninstall a program
- Once inside Programs and Features, click the problem program and click Update or Uninstall.
- If you chose to update, then you will just need to follow the prompt to complete the process, however if you chose to Uninstall, you will follow the prompt to uninstall and then re-download or use the application’s installation disk to reinstall the program.
Using Other Methods
- For Windows 7, you may find the list of all installed programs when you click Start and scroll your mouse over the list that appear on the tab. You may see on that list utility for uninstalling the program. You may go ahead and uninstall using utilities available in this tab.
- For Windows 10, you may click Start, then Settings, then choose Apps.
- Scroll down to see the list of Apps and features installed in your computer.
- Click the Program which is causing the runtime error, then you may choose to uninstall or click Advanced options to reset the application.
Method 4 — Re-install Runtime Libraries
You might be getting the error because of an update, like the MS Visual C++ package which might not be installed properly or completely. What you can do then is to uninstall the current package and install a fresh copy.
- Uninstall the package by going to Programs and Features, find and highlight the Microsoft Visual C++ Redistributable Package.
- Click Uninstall on top of the list, and when it is done, reboot your computer.
- Download the latest redistributable package from Microsoft then install it.
Method 5 — Run Disk Cleanup
You might also be experiencing runtime error because of a very low free space on your computer.
- You should consider backing up your files and freeing up space on your hard drive
- You can also clear your cache and reboot your computer
- You can also run Disk Cleanup, open your explorer window and right click your main directory (this is usually C: )
- Click Properties and then click Disk Cleanup
Method 6 — Reinstall Your Graphics Driver
If the error is related to a bad graphics driver, then you may do the following:
- Open your Device Manager, locate the graphics driver
- Right click the video card driver then click uninstall, then restart your computer
Method 7 — IE related Runtime Error
If the error you are getting is related to the Internet Explorer, you may do the following:
- Reset your browser.
- For Windows 7, you may click Start, go to Control Panel, then click Internet Options on the left side. Then you can click Advanced tab then click the Reset button.
- For Windows 8 and 10, you may click search and type Internet Options, then go to Advanced tab and click Reset.
- Disable script debugging and error notifications.
- On the same Internet Options window, you may go to Advanced tab and look for Disable script debugging
- Put a check mark on the radio button
- At the same time, uncheck the «Display a Notification about every Script Error» item and then click Apply and OK, then reboot your computer.
If these quick fixes do not work, you can always backup files and run repair reinstall on your computer. However, you can do that later when the solutions listed here did not do the job.
Other languages:
Wie beheben Fehler 28 (Kein Stapelplatz) — Der Stack ist ein Arbeitsbereich des Speichers, der dynamisch mit den Anforderungen Ihres ausgeführten Programms wächst und schrumpft.
Come fissare Errore 28 (Spazio fuori pila) — Lo stack è un’area di lavoro della memoria che cresce e si riduce dinamicamente con le esigenze del programma in esecuzione.
Hoe maak je Fout 28 (Geen stapelruimte) — De stapel is een werkgebied van het geheugen dat dynamisch groeit en krimpt met de eisen van uw uitvoerende programma.
Comment réparer Erreur 28 (Manque d’espace de pile) — La pile est une zone de travail de la mémoire qui grandit et se rétrécit dynamiquement avec les exigences de votre programme d’exécution.
어떻게 고치는 지 오류 28 (스택 공간 부족) — 스택은 실행 프로그램의 요구에 따라 동적으로 증가하고 축소되는 메모리 작업 영역입니다.
Como corrigir o Erro 28 (Sem espaço de pilha) — A pilha é uma área de trabalho da memória que aumenta e diminui dinamicamente com as demandas de seu programa em execução.
Hur man åtgärdar Fel 28 (Slut på stackutrymme) — Stacken är ett arbetsområde för minne som växer och krymper dynamiskt med kraven i ditt körprogram.
Как исправить Ошибка 28 (Нет места в стеке) — Стек — это рабочая область памяти, которая динамически увеличивается и уменьшается в соответствии с требованиями вашей исполняемой программы.
Jak naprawić Błąd 28 (Brak miejsca w stosie) — Stos jest obszarem roboczym pamięci, który rośnie i kurczy się dynamicznie wraz z wymaganiami wykonywanego programu.
Cómo arreglar Error 28 (Fuera de espacio de pila) — La pila es un área de trabajo de la memoria que crece y se reduce dinámicamente con las demandas de su programa en ejecución.
About The Author: Phil Hart has been a Microsoft Community Contributor since 2010. With a current point score over 100,000, they’ve contributed more than 3000 answers in the Microsoft Support forums and have created almost 200 new help articles in the Technet Wiki.
Follow Us: 
Last Updated:
16/08/22 01:27 : A Android user voted that repair method 3 worked for them.
This repair tool can fix common computer problems such as blue screens, crashes and freezes, missing DLL files, as well as repair malware/virus damage and more by replacing damaged and missing system files.
STEP 1:
Click Here to Download and install the Windows repair tool.
STEP 2:
Click on Start Scan and let it analyze your device.
STEP 3:
Click on Repair All to fix all of the issues it detected.
DOWNLOAD NOW
Compatibility
Requirements
1 Ghz CPU, 512 MB RAM, 40 GB HDD
This download offers unlimited scans of your Windows PC for free. Full system repairs start at $19.95.
Article ID: ACX09216EN
Applies To: Windows 10, Windows 8.1, Windows 7, Windows Vista, Windows XP, Windows 2000
Speed Up Tip #98
Upgrade Windows to 64-bit:
Most software today run on a 64-bit platform. So, if you are still using 32-bit, upgrading to 64-bit Windows version is a must. This, however, would require a hardware upgrade in order to run the new Windows software.
Click Here for another way to speed up your Windows PC
Microsoft & Windows® logos are registered trademarks of Microsoft. Disclaimer: ErrorVault.com is not affiliated with Microsoft, nor does it claim such affiliation. This page may contain definitions from https://stackoverflow.com/tags under the CC-BY-SA license. The information on this page is provided for informational purposes only. © Copyright 2018
Permalink
Cannot retrieve contributors at this time
| title | keywords | f1_keywords | ms.prod | ms.assetid | ms.date | ms.localizationpriority |
|---|---|---|---|---|---|---|
|
Out of stack space (Error 28) |
vblr6.chm1000028 |
vblr6.chm1000028 |
office |
ce345551-ad57-1120-546a-239d144c330a |
06/08/2017 |
medium |
The stack is a working area of memory that grows and shrinks dynamically with the demands of your executing program. This error has the following causes and solutions:
-
You have too many active Function, Sub, or Property procedure calls. Check that procedures aren’t nested too deeply. This is especially true with recursive procedures, that is, procedures that call themselves. Make sure recursive procedures terminate properly. Use the Calls dialog box to view which procedures are active (on the stack).
-
Your local variables require more local variable space than is available.
Try declaring some variables at the module level instead. You can also declare all variables in the procedure static by preceding the Property, Sub, or Function keyword with Static. Or you can use the Static statement to declare individual Static variables within procedures.
-
You have too many fixed-length strings. Fixed-length strings in a procedure are more quickly accessed, but use more stack space than variable-length strings, because the string data itself is placed on the stack. Try redefining some of your fixed-length strings as variable-length strings. When you declare variable-length strings in a procedure, only the string descriptor (not the data itself) is placed on the stack. You can also define the string at module level where it requires no stack space. Variables declared at module level are Public by default, so the string is visible to all procedures in the module.
-
You have too many nested DoEvents function calls. Use the Calls dialog box to view which procedures are active on the stack.
-
Your code triggered an event cascade. An event cascade is caused by triggering an event that calls an event procedure that’s already on the stack. An event cascade is similar to an unterminated recursive procedure call, but it’s less obvious, since the call is made by Visual Basic rather than by an explicit call in your code. Use the Calls dialog box to view which procedures are active (on the stack).
To display the Calls dialog box, select the Calls button to the right of the Procedure box in the Debug window or choose the Calls command. For additional information, select the item in question and press F1 (in Windows) or HELP (on the Macintosh).
[!includeSupport and feedback]
Runtime Error 28
Runtime error 28 is an error that occurs on Windows 7, Vista and XP computers. Essentially, this error arises from the fact that Visual Basic (VB) makes intense use of functions and “sub calls”, taking up so much memory that your system simply cannot keep up with the requests your system it making. The “Stack Space” of your system is basically a technical term used to describe the memory that your PC will use to run the programs on your system, and as your PC will be using too many memory allocations, it’s continually causing the likes of the runtime 28 error to show.
What Causes Runtime Error 28?
You can experience this error in this form:
Runtime Error 28 – Out of stack space
When software runs, it requires a lot of the system memory to operate (RAM). If it is the case that a certain application, in this case VB, is causing the operating system to continually ask for more memory that is available, the process cannot continue and so a “Stack overflow” occurs.
Possible causes of this issue are quite varied. It could be the application you are using is buggy and is attempting to use a lot of memory, which your system may not have. It could well be that a background application could be hogging system resources, causing other applications to be allocated less than what they need. Finally, there is a possibility that it could be the operating system that needs updating, as there may be certain bugs in the software that Microsoft remove via the issue of hotfixes.
How To Fix The Runtime 28 Error On Your PC
Step 1 – Re-Install Any Software Causing The Problem
Re-installing software should be your first step when attempting to deal with this problem, as it is the easiest method to carry out. Here is how you should go about it:
- Take a note of the application causing the “Out of Stack Space” runtime error 28.
- Go to Start > Control Panel > Add/Remove Programs
- Locate the problem application
- Highlight this application and click “Remove“
- Follow the un-install wizard and then once it has finished, restart your PC
- Install the latest version of the software again on your system
This method should remove any buggy installation files that may be hindering the operation of the process. This is not a sure fire way to remove the “Runtime error 28”, so if this did not help carry onto step 2.
Step 2 – Close Any Other Programs
Some programs that run in the background take up more memory than they should, hogging the system resources from other applications and process, which could cause the “Runtime Error 28”. To solve this issue:
- Open Task Manager (CTRL + ALT + DEL)
- Click the “Processes” tab
- Sort the list of processes by memory
- End task any processes that are not critical for system continuity
This should free up some more memory for that application you wish to use, allowing the program to operate without the constraints of an insufficient memory allowance.
Step 3 – Update Your Windows System
Sometimes it is wise to update your Windows System, as Microsoft may release hotfixes and updates to deal with issues such as this. These can easily be accessed by following these steps:
- Click Start > All Programs > Windows Update
- Let Windows Update scan your PC
- Let Windows Update scan the internet for updates
- Windows Update will then install the updates
- Restart PC when prompted
This method should help remove any issues you could encounter with “Runtime Error 28”, however it may still be present if the problem is more deep rooted, such as in the registry.
Step 4 – Clean Out The Registry Of Windows
- Download this registry cleaner
Registry cleaners can play a very important role in how well Windows operates, and can help stop the Runtime 28 error. The registry is basically a central database which stores vital settings and information for your system, allowing Windows to remember a huge number of details for your PC. Unfortunately, the registry is also prone to becoming corrupt, leaving your system running extremely slowly and unreliably. To fix this problem, you should use a ‘registry cleaner’ to scan through your registry and repair any of the damaged parts of it that are causing your computer to run extremely slowly or with errors. You can download our recommended registry cleaner below:
 |
Error Number: | Runtime Error 28 |
| Error Name: | Out of stack space | |
| Error Description: | The stack is a working area of memory that grows and shrinks dynamically with the demands of your executing program. | |
| Developer: | Microsoft Corporation | |
| Software: | Windows Operating System | |
| Applies to: | Windows XP, Vista, 7, 8, 10, 11 |
Overview of Out of stack space
People often prefer to refer to Out of stack space as a «runtime error», also known as a software bug. Software developers try to ensure software are free from these glitches until it is publicly released. Although these preventive actions are taken, at times errors like error 28 will be missed.
Error 28 might be faced by Windows Operating System users if they are using the program regularly, also seen as «The stack is a working area of memory that grows and shrinks dynamically with the demands of your executing program.». When that occurs, software end-users can inform Microsoft Corporation about the existence of error 28 bugs. Microsoft Corporation can then fix these errors in the source code and prepare an update for download. Therefore, when you encounter a prompt for a Windows Operating System update, it is usually because it’s a solution for fixing error 28 and other bugs.
What Produces Runtime Error 28?
Execution faults at the startup of Windows Operating System is when you’re most likely to run into Out of stack space. The following three most significant causes of error 28 runtime errors include:
Error 28 Crash — Error 28 can lead to total program freeze, which prevents you from doing anything. This emerges when Windows Operating System fails to respond to input properly, or does not know what output is required in return.
Out of stack space Memory Leak — When a Windows Operating System Memory leak occurs, this can result in the device running slow due to system resources running short. There are some potential issues that may be the reason for getting runtime problems, with incorrect coding leading to infinite loops.
Error 28 Logic Error — A logic error occurs when the machine generates the incorrect output, even when the user provides the right input. This occurs when Microsoft Corporation’s source code triggers vulnerability in information processing.
Microsoft Corporation problems with Out of stack space most often stem from a corrupt or missing Windows Operating System file. Obtaining a new, uninfected copy of your Microsoft Corporation file will usually resolve the problem. As a last measure, we recommend using a registry cleaner to repair any invalid Out of stack space, Microsoft Corporation file extension, and other file path references which could be causing the error message.
Typical Out of stack space Errors
Common Out of stack space Problems Encountered with Windows Operating System:
- «Out of stack space Error.»
- «Out of stack space is not a valid Win32 application.»
- «Sorry, Out of stack space encountered a problem.»
- «Sorry, we can’t find Out of stack space.»
- «Out of stack space is missing.»
- «Problem starting application: Out of stack space.»
- «Out of stack space not executing.»
- «Out of stack space quit.»
- «Faulting Application Path: Out of stack space.»
Windows Operating System Out of stack space issues occur with installation, while Out of stack space-related software runs, during shutdown or startup, or less-likely during operating system updates. Documenting Out of stack space problem occasions in Windows Operating System is key to determine cause of the Windows problems, and reporting them to Microsoft Corporation.
Out of stack space Issue Origins
Most Out of stack space problems stem from a missing or corrupt Out of stack space, virus infection, or invalid Windows registry entries associated with Windows Operating System.
Specifically, issues with Out of stack space caused by:
- Out of stack space registry keys invalid / corrupted.
- Malware infestation corrupted Out of stack space file.
- A different program (not related with Windows Operating System) deleted Out of stack space maliciously or by mistake.
- Another program is in conflict with Windows Operating System and its shared referenced files.
- Corrupt download or incomplete installation of Windows Operating System software.
Product by Solvusoft
Download Now
WinThruster 2022 — Scan your PC for computer errors.
Compatible with Windows 11, 10, 8, 7, Vista, XP and 2000
Optional Offer for WinThruster by Solvusoft | EULA | Privacy Policy | Terms | Uninstall
- Remove From My Forums
-
Question
-
Hi All,
I created a spreadsheet in excel 2013-VB v7.1 and had no issues with the code i created. when i try to run it i get the error code ’28’ and i have no idea to solve this.
Public Declare PtrSafe Sub Sleep Lib "kernel32" (ByVal A_Scound As Long) Public Sub ScheduleJoodi_API() ActiveWorkbook.UpdateLink Name:=ActiveWorkbook.LinkSources DoEvents Sleep (100) ActiveWorkbook.UpdateLink Name:=ActiveWorkbook.LinkSources Joodi Exit Sub End Sub Sub Joodi() If Sheet1.Range("A1").Value = 1 Then Application.Calculation = False Sheet1.Range("A2:A4").Copy Sheet1.Range("B2").PasteSpecial Paste:=xlPasteValues, Operation:=xlNone, SkipBlanks:=False, Transpose:=False Application.CutCopyMode = False Range("B1").Select Application.Calculation = True End If Call ScheduleJoodi_API End SubIf anyone could help out it would be greatly appreciated.
Thanks in advance,
Alex
Answers
-
You have two procedures; each calls the other one. As a result, you keep on pushing procedure calls onto the call stack ad infinitum — or rather, until you run out of stack space.
Try something like this instead:
Public Declare PtrSafe Sub Sleep Lib "kernel32" (ByVal A_Scound As Long) Public Sub ScheduleJoodi_API() ActiveWorkbook.UpdateLink Name:=ActiveWorkbook.LinkSources DoEvents Sleep 100 ActiveWorkbook.UpdateLink Name:=ActiveWorkbook.LinkSources End Sub Sub Joodi() If Sheet1.Range("A1").Value = 1 Then Application.Calculation = False Sheet1.Range("A2:A4").Copy Sheet1.Range("B2").PasteSpecial Paste:=xlPasteValues Application.CutCopyMode = False Range("B1").Select Application.Calculation = True End If Call ScheduleJoodi_API Application.OnTime Now + TimeSerial(0, 1, 0), "Joodi" End Sub
Regards, Hans Vogelaar
-
Marked as answer by
Friday, December 14, 2012 12:35 PM
-
Marked as answer by
-
You can combine the two procedures, if you wish:
Sub Joodi() If Sheet1.Range("A1").Value = 1 Then Application.Calculation = False Sheet1.Range("A2:A4").Copy Sheet1.Range("B2").PasteSpecial Paste:=xlPasteValues Application.CutCopyMode = False Range("B1").Select Application.Calculation = True End If ActiveWorkbook.UpdateLink Name:=ActiveWorkbook.LinkSources DoEvents Sleep 100 ActiveWorkbook.UpdateLink Name:=ActiveWorkbook.LinkSources Application.OnTime Now + TimeSerial(0, 1, 0), "Joodi" End SubWhen you run Joodi, it will run every minute (or at whatever interval you set in Application.OnTime).
Regards, Hans Vogelaar
-
Marked as answer by
Quist Zhang
Friday, December 14, 2012 12:35 PM
-
Marked as answer by