This looks like some severe hardware issue. On the one hand, we have:
Stats 3578.6: gcodein=0 mcu: mcu_awake=0.001 mcu_task_avg=0.000006 mcu_task_stddev=0.000005 bytes_write=3561215 bytes_read=745871 bytes_retransmit=272 bytes_invalid=363 send_seq=67943 receive_seq=67943 retransmit_seq=65848 srtt=0.003 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=167997418 pad_7: temp=50.5 heater_bed: target=0 temp=41.8 pwm=0.000 sysload=0.15 cputime=139.300 memavail=658888 print_time=3486.724 buffer_time=0.000 print_stall=0 extruder: target=0 temp=268.1 pwm=0.000
Stats 3579.6: gcodein=0 mcu: mcu_awake=0.001 mcu_task_avg=0.000006 mcu_task_stddev=0.000005 bytes_write=3561221 bytes_read=745974 bytes_retransmit=272 bytes_invalid=363 send_seq=67944 receive_seq=67944 retransmit_seq=65848 srtt=0.003 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=167997417 pad_7: temp=51.1 heater_bed: target=0 temp=41.7 pwm=0.000 sysload=0.15 cputime=139.319 memavail=658888 print_time=3486.724 buffer_time=0.000 print_stall=0 extruder: target=0 temp=270.3 pwm=0.000
Stats 3580.6: gcodein=0 mcu: mcu_awake=0.001 mcu_task_avg=0.000006 mcu_task_stddev=0.000005 bytes_write=3561227 bytes_read=746091 bytes_retransmit=272 bytes_invalid=363 send_seq=67945 receive_seq=67945 retransmit_seq=65848 srtt=0.003 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=167997414 pad_7: temp=50.8 heater_bed: target=0 temp=41.7 pwm=0.000 sysload=0.15 cputime=139.338 memavail=658888 print_time=3486.724 buffer_time=0.000 print_stall=0 extruder: target=0 temp=272.5 pwm=0.000
Stats 3581.6: gcodein=0 mcu: mcu_awake=0.001 mcu_task_avg=0.000006 mcu_task_stddev=0.000005 bytes_write=3561233 bytes_read=746200 bytes_retransmit=272 bytes_invalid=363 send_seq=67946 receive_seq=67946 retransmit_seq=65848 srtt=0.003 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=167997412 pad_7: temp=50.2 heater_bed: target=0 temp=41.6 pwm=0.000 sysload=0.15 cputime=139.359 memavail=658888 print_time=3486.724 buffer_time=0.000 print_stall=0 extruder: target=0 temp=275.5 pwm=0.000
Transition to shutdown state: MCU shutdown
Dumping gcode input 0 blocks
...
MCU 'mcu' shutdown: ADC out of range
As you can see, the temperature is increasing, ALTHOUGH Klipper commanded pwm=0.0, which effectively means no power to the heater. The board seems to ignore this.
On the other hand, there are multiple:
Timeout with MCU 'mcu' (eventtime=95.867656)
Transition to shutdown state: Lost communication with MCU 'mcu'
Dumping gcode input 0 blocks
See Timeout with MCU / Lost communication with MCU. In the context we see here, it could mean that your board crashed somehow and is no longer talking to the Klipper host on the Pad7.
Hard to diagnose remotely, but my money goes to a defect board or a severely messed up installation. The latter would not surprise me as well, given that we talk about a Kobra 2.
This printer uses a heavily modified Klipper version and already from this aspect no meaningful support can be provided.
Make sure that you do not burn down your home.