T410 Boot Lag / Cycle Issue SOLVED

[davidblackshoes]

Would someone take a look at this video that shows the behavior of my T410 at boot?
2.0GHz
8GB RAM
500GB SATA HDD
NVIDIA graphics
Win 10 Pro
Boot Menu 1)Optical drive 2) HDD0, and down the line.

Everything works great once it's into Windows. It's peppy in its responses, but it's odd in its behavior during boot.
I have an identical T410 but with Intel HD graphics and it boots right into Windows. I don't know if this is the difference. ?
I don't know if this lag/cycling is normal. I don't recall it doing this in the past, but I may be foggy on that and it did.
Thanks for any help.
Watch the status indicators during the video (might help?).
https://youtu.be/i9YIVSaAcVY

[RealBlackStuff]

This is not a T410 problem, it's (no) thanks to W10, that you have this unwanted delay!
Time to teach W10 to COMPLETELY switch off, instead of "forced sleep".
Then try again.
Maybe remove the optical drive?

[davidblackshoes]

This is not a T410 problem, it's (no) thanks to W10, that you have this unwanted delay!
Time to teach W10 to COMPLETELY switch off, instead of "forced sleep".
Then try again.
Maybe remove the optical drive?

You were right, it was a WIN 10 issue.
I had removed optical drive, etc but no luck.
Copied every BIOS setting from my identical T410 that has Intel HD graphics and doesn't have this issue but no luck.
Disabled duplicate NVIDIA drivers in Device Manager (I suspected it was the difference between the graphics on the two machines) but no luck.
Today I looked at Event Viewer logs and I got my clue from "Critical" events. Wasn't shutting down cleanly.
I turned off Quick Start and LUCK. That solved it.
Before: Lenovo splash screen would come up min 2 times (first time, Thinkvantage button was inoperable) before finally loading windows. Time from power on to Win log in screen: ~90-105 secs.
Now: Splash screen comes up just once, is operable, and time from power on to Win log In is ~40 secs.
**Shut down time is 15 secs. Not a huge difference.

Apparently, Quick Start causes no issues with the T410s that have Intel HD integrated graphics but is an issue with the types with dedicated NVIDIA graphics.
I assume it has something to do with drivers being loaded (or not) but whatever it is, I don't care: the machine works perfectly now.

(T410 with Intel HD graphics integrated with Quick Start enabled: power on to Win Log In: ~20 secs. **Shut down is ~2 secs)

**EDIT: Shutdown time really isn't any different between these two machines, now that I think about it. It's really ~20 secs for both, it's just that the machine with Intel HD goes to black screen in 2 secs but it's ~18 secs more for the power button and status lights to go off. The machine with NVIDIA shows Windows "shutting down" screen for ~20 secs until the power button and status lights go off.

Thanks for replying!

[dr_st]

Quick Start basically means that when you "Shut down" the laptop, it doesn't actually shutdown, but hibernates. Then the next "cold boot" is actually resume from hibernation.

Driver problems often cause issues with suspend/hibernate or resume from them. Apparently, what was happening in your case is:
* Laptop was successfully hibernating
* Resume from hibernation was failing
* After a while, Windows would give up, and do a full system restart
* From system restart, system boots fine

From your description, it sounds like you don't need hibernation, so your solution is perfect. Thanks for sharing!

[kfzhu1229]

I had similar issues with a ThinkPad E420 with its Radeon switchable graphics. It's slightly different that it does boot up with quick start but what happens is it takes upwards of 90 seconds to do so and it gets annoying very quickly.
The solution there is to use unofficial drivers that someone wrote just to make it work with Windows 10.
But since you are already on driver versions designed to work with Windows 10 (as is the case with NVS140M and 160M), I have no clue why the driver can cause this issue

[davidblackshoes]

Quick Start basically means that when you "Shut down" the laptop, it doesn't actually shutdown, but hibernates. Then the next "cold boot" is actually resume from hibernation.

Driver problems often cause issues with suspend/hibernate or resume from them. Apparently, what was happening in your case is:
* Laptop was successfully hibernating
* Resume from hibernation was failing
* After a while, Windows would give up, and do a full system restart
* From system restart, system boots fine

From your description, it sounds like you don't need hibernation, so your solution is perfect. Thanks for sharing!

Thanks for running this site!