Can a faulty hibernation cause laptop to fail to boot?

Hi all. First post - I think it's in the correct section!

I am running Windows 10 using 2xSSD drives in RAID(0). I have one other 750GB HDD for data.

I had an issue with my laptop this week which seems to have resolved itself. Except, issues don't tend to resolve themselves so I would like to try and figure out what went wrong and whether something like this could go wrong again.

I had hibernated the laptop and when I turned the laptop on, the MSI logo displayed on the screen for approximately 10 seconds before the laptop switched off. Could not get in to BIOS at all. I (wrongly) assumed that a faulty fan was causing the laptop to overheat so I took it to a laptop repair centre.

We were able to get the laptop to boot in to the BIOS by removing the 2xSSD drives. We disabled RAID and connected each SSD individually. Both were detected fine. We reconnected both drives (booting with RAID disabled) and the BIOS detected the two drives just fine and also said that the RAID was also OK. The laptop shop told me that the RAID configuration was probably knackered and I would need to reconfigure it and reinstall Windows 10 (to the tune of at least £100).

I decided to take the laptop home with me as I knew I'd be able to do this myself. First, I booted in to Ubuntu using Ubuntu Live on a USB stick on the laptop. I did this to take off the few files I did not have backed up. At first, Ubuntu would not mount the drives because they were in a hibernated state so I mounted them as Read Only in order to copy files across. I did nothing else.

When I came to reconfigure the RAID and reinstall Windows 10, I took the Ubuntu live USB stick out of the laptop, inserted a Windows 10 installation USB and turned the laptop on to ensure that it recognised the Windows 10 installation first. As expected, I saw the Windows 10 setup screen. I turned the laptop back off, removed the USB stick and turned it back on so I could go in to the BIOS and reconfigure RAID....

My installation of Windows 10 booted just fine. It was no longer in its hibernation state but it booted. So far, no problems.

I have absolutely no idea what really went wrong to prevent the laptop from even getting to the BIOS in the first place. The computer repair shop told me that the RAID was broken and that was dragging the BIOS down but I am not convinced. Is there anything to do with a faulty/dodgy/incorrect hibernation that could have caused the symptoms I have described?

If so, what happened to allow me to boot back in to Windows 10? The only thing I did in between the laptop first becoming faulty and it resolving "itself" was mount the drives as read-only in Ubuntu. I don't see how this changed anything?

Thanks in advance for any words of wisdom

Gentle bump. Any ideas?

Welcome to the forum.

Just reading your post. Myself I would disable Hibernation. I've seen hibernation issues on so many machines.

I had something similar on a Dell. Person came in in the morning and tried to wake up laptop. No go. I too accessed the device with Ubuntu as the person had no backups so we needed his files before we tried Windows repair. After I got the files, ran repair and it booted.

So yes, I think faulty hibernation can cause a machine not to boot.

Before you make any changes you may want to reference Brink's article here on Fast Startup https://www.tenforums.com/tutorials/4...dows-10-a.html

My Asus MB desktop has never slept well and I gave up on hibernation a long time ago. Fast Startup is nice but not a must for me. Of course this is my opinion.

Can't say why you couldn't get to BIOS. Does your machine have a BIOS or a UEFI? I wonder if the outcome would have been different with a UEFI, assuming you have a BIOS? Hopefully there is an answer in one of the links in Brink's article.

Here is another article you may wish to check out. http://www.howtogeek.com/243901/the-...-startup-mode/