More information: fedora 25 works on kernel 4.8.7 but crashed after updating to 4.12

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs.
 
Fedora 26 has now been rebased to 4.15.4-200.fc26.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27.
 
If you experience different issues, please open a new bug report for those.

Thanks for the answer.
I have tried to upgrade to Fedora 26 (4.15.6) and there is a very similar problem. I can boot with acpi=off, but without this option system totally stacks and I even can't use ctrl+alt+f2 to open other terminal and collect logs.
The problem on boot screen looks like this:
NMI: watchdog: Watchdog detected hard lookup on cpu1
Watchdog: BUG: Soft lookup - CPU#2 stuck for 23s!

I got this log from journalctl after reboot to the previous kernel.
https://paste.fedoraproject.org/paste/tz0-1GBgWNw6dIKIAsqn6Q

I'll try to upgrade directly to Fedora 27 in a while, and give you a feedback.

I have tried Fedora 27 (14.15.6). There is the same problem, but one more string in boot log:
tmp_crb MSFT010:00: [Firmware Bug] ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80

I have searched this problem and found two answers:
https://unix.stackexchange.com/questions/422454/acpi-region-does-not-cover-the-entire-command-response-buffer
https://patchwork.kernel.org/patch/9585671/
Disabling fast boot didn't help. So I made a request for BIOS upgrade in ASUS tech support. I'll let you know when they answer me.

Asus answered, that they don't support linux on notebooks and they wouldn't fix it.

I have created a ticket in kernel.bugzilla, because as I found it's not only fedoras bug.
https://bugzilla.kernel.org/show_bug.cgi?id=199045

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.