I’ve noticed that between the first and second log it went from unknown type 3 event to unknown type 2 event. In each case it is related to an event which in turn says it is related to events and not graphics, nor to memory issues (including both human memory programming errors and hardware memory errors). The handling of HID (human interface device) hardware is almost certainly the main component of the failure. This in turn could be caused by the USB communications, or the drivers to the individual components, or from the X server simply not being able to handle some modern event. I tend to lean to the side that the handling from the HID devices or the USB communications somehow corrupt or send an unusual event (or perhaps a usual event with an unusual timing).
It is also possible audio or multimedia is indirectly related, for example, headphones often have a volume control on the cord for increasing/decreasing volume. Sometimes software will generate an event in response to something, e.g., the “bell” or “alert” character might play through stdout of a terminal, but have something in X11 react to it (visual bell).
It is unlikely that the USB hard drive has any influence on events, but it could certainly have an influence on USB drivers which brings out some fringe case in USB or the other devices connected to it. FYI, it might be useful to test something the reverse of what you are thinking of for the drive: Just temporarily try without the hard drive if you can, or with the drive connected to the micro connector…just to use the same USB on HID devices while reducing USB load for that port. Then again with the HID items on the micro connector, but USB drive on the full size connector.
FYI, that micro connector is neither type A nor type B, it is “on the go”, OTG (micro A/B). It’s behavior as a device versus host changes depending on whether a micro A or micro B is connected. For this to work with keyboard, mouse, or other standard items, it must be a host (keyboard, mouse, and other similar items are devices). Thus your connector/adapter must be micro A, not micro B. The supplied cable is micro B which is strictly for recovery/flash mode when Jetson becomes a device instead of a host. If the cable you ordered really was micro B it won’t work with your HUB and keyboard/mouse.
EDIT/Additional note: Plugging in or removing a microphone or headphone (non-USB) is also an event generator.