I asked the same question in Lenovo Forums, but I'm not very hopeful they'll solve it anytime soon, similar problems began in different ways and had solutions that don't fit me.
I got a brand new Ideapad S145-15IWL around 1 month ago. As soon as I got it I zero-filled the entire hard drive (deleting all partitions) and installed a Linux Mint 19 in a single ext2 partition. It boots in legacy mode and there are no UEFI partitions nor anything UEFI related.
I never updated the BIOS either, it's in the version ASCN36WW.
Everything was running OK. After I got it I tested the hardware using Memtest86+ and some DOS-based utilities, everything alright.
But then, today, I entered the BIOS menu (which I have already entered dozens of times) to change a setting, and it rebooted out of the blue.
I tried entering it again and the same thing happens, always about 12 seconds after powering up (or after rebooting).
And it's not only the BIOS menu: The boot menu (entered through F12), any bootloader (like syslinux), DOS and DOS-based softwares and Memtest86+ will also suffer the same problem: The computer will reboot 12 seconds after power up disregard of anything that's running.
All of that being that those same software were running OK just a few days ago.
None of the diagnostic tools are detecting problems in the few seconds they have until the computer reboots.
Complete operational systems like Linux or Windows still boot and run normally, without any issues. After their kernels take over control, they do something that avoids the rebooting.
Does this sound familiar to anyone? I really can't understand why this started out of the blue.
Some other people had similar problems, but always related to an update. One guy tried to correct that making an update and guess what: The computer rebooted in the middle of the UEFI capsule update and corrupted the BIOS. So I'm not trying that.
Thanks!
Ps.: I have already tried cleaning the CMOS memory. I disconnected the battery and the CMOS battery, letting it off for 5 minutes and put all back again: No change. It did clear the CMOS memory but didn't improve it's behavior.
I also tried powering it on without the battery and the hard drive: No change either, still the same behavior.
I got a brand new Ideapad S145-15IWL around 1 month ago. As soon as I got it I zero-filled the entire hard drive (deleting all partitions) and installed a Linux Mint 19 in a single ext2 partition. It boots in legacy mode and there are no UEFI partitions nor anything UEFI related.
I never updated the BIOS either, it's in the version ASCN36WW.
Everything was running OK. After I got it I tested the hardware using Memtest86+ and some DOS-based utilities, everything alright.
But then, today, I entered the BIOS menu (which I have already entered dozens of times) to change a setting, and it rebooted out of the blue.
I tried entering it again and the same thing happens, always about 12 seconds after powering up (or after rebooting).
And it's not only the BIOS menu: The boot menu (entered through F12), any bootloader (like syslinux), DOS and DOS-based softwares and Memtest86+ will also suffer the same problem: The computer will reboot 12 seconds after power up disregard of anything that's running.
All of that being that those same software were running OK just a few days ago.
None of the diagnostic tools are detecting problems in the few seconds they have until the computer reboots.
Complete operational systems like Linux or Windows still boot and run normally, without any issues. After their kernels take over control, they do something that avoids the rebooting.
Does this sound familiar to anyone? I really can't understand why this started out of the blue.
Some other people had similar problems, but always related to an update. One guy tried to correct that making an update and guess what: The computer rebooted in the middle of the UEFI capsule update and corrupted the BIOS. So I'm not trying that.
Thanks!
Ps.: I have already tried cleaning the CMOS memory. I disconnected the battery and the CMOS battery, letting it off for 5 minutes and put all back again: No change. It did clear the CMOS memory but didn't improve it's behavior.
I also tried powering it on without the battery and the hard drive: No change either, still the same behavior.
Last edited: