Fortus® Startup & Boot Failures
If you searched for Fortus won’t boot, Fortus not powering on, black screen, no display, controller computer dead, reboot loop, or UPS failure — this page is the master reference for structured startup diagnostics. The goal is to isolate whether the failure is incoming power, internal power distribution, onboard UPS behavior, computer power state, BIOS/POST, storage/boot, or printer interface initialization.
Request Diagnostic Support Back to Support Hub Jump to Fast Isolation Jump to FAQ
No power Black screen UPS path VGA check Controller boot Boot drive
Platforms Startup Sequence Fast Isolation Common Failure Points Repair Strategy Related Guides FAQ
Platforms Covered
Applies to Fortus® 360mc, 380mc, 400mc, 450mc, 900mc, and F900. Startup behavior varies slightly by revision and configuration, but the diagnostic logic is consistent.
Fastest Way to Start
Send your model + a photo of the exact screen message (or describe the symptom: no power / black screen / reboot loop). We can usually route you to the correct next checks quickly.
Send Details / Request Support Email With Template
Startup Sequence Overview
This is the chain you’re trying to validate. Failures usually live at one specific step.
  • Incoming facility power
  • Internal power distribution and protection
  • Onboard UPS module engagement
  • Computer power-on (controller SBC/motherboard)
  • BIOS / POST initialization
  • Operating system load
  • Printer interface initialization
Fast Isolation Sequence
Answer one question at a time: Is the computer receiving power? Is it posting? Is it booting? Is it initializing the printer interface?
1) Separate “no power” vs “no boot”
  • Is the system completely dead, or do you see partial activity?
  • Note any fans/LEDs you can observe on the controller computer (if accessible)
  • Intermittent behavior is a clue (powers sometimes / resets / clicks)
2) Confirm computer power state
  • Determine if the controller computer appears to power on (fan/LED behavior where present)
  • Separate “powered but not posting” from “powered and posting” early
  • Document any repeating cycle timing (example: resets every 10–30 seconds)
3) VGA monitor check
  • Connect an external VGA monitor to evaluate output state
  • Confirm whether BIOS/POST activity is present
  • Document what you see: no signal, BIOS screen, boot progress, loop
4) UPS as a diagnostic checkpoint
  • The controller computer power path includes an onboard UPS module
  • UPS degradation is a common failure point (random resets / won’t hold state)
  • Isolation helps separate UPS behavior from power supply/computer failure paths
Key Output You Want
The fastest repair decision comes from confirming the boot state: (1) no incoming power / no internal power, (2) UPS/power path instability, (3) computer powered but not posting/booting, (4) booted but not initializing the printer interface.
Get Help Diagnosing Support Hub
Common Failure Points
  • Onboard UPS module degradation (instability, resets, inconsistent startup)
  • Internal power supply failure (no power or brown-out under load)
  • Motherboard / controller SBC failure (no POST, no video, random resets)
  • Boot drive corruption or failure (stalls during boot, repeated boot attempts)
  • Loose or degraded internal cabling (intermittent behavior that worsens over time)
  • Progressive component degradation (symptoms worsen gradually across weeks/months)
Repair Strategy
Startup failures do not always require full controller replacement. Structured diagnostics can isolate whether the issue is limited to the UPS module, power supply, motherboard/controller SBC, storage device, or an initialization/interface condition — which often enables a targeted repair instead of an assembly swap.
What We Typically Do First
  • Confirm whether the controller is posting (BIOS/POST) vs stuck before that point
  • Confirm whether it boots the OS vs fails during storage/boot
  • Confirm whether it boots but fails to initialize the printer interface
Request Support
Related Fortus® Troubleshooting Guides
The other two Fortus “big three” failure families:
Loss of Extrusion
Blocked-at-head, ghost printing, liquefier restriction, drive/feed issues.
Open Guide
Motion Faults
Auto Home XYZ failures, Failed Auto Z, limit switch states, enable conditions.
Open Guide
Support Hub
Return to the main Fortus + F123 support map.
Open Hub
FAQ
Why won’t my Fortus power on?
Common causes include internal power supply failure, UPS module degradation, controller motherboard/SBC failure, or a power distribution issue.
What causes a black screen on startup?
A black screen can indicate no POST/BIOS activity, a controller hardware fault, or a boot failure. A VGA monitor check helps separate “no signal” vs “booting but not displaying.”
Why do reboot loops happen?
Reboot loops are often caused by power instability (including UPS degradation), boot device issues, or a failing controller subsystem. Isolation helps identify the failure path.
Which models does this apply to?
Fortus 360mc, 380mc, 400mc, 450mc, 900mc, and F900 systems.
Still Stuck?
Send your model + a photo of the screen (or tell us: no power / black screen / reboot loop / boots but won’t initialize). We’ll point you to the fastest next checks.
Request Diagnostic Support Email Support
NEXT 3DP is an independent service provider and is not affiliated with or authorized by Stratasys Ltd.