Didn’t notice any charger compatability issues, except sometimes plugging it into my Samsung charger would cause the light to blink for a few seconds before it connected. Will try the firmware.
EDIT: Should add that my chargers I use now are usually fast chargers at least
And yes, it would’ve been nice for Framework to have someone pop into the thread and say “Hey guys, we’ve released a beta BIOS to try and fix this issue you’ve all had for four months without acknowledgment or communication”
Most of my chargers I use on the laptop are 65w+, I think the flaky charging/USB-C PD experience mainly affected chargers with less than 60w power output but I could be wrong.
So far so good here
This was answered way back when the delay happened
I’ve installed that version yesterday, and didn’t had a freeze… But… It’s still too early to tell if the freezes have been resolved.
First sign looks good!
Not really. FW rely on a third party for BIOS changes, but not for EC updates. Here you can see where the EC fix was committed:
And here you can see where Nirav explains the BIOS update process:
So I can understand that a blocking issue in the BIOS itself “when the beta release arrived” can delay things, but not fixes to the EC firmware.
this is just my guess, but reading between the lines, I assume that since Framework usually update the BIOS and EC together, they were planning to do so here too, but unfortunately the BIOS update introduced regressions. After they got the timeline for the next BIOS update, they determined it was too long to have people wait for the EC changes, and made their own 3.03b (or had to ask Insyde to make this installer) which took a little more time, but allowed them to split the update in order to get the EC changes out faster, even if it meant not having them be a part of the BIOS update. This is all just a guess though, and I don’t have any insider knowledge on this sort of thing.
Has anyone seen their battery die faster than before the update? It could just be me, since I’m beta testing Arc browser and it isn’t fully optimized, but my battery doesn’t last much longer than 4 hours now.
It’s early days yet, but for me battery life seems the same. Light web browsing and Slack etc has cost me 10% battery in about 90 mins (in the “Best power efficiency” power profile).
Can’t say I’ve noticed any battery degradation but then my laptop hasn’t been charged to full since a good couple days ago.
can’t say i’ve noticed my battery draining faster than usual, though tbh the battery has never been a strong point of this laptop, imo
also yeah i have the Arc Browser beta too and for the time i used it, it seemed to eat even more battery than Firefox, so that might be the issue.
i was actually about to say this too, my theory is that framework initially wanted to update the BIOS and EC together, saw that it was going to take a while to update the BIOS due to aforementioned regression, decided to release the EC update first as a stop gap while waiting on a fix for the regressions in the new BIOS
Hey guys, sorry to bombard this post, but I wanted to ask if anyone else had faced this issue after the new BIOS update.
So it seems that the new BIOS update did indeed fix the BSOD issue, in that the computer will no longer BSOD when it freezes up.
However, just now I saw some weird new behavior, rather than blue screening like previously, the display driver, amduw23g, will instead repeatedly stop responding, then recover multiple times in a row. At the time I was simply just using Firefox when this happened. The constant freezing did not resolve itself until I forced the computer to turn off by holding down the power button. The AMD software would also repeatedly report a driver timeout according when this happened.
This is the event log after I rebooted, all of the “Warning” events are related to the AMD display driver aforementioned above.
Interesting, I am suspecting it may be due to the fact that I’m on the absolute latest AMD Adrenalin drivers, are you using the Framework drivers?
I’ll have to check my event log because it’s not something I’ve noticed during usage normally. If the driver has crashed and restarted, it’s been doing it very quietly. I am using the Framework supplied drivers, after going between the Framework, latest and then DDU’ing back to the Framework ones
I’m proceeding with caution that the BSOD has been fixed. I’ll consider it fixed if I make it a month of using it without one occurring given how unpredictable they’ve been.
As for the battery life, I did drain 15% from usage in Firefox over a few hours, but I’m not sure what the average battery expectancy is. I come from a laptop that had a battery shot so to bits the i7 3667U it uses would have it dead in 30 minutes from full charge (granted it was a refurb but still…) so just getting a few hours is an improvement to me.
Yeah i’ll just say that if you run into this issue (and hopefully you don’t), you will definitely notice it because the computer will lock up and unfreeze every 15-30 seconds until any apps with hardware acceleration are closed. Reopen them and the freezes will continue.
Also okay, it seems in that case what I will do is DDU the current graphics drivers in safe mode and revert back to the Framework drivers, see if that stabilizes my display driver a bit.
And yeah, Firefox might have better battery life than Arc on Windows rn, but it is still imo one of the worst browers to use if you prioritize battery life, it drains the battery on both my Framework and MacBook, even taking into account the different operating systems and CPU architecture. I’ve found that Microsoft Edge delivers the best battery life on the Framework, but I also do not like Edge and it’s bloated amount of features I never use, so there’s that lol.
In my experience, while the AMD Ryzen 7 7840u 13 battery life is not the best, it is still far and away better than the i7-1165G7, even before i upgraded my battery to the 61 wh one.
I have honestly lost track at this point. If I recall correctly, about 2 weeks ago I freshly installed the Framework drivers then installed the AMD drivers on top of that.
Just wanted to chime in that I’ve also had a few of these DPC_WATCHDOG blue screens on a month old DIY Ryzen 7640u version (didn’t upgrade up from anything, everything is new and all of the components are from framework except for my SSD). Had this happen on Windows 10 and now Windows 11 (thinking me using an unsupported W10 was the culprit 
). I’ve only installed the drivers from framework too.
Skimming this thread some it looks like an upcoming BIOS update might fix it? Anything I can do to help the debug process here?
A beta version of that bios is out that supposedly fixes the issue. We’re kinda community testing at this point to see if that’s the case.
Process for that is just seeing if no more BSODs like this occur, and that no new bugs surface from this (given its a beta).
