I have a Framework Laptop 13 running Windows 11, connected via Thunderbolt to an LG ultrawide monitor (40WP95-C). Every so often (maybe every 10-15 minutes), my LG monitor will go black, and all of the USB devices connected through the monitor will disconnect. A couple seconds later, the display will come back alive and the devices will reconnect.
I thought it was originally an Intel graphics-related issue, but even when I upgraded my original 11th gen mainboard to the Ryzen mainboard, the exact same issue persists. A couple different Apple Silicon MacBook Pros connected to the monitor don’t have this issue.
I’ve tried connecting a higher-wattage (100W) power source to the Framework laptop in parallel to the monitor (96W), in case this is a Power Delivery issue, but power still seems to be coming from the monitor, based on the charge LED on the Framework.
Has anyone successfully resolved an issue like this? It seems like similar finicky issues with Thunderbolt are pretty common. Thanks!
I haven’t noticed this issue with any of the expansion ports—but then again, besides charging, I don’t use the other ports for anything where I would notice something like this.
I am experiencing the exact same problem with the exact same monitor, almost same setup, 13th gen Intel i7-1360 board Framework 13, but Windows 10.
I also did not see this problem before with any expansion card or peripheral device. I own another USB-C dock with HDMI support that does not show this behavior.
If it’s of any interest, the charging port LED on the laptop goes blinking orange once this happens and in the Device Manager you can see devices repeatedly dis- and reconnecting.
@shubaksa: Unfortunately, I haven’t found a solution for this. I’m curious, which USB-C dock are you using? I’m thinking I might have to switch to using a dock instead.
I was using a cheap Codeway 8 port USB C dock before, but since it only supports up tp 4K displays I cannot use it with the LG monitor. My intermediate solution is to use the monitor with the HDMI port extension card, no outages since.
I am also suspecting issues with the PowerDelivery protocol by now as I also saw constant power profile renegotiations during those periods.
Things getting more interesting. It seems the notebook (not the monitor) is causing the power profile renegotiations regularly, independent of a Thunderbolt display being used or not. I just never paid attention before since there was no obvious sign.
Framework Team, I think the ball is in your court now.
I am having this same issue. I have a 12th Gen and a 13th gen intel framework’s both use the Anker 575 USB-C Docking Station (13-in-1). I also have the framework 16 using the same docking station. all of the 13 inch laptops one of the displays will randomly turn blank for a few seconds and then turn back on. the framework 16 has no problems.
The 13 inch laptops drive 2 display’s and 16inch is driving 3 displays through the Anker hub. My employees are complaining about the screens blanking out often.
Does anyone have any idea what could be causing the problem?
I had a similar issue with my old Dell and an ultrawide. For me, it turned out to be a dodgy Thunderbolt cable. Have you tried swapping out the cable connecting your Framework to the monitor?
Hello, I have the exact same symptoms with a Framework 13 (12th Gen Intel) and Dell U4025QW 5K monitor (Debugging Thunderbolt (Monitor) Issues). The issues are the same (screen going blank and all peripherals disconnecting) irrespective of if I use the Dell-supplied “Thunderbolt 4 140W (EPR Active)” cable or a “Thunderbolt 4 (Passive)” cable. The point here being that if it was a marginal signal integrity issue, I would expect that using the Passive cable would result in more regular disconnection, but this does not appear to be the case.
I have a feeling that when suddenly doing something intensive with graphics or the CPU that the problem occurs more regularly.
Turning off GPU acceleration on my Browsers appears to have reduced the regularity of the drop-offs.
Its almost as if the CPU gets too busy to do “something” related to Thunderbolt and the peripheral drops off until it is re-enumerated again. Could this be a simple time-out value that needs adjusting in the Thunderbolt driver?
I’m facing the exact same issues on a FW13 Ryzen AI running Fedora, and a LG 5k2k Display connected via the boxed TB cable. As soon as there is any load on the machine, display & all peripherals disconnect. This is pretty much unusable for me in that state.
However, when I plug in an external power source to a separate port which delivers more power than the display, it seems like that stabilizes the situation. I have to still check, if that works reliably.
One workaround I could find is to use DP 1.4 (as the built-in HDMI on the monitor does not support the native resolution for some reason), but that requires me to use another port for PD and peripherals.
Since this seems to be a more widespread problem that affects multiple board types, is this something that Framework can look into? Happy to assist if required, just let me know.
Any updates on this topic? I am having the same issue. I upgraded to a newer Dell dock, but it is frequent enough to make me consider returning my FW13. I otherwise love the laptop, so if anyone has a specific dock that works I would appreciate a recommendation.
I have tried using a few different dell docks. They all have integrated thunderbolt cables. I did try adding a high wattage power adapter in the other USBC port and that reduced the frequency from both monitors every couple minutes to one monitor every 30ish minutes.
This may or may not be your problem, but I finally fixed my AMD + Thunderbolt 4 + dock + TB display blanking for a second or 2 while browsing certain web sites.
Tried different docks, cables, display settings, VRR off, etc, etc. Ultimately what fixed it for me was disabling HDCP Support in AMD Settings > Display Overrides.
Thanks for the help. In the end I tried a DisplayLink dock from Targus that my work issues. It fixed the problem and DisplayLink is good enough for this use case. I will update if I try going back to TB for any reason.