Ubuntu not working on ASUS Q304U

[Jigar Mehta]

I bought a new ASUS Q304U - Intel i5 6200 + 6 GB RAM + 1 TB HDD + Touch screen + 360 Degree Mode + Win 10 Home pre-installed. A nice laptop I wish to use for web development.

Now, the problem / problems which I am facing:
* When I run Ubuntu 16.x from a USB in live mode, everything works perfectly including touchscreen, trackpad, etc.
* When I install Ubuntu to a 100GB partition on the HDD, the first boot works perfectly including touchscreen, trackpad, etc.
* Now, when I restart the computer or boot to Windows and then come back to Ubuntu on the next boot, I get multiple messages during boot (mentioned below) and finally it stops at the error message "Fixing recursive fault but reboot is needed"

Some of the messages I get during boot:
* tpm_crb MSFT0101:00 Can't request region for resource [mem xxxx-xxxx]
* Bluetooth: hci0 sending frame failed (-19)
* Bluetooth: hci0: Entering manufacturer mode failed (-110)
* ata1.00: failed command: READ FPDMA QUEUED

So I resorted to using 'acpi=noirq' as a boot parameter as per another article where someone is facing the same problem with a Lenevo Yoga. This user claims the issue might be with touchscreen devices:
https://ubuntuforums.org/showthread.php?t=2328462

The issue is also well-described with screenshots of error messages on this link:
http://askubuntu.com/questions/820721/problems-booting-ubuntu-16-04-and-14-04

NOTE: The retailer upgraded the RAM to an 8GB stick at the time of purchase. Do you think the RAM might be misplaced? If not, then what might be the problem and how can I fix it as I can neither use the laptop nor return it :(

[Daniel (danielrd6)]

I confirm the problem with a laptop ASUS Q304U, Intel i5-7200, 6GB of RAM, running Ubuntu 16.04.2 64bit. I also find that given enough tries, even without the "acpi=noirq" option, the kernel eventually loads with no problems. But that successful boot only happens once on every dozen attempts.

[Po-Hsu Lin (cypressyew)]

Hello,
this is not a right place for this bug.

Please open a new bug report with command "ubuntu-bug linux" in a terminal (ctrl + alt + t) if you're still experiencing this issue. (Please file one issue with a bug report)

Thanks