Hi everyone.
Lenovo Thinkpad E14 Gen 3, stuck on the "To interrupt normal startup, press Enter" screen.
Found a lot of people with this issue, but with no definitive answer. Some people managed to get away accessing BIOS, going to Startup and turning off "Option Key Display". For me that only removed the interrupt normal start up message, leaving only the Lenovo logo.
Most people say hitting Enter does not work. It's true, if you wait a few seconds. But if you hit Enter right away you get the options to enter BIOS (which works), run diagnostics (goes to a blank screen), chose another boot option (goes to a blank screen). So no luck with that.
Tried different USB boot devices, same blank screen. Different M.2 drives (all detected in BIOS), no luck either.
Disconnected peripherals from the board, no luck. Also tried with only battery, or only AC. Did a BIOS reset. Remove RAM stick, so it would force a BIOS reset, cause it detected a different RAM configuration. And it did detect. But also no luck.
It seems to me a BIOS issue, but can't confirm that.
Did anyone have this issue before? How was it fixed?
Thanx a lot.
Lenovo Thinkpad E14 Gen 3, stuck on the "To interrupt normal startup, press Enter" screen.
Found a lot of people with this issue, but with no definitive answer. Some people managed to get away accessing BIOS, going to Startup and turning off "Option Key Display". For me that only removed the interrupt normal start up message, leaving only the Lenovo logo.
Most people say hitting Enter does not work. It's true, if you wait a few seconds. But if you hit Enter right away you get the options to enter BIOS (which works), run diagnostics (goes to a blank screen), chose another boot option (goes to a blank screen). So no luck with that.
Tried different USB boot devices, same blank screen. Different M.2 drives (all detected in BIOS), no luck either.
Disconnected peripherals from the board, no luck. Also tried with only battery, or only AC. Did a BIOS reset. Remove RAM stick, so it would force a BIOS reset, cause it detected a different RAM configuration. And it did detect. But also no luck.
It seems to me a BIOS issue, but can't confirm that.
Did anyone have this issue before? How was it fixed?
Thanx a lot.
Comment