Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Exit code 137 usually means the operating system killed the Minecraft server because it ran out of memory. Exit code 1 is only a generic failure indicator; the useful diagnosis is the first actual error in the server console or crash report. A Java version that does not match the Minecraft release is another frequent cause of startup failure.
Godlike.Host offers hosted Minecraft Java servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
Minecraft does not define one universal meaning for every number shown after a server stops. The number is often supplied by the operating system, a hosting panel, or a wrapper script. Treat it as a starting clue, not as the complete error message.
As an Amazon Associate I earn from qualifying purchases.
What the common exit codes mean
| Exit code | Most likely meaning | What to inspect first |
|---|---|---|
| 137 | The process received Linux signal 9 (SIGKILL), commonly because the operating system or container ran out of memory. | Memory limits, heap allocation, concurrent processes, view and simulation distance, entities, plugins and mods. |
| 1 | A generic failure wrapper. It does not identify one specific fault. | The first real error in the console, the crash report, the server JAR, Java version, EULA and mod or plugin logs. |
| Other values | Could be a wrapper, operating-system signal conversion or application-specific result. | The complete console output and the way the server was launched. |
The Linux convention behind 137 is important: 128 plus signal 9 equals 137. SIGKILL is abrupt, so the JVM may not have time to print a normal stack trace. That is different from a Java heap failure, which normally reports an OutOfMemoryError before exiting. Hosting articles from Specific Languages and several game hosts describe this distinction; their recommendations are practical guidance rather than Minecraft standards.
Fix Minecraft server exit code 137
Work through the following order. Increasing memory before checking for a leak can make the next crash take longer, but it does not remove the underlying fault.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
1. Confirm that memory was actually exhausted
Check the host panel’s event or console history and the operating system log. Some panels display an “Out of Memory: true” status, although the exact wording differs by provider. On a Linux host, run the command below while logged in to the machine:
free -hLook at available memory and swap, not only the total installed RAM. If the server runs in a container, virtual machine or managed game panel, the relevant limit may be lower than the physical machine’s total. Check the container or plan limit as well as the Java heap setting. A second service, backup job, map renderer or another game server can consume the remaining memory and trigger the kill.
2. Check the heap setting and leave room for the system
The -Xms option sets the initial heap and -Xmx sets the maximum heap. Do not set -Xmx equal to every megabyte available on the host: Java, native libraries, operating-system services, the launcher and plugins can use memory outside the Java heap. If the configured heap is genuinely too small for your player count, world size and mod set, raise it in a controlled step and retest.
A hosting panel may expose this as “maximum memory,” “RAM,” or an -Xmx field. Change the panel value rather than editing a generated startup command that the panel will overwrite. After saving, verify the actual command or startup log so you know the new limit was applied.
3. Reduce the workload before buying more RAM
Lower view-distance and simulation-distance in server.properties. Hosting guides commonly suggest trying values around 6–8 as a troubleshooting range, not as an official requirement. Restart after changing them and observe whether the process remains stable.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Also investigate unusually large numbers of entities. Mob farms, dropped item stacks, minecarts and other ticking entities increase both memory use and server work. Remove or temporarily disable the farm or affected chunk, then compare the server’s behavior. Make a backup before deleting entities or editing a world.
Recommended Free Tools
4. Look for a plugin or mod leak
A leak can gradually consume memory until the operating system kills the process. If the server is stable immediately after a restart but fails after hours or days, suspect a plugin, mod, world component or scheduled task. Record when memory usage rises and what changed before the problem began.
The Spark profiler is commonly recommended for locating performance and memory problems. Use it to identify a plugin, mod or task that grows over time, then update, reconfigure or remove the suspected component. Test one change at a time on a copy of the server so you can identify the cause without risking the live world.
5. Apply JVM flags only when they fit your server
Some hosting guides name Aikar’s flags as a useful garbage-collection configuration for supported Minecraft server setups. They are not a cure for a leaking plugin, an undersized container or an incompatible Java runtime. Follow the flag set’s instructions for your Java and server version; do not paste a command designed for a different release and assume every option remains valid.
6. Retest and distinguish a leak from a capacity problem
After each change, note the player count, loaded worlds, view distances, Java version and time until failure. If memory reaches the limit only during a predictable peak, the server may need more capacity. If usage climbs continuously at a steady workload, find the leak instead. Adding RAM to the second case merely delays the next SIGKILL.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Fix Minecraft server exit code 1
Exit code 1 has no single repair. It is a generic result used when the server process fails, so changing memory settings at random is usually inefficient.
1. Read the first meaningful error
Open the complete console output from the failed start and the newest file in the crash-reports directory. Start at the first exception or “caused by” line, not the final wrapper line that says the process exited with code 1. Later errors are often cascading symptoms. Copy the Java version, server version and the names of any mod or plugin mentioned in that first error.
2. Verify the server JAR and launch path
A missing, misnamed or corrupt server JAR is a common cause. Confirm that the startup command points to the file that actually exists in the server directory and that the filename matches the command exactly, including capitalization. If you replaced a JAR, check that the download completed and that the file is not an HTML error page saved with a .jar extension.
For a modpack, Forge or Fabric installation, use the launch files generated for that pack rather than substituting a vanilla JAR. Hosting guides from Shockbyte and UltraServers specifically list reinstalling Forge, Fabric or a custom JAR as a remedy when those files are damaged or incomplete. Back up the world and configuration before reinstalling.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors3. Check Java before changing the world
Run:
java -versionIf the command reports a different runtime from the one used by the panel or startup script, correct the path first. An incompatible runtime commonly produces an UnsupportedClassVersionError or another class-loading message. A JDK includes the JRE components needed to run a server, so a JDK is acceptable when the required Java version is installed.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
4. Isolate mods and plugins
A newly installed or updated plugin can crash during startup because of a missing dependency, incompatible API or invalid configuration. A mod can do the same, particularly after a Minecraft or loader update. Compare the first error with the component list, then test on a copy:
- Stop the server and make a complete backup.
- Remove or disable only the component named by the error.
- Start the copy and check whether the original exception disappears.
- Install a version that supports your exact Minecraft and loader version, or restore the previous working version.
Do not delete a plugin’s data directory as a first step. It may contain permissions, claims or other state. Rename it only after a backup and only when the error identifies a corrupt configuration.
5. Validate configuration and the EULA
Malformed JSON, YAML or properties files can stop a server before it opens a port. Restore the last known-good configuration, then reapply changes individually. A fresh server also stops if the EULA has not been accepted. Review eula.txt and follow the license terms before changing its setting; accepting it is a legal choice, not merely a technical workaround.
6. Reinstall only after preserving evidence
If the JAR, loader files or libraries are corrupt, a clean reinstall can fix exit code 1. Preserve the world, server.properties, whitelist, operators, plugin and mod lists, and the crash report. Reinstall the same Minecraft release and loader first, start an empty test world, then restore content in stages. This prevents a damaged world or incompatible component from being mistaken for a successful repair.
Use the Java version required by your Minecraft release
The Minecraft Wiki’s server requirements page gives a general baseline of Java 8 or newer, but release-specific requirements override that baseline. The table below combines that baseline with the version ranges reported by the Minecraft Wiki and modded-server guides. “Java 25” for 26.x comes from third-party guides and was not confirmed on the official wiki page available for this article.
| Minecraft Java Edition server | Reported Java requirement | Practical qualification |
|---|---|---|
| 1.8–1.16.5 | Java 8 | Java 11 often works; Forge modpacks are safest on Java 8 according to the cited guides. |
| 1.17–1.17.1 | Java 16 or newer | Use a runtime supported by the exact server and loader build. |
| 1.18–1.20.4 | Java 17 or newer | The Minecraft Wiki confirms Java 17 as the requirement beginning with 1.18. |
| 1.20.5–1.21.x | Java 21 | Do not assume Java 17 remains sufficient after upgrading. |
| 26.x | Java 25 reported by third-party guides | Not confirmed by the official wiki page retrieved; verify the requirement for the specific release before upgrading. |
Modded servers can differ from vanilla. Forge, and sometimes Paper-based plugin stacks, may require a different runtime than the underlying Minecraft release. ModReady and mc-node both advise matching Mojang’s minimum or the next suitable long-term-support release, but their guidance is not a substitute for the loader’s own compatibility notes.
Commands and checks for a Linux server
These checks help separate a Java problem from a host-limit problem. Run them as the same user and in the same environment that starts the server whenever possible.
Free tools Windows power users keep installed
One-click scans. No signup required.
java -version— identifies the runtime selected by the shell.which java— shows which executable that shell will use.free -h— displays total, used and available memory plus swap.ps aux | grep '[j]ava'— shows the running Java command, including visible heap options.df -h— checks whether a full disk prevented logs, libraries or world data from being written.
On managed hosting, you may not have permission to run these commands. Ask the host for the container memory limit, the exact Java command, the termination reason and the complete console log. A panel’s “restart failed” message is not enough to diagnose either code 137 or code 1.
How to read the symptoms
The server dies during startup with code 1
Prioritize Java compatibility, a missing or corrupt JAR, loader files, EULA status and malformed configuration. A startup failure before players join is less consistent with a gradual memory leak than with a deterministic configuration or class-loading error.
The server runs, then suddenly reports code 137
Check memory pressure, container limits, entity counts and plugins or mods that grow over time. The lack of a normal Java stack trace is expected when SIGKILL arrives from outside the JVM. Use timestamps and memory observations to distinguish a leak from a workload spike.
The server reports an OutOfMemoryError instead
An OutOfMemoryError is a JVM-level heap failure and normally leaves a stack trace. It can still require more heap or less workload, but investigate the named allocation and component rather than treating it as identical to an operating-system SIGKILL.
Prevent repeat crashes
- Record the Minecraft, loader, Java, plugin and mod versions before every upgrade.
- Back up the world and configuration before changing memory, loaders or content.
- Keep view and simulation distances appropriate for the available capacity.
- Set alerts for memory growth and disk usage instead of waiting for a restart failure.
- Test updates on a copy with a small world and the same Java runtime.
- Keep the full console and crash-report history; the first exception is more valuable than the final exit number.
Exit code 137 is a resource and process-termination clue; exit code 1 is a request to inspect the real error. Matching Java to the Minecraft release, preserving logs, and changing one variable at a time turns both messages into diagnosable problems rather than repeated blind restarts.
Quick Recap
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.
