OpenComputers · Troubleshooting · Beginner

OpenComputers Troubleshooting Guide: Boot Failures and Component Limits

Setting up your first modular system in OpenComputers often leads to frustrating red error screens or unexplained shutdowns. This guide will walk you through diagnosing and fixing the most common boot failures, memory crashes, and component limit errors. Mastering these troubleshooting steps ensures your automation networks and Lua scripts run reliably without hardware bottlenecks.

What you need

  • An assembled OpenComputers setup (Computer Case, Screen, Keyboard, and internal components)
  • An Analyzer (for diagnosing hardware and component connections)
  • A Lua BIOS EEPROM
  • An OpenOS Floppy Disk (and a Disk Drive if using a Tier 1 or Tier 2 Computer Case)
  • A Power Converter and a stable energy source from another mod (unless power requirements are disabled in the config)
  • Higher-tier CPUs, APU, or Memory sticks for hardware upgrades

Step by step

  1. 1Read the Error Message or Beep Code

    When a computer fails to start, your first clue is either text on the Screen or an audible beep pattern from the Computer Case. If your Screen stays completely black while the case beeps, ensure your Graphics Card (or APU) matches the tier of your Screen and is properly seated inside the case. If the Screen works, read the exact blue or red error text displayed, as it points directly to the failing hardware layer.

    Tip: Sneak and right-click the Computer Case with an Analyzer to print the last crash error directly into your chat log, even if you do not have a Screen attached.

  2. 2Fix 'No Bootable Medium Found'

    This error means the Lua BIOS cannot find an operating system on any connected storage device. Brand-new Hard Disk Drives are completely blank and cannot boot a computer on their own. To fix this, insert an OpenOS Floppy Disk into your case's built-in floppy slot (Tier 3) or an adjacent Disk Drive block (Tier 1 and 2), then press the power button.

    Tip: Once booted from the floppy, type 'install' in the command line to copy OpenOS permanently onto your internal Hard Disk Drive so you no longer need the floppy.

  3. 3Resolve 'Missing EEPROM' or BIOS Errors

    If the computer refuses to even look for a floppy disk and complains about the BIOS or EEPROM, check the small EEPROM slot on the left side of the Computer Case GUI. A raw crafted EEPROM is empty; you must combine it with an OpenComputers Manual in a crafting grid to flash the standard Lua BIOS onto it. Place the flashed Lua BIOS EEPROM back into the slot and reboot.

  4. 4Solve 'Too Many Components Connected'

    When your computer shuts down immediately upon booting or refuses to start after you connect a new cable or Adapter, you have exceeded your CPU's component bus limit. Open the Computer Case and look at your CPU or APU; hovering over it while holding the Shift key in your inventory or JEI will show the maximum number of supported components. Either disconnect non-essential external blocks from your Cable network or upgrade to a higher-tier CPU.

    Tip: Internal parts like the Graphics Card, Memory, Hard Disk Drives, and even the Screen and Keyboard count toward this total component limit!

  5. 5Eliminate 'Out of Memory' Crashes

    If the computer starts to boot into OpenOS, freezes, and displays an 'Out of memory' error, your installed RAM is insufficient for the operating system and running scripts. Open the Computer Case GUI and inspect the memory slots. Replace your Tier 1 Memory sticks with Tier 1.5, Tier 2, or Tier 3 Memory sticks, or simply fill both memory slots to expand the total available pool.

    Tip: Running complex GUI programs or connecting high-tier Screens consumes significantly more RAM during startup than simple text-only setups.

  6. 6Prevent Unexpected Shutdowns (Power Starvation)

    If your computer turns on, runs for a few seconds, and suddenly powers off without displaying an error message, it is starving for energy. When played alongside power mods, OpenComputers requires a continuous energy supply converted through a Power Converter block placed adjacent to the case or connected via Cables. Check your power generation and attach a Capacitor block to your computer network to buffer against sudden energy spikes caused by heavy disk usage or wireless messages.

    Tip: You can check the exact internal energy buffer of a network by right-clicking the Computer Case or Capacitor with your Analyzer.

  7. 7Isolate Network Bleed with Switch or Access Point

    In larger bases, running a single continuous line of OpenComputers Cable between multiple machines will merge all their components together, instantly crashing every computer on the line with a 'Too many components' error. Break the direct cable link between separate systems. Instead, use a Relay block or Wireless Network Cards to let computers communicate via network messages without sharing their physical component connections.

How it works

OpenComputers mimics real-world computer architecture rather than giving you a magic block that works out of the box. When you press the power button, the machine goes through a strict boot sequence. First, it checks the energy buffer. Second, it executes the low-level code stored on the EEPROM (usually the Lua BIOS). The BIOS then scans all connected storage components for a bootable file named 'init.lua', which is what loads OpenOS into your system's Memory.

The component limit mechanic exists to balance progression and server performance. Every CPU and APU has a strict bus budget based on its tier. Whenever a computer is connected to a block—whether it lives inside the case like a Redstone Card, sits adjacent like a Screen, or connects down the hall via Cables and Adapters—the computer registers it as an active component. If the total count exceeds the CPU's rating, the hardware halts execution to force you into upgrading your processor or designing cleaner, segmented networks.

Memory and power operate dynamically in real time. Lua scripts, loaded libraries, and screen buffers physically occupy space in your installed Memory items; if garbage collection cannot free up enough bytes, the virtual machine throws an out-of-memory panic. Similarly, every tick of CPU execution, screen pixel update, and robot movement drains energy from the network's internal buffer. If a sudden spike draws more energy than your Power Converter and Capacitors hold, the machine immediately loses state and powers down.

Common mistakes

  • Putting a blank EEPROM into the case instead of crafting it into a flashed Lua BIOS EEPROM first.
  • Connecting two separate computers with regular Cables to send data, which accidentally forces both CPUs to load every single component from both setups.
  • Attempting to boot a brand-new computer using only a crafted Hard Disk Drive without inserting the OpenOS Floppy Disk to install the operating system first.
  • Matching a high-tier Screen with a low-tier Graphics Card, or forgetting the Graphics Card entirely while using a standard CPU instead of an APU.
  • Connecting external mod cables (like RF conduits or EU wires) directly to the Computer Case without routing them through an OpenComputers Power Converter block.

FAQ

Why does my computer beep and show nothing on the screen?

Audible beep codes mean the computer is failing before it can initialize the display. Check that you have a valid Lua BIOS EEPROM, at least one stick of Memory, a CPU, and a Graphics Card inserted, and make sure the Screen is connected to the case.

Do Cables and Capacitors count toward the CPU component limit?

Basic Cables, Power Converters, and Capacitors do not consume component slots on your CPU. However, blocks like Screens, Keyboards, Disk Drives, Adapters, and all internal cards and drives do count toward the limit.

How do I fix a computer stuck in an infinite crash loop from a bad startup script?

Insert an OpenOS Floppy Disk into an attached Disk Drive and boot the computer. It will usually prioritize or let you select the floppy disk, allowing you to access the command prompt, mount your internal Hard Disk Drive, and delete or edit the broken script.

Can I turn off the power requirement if my computer keeps shutting down?

Yes. If you have access to the configuration files, open the OpenComputers config folder and adjust the power settings to ignore energy requirements, which is very helpful for learning Lua without worrying about power generation.

By systematically checking your BIOS EEPROM, OpenOS boot media, RAM capacity, CPU component limits, and power buffers, you can quickly diagnose and fix any OpenComputers hardware failure.

More OpenComputers guides

OpenComputers · Getting startedHow to Build Your First Computer and Install OpenOSIn this guide, you will learn how to assemble your very first modular Tier 1 computer in OpenComputers and install the standard OpenOS operating system onto its hard drive. Mastering this initial setup is essential because it provides the foundational terminal required to write Lua scripts, control redstone, and automate complex factory systems.Beginner8 steps
OpenComputers · ProgressionOpenComputers Hardware Tiers and Progression GuideOpenComputers relies on a strict modular tier system where every component, from memory sticks to graphics cards, must be carefully matched to your computer case. This guide will walk you through the progression from a basic Tier 1 machine up to a fully loaded Tier 3 Server Rack. Mastering these hardware limits ensures you never waste valuable resources on incompatible parts or crash your scripts due to insufficient memory.Beginner7 steps
OpenComputers · PowerOpenComputers Power Converter and Networking ExplainedIn OpenComputers, a single Cable carries power, component connections, and network messages all at the same time. While convenient, this all-in-one behavior causes massive chaos when you try to power two computers from the same energy source, as they will accidentally hijack each other's screens and keyboards. This guide explains how to convert modded energy using the Power Converter and how to isolate your systems using Power Distributors and Relays.Beginner7 steps
OpenComputers · ExplainedOpenComputers Component API and Event Logic ExplainedIn this guide, you will learn how to bridge the gap between your Lua scripts and physical hardware in OpenComputers by mastering the Component API and the event system. Understanding how component addresses, proxy tables, and event pulling work is essential for automating complex multi-device networks and interacting with other mods via the Adapter.Intermediate7 steps
OpenComputers · AutomationHow to Automate Other Mods with the OpenComputers AdapterIn this guide, you will learn how to use the OpenComputers Adapter and Redstone I/O blocks to read data from external tech mod machines and automatically control them using Lua scripts. Mastering this setup allows you to build smart power grids that toggle generators based on energy storage levels, prevent reactor meltdowns, and coordinate complex factory lines without manual intervention.Intermediate8 steps
OpenComputers · Setup guideHow to Assemble and Program OpenComputers RobotsIn this guide, you will learn how to construct a modular OpenComputers Robot using the Electronics Assembler and program it in Lua to automate resource gathering. Mastering robots allows you to offload tedious tasks like branch mining and crop harvesting to persistent, self-contained machines that interact with the world just like a player.Intermediate8 steps