<p>Few things to try,</p>
<p><strong>Check G-Code</strong> - Verify that the slicer is not the problem, slice using some other program / make a new default profile and re-slice.</p>
<p><strong>3D File</strong> - Also In parallel with the above point, I would get a standard test cube STL to start with. This will be a simple quick print to get a solid reference.</p>
<p><strong>Voltages</strong> - Get a Multi-meter on the Regulated Voltage rails, 5V Rail, 12V rail / 24V rail. See if at the moment of crash a voltage rail collapse, the most likely one would be the microcontroller rail, but you may be able to see the problem somewhere else.</p>
<p><strong>Current</strong> - If possible, measure the current draw of the printer either from the mains or after the AC/DC regulator. Its possible something is going horribly wrong and current limiting.</p>
<p><strong>Serial Port</strong> - Possibly connect the printer to a PC via its serial port and open a com port. See if the printer spits out an error code at the time of crash?</p>
<p><strong>End Stops</strong> - Double check that none of the End Stops are accidently being triggered (Although this should not crash the system, it might be part of the problem)</p>
<p><strong>Verify Sensor Readings</strong> - Check all end stops, check the bed temperature readings, check the nozzle temperature reading. Maybe a sensor has failed and is causing the controller to crash out.</p>

CC BY-SA 4.0
2020-08-03T16:57:23.460Z
of your suggestions, only the voltage and current could be relevant, because the rest would have resulted not in a crash like that, it's a print from SD-card afaict, making Serial port a non-issue, the file wouldn't result in a hangup, the G-code does not result in a self-reset/bluescreen, endstops are ignored during actual printing (printers use software endstops only then)
Trish
CC BY-SA 4.0
2020-08-04T04:11:10.140Z
@Trish: While the serial port isn't being used for printing, it could spill useful debug output indicating the cause of the crash at the moment it happens.
R.. GitHub STOP HELPING ICE
CC BY-SA 4.0
2023-03-16T12:18:08.017Z
+1 for serial port debugging, you could put more emphasis on that option. I am surprised that no one else mentioned this.
Greenonline
CC BY-SA 4.0
2020-08-03T13:51:47.613Z
2020-08-03T13:51:47.613Z
Sneaky Puffin
<p>I see a couple likely culprits for a hardcrash like this</p>
<ul>
<li>problems with the power supply. If the power supply does not provide enough voltage an/or current to the board, this can lead to a lockup of the board.</li>
<li>temperature issues of the board. If the board overheats, it could fail to execute properly, leading to abort. make sure that the board is not overheating.</li>
<li>faulty firmware. recompile your firmware and reflash it.</li>
<li>faulty board.</li>
</ul>

CC BY-SA 4.0
2020-08-03T17:05:02.800Z
2020-08-03T17:05:02.800Z
Trish
<p>If you compiled your own firmware using visual studio code, use platformio's inspector found on the platformio homepage to make sure there are no memory overrun issues. You must read the whole prompt because sometimes it will not explicitly state that there is an issue</p>

CC BY-SA 4.0
2023-03-15T22:21:40.457Z
2023-03-15T22:21:40.457Z
greenice24
<p>I am converting an old Makerbot Replicator 2 to Marlin Firmware and everything works. The printer heats up, auto bed levels, and starts the print. However, after a couple minutes (usually after the 1<sup>st</sup> or 2<sup>nd</sup> layer), the printer crashes and stops. It does not continue printing and I have to restart it again. It crashed for every single print, I have not had any successful prints yet.</p>
<p>Here is a video showing the issue:</p>
<p><div class="youtube-embed"><div>
                <iframe width="640px" height="395px" src="https://www.youtube.com/embed/MzcrX3wcA-Q?start=0"></iframe>
            </div></div></p>
<p>The camera was started right when the print started. After about 1.5 minutes, the printer crashes, and the LCD screen freezes.</p>
<p>Here are photos of a couple of prints that crashed:</p>
<p><a href="https://i.sstatic.net/VHzNi.jpg" rel="nofollow noreferrer" title="Photos of sample prints"><img src="https://i.sstatic.net/VHzNi.jpg" alt="Photos of sample prints" title="Photos of sample prints" /></a></p>
<p>I have all of my code here: <a href="https://github.com/RosalieWessels" rel="nofollow noreferrer">RosalieWessels</a> / <a href="https://github.com/RosalieWessels/Marlin_MakerbotReplicator2" rel="nofollow noreferrer"><strong>Marlin_MakerbotReplicator2</strong></a></p>
<p>My models are sliced with Cura and printed in PLA.</p>
<p>I tried hotend temperatures of 200, 210, and 220 degrees C. My print speed is around 50 or 60 mm/s.</p>
<p>Here is a sample sliced file that was used:
<a href="https://filebin.net/df33a3jjwgemz0m8" rel="nofollow noreferrer">https://filebin.net/df33a3jjwgemz0m8</a></p>

CC BY-SA 4.0
2020-08-03T06:38:11.967Z
I want cake too! https://youtu.be/MzcrX3wcA-Q?t=32
0scar
CC BY-SA 4.0
2020-08-03T06:44:31.423Z
One thing you should fix is the attachment of the belts to the carriage; the belt (tensioned with a tie wrap is quite original) has a lot of play. This causes the layer shifts in your prints. But, I don't think this is related to the crashing.
0scar
CC BY-SA 4.0
2020-08-03T08:15:41.820Z
Can you measure the voltage draw of heater and bed?
Trish
CC BY-SA 4.0
2020-09-02T18:35:30.573Z
Hello Rosalie, I noticed your question has been up for a while now. Have any of the answers below been able to solve your question? If so, would you mind accepting the appropriate answer. If not, what is missing so that we may help you further? Also, if you have figured it out on your own, you can always answer and accept your own solution after 48 hours. Thank you!
0scar
CC BY-SA 4.0
2023-03-15T23:30:38.400Z
The [filebin link](https://filebin.net/df33a3jjwgemz0m8) seems to be empty or dead.
Greenonline
<marlin>
Printer crashes at the beginning of a print
Rosalie W
# Printer crashes at the beginning of a print

(Asked by: username_0 on 2020-08-03)

I am converting an old Makerbot Replicator 2 to Marlin Firmware and everything works. The printer heats up, auto bed levels, and starts the print. However, after a couple minutes (usually after the 1st or 2nd layer), the printer crashes and stops. It does not continue printing and I have to restart it again. It crashed for every single print, I have not had any successful prints yet.

Here is a video showing the issue:

The camera was started right when the print started. After about 1.5 minutes, the printer crashes, and the LCD screen freezes.

Here are photos of a couple of prints that crashed:

[![Photos of sample prints](https://i.sstatic.net/VHzNi.jpg "Photos of sample prints")](https://i.sstatic.net/VHzNi.jpg "Photos of sample prints")

I have all of my code here: [RosalieWessels](https://github.com/RosalieWessels) / [**Marlin\_MakerbotReplicator2**](https://github.com/RosalieWessels/Marlin_MakerbotReplicator2)

My models are sliced with Cura and printed in PLA.

I tried hotend temperatures of 200, 210, and 220 degrees C. My print speed is around 50 or 60 mm/s.

Here is a sample sliced file that was used:
<https://filebin.net/df33a3jjwgemz0m8>

**Tags:** marlin
> **Comments:**
> **username_1**: I want cake too! https://youtu.be/MzcrX3wcA-Q?t=32  
> **username_1**: One thing you should fix is the attachment of the belts to the carriage; the belt (tensioned with a tie wrap is quite original) has a lot of play. This causes the layer shifts in your prints. But, I don't think this is related to the crashing.  
> **username_2**: Can you measure the voltage draw of heater and bed?  
> **username_1**: Hello Rosalie, I noticed your question has been up for a while now. Have any of the answers below been able to solve your question? If so, would you mind accepting the appropriate answer. If not, what is missing so that we may help you further? Also, if you have figured it out on your own, you can always answer and accept your own solution after 48 hours. Thank you!  
> **username_3**: The [filebin link](https://filebin.net/df33a3jjwgemz0m8) seems to be empty or dead.  

---

## 3 answers

### Answer by username_4 on 2020-08-03. Score: 1

Few things to try,

**Check G-Code** - Verify that the slicer is not the problem, slice using some other program / make a new default profile and re-slice.

**3D File** - Also In parallel with the above point, I would get a standard test cube STL to start with. This will be a simple quick print to get a solid reference.

**Voltages** - Get a Multi-meter on the Regulated Voltage rails, 5V Rail, 12V rail / 24V rail. See if at the moment of crash a voltage rail collapse, the most likely one would be the microcontroller rail, but you may be able to see the problem somewhere else.

**Current** - If possible, measure the current draw of the printer either from the mains or after the AC/DC regulator. Its possible something is going horribly wrong and current limiting.

**Serial Port** - Possibly connect the printer to a PC via its serial port and open a com port. See if the printer spits out an error code at the time of crash?

**End Stops** - Double check that none of the End Stops are accidently being triggered (Although this should not crash the system, it might be part of the problem)

**Verify Sensor Readings** - Check all end stops, check the bed temperature readings, check the nozzle temperature reading. Maybe a sensor has failed and is causing the controller to crash out.

> **Comments:**
> **username_2**: of your suggestions, only the voltage and current could be relevant, because the rest would have resulted not in a crash like that, it's a print from SD-card afaict, making Serial port a non-issue, the file wouldn't result in a hangup, the G-code does not result in a self-reset/bluescreen, endstops are ignored during actual printing (printers use software endstops only then)  
> **username_5**: @Trish: While the serial port isn't being used for printing, it could spill useful debug output indicating the cause of the crash at the moment it happens.  
> **username_3**: +1 for serial port debugging, you could put more emphasis on that option. I am surprised that no one else mentioned this.  

---

### Answer by username_2 on 2020-08-03. Score: 1

I see a couple likely culprits for a hardcrash like this

* problems with the power supply. If the power supply does not provide enough voltage an/or current to the board, this can lead to a lockup of the board.
* temperature issues of the board. If the board overheats, it could fail to execute properly, leading to abort. make sure that the board is not overheating.
* faulty firmware. recompile your firmware and reflash it.
* faulty board.


---

### Answer by username_6 on 2023-03-15. Score: 0

If you compiled your own firmware using visual studio code, use platformio's inspector found on the platformio homepage to make sure there are no memory overrun issues. You must read the whole prompt because sometimes it will not explicitly state that there is an issue


---

