Same here. I have my FW16 on almost 24/7 and game on it every other night at least. Been rock solid. Not sure what this guy is on about, but that’s not my experience at all.
2 Likes
I share the same experience, FL16 near 12 hours everyday for work and gaming, one blue screen because of the first bios version then not any since the end of march 
Hope you’ll have a fix of some sort. Just avoid unecessary alarming title, even more with so few information
1 Like
I bought a Framework a year ago, and it handles the craziest Minecraft TNTs (mods) better than my brother’s 2000€ Gaming Laptop (from 2018).
So, you’re problem is a special case.
If you had Windows, it’s crap. (Ok, that’s a personal opinion which doesn’t help much, I guess).
Anyway, Framework laptops are amazing. Of course there are things to improve here and there, but that’s just inherent to cutting edge technology and design : it’s experimental nature is what makes it so amazing too !
Computer from the 90s are from another world. Certainly reliable, but also not very powerful.
1 Like
I find it quite puzzling that the original poster damns all Framework computers, claims to have all sorts of problems and, yet, never gives any details about the problems or the configuration of their Framework computer, and never replies or posts again. This makes me wonder if this is nothing more than a MacFan or WindowsFan who thinks Framework computers and, perhaps Linux, are a threat to their personal favorite brand of computers and operating systems and is simply trolling…perhaps not even an owner of a Framework computer? Given the huge improvements in all operating systems in the past 30 years, it seems quite unlikely that a computer from the 1990s, running Windows 3.1 or Windows 95 or Mac “Classic” OS from the 1990s would be superior to a decent current computer running one of the better Linux distros or even a current Windows or a current Mac OS version.
Y’all, nah. I find windows deplorable and mac is not my favorite either. Pure linux fan here. I have a framework running the recommended os. The hardware simply blows.
I have spent days worth of hours of my life sending videos to the support team repeating the same troubleshooting steps they keep feeding me over and over and over. Many times every single day, everything on my screen just freezes. Like, not blue screen, nothing fancy, just freeze. Everything stuck exactly where it is, and nothing will happen again until I hard restart the computer. I’m not looking for any more troubleshooting suggestions. I already tried those recommended by the community and, as mentioned, the support team. (See: fed up, cutting my losses after days worth of hours of my life sunk, I tend to enjoy tinkering but gotta draw a line SOMEWHERE).
The problems started cropping up just a couple weeks after the end of the warranty period so no that’s not an option. I’ve pleaded and begged with support to get any replacement parts to no avail. People are in here telling me not to talk trash about all framework computers when I haven’t used all framework computers. Of course I haven’t used all framework computers. I’m a single human being.
I’m so happy for everybody who has one and loves it. I can only possibly speak from the perspective of my experience, and I do wanna share, so that anybody can see, that some framework experiences are really quite negative.
1 Like
This is called “once you’ve been in tech a while, you end up hating 90% of your customers!”
It happens to everyone in tech. Natural way of things.
Think about it, the bigger you get the more “less clever” you have to deal with. Initially Frameworks customer base was pretty clued up and enthusiast. You can work with that. The bigger and more exposed you get…the more less clued up customers you get.
“So can I install my SATA drive in this?”
In which case they made a big mistake: in my experience Apple fanboiz are not a patch on the Framework zealot!
1 Like
As a person that acquired my laptop for my small business, I expected very few hiccups with the Framework laptop I received. I bought the AMD 7840U with the 2.8k screen added 32gb ram and a 1tb ssd.
The reality was a little different than that. I performed many actions above and beyond what a reasonable person should expect to do to a new laptop. I do not blame Framework for that, but I also couldn’t keep the laptop for it’s intended purpose. It just did not suit the needs of this small business owner without an internal team dedicated to device hardware/software concerns.
I will strongly consider purchasing a framework device for my personal needs when I reach that point. It just wasn’t fool proof enough, for what I needed.
Framework is currently in the process of accepting my return and I see no reason why it wouldn’t go smoothly based on our ongoing communications.
I could be angry it didn’t work out for me, but that anger wouldn’t be justified if directed at this company based on my experience(s).
3 Likes
I mean, if you’re out of warranty, then you’re kind of on your own really. Definitely, not a pleasant experience, and you might expect better longevity, but the thing is, there would always be manufacturing variations amongst the parts that are shipped, and you need to be ready to be the unlucky one.
When I was a Dell XPS enthusiast, all I really wanted out of Dell was a first-party known-good parts store, and here you are supported really nicely if ever you’re in the situation where you’re out of warranty, or just did accidental damage to your machine.
Well, in my case, doesn’t hurt that EU has a mandatory 2-year warranty window. And I also just learned that Spain, I guess, has an even longer warranty.
1 Like
There is a thread here that talks about things that could be improved on a FW16:
And also things that we would like to see improved in the current FW16 and delivered as a BIOS update:
I think a combination of those two would make for a laptop that more people would buy.
2 Likes
Looking at the OP’s thread history…he/she has a 1st gen FL13. That is unfortunate…because nrp, in the FL13 Core Ultra Series 1 (release / announcement / introduction) video, did say the FL13 is “getting closer and closer to perfection each time”:
Maybe OP can give Framework a more up-to-date chance / evaluation base on 2024 offerings.
The whole USP is that the laptop can be upgraded incrementally. What parts should the OP replace with 2024 “offerings”?
I had something similar happen twice one day. I was in a video conference for work and everything froze but oddly enough my audio was still working (both playback and microphone) so I was able to continue the video conference, just unable to do anything on my computer and everyone/everything visually frozen. Happened again during another meeting later that day. Afterwards, I updated everything including the kernel, and unplugged everything on my desk to power-cycle them (including my monitor and thunderbolt 4 dock). It hasn’t happened again since then 
.
Eh, SATA drives come in the M.2 form factor so thats not an unreasonable question. I, frankly, was surprised to find out my AMD framework laptop does not support SATA m.2 drives when I needed to recover data off a drive from my mom’s dead laptop while away from home.
1 Like
Any of the following in any combination (OP didn’t state the specific issue(s)): CNC Lid, matte 2.8k display, larger battery, new web cam module, new mainboard, new expansion module…
That’s just because you haven’t purchased a Smart coffee maker or an arduino yet. 
2 Likes
Happened to me twice again today! Grabbed the logs this time.
Sep 25 16:31:22 odowork kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=4501735, emitted seq=4501737
Sep 25 16:31:22 odowork kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process firefox pid 1616 thread firefox:cs0 pid 1701
Sep 25 16:31:22 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset begin!
Sep 25 16:31:22 odowork pipewire[1305]: pw.node: (alsa_output.usb-Lenovo_ThinkPad_Thunderbolt_4_Dock_USB_Audio_000000000000-00.analog-stereo-88) graph xrun not-triggered (2 suppressed)
Sep 25 16:31:22 odowork pipewire[1305]: pw.node: (alsa_output.usb-Lenovo_ThinkPad_Thunderbolt_4_Dock_USB_Audio_000000000000-00.analog-stereo-88) xrun state:0x737d3ad05008 pending:0/2 s:25399261441791 a:25399261517779 f:25399261533214 waiting:75988 process:15435 status:triggered
Sep 25 16:31:22 odowork pipewire[1305]: pw.node: (alsa_input.usb-Shure_Incorporated_Shure_Digital-00.analog-stereo-86) graph xrun not-triggered (0 suppressed)
Sep 25 16:31:22 odowork pipewire[1305]: pw.node: (alsa_input.usb-Shure_Incorporated_Shure_Digital-00.analog-stereo-86) xrun state:0x737d3ad06008 pending:0/4 s:25399246368861 a:25399247482560 f:25399247486122 waiting:1113699 process:3562 status:triggered
Sep 25 16:31:22 odowork kernel: [drm] DMUB HPD IRQ callback: link_index=8
Sep 25 16:31:22 odowork kernel: [drm] DMUB HPD IRQ callback: link_index=8
Sep 25 16:31:23 odowork kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Sep 25 16:31:23 odowork kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Sep 25 16:31:23 odowork kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Sep 25 16:31:23 odowork kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Sep 25 16:31:23 odowork kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Sep 25 16:31:23 odowork kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Sep 25 16:31:23 odowork kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Sep 25 16:31:23 odowork kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Sep 25 16:31:23 odowork kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Sep 25 16:31:23 odowork kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Sep 25 16:31:23 odowork kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Sep 25 16:31:23 odowork kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Sep 25 16:31:24 odowork kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Sep 25 16:31:24 odowork kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Sep 25 16:31:24 odowork kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Sep 25 16:31:24 odowork kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Sep 25 16:31:24 odowork kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Sep 25 16:31:24 odowork kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Sep 25 16:31:24 odowork kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Sep 25 16:31:24 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: MODE2 reset
Sep 25 16:31:24 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset succeeded, trying to resume
Sep 25 16:31:24 odowork kernel: [drm] PCIE GART of 512M enabled (table at 0x00000080FFD00000).
Sep 25 16:31:24 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
Sep 25 16:31:24 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
Sep 25 16:31:24 odowork kernel: [drm] DMUB hardware initialized: version=0x08004300
Sep 25 16:31:24 odowork kernel: [drm] DMUB HPD callback: link_index=8
Sep 25 16:31:25 odowork kernel: [drm] kiq ring mec 3 pipe 1 q 0
Sep 25 16:31:25 odowork kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: recover vram bo from shadow start
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: recover vram bo from shadow done
Sep 25 16:31:25 odowork kernel: [drm] ring gfx_32775.1.1 was added
Sep 25 16:31:25 odowork kernel: [drm] ring compute_32775.2.2 was added
Sep 25 16:31:25 odowork kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Sep 25 16:31:25 odowork kernel: [drm] ring sdma_32775.3.3 was added
Sep 25 16:31:25 odowork kernel: [drm] ring gfx_32775.1.1 ib test pass
Sep 25 16:31:25 odowork kernel: [drm] ring compute_32775.2.2 ib test pass
Sep 25 16:31:25 odowork kernel: [drm] ring sdma_32775.3.3 ib test pass
Sep 25 16:31:25 odowork kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset(2) succeeded!
Sep 25 16:31:44 odowork systemd-logind[905]: Lid opened.
Sep 25 16:31:45 odowork kernel: [drm:amdgpu_dm_process_dmub_aux_transfer_sync [amdgpu]] *ERROR* wait_for_completion_timeout timeout!
Sep 25 16:31:55 odowork kernel: [drm:amdgpu_dm_process_dmub_aux_transfer_sync [amdgpu]] *ERROR* wait_for_completion_timeout timeout!
Sep 25 16:31:59 odowork systemd-logind[905]: Power key pressed short.
Sep 25 16:31:59 odowork systemd-logind[905]: Powering off...
Sep 25 16:31:59 odowork systemd-logind[905]: System is powering down.
If you’re talking about a Windows 11 setting to right click “when you touch a lower right corner of the touchpad”, the area seems to be programmatically defined by Windows. I found it unreliable as well, so I turned it off and now use two-finger tap/click, which works across the whole surface. Much more reliable, can recommend.
Windows 11 touchpad settings are pretty great overall, I also heavily use middle mouse button (to close windows in Alt+Tab, close tabs in all programs, dismiss notifications, open folders in new tabs in explorer, etc) and found that a triple-finger tap (and click, if you like clicks) for middle mouse button works great!
Because it matches the description of one of the problems OP is experiencing. Providing the logs provides additional context / debugging information, and frankly is a normal and constructive thing to do on any bug report. OP describing the same problem:
I never said that. Re-read the thread, don’t put words in my mouth. Also take a moment to reflect on why you respond that way when someone reports a bug with a product you didn’t create from a company you do not work for.
No. Just like OP, this problem didn’t manifest during the cooling off period.
2 Likes
Sounds like the issue is with the AMD driver. Recently linux kernel had an update which breaks it due to a vector size being changed in the linux side of the kernel. See [Issue]: amdgpu-dkms fails with Ubuntu kernel 6.8.0-44 · Issue #3701 · ROCm/ROCm · GitHub
Note: this update was due to a security vulnerability from what I’ve been able to find.
1 Like
I can’t tell if your experience was really like you described and I don’t know if you really have not fault in creating them, since I was not there. I guess it is your personal experience and I guess things like this can happen, but it definitely cannot be generalized.
Nevertheless, my experience is the complete opposite. I had a minor cosmetic issue with my FW16 and I only had to take some pictures and they compensated me without hessitation. So, I was really glad to own my FW16 before the issue was resolved and I was even more glad afterwards.
Their mission is very important and they are doing a fabulous job in providing a great user experience and helping customers in case of anything not working as it should.
I hope anybody considering buying a frameworkt reads THIS and gets reassured in doing so.
5 Likes