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
Mar 19 2021 04:41 AM
Mar 19 2021 09:07 AM - edited Mar 19 2021 09:29 AM
@Brad Wilson
This has been happening since February, I have only one restore point, but unfortunately, that's in March.
I've tried teams web but sometimes the image freeze, I can hear people typing and talking, but the screen gets stuck(frozen), so that's why I use the complete APP
As the most effective fix so far is limiting the CPU, right now I'll try to underpower the CPU(i7-10510U), setting both POWER MAX and short power max to 10W on intel XTU as this is listed on ARK as Configurable TDP-down. (+ the 99% CPU max CPU state)
Since we are talking about CPU, I do remember that bios 1.15 had some CVE mitigations for the CPU.
Effectively this changed the CPU microcode. MAYBE what was a happy working CPU now gets mad with some specific teams instructions and shuts the entire system down.
Anyway, as most people here think this is a driver issue, maybe it is a bios/hardware one.
#Edit----
Can't install Bios 1.14 as there's anti-rollback enabled
https://download.lenovo.com/pccbbs/mobiles/r16uj12w.txt
Would be nice if Lenovo/IBM joins the thread too
#Edit 2 ----
This is not a temperature problem, CPU gets stable at 78-82°C on my workload(even hit some temps as 95°C on stress tests). Shutdowns happen when temp is below or at 65°C
Mar 19 2021 10:58 AM
Mar 23 2021 11:06 AM
Mar 27 2021 11:29 AM
I can confirm that we're having the same problem, using Lenvo Thinkpad T490 machines. The machines (only)crash during Teams meetings and simply shut themselves down.
We think it only happens when connected to external monitors ( which is how 80% of the people work ) and it does NOT happen if it's only running on the laptop monitor itself ( not connected to external monitor ) and on the battery ( not connected to AC adapter ). Really frustrating!!
Mar 27 2021 11:39 AM
Mar 29 2021 10:52 AM
Apr 01 2021 02:19 PM
Apr 07 2021 08:45 PM
Apr 07 2021 09:25 PM
Apr 08 2021 04:23 AM
Apr 08 2021 09:37 AM
Apr 22 2021 02:28 AM - edited Apr 22 2021 02:28 AM
Are there any news regarding validating the root cause of this issue?
Apr 30 2021 01:31 PM
May 04 2021 11:09 PM
Are there any news regarding validating the root cause of this issue?
May 05 2021 07:24 AM
@RayDilsons Hello,
I have the same problem starting february with Lenovo ThinkPad L13... starting from february a few days before 1 year warranty expires.
It makes a random forced shutdown when in Teams calls (i noticed a high temperature, sensor indicate sometimes 100 degree celsius). I changed the thermal pasta, but the same problem occures. I am monitorign the rtemparature, thinking that this might be cause. But in rest the laptop does not have a problems even when rendering video 1 hour....
May 05 2021 07:29 AM
Hi, after running a BIOS update v1.29, it seemed to have sorted out the problem. I tested it on 2 laptops that had the Teams shutting down the laptop problem. Maybe worth giving that a try.
May 07 2021 03:38 AM - edited May 07 2021 03:41 AM
Hi, I've also just updated my BIOS and it seems to work fine now but I have a quick question if I may. After it shuts off, when turning it back on does your L13 also shuts down a few more (1-3) times before finally it gets to work? I hope its not just me. Thanks in advance
Caleb
May 07 2021 05:19 AM
May 07 2021 05:56 AM - edited May 07 2021 11:17 AM
I just installes lastest BIOS and Intel Firmware using Lenovo Vantage (until 1-2 months ago i had all up to date - system and bios, but the problem still persisted).
I am curios if this will help.