Message from syslogd@localhost at Mar 7 06:27:06 ... kernel:Uhhuh. NMI received for unknown reason 0c on CPU 9...

Those messages are from the kernel. That's why it says "kernel:". systemd is just forwarding them.
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/kernel/nmi.c?h=v4.16-rc4#n295

here's why

said no-one ever

oh thats right, i forgot that Holla Forums jusp reformats, reinstalls, and reconfigures any time a problem arises.

I use it a lot, for hardware problems. If some driver is acting up it'll usually start spewing into the syslog, which at the very least tells you which driver/piece of hardware is malfunctioning. If some USB device is having issues you can watch it to see which stages it does and doesn't go through when you log in.
This is bog standard stuff. It's not weird or obscure.

See, if you weren't using systemd you wouldn't have this problem since the system wouldn't even get that far.

I use the system logs when trying to debug USB devices for seeing errors when plugging it in.

why wouldn't you just enable it when you notice problems so you can catch errors, instead of leaving it enabled 24/7 while it mindlessly write's garbage and other possibly sensitive data to your disk that your never going to read?

Because then I can't catch errors that happened before I enabled it, and the disk is where I keep my other sensitive data anyway.

but le systemd hate!
systemd bad rite?