[SOLVED] New DIY Framework 13 Ryzen 5 7640U DEAD

I wouldn’t think so either but @Destroya stated that it might delay things further which, to me, suggests that the technical support system in itself is really immature, ill organized and unresponsive. No case number, no support portal, just “spray and pray email” interface which I now understand could potentially punt one further back in the response queue.

The community here has been stellar right out of the gate and without it, I’d be way worse off. For certain. Whatever the outcome, I’ll be sure to share it here. Come on tech support, you have everything you asked for. Come on with it already!

1 Like

Alright, I’m going to call it quits here. Support is MIA and this isn’t the kind of experience I’m looking for. Before I pull the trigger, @Destroya is there anything else you might glean from the folks over there? You had mentioned escalation but I’m not seeing it.

Hey Frank, I see that we have sent you an email 3 days ago saying that we will be replacing the mainboard and we requested your address information, did you receive this email? Thanks!

1 Like

Oh!!! No I did not! Just searched my email and I don’t have anything at all. Any way to resend? The last communication I received from anyone at support was a week ago.

Ok just searched through everything again and sure enough there is something from support from July 5. Looks like it wound up being trashed. I’m responding to it now. Thank you!

1 Like

Glad to hear that, it’s great that we were able to catch this before you changed your mind I guess :smiley: when the replacement process is over and your issue is resolved please share your feedback here or DM me, this should help us improve our internal processes.

Absolutely! Yes. I’m willing to go through the replacement process. I just hope I don’t regret it. Thanks again, more to come.

1 Like

@Destroya I hate to sound like a broken record here but I am once again waiting. How long is this RMA process going to take? I got approved for a motherboard RMA, sent them my shipping info and the last I got yesterday is this:

Please note that our RMA and Repair teams are currently experiencing high contact volume, and response times have been impacted, resulting in minor delays.

This agonizing man and really rubbing me the wrong way.

It is unfortunate but not unusual or unexpected for the turnaround not to be immediate. If that is unacceptable to you, you may need to consider if the current state of things is a good fit for your needs and expectations. I hope that whatever choice you make works out well for you, Have a good evening.

1 Like

I believe Frank is just seeking something more than the automated messages that keep getting sent out. This has been a bit of a process and his machine was working fine for literally weeks before this happened.

I see both sides of the issue here: the support team is somewhat small and has a lot going on and Frank wants his shiny laptop working again after being pretty happy with it before it decided to GAME OVER on him.

Rightfully so, as he mentioned before, he did not want to get stuck in a position outside his 30-day return window with a product that failed to meet his expectations. It is really why that window exists to make sure a product is a good fit for the consumer.

Some of this is the risk purchasing a new product with a small growing company, other parts of that is a learning opportunity for companies to identify where gaps are in their product support.

Hang in there Frank! Hopefully @Destroya can shed some insight or get a tracking number!

1 Like

I am sympathetic to his situation. That does not change that the current state of affairs for the company is such that responses can take time. One can wish that that were not the case, but it does not change the fact that it is the current state of affairs. Given that, each individual must decide if that will work for him or her. If it will not work, then one should return the product.

1 Like

Yeah guys. I was fully expecting to go through the support routine at some point… Just not 2 weeks after receiving it and not for that long.

1 Like

I agree with you that it could use some optimization. I do expect that that will happen, but I have no idea on the timeline. Note that I am just an end user, with no connection to Framework other than that, so what I have to say next is just, like, my opinion, man. The reliance on email seems to be problematic - it’s easy to miss an email, for one to be caught in spam filters or blocked, and so on. It also provides no means for the end user to check on status - so one turns back to the potentially problematic email route. As you have experienced firsthand, any bumps only delay a process that is already slow (if I understand correctly that is in the process of being addressed, in terms of bringing additional staff online).

Again, I speak only for myself, not for Framework. Hopefully their processes evolve and improve. Their track record from my view has shown that they continue to work to improve, albeit sometimes not at a rate that we as end-users fully understand (for example, firmware updates). I still believe in the company and have been happy with my machines, but if one goes south - fingers crossed that that does not happen - I have another to fall back on temporarily.

I hope that everything gets sorted out for you, and soon. Have a great day.

All points agreed. I just wish that I had gotten the opportunity to experience some longevity before going through this. If @destroya hadn’t have advised via this forum that support had responded to my last enquiry, I would have completely missed it - just as you described. Fortunately it only amounted to a single lost business day and I also have another laptop I can use in the meantime but it is a work asset which I prefer not to use.

Today is the last day of my 30 day return window - I called the number listed on the “contact us” section and the recorded message that greets you immediately is:

“You’ve reached Framework. We don’t have a phone support system but you can get a response quickly by submitting a support request at frame.work/support”

Later today I’ll decide whether or not this will work out for me. Thanks for all your feedback.

We do not actually provide phone support, as mentioned in the message. I understand it may be mandatory to provide a “contact us” number, but that number is not for support.

I see that your ticket is now assigned to the correct person for replacement. You should receive an update soon.

It’s very unfortunate that you experienced this. Most of the time, troubleshooting takes some time, but the part replacement process is straightforward and rather fast. Unfortunately, we had a significantly large backlog when you contacted us, which caused delays. I definitely understand your frustration.

Please keep us updated and share your feedback with us.

Yes and I just figured out it’s not really for anything other than to advise to people that there is no phone support.

I fully understand that the troubleshooting process takes some time but this was really obviously a hardware problem that should not have taken 2 weeks to deliberate on and agree to. Be that as it may, the circumstances are what they are and after mulling it over, I’ve decided to cancel the RMA and request instructions for a return. Had the part replacement process been initiated sooner, I’d have stuck it out but I need a working unit and this experience has soured my interest for the time being. While I don’t have confidence right now that I would have a working unit in a reasonable amount of time, I am thankful that this occurred during the return window and not after.

Thank you for your support @destroya and to the rest who have chimed in here, all of you have been a real help. Hopefully Framework doesn’t decide to hit me with a restocking fee after all this. I’ll continue to provide updates for any who are interested.


I think you will find that the 30 day window is irrelevant here. That is for a ‘no-fault, just don’t want it’ money back return. This thread is about a problem, and if not resolved, even outside the 30 days, the client would be entitled to get their money back under warranty, as they regard the product unfit for purpose.

Not necessarily. “Defective” is one of 3 reasons to choose from for return and the one I selected. The other two being “remorse return” and “repair return.”. The 30 day window allows for the customer to choose vs repair or replacement only occurring at the discretion of going through the process with support. You might even get a replacement unit of equal value / performance if deemed appropriate but that’s not the customers choice.

Unfortunately that’s not been my experience I’m in a very similar boat to @Frank4 having been taken through various unfortunately fruitless troubleshooting steps, only to be left on read for 8 days by support. And this is despite my own community support thread getting picked up by Loell.

Really seems like there is a major bottleneck currently getting support tickets out of troubleshooting and into the RMA.

I see that you are still troubleshooting with the support team. If a part replacement is needed, your case will be assigned to the part replacement team, and the process is relatively easy.

To provide some additional context, we had a backlog of tickets in the general troubleshooting queue, which caused significant response delays a couple of weeks ago. The support team has worked through this backlog, and now responses are sent within reasonable times. The majority of tickets were resolved, while some were escalated internally due to requiring further troubleshooting by specialists. This has created a mini-backlog for the escalation queues, causing the delay you are experiencing.

I see that you submitted your ticket on the first of July and exchanged 12 emails until the second of July, when your case was escalated. The agent should have informed you accordingly to set expectations. I also would have expected a response immediately after such frequent communication with an agent.

While I understand your frustration, I don’t think the initial troubleshooting steps were fruitless. The more tech-savvy we are, the more we tend to skip basic steps and look for complex problems. In reality, the majority of issues can be solved with basic steps. Although that wasn’t true in your case, the agent couldn’t have escalated your case internally without first ensuring the basic troubleshooting steps were not solving your problem.

I hope this provides some context about what we are doing, why we are doing it, and why you haven’t heard from us in a while. The support team is now working on a plan to resolve the mini-backlog in the escalation queues, and you should receive a response very soon. Thank you for letting me know, and thank you for your patience.