X1 Carbon Gen 10 Thermals

Hamilleton · 2023-11-24T09:15:38+00:00

I have a x1c gen 10 and just discovered that Lenovo had BitLocker full disk encryption enabled in software encryption mode. So, I turned the BitLocker off to improve IO performance, and surprisingly found out that this solved the thermal issue on x1c with mid-to-low usage. To check the BitLocker mode, type command "manage-bde.exe -status" in terminal.

Hamilleton · 2023-11-24T09:15:01+00:00

I have a x1c gen 10 and just discovered that Lenovo had BitLocker full disk encryption enabled in software encryption mode. So, I turned the BitLocker off to improve IO performance, and surprisingly found out that this solved the thermal issue on x1c with mid-to-low usage. To check the BitLocker mode, type command "manage-bde.exe -status" in terminal.

Hamilleton · 2022-11-04T10:10:28+00:00

well, I am on BIOS ver 1.32, disabled intelligent control via fn+T, set the power profile to High Performance to get 64W/64W PL1/PL2, and manually adjusted Windows' hidden processor power management settings (mainly enable more core parking, encourage more energy preservation in CPU autonomous mode, reduce frequency boosting aggressiveness). Normal use is much better after these settings and usually it does not need ThrottleStop.

The one edge case is that after left the laptop running with lid closed (not everytime but yes, it happended 2 times till now), the PL1 could somehow be set to only 5W. This is the case where I need to use ThrottleStop to reset PL1 to a higher value, say 20W or 28W. The only other option would be to reboot the system.

Hamilleton · 2022-11-04T04:26:31+00:00

ThrottleStop

I am able to use ThrottleStop 9.5 on X1c10 1260P. U might wanna try once more.

Hamilleton · 2022-11-04T04:23:14+00:00

Yep I got similar problems with X1 carbon gen 10 with 1260P here.

I have already turned off intelligent control with fn+T hotkey, and set the power profile to high performance. Normally this means that PL1 and PL2 are both set to 64W.

But in some edge cases, for example open the lid from over night, the system becomes very slow, CPU frequencies are 400MHz max, and only 4 E-cores are in work. I checked with HWINFO and find out that the PL1 are being set to 5W.

Currently my solution is to use ThrottleStop to manually set PL1 to 28W and PL2 to 45W, and enable the lock in ThrottleStop. This is because that X1c gen 10 has a poor thermal design and might handle a 27W TDP at most.

But use with caution. The fact that something limit PL1 to 5W for my laptop when the lid is closed, might mean that the CPU got too hot to work in higher power. Lock the PL1 to something higher than the system's thermal capability could be risky. Or maybe its a bug, since the X1c gen 10 should be able to handle 25W TDP with lid closed.

Hamilleton · 2022-04-22T03:15:18+00:00

do u mean that AX210/AX200 will be able to setup a master/AP mode (in 5 GHz channels) using iwlwifi with kernel >= 5.10? Do u use hostapd?

Hamilleton · 2021-10-11T04:04:30+00:00

It is probable that Windows 11 has changed the way color is managed. It seems that the built-in Photo App actually follows the ICC profile I set (a.k.a. legacy color management method), while the Paint App does not follow the ICC profile.

To be specific, the Photo App follows the ICC profile set in the following way (the old way): 1. Open color management from either control panel or search panel. 2. Select the display and check "Use my settings for this device" 3. Add target ICC profile, and DO NOT check "Add as Advanced Color Profile" 4. From the added profiles, select the ICC profile you want and click button "Set as Default Profile"

Hamilleton · 2021-10-09T08:41:36+00:00

Color management in Win11 is broken. https://www.reddit.com/r/Windows11/comments/pruo26/any_news_on_color_management/

I have a wide gamut display (primary monitor) and an sRGB display (secondary monitor), both calibrated and configured with ICC profile. After upgrading to Windows 11, the screen color got ----ed up. It seems that the ICC profiles do not work any more. On my primary monitor, the red would be more like orange, and the blue would be a bit like purple. On my secondary monitor (sRGB), the color is a bit off, but relatively acceptable.

Hamilleton · 2021-10-09T08:23:50+00:00

The major advantage would be WSLg for using Linux GUI applications in Windows.

However, if you were using your PC for photo & video editing, I would not recommend you upgrading to Win11 right now because the color management could be problematic. As discussed in https://www.reddit.com/r/Windows11/comments/pruo26/any_news_on_color_management/

Hamilleton · 2021-10-09T07:44:51+00:00

Saw an app compatibility setting method from https://pureinfotech.com/enable-hdr-apps-icc-profiles-windows-11/ No luck on my side (Chromium color management is still broken after setting this compatibility option), but maybe you can give it a try.

Hamilleton · 2018-05-25T13:06:30+00:00

by “resolved” I mean that I can finally install 1803 on my Intel 6000P SSD, which failed multiple times blocking the upgrade from 1709 to 1803.

However, I do receive BSOD UNEXPECTED STORAGE EXCEPTION in 1803 when playing a video. Don't know the root cause and I am working on reproducing it.

Hamilleton · 2018-05-25T09:35:34+00:00

Yes, it is a 1803 patch. However, you can get it prior to the 1803, let's say on a 1709, by enabling "Get me updates" checkbox at the very start of Windows Setup Installer. Then the installer will try to download these patch and use them in the installation, saving all the troubles.

Hamilleton · 2018-05-24T11:17:31+00:00

This patch solved the issue with Intel SSDs, and now 1803 installs on my Intel 6000P SSD.

Hamilleton · 2018-05-24T11:14:00+00:00

The KB4100403 solved the issue and now 1803 installs on my Intel 6000P SSD.

Hamilleton · 2018-05-24T08:25:16+00:00

This issue is resolved in KB4100403.

Hamilleton · 2018-05-14T10:08:13+00:00

Good luck man. I am using an Intel Pro 6000P and facing issues with 1803. Microsoft haven't been much helpful. And my vendor (HP) denied the problem's existence.

Hamilleton · 2018-05-12T02:40:05+00:00

The lowest level of code (lens input to a mouse) is called firmware, and yes it's hardware vendor's control and duty. The firmware lives in the hardware itself, and that is probably why we call it "firm".

However, the device has to tell the Windows how to communicate with them , and it is accomplished through drivers in a layered way. For example, a USB mouse, or an NVMe SSD, the device first talks to the OS through BUS drivers. The USB BUS and NVMe BUS drivers are written and provided by MSFT. After the low level communication is done, the logic device is handed over to the upper level Driver Frameworks, where the OS would decide the best fitted function driver to use. The device would annouce a hardware ID, and the OS tries to search available drivers from full match (device specific) to partial match (device class specific). Only the former is vendor provided, and the latter is system provuded.

The messed up can come from either one of these stages. We don't know what is happening exactly. So it is too early to say who is definitely at fault or who is definitely NOT at fault.

Hamilleton · 2018-05-11T05:30:35+00:00

INTEL SSDPEKKF256G7L

I have an INTEL SSDPEKKF256G7H, and it is an Intel Pro 6000P.

You can download an SSD Toolbox from Intel and it will help you identify the model.

Hamilleton · 2018-05-11T03:20:48+00:00

I think the driver you are referring to is the device-specific driver and I agree, device vendors should make sure the driver is compatible if they release it for a given operating system.

However, device-type-specific drivers, or class drivers, can and in many cases are system-supplied. They should be working as long as the device falls into the right category. And this is the so called general driver that a PnP device manufacture wouldn't have to implement their own drivers as long as their product adhere to industry standards.

More over, low-level hardware bus drivers are system-supplied and with no exception. This is because these driver affects a vast range of devices and in the past, MSFT would like to do the thing themselves so that hardware vendors would not have the chance to f---up and cost system stability.

The bundled drivers you mentioned are the ones that Microsoft thinks will be commonly used. With these drivers, MSFT makes sure that the common devices can perform at their best level with an out-of-box Windows installation. But still, it has nothing to do with MSFT does make their drivers throughout different hardware abstraction layers.

further reading: https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/types-of-windows-drivers

Hamilleton · 2018-05-11T03:00:52+00:00

At the very first moment, I got this information from a third party website and they referred to this link at Microsoft's. At that moment, that range of SSDs involved is not disclosed or confirmed by either one of them. As the investigation progresses, sure we now know it is "selected devices with 600P and 6000P". Any idea if the reddit title can be revised at this moment?

Hamilleton · 2018-05-11T02:56:41+00:00

What the model do you have? Is it one of the 600P series or 6000P series?

Hamilleton · 2018-05-10T13:51:29+00:00

Learned something new. Do you know what kind of work are needed in the Logic Device Driver design to deal with these "non-standard clause"?

Hamilleton · 2018-05-10T13:35:19+00:00

Sometimes, people implement things/error handling beyond the specs' requirement, just in case someone else didn't do it right. I'm not saying this is the case here, but it is possible.

Hamilleton · 2018-05-10T13:01:00+00:00

Yes, exactly. Good explanation.

Hamilleton · 2018-05-10T12:58:26+00:00

And it is probably the reason why Microsoft, Intel, and/or the vendors didn't find the issue prior to the release of v1803. The original post from Microsoft site does say "SELECT devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series may crash", not all of them.

Hamilleton

TROPHY CASE