• Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Laptop fails to boot after hard shutdown

Status
Not open for further replies.
Hey guys,
Usually I fix all kinds of tech related problems myself without having to post here but this one is really questioning my wits.

Context:
I was using my MicroOS desktop for casual browsing. I had to rush somewhere so I hard shutdown my computer, packed up and left. The place where I landed is pretty remote so the laptop had to go through some bumpy roads.

Problem:
I turned on the computer and it froze in the boot logo. I turned it off and restarted it landed me in the BIOS. Interestingly I found out that both the storage devices were not detected and all the boot devices slots were empty. I thought this might be due to me holding the power button too long such that the BIOS got reset, so I asked the BIOS to reset to default settings and boot. It showed me a screen filled with colour noise and subsequent boots blank out the screen, even the BIOS does not load.

Diagnostic details:

Hardware details:
The laptop I run is an ASUS TUF FX505 I beleive with AMD Ryzen 5 3rd Gen (3550H) with GeForce GTX 1650. Storage is handled by an Intel NVMe SSD 512GB and Seagate Barracuda 1TB SATA

Software details:
I have manual partitioning with GPT scheme dual booting OpenSUSE MicroOS as my primary workstation and Pop!_OS 20.04LTS as my secondary backup OS. I can provide the partition details but I think they are not relevant here.

Any thoughts on what in the world is happening here?
 
Unlikely it was the bumpy ride, but depending on how bumpy, open up the backplate and double check all connections.

more likely would be corrupted system files or failed drive.
can you make a bootable Linux distro USB and try to get the laptop going from that?
have you got an external enclosure for the NVMe drive to test it outside the laptop?
disconnect the HDD and see if that’s the cause.
remove, clean and reseat the memory.
 
@Bruce Thanks for replying.
Here, is an update: Later that day I opened the backplate and rechecked battery and display connections and then it started working. The OS was not corrupted although openSUSE was trying to repair itself. The next morning it showed no signs of problems. That evening it magically crashed again but for that whole period the laptop was just sitting on my table. The pattern of crash was also the same: on the first and second boot the Kernel panicked. The third, fourth and fifth restart froze in the boot screen and successive restarts did not even light up the screen.
Later that afternoon I reopened the backplate reseated the RAM, battery and display. It did not work. I decided it must be an issue with the battery or the display. I removed the battery and ran the laptop on AC power. It worked only for sometime after which the display filled with random color noise. I called up on ASUS Tech Support and explained them about my efforts. They told me to get the laptop to Service Center. But in this time nobody in my area (in which there are about 13 ASUS Certified Repair Centers) none was willing to repair my computer. I just left it sitting there for the next 4 hours. Late in the night I reassembled the computer and turned it on for one last time. It came back to life. I took a backup and did a fresh install of Fedora Workstation 35. I did not shutdown my computer for the next 3 days I just put it on Suspend whenever I did not use.
As of now the computer is fully functionally, but I have no idea what caused the problem, what solved it or is it even solved? What do you recommend I do?
 
Status
Not open for further replies.