It indeed was from the kernel-firmware update. It still does happen, though not as frequently. I will post new logs when it happens again.