# Klipper Starts up and then gives error 'MCU 'mcu' shutdown: Invalid oid type' **URL:** \ **Category:** General Discussion\ **Created:** [December 1, 2024, 9:24pm UTC](https://klipper.discourse.group/t/klipper-starts-up-and-then-gives-error-mcu-mcu-shutdown-invalid-oid-type/20387 "2024-12-01T21:24:21Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ollieh](https://avatars.discourse-cdn.com/v4/letter/o/dec6dc/32.png) [@ollieh](https://klipper.discourse.group/u/ollieh)\ **Post date:** [December 1, 2024, 9:24pm UTC](https://klipper.discourse.group/t/klipper-starts-up-and-then-gives-error-mcu-mcu-shutdown-invalid-oid-type/20387/1 "2024-12-01T21:24:21Z")
### Basic Information: Printer Model: Ender 5 Pro [klippy.log](https://klipper.discourse.group/uploads/short-url/iXjAqG57c1AmnCvTjuL0mywWSy2.log) (391.4 KB) MCU / Printerboard: Creality 1.1.5 Host / SBC Raspberry Pi Zero W klippy.log Describe your issue: Ive just fitted a new spider hot end to the printer and when i power it up it right away throws up the error message above. Ive tried disconnecting the new lead to the hot end but it still persists. Any ideas? … ---
**Author:** ![koconnor](https://avatars.discourse-cdn.com/v4/letter/k/aca169/32.png) [@koconnor](https://klipper.discourse.group/u/koconnor)\ **Post date:** [December 2, 2024, 5:59pm UTC](https://klipper.discourse.group/t/klipper-starts-up-and-then-gives-error-mcu-mcu-shutdown-invalid-oid-type/20387/2 "2024-12-02T17:59:14Z")
Unfortunately, it looks like your micro-controller is spontaneously resetting itself. The Klipper host code had an error that caused the spontaneous restart report to not propagate correctly. This should, hopefully, be fixed now (commit 9ce631e8). As to why the micro-controller is resetting itself - I’d try investigating the possibilities described at [Timeout with MCU / Lost communication with MCU](https://klipper.discourse.group/t/timeout-with-mcu-lost-communication-with-mcu/6639) . You may also want to try running “make menuconfig”, compiling, and reflashing the micro-controller again. -Kevin ---
**Author:** ![hcet14](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@hcet14](https://klipper.discourse.group/u/hcet14)\ **Post date:** [December 2, 2024, 7:26pm UTC](https://klipper.discourse.group/t/klipper-starts-up-and-then-gives-error-mcu-mcu-shutdown-invalid-oid-type/20387/3 "2024-12-02T19:26:20Z")
> [@koconnor](#): > > This should, hopefully, be fixed now (commit 9ce631e8). Could you please post a link? Thank you. ---
**Author:** ![koconnor](https://avatars.discourse-cdn.com/v4/letter/k/aca169/32.png) [@koconnor](https://klipper.discourse.group/u/koconnor)\ **Post date:** [December 2, 2024, 7:43pm UTC](https://klipper.discourse.group/t/klipper-starts-up-and-then-gives-error-mcu-mcu-shutdown-invalid-oid-type/20387/4 "2024-12-02T19:43:54Z")
To the commit? [klippy: Fix missing default parameter of invoke\_async\_shutdown() · Klipper3d/klipper@9ce631e · GitHub](https://github.com/Klipper3d/klipper/commit/9ce631e8d1a7b739f96c360a7a4250489ae8deb8) -Kevin ---
**Author:** ![ollieh](https://avatars.discourse-cdn.com/v4/letter/o/dec6dc/32.png) [@ollieh](https://klipper.discourse.group/u/ollieh)\ **Post date:** [December 4, 2024, 2:38am UTC](https://klipper.discourse.group/t/klipper-starts-up-and-then-gives-error-mcu-mcu-shutdown-invalid-oid-type/20387/5 "2024-12-04T02:38:55Z")
Its not been fiex yet, im reflashing it tonight having checked my wires with a multi meter and found no shorts. ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [December 4, 2024, 9:22am UTC](https://klipper.discourse.group/t/klipper-starts-up-and-then-gives-error-mcu-mcu-shutdown-invalid-oid-type/20387/6 "2024-12-04T09:22:13Z")
> [@ollieh](#): > > Its not been fiex yet As stated by @koconnor: Your issue is most likely related to some hardware instability. Provide a new log after updating to latest Klipper and see: > [@koconnor](#): > > As to why the micro-controller is resetting itself - I’d try investigating the possibilities described at [Timeout with MCU / Lost communication with MCU](https://klipper.discourse.group/t/timeout-with-mcu-lost-communication-with-mcu/6639) . You may also want to try running “make menuconfig”, compiling, and reflashing the micro-controller again. What has been fixed is that the actual error is not “correctly recorded” ---
**Author:** ![ollieh](https://avatars.discourse-cdn.com/v4/letter/o/dec6dc/32.png) [@ollieh](https://klipper.discourse.group/u/ollieh)\ **Post date:** [December 4, 2024, 8:51pm UTC](https://klipper.discourse.group/t/klipper-starts-up-and-then-gives-error-mcu-mcu-shutdown-invalid-oid-type/20387/7 "2024-12-04T20:51:56Z")
This is my latest log [klippy(1).log](https://klipper.discourse.group/uploads/short-url/f4LmRe7p3sBizI2frUsb0gNcuiZ.log) (688.9 KB) ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [February 2, 2025, 8:52pm UTC](https://klipper.discourse.group/t/klipper-starts-up-and-then-gives-error-mcu-mcu-shutdown-invalid-oid-type/20387/8 "2025-02-02T20:52:19Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.