06-16-2019 01:59 PM - edited 06-17-2019 07:10 PM
Both in Windows 1809 and 1903 when resuming from sleep it will randomly happen that:
Connectivity is unreliable regarding internal graphics, external screens and thunderbolt.
It seems to me that these recurring graphics, display and thunderbolt issues found in P1 X1 machines are related to it.
This is a summary of bios versions with fixes related to issues alike.
UEFI: 1.21 / ECP: 1.10
- (Fix) Fixed an issue where WMI BootDisplayDevice option is incorrect.
- (Fix) Fixed an issue where the system might not resume from hibernation on Discrete Graphics mode with Windows10 version 1809.
UEFI: 1.19 / ECP: 1.10
- (Fix) Fixed an issue where the system might BSOD when connected the external monitor.(Note)
NVIDIA Graphics Driver v184.108.40.2065 or later version is required.
UEFI: 1.18 / ECP: 1.08u
- (Fix) Fixed an issue where the system might not boot with Hybrid Graphics.
- (Fix) Fixed an issue where the system might not boot when disabled Audio device by ThinkPad Setup on UEFI BIOS version 1.15 and 1.17.
UEFI: 1.17 / ECP: 1.08
- (Fix) Fixed an issue where the system might not boot with Discrete Graphics.
- (Fix) Fixed an issue where the system will black screen under OS environment.
UEFI: 1.15 / ECP: 1.08
- (Fix) Fixed an issue where the system might hang up when Thunderbolt BIOS Assist Mode is changed on Diagnostics Boot Mode.
06-17-2019 10:12 AM - edited 06-17-2019 10:15 AM
A litle update to the issue.
It seems that it has to do with the computer going into hibernate ( or deep sleep ) after a long sleep period.
06-22-2019 05:06 PM
As for today I've discovered external monitor not switching on after long periods of time is 32UD99-W monitor fault.
There is a setting in the monitor that reads Automatic Standby that will cause the problem. Once the monitor reaches the threshold it will not wake up or recognize the signal in the port it went to sleep. Interestingly It will say that signal is detected in a different input and will prompt you to switch will still connected to the same input.
It's almost certainly a firmware fault in the monitor.
It' is indeed not necessary to have it enabled as it only performs some kind of force standby whenever it detects that the image didn't change for a long period of time. In a normal scenario the computer would trigger screen saver, black screen or sleep mode. This is therefore not needed.
The monitor will still go to standby normally when no signal is detected.
About the audio.
I still get the yellow mark at times and need to disable/re-enable the audio device to get it back working.
I will continue with the tests and update the thread.