Feb 09 2021 11:30 PM
Like few other collogues I'm using a new Lenovo L13 Yoga. We are using Microsoft TEAMS as our formal application for conference and video calls.
Recently we started facing a "random" issue in which after some time in the call, the computer shuts down. the shut down accrues without a warning and it is a brute force shutdown i.e. without a safe close of all applications. It is as if you were pressing a long press on the power button.
We tried to reinstall TEAMS and to make sure that our laptops are working with the latest update, with no change.
Did anyone ever faced this phenomenon?
Any suggestions?
Thanks,
Eric
Feb 24 2021 06:15 AM
@bwilson Just a quick update. I made the Power changes on the 4 problem L13 laptops and so far after 48 hours no reported shutdowns. I would like to add that this morning a 5th (mine) shut down when I joined a TEAMS meeting. Up until now it has been the L13's with the i5 processor and 8gb ram. I have not used mine for 3-4 weeks as I've been using the problem laptops so I can troubleshoot them live. I was still on a 1.3 version of TEAMS and my laptop is an L13 however I have an i7 with 16gb ram. The good news is I changed the power settings and was successfully in a meeting for the duration (35 minutes). Fingers crossed and hope I didn't jinx things! JD
Feb 24 2021 06:21 AM
Thanks everyone for the replies and assisting us here. Glad to hear it is working so far, and please let us know any successes or failures in testing. Sorry I was away for most of the day yesterday and couldn't reply but thank you all for taking the time to post back here.
Feb 24 2021 06:51 AM
Feb 25 2021 06:42 AM
@eric_joely Hi guys, if like us you have a lot of L13 devices deployed then you can use the below script to automate this paired with whatever MDM you use.
REM Set Plugged in value
powercfg -setacvalueindex SCHEME_BALANCED SUB_PROCESSOR PROCTHROTTLEMAX 99
REM Set On Battery value
powercfg -setdcvalueindex SCHEME_BALANCED SUB_PROCESSOR PROCTHROTTLEMAX 99
Feb 26 2021 02:48 PM - edited Feb 26 2021 02:58 PM
We are seeing a lot of this as well at our school. Teams meetings are causing an abrupt shutdown. It is not happening with any other application. We also are using Lenovo Yoga L13s. We have about 160 of these deployed. We would be very interested in a solution. It is wreaking havoc on our teacher's ability to conduct remote classes.
Mar 02 2021 06:05 AM
The workaround seems to be working for our devices.
Mar 02 2021 06:08 AM
@bwilson Just a quick update, so far so good. Every L13 that I have made the power change on has not experienced the problem any further.
Mar 02 2021 06:13 AM
Mar 02 2021 06:13 AM
Mar 02 2021 07:23 AM
Mar 02 2021 07:29 AM
Mar 03 2021 12:47 AM
Mar 03 2021 04:50 PM
@Sam Cosby
I'm having the same issues with my Thinkpad E14(intel)
Disabling Hardware Acceleration for Microsoft Teams and Setting the Maximum processor state to 99% instead of 100% did not solve the problem for me as today my laptop shut down again while using teams
Mar 04 2021 01:21 AM
I think that is a problem with several model of Lenovo,
We have reported problem with T480, T490 and T580 as well.
that is sad 😞
Mar 04 2021 04:58 AM
Mar 04 2021 05:54 AM
@HongKongPhooeyGal
My current Lenovo Intelligent Thermal Solution Driver Version was 2.0.369.1 on E14 (intel) dated as 01/14/2021 and installed on 02/08/2021.
Reverted it today to 1.0.1.363 (dated as 11/16/2020)
Relevant information about my system I've posted in this thread
https://www.reddit.com/r/thinkpad/comments/lslhja/e14_suddenly_shuts_down
I've also suspected about the drivers since shutdown only happens while using teams and after February updates
I thought the culprit was "BIOS" or "LENOVO SYSTEM"
PS: I always use my laptop on balanced mode, because of the slider that allows me to control fan behavior
Mar 04 2021 08:50 AM
Mar 04 2021 09:01 AM
@bwilson Nothng at all in the event Viewer. It took a lot of digging to track down the Driver updated for the Intelligent Thermal Solution Driver to the EXACT time that one of our first Users experienced the issue for the very first time.
The 369 Driver seems to be causing the issue when a system in not set to the Balanced Power Settings and the Max Processor is set to 100% versus 99%.
Mar 04 2021 09:05 AM