Failed to start systemd-timesyncd.service after crash

Troubleshooting
41 
May 23 01:25:36 DietPi hassio-supervisor[3515]: 22-05-23 01:25:36 INFO (SyncWorker_4) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/tasmoadmin/aarch64 with version 0.17.0
May 23 01:25:36 DietPi f4262df47a1d[2004]: [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
May 23 01:25:36 DietPi f4262df47a1d[2004]: [s6-init] ensuring user provided files have correct perms...exited 0.
May 23 01:25:36 DietPi f4262df47a1d[2004]: [fix-attrs.d] applying ownership & permissions fixes...
May 23 01:25:36 DietPi f4262df47a1d[2004]: [fix-attrs.d] 01-tasmoadmin: applying... 
May 23 01:25:37 DietPi kernel: USB_PWR_EN: disabling
May 23 01:25:37 DietPi kernel: TF_IO: disabling

Thats wired… Last time my Odroid crashed at exact the same time.
And I have a kernel log entry.

42

I think its only happening when I use a USB Device.

43

Did you exchanged PSU or USB cable already? It might be hardware related if it comes down to the usage of USB devices.

44

I tried two USB HDDs… With my PI is everything fine (but the overall performance is terrible).
I have a 15V/4A PSU
Edit:
12V/2A PSU
But it consumes around 5W