Just to ensure that I got you right: The freeze only happens immediately after you press CTRL+ALT+F9. And when you press CTRL+ALT+F9, the switch to TTY9 works, but then you get the output you mentioned, and with this output on screen, the system is then frozen?
Besides the points @ankursinha mentioned, I could offer you an implicit way that might identify the problem. The logs you have shown contain two services that could be related, and that have already been related to such issues on other users’ systems: bluetoothd and virtqemud.
You may try to deactivate them, one by one, and see if it makes a difference (use systemctl stop <service name> to stop it immediately; usesystemctl disable <service name> to make it not start again after reboot. But “disable” does not contain “stop”!). Also, you can use acpitool (it can be installed using dnf) to find out if it is not bluetooth in general, but a specific Bluetooth device that causes the issue. Some elaboration about how to use acpitool for that can be found in this thread.
Further, did you have the problem also with other kernels? When booting your system, you have three kernels you can choose in grub. Test it with the other kernels and let us know if the problem persists with them as well.
Sometimes it can happen that a specific kernel and a piece of hardware don’t like each other 
In such a case, it is the easiest work around to jump over the related kernel (but ensure that you do not use a kernel with security vulnerabilities) and file a bug. In any case, testing the issue with the different kernels is an important initial step to identify if the issue is related to a specific kernel or not.