Framework 16 Main Board Issue?
Framework 16 Main Board Issue?
I own a laptop from Wave 1 of the Framework 16. It features the Ryzen™ 9 7940HS and a dedicated GPU. Around six months after purchase, I experienced strange visual artifacts on the screen and frequent system freezes. After restarting it, the problems disappeared temporarily. However, in recent months, I've noticed intermittent glitches across the display that appear and disappear as I move the mouse or scroll. I reached out to Framework support, but after several weeks of communication, they advised replacing the mainboard for around $1500, which they couldn't assist with. This issue appears in Windows 11 and Ubuntu 24.04, affecting most programs—except OBS, where it shows up in Chrome, Firefox, and Word. It occurs on both internal and external displays, regardless of whether they're connected via expansion cards or directly to the GPU. I have the latest BIOS and Framework-provided drivers installed. I attempted a fresh Windows installation and an Ubuntu live USB, swapped my RAM for ones listed as compatible by Framework, and even contacted them about warranty exceptions since I posted about it on their subreddit. Unfortunately, they haven't provided any help and I'm exploring other options. Based on my experience, I wouldn't recommend Framework given this persistent problem, especially since the device seems to have a short lifespan...
The issues appear on both internal and external screens, eliminating driver or OS problems. It’s likely a hardware fault—possibly the motherboard or graphics card. There’s no DIY solution; you’d need to return via RMA or replace the board. The developer acknowledged earlier cooling concerns, so with your proof it would be a strong case for replacement. In the long run, swapping parts is the only viable option.
These items seem quite odd. It appears one line has been stretched or distorted before it reaches the screen. I suspect this isn't just a hardware problem, but even if it is a driver issue, it can be challenging to resolve on your side. It might be due to a bug in a display protocol or a broken link in memory data. What options do you have? I’d suggest trying Windows 10—it still works with most software for Windows 11, and the upcoming update in October seems far less concerning than the Y2K fix. You could reach out to repair shops for guidance, as they have some schematics for their laptops. If you’re in the US, Louis Rossmann is a good name to look up. Good luck!