# ESP32 restarts after exakt 60 seconds - Core 0 panic´ed **URL:** \ **Category:** Issues\ **Created:** [September 7, 2023, 4:12am UTC](https://wled.discourse.group/t/esp32-restarts-after-exakt-60-seconds-core-0-panic-ed/9152 "2023-09-07T04:12:18Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Maveric2005](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@Maveric2005](https://wled.discourse.group/u/Maveric2005)\ **Post date:** [September 7, 2023, 4:12am UTC](https://wled.discourse.group/t/esp32-restarts-after-exakt-60-seconds-core-0-panic-ed/9152/1 "2023-09-07T04:12:18Z")
Hi I have a problem with my ESP32 controller with WLED. WLED ran stable for the last 2 years without any problems. Since yesterday the controller started to restart after exactly 60 seconds. As far as I know nothing has changed in the network. What have I already tried? - Controller without LED’s operated (so only the controller without consumers) - flashed a 2nd ESP32 with the latest WLED version (Webflasher) also the 2nd ESP shows the same behavior → after exactly 60 seconds it restarts. If I take out the hooks from the times within the Time&Macro settings and save, they are there again after the reboot. I get today a 3rd completely new ESP32 delivered and would test it again with the wled (fresh install). Do you have an idea? Attached are the logs that I have saved via the Webflasher console. rst:0x1 (POWERON\_RESET),boot:0x13 (SPI\_FAST\_FLASH\_BOOT) configsip: 0, SPIWP:0xee clk\_drv:0x00,q\_drv:0x00,d\_drv:0x00,cs0\_drv:0x00,hd\_drv:0x00,wp\_drv:0x00 mode:DOUT, clock div:2 load:0x3fff0018,len:4 load:0x3fff001c,len:1044 load:0x40078000,len:10124 load:0x40080400,len:5828 entry 0x400806a8 Ada Guru Meditation Error: Core 0 panic’ed (LoadProhibited). Exception was unhandled. Core 0 register dump: PC : 0x4016b1f0 PS : 0x00060c30 A0 : 0x8016bbd6 A1 : 0x3ffd9080 A2 : 0x00000000 A3 : 0x00000010 A4 : 0x000000c3 A5 : 0x3ffd95e8 A6 : 0x3ffdf061 A7 : 0x3ffdf124 A8 : 0x8016ad0a A9 : 0x3ffd9060 A10 : 0x00000001 A11 : 0x3ffdf061 A12 : 0x000000c3 A13 : 0x00000001 A14 : 0x00060823 A15 : 0x00000010 SAR : 0x00000010 EXCCAUSE: 0x0000001c EXCVADDR: 0x00000004 LBEG : 0x4000c349 LEND : 0x4000c36b LCOUNT : 0x00000000 ELF file SHA256: 0000000000000000 Backtrace: 0x4016b1ed:0x3ffd9080 0x4016bbd3:0x3ffd9100 0x4016bc33:0x3ffd9130 0x4008b546:0x3ffd9160 Rebooting… ets Jun 8 2016 00:22:57 rst:0xc (SW\_CPU\_RESET),boot:0x13 (SPI\_FAST\_FLASH\_BOOT) configsip: 0, SPIWP:0xee clk\_drv:0x00,q\_drv:0x00,d\_drv:0x00,cs0\_drv:0x00,hd\_drv:0x00,wp\_drv:0x00 mode:DOUT, clock div:2 load:0x3fff0018,len:4 load:0x3fff001c,len:1044 load:0x40078000,len:10124 load:0x40080400,len:5828 entry 0x400806a8 Ada ---
**Author:** ![blazoncek](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/blazoncek/32/1886_2.png) [@blazoncek](https://wled.discourse.group/u/blazoncek)\ **Post date:** [September 7, 2023, 5:40am UTC](https://wled.discourse.group/t/esp32-restarts-after-exakt-60-seconds-core-0-panic-ed/9152/2 "2023-09-07T05:40:14Z")
Do you have HA integration? ---
**Author:** ![Maveric2005](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@Maveric2005](https://wled.discourse.group/u/Maveric2005)\ **Post date:** [September 7, 2023, 5:58am UTC](https://wled.discourse.group/t/esp32-restarts-after-exakt-60-seconds-core-0-panic-ed/9152/3 "2023-09-07T05:58:41Z")
Hey 🙂 First of all, thank you for the fast reply 🙂 If you mean Home Asistant → no i dont have HA. My network ist a fritzbox with Unifi AP if this helps. ---
**Author:** ![blazoncek](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/blazoncek/32/1886_2.png) [@blazoncek](https://wled.discourse.group/u/blazoncek)\ **Post date:** [September 7, 2023, 6:15am UTC](https://wled.discourse.group/t/esp32-restarts-after-exakt-60-seconds-core-0-panic-ed/9152/4 "2023-09-07T06:15:15Z")
Get a debug build and monitor serial output. You may also want to fire-up Wireshark to see what’s happening on the network. ---
**Author:** ![Maveric2005](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@Maveric2005](https://wled.discourse.group/u/Maveric2005)\ **Post date:** [September 7, 2023, 6:17am UTC](https://wled.discourse.group/t/esp32-restarts-after-exakt-60-seconds-core-0-panic-ed/9152/5 "2023-09-07T06:17:56Z")
do you have a link how to get a debug build to monitor serial output (or some tutorial)? You mean its network related? ---
**Author:** ![blazoncek](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/blazoncek/32/1886_2.png) [@blazoncek](https://wled.discourse.group/u/blazoncek)\ **Post date:** [September 7, 2023, 9:00am UTC](https://wled.discourse.group/t/esp32-restarts-after-exakt-60-seconds-core-0-panic-ed/9152/6 "2023-09-07T09:00:51Z")
@srg74 used to have debug binaries in his Github repo. I am just suggesting things to check to isolate the cause. WLED does not reset on its own. ---
**Author:** ![Maveric2005](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@Maveric2005](https://wled.discourse.group/u/Maveric2005)\ **Post date:** [September 7, 2023, 10:05am UTC](https://wled.discourse.group/t/esp32-restarts-after-exakt-60-seconds-core-0-panic-ed/9152/7 "2023-09-07T10:05:17Z")
Thank you for the info!!! Will try it. Its confusing that its exactly after 60 seconds (it reboots after 60 seconds uptime) ---
**Author:** ![Maveric2005](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@Maveric2005](https://wled.discourse.group/u/Maveric2005)\ **Post date:** [September 7, 2023, 2:25pm UTC](https://wled.discourse.group/t/esp32-restarts-after-exakt-60-seconds-core-0-panic-ed/9152/8 "2023-09-07T14:25:41Z")
so i flashed this binary > with the ESP-Flasher If the controller is NOT connected with the WIFI (default WLED AP with ip 4.3.2.1) the controller is stable. If i connect the controller with the Wifi ( i tryed different SSID´s and with simple passwords) the controller restarts every 60 seconds. ---
**Author:** ![Maveric2005](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@Maveric2005](https://wled.discourse.group/u/Maveric2005)\ **Post date:** [September 7, 2023, 2:53pm UTC](https://wled.discourse.group/t/esp32-restarts-after-exakt-60-seconds-core-0-panic-ed/9152/9 "2023-09-07T14:53:17Z")
flashed now the b4. this is the log from the console: [16:49:23]—DEBUG INFO— [16:49:23]Runtime: 60016 [16:49:23]Unix time: 60,016 [16:49:23]Free heap: 201140 [16:49:23]Wifi state: 3 [16:49:23]State time: 60016 [16:49:23]NTP last sync: 999000000 [16:49:23]Client IP: 192.168.2.216 [16:49:23]Loops/sec: 2265 [16:49:23]Loop time[ms]: 0/717 [16:49:23]UM time[ms]: 0/1 [16:49:23]Strip time[ms]: 0/11 [16:49:23]Segments: 1 → 68B [16:49:23]Modes: 4_187=748B [16:49:23]Data: 4_187=748B [16:49:23]Map: 2_0=0B [16:49:23]Buffer: 3_30=90B [16:49:25]Guru Meditation Error: Core 0 panic’ed (LoadProhibited). Exception was unhandled. [16:49:25]Core 0 register dump: [16:49:25]PC : 0x4016d078 PS : 0x00060a30 A0 : 0x8016da5e A1 : 0x3ffe1300 [16:49:25]A2 : 0x00000000 A3 : 0x00000010 A4 : 0x000000c3 A5 : 0x3ffdda38 [16:49:25]A6 : 0x3ffe1b1d A7 : 0x3ffe1be0 A8 : 0x8016cb92 A9 : 0x3ffe12e0 [16:49:25]A10 : 0x00000001 A11 : 0x3ffe1b1d A12 : 0x000000c3 A13 : 0x00000001 [16:49:25]A14 : 0x00060623 A15 : 0x00000010 SAR : 0x00000010 EXCCAUSE: 0x0000001c [16:49:25]EXCVADDR: 0x00000004 LBEG : 0x4000c349 LEND : 0x4000c36b LCOUNT : 0x00000000 [16:49:25] [16:49:25]ELF file SHA256: 0000000000000000 [16:49:25] [16:49:25]Backtrace: 0x4016d075:0x3ffe1300 0x4016da5b:0x3ffe1380 0x4016dabb:0x3ffe13b0 0x4008b5d2:0x3ffe13e0 [16:49:25] [16:49:25]Rebooting… [16:49:25]ets Jun 8 2016 00:22:57 [16:49:25] [16:49:25]rst:0xc (SW\_CPU\_RESET),boot:0x13 (SPI\_FAST\_FLASH\_BOOT) [16:49:25]configsip: 0, SPIWP:0xee [16:49:25]clk\_drv:0x00,q\_drv:0x00,d\_drv:0x00,cs0\_drv:0x00,hd\_drv:0x00,wp\_drv:0x00 [16:49:25]mode:DOUT, clock div:2 [16:49:25]load:0x3fff0030,len:1184 [16:49:25]load:0x40078000,len:13132 [16:49:25]load:0x40080400,len:3036 [16:49:25]entry 0x400805e4 [16:49:26] [16:49:26]—WLED 0.14.0-b4 2309050 INIT— [16:49:26]esp32 v3.3.6-16-gcc5440f6a2 [16:49:26]arduino-esp32 v1.0.x [16:49:26] [16:49:26]CPU: ESP32-D0WDQ6 rev.1, 2 core(s), 240MHz. [16:49:26]FLASH: 4MB, Mode 3 (DOUT), speed 40MHz. [16:49:26]heap 292392 [16:49:26]PIN ALLOC: Pin 1 successfully allocated by 0x89 (137) [16:49:26]Registering usermods … [16:49:26]heap 292392 [16:49:26]Reading config [16:49:26]Reading settings from /wsec.json… [16:49:26]JSON buffer locked. (3) [16:49:26]JSON buffer released. (3) [16:49:26]JSON buffer locked. (1) [16:49:26]Reading settings from /cfg.json… [16:49:26]Removing all. [16:49:26]PIN ALLOC: Pin 16 successfully allocated by 0x82 (130) [16:49:26]Successfully inited strip 0 (len 30) with type 22 and pins 16,186 (itype 21) [16:49:26]PIN ALLOC: Pin 0 successfully allocated by 0x85 (133) [16:49:26]Starting usermod config. [16:49:26]JSON buffer released. (1) [16:49:26]Initializing strip [16:49:26]Loading custom palettes [16:49:26]Loading custom ledmaps [16:49:26]heap 288956 [16:49:26]Usermods setup [16:49:26]heap 288956 [16:49:26]initServer [16:49:26]heap 284920 [16:49:26]lastReconnectAttempt == 0 [16:49:26]Access point disabled (init). [16:49:26]Connecting to IoT2… [16:49:26]Loop took 136ms. [16:49:26]Usermods took 0ms. [16:49:26]Strip took 2ms. [16:49:29]Loop took 716ms. [16:49:29]Usermods took 0ms. [16:49:29]Strip took 1ms. [16:49:29] [16:49:29]Connected! IP address: 192.168.2.216 [16:49:29]Init STA interfaces [16:49:29]mDNS started [16:49:29]Loop took 31ms. [16:49:29]Usermods took 0ms. [16:49:29]Strip took 0ms. [16:49:32]WS FileRead: /index.htm [16:49:32]Not-Found HTTP call: [16:49:32]URI: /skin.css [16:49:32]WS FileRead: /skin.css [16:49:32]JSON buffer locked. (17) [16:49:32]JSON buffer size: 7890 for request: 6 [16:49:32]JSON content length: 5285 [16:49:32]JSON buffer released. (17) [16:49:32]JSON buffer locked. (17) [16:49:32]JSON buffer size: 4801 for request: 8 [16:49:32]JSON content length: 2184 [16:49:32]JSON buffer released. (17) [16:49:32]JSON buffer locked. (17) [16:49:32]JSON buffer size: 2165 for request: 3 [16:49:32]JSON content length: 1188 [16:49:32]JSON buffer released. (17) [16:49:32]Not-Found HTTP call: [16:49:32]URI: /presets.json [16:49:32]WS FileRead: /presets.json [16:49:33]Loop delayed more than 8ms. [16:49:33]WS client connected. [16:49:33]JSON buffer locked. (12) [16:49:33]JSON buffer size: 2166 for WS request (1188). [16:49:33]heap 203456 [16:49:33]Sending WS data to a single client. [16:49:33]JSON buffer released. (12) [16:49:56]—DEBUG INFO— [16:49:56]Runtime: 30000 [16:49:56]Unix time: 30,000 [16:49:56]Free heap: 203828 [16:49:56]Wifi state: 3 [16:49:56]State time: 0 [16:49:56]NTP last sync: 999000000 [16:49:56]Client IP: 192.168.2.216 [16:49:56]Loops/sec: 3215 [16:49:56]Loop time[ms]: 0/716 [16:49:56]UM time[ms]: 0/1 [16:49:56]Strip time[ms]: 0/30 [16:49:56]Segments: 1 → 68B [16:49:56]Modes: 4_187=748B [16:49:56]Data: 4_187=748B [16:49:56]Map: 2_0=0B [16:49:56]Buffer: 3_30=90B [16:50:04]WS client connected. [16:50:04]JSON buffer locked. (12) [16:50:04]JSON buffer size: 2166 for WS request (1189). [16:50:04]heap 201644 [16:50:04]Sending WS data to a single client. [16:50:04]JSON buffer released. (12) [16:50:24]JSON buffer locked. (11) [16:50:24]JSON buffer released. (11) [16:50:24]JSON buffer locked. (12) [16:50:24]JSON buffer size: 2166 for WS request (1189). [16:50:24]heap 201424 [16:50:24]Sending WS data to a single client. [16:50:24]JSON buffer released. (12) [16:50:25]Guru Meditation Error: Core 0 panic’ed (LoadProhibited). Exception was unhandled. [16:50:25]Core 0 register dump: [16:50:25]PC : 0x4016d078 PS : 0x00060030 A0 : 0x8016da5e A1 : 0x3ffd7560 [16:50:25]A2 : 0x00000000 A3 : 0x00000010 A4 : 0x000000c3 A5 : 0x3ffdffc8 [16:50:25]A6 : 0x3ffe0549 A7 : 0x3ffe060c A8 : 0x8016cb92 A9 : 0x3ffd7540 [16:50:25]A10 : 0x00000001 A11 : 0x3ffe0549 A12 : 0x000000c3 A13 : 0x00000001 [16:50:25]A14 : 0x00060c23 A15 : 0x00000010 SAR : 0x00000010 EXCCAUSE: 0x0000001c [16:50:25]EXCVADDR: 0x00000004 LBEG : 0x4000c349 LEND : 0x4000c36b LCOUNT : 0x00000000 [16:50:25] [16:50:25]ELF file SHA256: 0000000000000000 [16:50:25] [16:50:25]Backtrace: 0x4016d075:0x3ffd7560 0x4016da5b:0x3ffd75e0 0x4016dabb:0x3ffd7610 0x4008b5d2:0x3ffd7640 [16:50:25] [16:50:25]Rebooting… [16:50:25]ets Jun 8 2016 00:22:57 [16:50:25] [16:50:25]rst:0xc (SW\_CPU\_RESET),boot:0x13 (SPI\_FAST\_FLASH\_BOOT) [16:50:25]configsip: 0, SPIWP:0xee [16:50:25]clk\_drv:0x00,q\_drv:0x00,d\_drv:0x00,cs0\_drv:0x00,hd\_drv:0x00,wp\_drv:0x00 [16:50:25]mode:DOUT, clock div:2 [16:50:25]load:0x3fff0030,len:1184 [16:50:25]load:0x40078000,len:13132 [16:50:25]load:0x40080400,len:3036 [16:50:25]entry 0x400805e4 [16:50:26] [16:50:26]—WLED 0.14.0-b4 2309050 INIT— [16:50:26]esp32 v3.3.6-16-gcc5440f6a2 [16:50:26]arduino-esp32 v1.0.x [16:50:26] [16:50:26]CPU: ESP32-D0WDQ6 rev.1, 2 core(s), 240MHz. [16:50:26]FLASH: 4MB, Mode 3 (DOUT), speed 40MHz. [16:50:26]heap 292392 [16:50:26]PIN ALLOC: Pin 1 successfully allocated by 0x89 (137) [16:50:26]Registering usermods … [16:50:26]heap 292392 [16:50:26]Reading config [16:50:26]Reading settings from /wsec.json… [16:50:26]JSON buffer locked. (3) [16:50:26]JSON buffer released. (3) [16:50:26]JSON buffer locked. (1) [16:50:26]Reading settings from /cfg.json… [16:50:26]Removing all. [16:50:26]PIN ALLOC: Pin 16 successfully allocated by 0x82 (130) [16:50:26]Successfully inited strip 0 (len 30) with type 22 and pins 16,186 (itype 21) [16:50:26]PIN ALLOC: Pin 0 successfully allocated by 0x85 (133) [16:50:26]Starting usermod config. [16:50:26]JSON buffer released. (1) [16:50:26]Initializing strip [16:50:26]Loading custom palettes [16:50:26]Loading custom ledmaps [16:50:26]heap 288956 [16:50:26]Usermods setup [16:50:26]heap 288956 [16:50:26]initServer [16:50:26]heap 284920 [16:50:26]lastReconnectAttempt == 0 [16:50:26]Access point disabled (init). [16:50:26]Connecting to IoT2… [16:50:26]Loop took 137ms. [16:50:26]Usermods took 0ms. [16:50:26]Strip took 2ms. [16:50:29]Loop took 716ms. [16:50:29]Usermods took 0ms. [16:50:29]Strip took 1ms. [16:50:29] [16:50:29]Connected! IP address: 192.168.2.216 [16:50:29]Init STA interfaces [16:50:29]mDNS started [16:50:50]WS client connected. [16:50:50]JSON buffer locked. (12) [16:50:50]JSON buffer size: 2166 for WS request (1188). [16:50:50]heap 203524 [16:50:50]Sending WS data to a single client. [16:50:50]JSON buffer released. (12) [16:50:56]—DEBUG INFO— [16:50:56]Runtime: 30000 [16:50:56]Unix time: 30,000 [16:50:56]Free heap: 203836 [16:50:56]Wifi state: 3 [16:50:56]State time: 0 [16:50:56]NTP last sync: 999000000 [16:50:56]Client IP: 192.168.2.216 [16:50:56]Loops/sec: 3373 [16:50:56]Loop time[ms]: 0/716 [16:50:56]UM time[ms]: 0/1 [16:50:56]Strip time[ms]: 0/9 [16:50:56]Segments: 1 → 68B [16:50:56]Modes: 4_187=748B [16:50:56]Data: 4_187=748B [16:50:56]Map: 2_0=0B [16:50:56]Buffer: 3_30=90B ---
**Author:** ![Maveric2005](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@Maveric2005](https://wled.discourse.group/u/Maveric2005)\ **Post date:** [September 7, 2023, 5:58pm UTC](https://wled.discourse.group/t/esp32-restarts-after-exakt-60-seconds-core-0-panic-ed/9152/10 "2023-09-07T17:58:21Z")
So after a long search I seem to have discovered the problem. The fritzbox firmware versions from 7.50 make problems in some constellations and lead to reboots. A downgrade to 7.29 (not save, old firmware!!!) Lets the esp run stable again. The wifi I distribute via unifi AP’s. Hope this helps some ---
**Author:** ![Maveric2005](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@Maveric2005](https://wled.discourse.group/u/Maveric2005)\ **Post date:** [September 7, 2023, 6:07pm UTC](https://wled.discourse.group/t/esp32-restarts-after-exakt-60-seconds-core-0-panic-ed/9152/11 "2023-09-07T18:07:18Z")
I also found this post > > > \### What happened? > > The WLED restarted after 59 seconds, since the new software …7.50 is on the Fritzbox and it was rebooted once. > I have see this bug still on the Beta Versions from the Router, with the old OS7.29 I have no problems. > > > > \### To Reproduce Bug > > Install the Version 7.50 and reboot the WLED, than it will restart after 59 Sec > > \### Expected Behavior > > No reboots > > \### Install Method > > Binary from WLED.me > > \### What version of WLED? > > WLED 0.13.3 (build 2208222) > > \### Which microcontroller/board are you seeing the problem on? > > ESP32 > > \### Relevant log/trace output > > \_No response\_ > > \### Anything else? > > \_No response\_ > > \### Code of Conduct > > \- \[X\] I agree to follow this project's Code of Conduct