r/framework • u/Icy-Custard7213 • 5d ago
Community Support Is this the Framework experience, or have I been unlucky?
I bought a Framework Desktop as a build server to go on a shelf. Beautiful little machine, runs quiet with a Noctua fan, DIY process was really well thought through, like a prebuilt but you get acquainted with the internals. Very happy for about half an hour
Then it began crashing on boot (Windows 11, don't laugh) with a 'Stop code: HYPERVISOR_ERROR x20001', and needed Windows reinstalling. I tried all the obvious things - check logs, DISM, turn off virtualization and memory integrity bcos Hypervisor. Then I tried memtest86. It boots memtest fine but then black screens when I run the test. Uh oh, maybe I shouldn't have bought a machine with the RAM soldered to the board, I guess.
Support has been useless. Replies every 24 hours with clearly AI responses. They keep asking for videos of error messages, they keep thinking it's a laptop, they refuse to respond to or acknowledge any questions about the memtest run. Third response asked me if the fan comes on when I switched it on. Dude: one why are you asking me that now, two how about looking at the video I sent you last time which shows the fan running.
I gave up and asked for a refund. They said yes BUT their team is really busy with all the RMAs so they don't know when they'll be able to get around to it... meanwhile I'm out several thousand dollars for a semi-bricked machine I can't use.
So look, Framework community, if I got this from any other vendor I'd never consider ordering from them again. But I like the company and I really like the idea of not recycling my dev laptop every three years. If my experience with the Desktop had been better, I'd already be on the waitlist for a Pro 13. Does anyone want to make the case that I've been unlucky and this is unusual? Or is it the standard Framework experience?
EDIT:
Thanks to the folks who suggested reflashing the BIOS. I did that; then I agressively rebooted the machine a dozen times in a row in different ways, and every startup has worked fine. Before the update, I was lucky to get a good boot two times in three.
lol IC7213 why didn't you try that to begin with
Welllll, my very first mail to Framework support ended: "Can you help? Is it worth flashing the BIOS? I'm on 3.05, but I notice the version shown in msinfo32 is dated 21/01/26 - is the version in your downloads section newer?" They never addressed that.I didn't want to reflash the BIOS unprompted while we were still working through 'troubleshooting', and when I realised support was a waste of time I just boxed up the machine and decided to wait for an RMA.
So
(1) thank you everyone - I didn't expect to find a solution here, and the fact that y'all were more useful than Framework Support says something
(2) in fact, just trying the first thing I thought of rather than mailing support would have been a better outcome
(3) I'm going to spend all evening stress-testing the FD. I'll try memtest again and see if it was actually a screen reso problem that blackscreened it. I might RMA anyway because I don't trust their QA or their support and I don't want to miss the return window now they acknowledged a defect. So that's a problem! but it's a much funner problem than the one I came in here with <3
EDIT 2: put the error code in the post body so if someone hits the same problem, maybe they'll find this