# Printer Complete Shutdown - No Log

**URL:** <https://klipper.discourse.group/t/printer-complete-shutdown-no-log/25987>\
**Category:** General Discussion\
**Created:** [May 16, 2026, 5:00pm UTC](https://klipper.discourse.group/t/printer-complete-shutdown-no-log/25987 "2026-05-16T17:00:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neelix](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/neelix/32/6919_2.png) [@Neelix](https://klipper.discourse.group/u/Neelix)\
**Post date:** [May 16, 2026, 5:00pm UTC](https://klipper.discourse.group/t/printer-complete-shutdown-no-log/25987/1 "2026-05-16T17:00:31Z")

</div>

### Basic Information:

Printer Model: Self Build, Double Core XY  
 MCU / Printerboard: BTT Octopus  
 Host / SBC: Raspberry Pi 3B+  
 klippy.log

### Describe your issue:

I have a very strange issue, my printer stops mid print and I can’t connect to it anymore. So far so normal if something goes very wrong. But I can find anything in the log (maybe some of you can spot something?). If I unplug the MCU, the Raspberry can be accessed again. A reconnect of the MCU crashes everything again. Just a full shutdown of the MCU helps.

Things I tried so far:

- Print slower
- More Cooling of the TMC Drivers, MCU and Raspberry
- Replacing the USB-Cable
- Even More Cooling of the TMC Drivers, MCU and Raspberry + Monitoring the Temps.
- Updating the MCU (MCU and Host now again different versions, but it really didn’t help)

The only idea I have currently is to buy a new MCU. Maybe someone has another idea what to try first?

[klippy.log](https://klipper.discourse.group/uploads/short-url/jzSY8bRXe8S6uaaMhzjB6R8cbzB.log) (3.1 MB)

---

<div class="post-metadata">

**Author:** ![nefelim4ag](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/nefelim4ag/32/2387_2.png) [@nefelim4ag](https://klipper.discourse.group/u/nefelim4ag)\
**Post date:** [May 16, 2026, 7:41pm UTC](https://klipper.discourse.group/t/printer-complete-shutdown-no-log/25987/2 "2026-05-16T19:41:10Z")

</div>

My pure guess RP3 + Hang → DWC2 thing  
So, it should probably be fixed with dtoverlay=dwc2 or with a kernel of 6.1+, which IIRC does not hang.

Ex: [PI freezes after setting mcu USB id - #9 by cyablo](https://klipper.discourse.group/t/pi-freezes-after-setting-mcu-usb-id/21538/9)

Hope that helps,  
-Timofey

---

<div class="post-metadata">

**Author:** ![Neelix](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/neelix/32/6919_2.png) [@Neelix](https://klipper.discourse.group/u/Neelix)\
**Post date:** [May 16, 2026, 8:15pm UTC](https://klipper.discourse.group/t/printer-complete-shutdown-no-log/25987/3 "2026-05-16T20:15:37Z")

</div>

Thx, it’s worth a try!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\
**Post date:** [June 16, 2026, 6:15am UTC](https://klipper.discourse.group/t/printer-complete-shutdown-no-log/25987/4 "2026-06-16T06:15:52Z")

</div>

Closed on June 16, 2026, 6:15am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
