Framework Laptop 13 AMD Ryzen™ 7040 Series Driver Bundle v2.06 Release - STABLE

Framework Laptop 13
, ,
1

The Driver Bundle v2.06 Stable for Framework Laptop 13 AMD Ryzen™ 7040 Series is now available. Please use the installer below to update your system.

Driver Bundle

Windows 24H2

Download Link SHA256
Framework_Laptop_13_and_16_AMD_Ryzen_7040_driver_bundle_W11_v2.06_2025_09_08.exe C17156A3B28623A8F46DCB5D67AB3EEA218A512CA4322958C38FBC60E6CF756E

Driver Bundle Components

Driver Version Updated
AMD Chipset Driver 7.02.24.1120 Same
AMD Graphics Driver 24.30.74 Updated
Realtek Audio Driver 6.0.9859 Same
Realtek Audio Console 1.53.374.0 Same
RZ616 WiFi Driver 3.4.0.1268 Same
RZ616 Bluetooth Driver 1.1043.0.543 Same
Goodix Fingerprint Driver 3.12804.1.270 Updated
Realtek MEP Driver 10.2000.10003 Same
AMD MEP Driver 32.1.0.0 Same
Microsoft MEP Driver 1.0.42.0 Same
Framework EC Driver 0.0.0.6 Same
Realtek Ethernet 11013_20_07272023_08042023 Same
SD Card Reader v4_5_10_201 Same
2nd Gen uSD Card Reader v4_5_10_202 Same
Monitor Driver 1.0.0.0 Same
2 Likes
2

Here’s my not-so-good experience with this update:

Persistent, consecutive (not intermittent) blue screens shortly after booting, a few seconds after the WiFi adapter connects to the AP. Doesn’t matter if you log in or not. I was able to avoid the blue screen by disabling my AP so the laptop was unable to connect to WiFi, and then I reverted back to v2.05_2025_07_18. Everything was fine after that.

Here’s relevant information from BlueScreenView; I can provide the .dmp if anyone requires it.

082525-18281-01.dmp 8/25/2025 7:15:22 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000'0000001e 00000000'00000002 00000000'00000001 fffff800'9b1a9401 mtkwl6ex.sys mtkwl6ex.sys+139401 MediaTek 802.11AX Wireless Adapter Driver MediaTek 802.11AX Wireless Adapters MediaTek Inc. 3.3.0.0908 x64 ntoskrnl.exe+4fec10 C:\WINDOWS\Minidump\082525-18281-01.dmp 16 15 26100 1,280,032 8/25/2025 7:15:49 PM

You’d think this has something to do with the wifi driver or the chipset driver, but according to the driver bundle components list above, none of those changed. I do know that when I installed the v2.05 release for the first time on August 14, before that I had the graphics driver/chipset driver from Ryzen’s download page (the one that keeps the graphics and chipset drivers up-to-date), and I began having the same issue starting around August 10, after Ryzen updated the graphics and chipset drivers. After I installed v2.05 and removed the Ryzen updater, that fixed the bluescreens until I installed v2.06 today.

Here’s the relevant information from BlueScreenView for a bluescreen on August 13, running the chipset/graphics drivers that Ryzen installed:

081325-19265-01.dmp 8/13/2025 3:10:50 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000'0000001e 00000000'00000002 00000000'00000001 fffff805'5b7a9401 mtkwl6ex.sys mtkwl6ex.sys+139401 MediaTek 802.11AX Wireless Adapter Driver MediaTek 802.11AX Wireless Adapters MediaTek Inc. 3.3.0.0908 x64 ntoskrnl.exe+4fec10 C:\WINDOWS\Minidump\081325-19265-01.dmp 16 15 26100 1,283,760 8/13/2025 3:11:20 PM

Again, now back on v2.05 and everything seems stable.

I have BIOS 03.16 installed, I just put that on today. Before that I think it was BIOS v3.09.

3

Having this issue as well. When the laptop comes off of sleep I don’t think the wireless adapter wakes up correctly.

I had this problem on v2.05 as well so I’m not sure that changed anything.

4

Thanks for the feedback. Based on your information, this issue occurs when the system detects an AP. Could you please let me know the model of the AP you’re using? When testing with our AP, I couldn’t reproduce the BSOD problem.

5

You’re welcome, hope the information goes to good use. My make/model of AP is TP-Link Archer A20 v3.0. I’m running firmware version 1.0.6 build 20231011 rel.85717(5553)

I think you are on to something because when this blue screen was happening the first time, it would blue screen consistently after booting and letting it connect to the AP. But then I went into the office, and it booted and was able to join the wifi on the work AP. It was still unstable and prone to bluescreens coming back from hibernate, but it didn’t consistently bluescreen on boot and connecting to the AP like it did at home.

Since moving back to the v2.05 driver package, everything is stable and no blue screens even coming back from suspend/hibernate.

6

Hi @Quin_Chou, just wondering if you’ve made any progress with this. I see the v2.06 release is now out of beta? Thanks.

8

We’re experiencing issues with 2.06 as well. We reloaded a Framework 13 AMD 7040 with Windows 11 24H2 and used only 2.06 for the drivers and everything installed properly except for the Bluetooth and WiFi adapter. It is using the stock RZ616 module. We retried the 2.06 driver install a couple of times to make sure with the same result each time. We had to install 2.05 to get the Bluetooth and WiFi to work and then install 2.06 for the updated fingerprint reader and graphics drivers (even though according to the release notes, the Bluetooth and WiFi drivers weren’t updated in 2.06). None of the other drivers had issues installing.

9

We are checking for the issue you feedback and will give the update next week.

10

I unzipped the 2.05 and 2.06 driver packs to run the driver installs manually (using only the fingerprint and graphics driver from 2.06) and found the following list of drivers failing to install:

Processing inf : mtkwl6ex.inf
Failed to install the driver : No more data is available.

Processing inf : mtkbtfilter.inf
Failed to install the driver : No more data is available.

Processing inf : RtExtFW.inf
Failed to install the driver : No more data is available.

Processing inf : AmdMepEnum.inf
Failed to install the driver : No more data is available.

Processing inf : MicrosoftEffectPack.inf
Failed to install the driver : No more data is available.

Processing inf : mep_camera_component.inf
Failed to install the driver : No more data is available.

Processing inf : crosecbus.inf
Failed to install the driver : No more data is available.

The Framework 13 AMD 7040 is running an AMD 7640 and bios 3.16 (latest). Many of the failures seem to be related to the Microsoft Effects Pack which is only intended to install and run on devices with NPU’s that offer 40+ TOPS (Copilot+ PCs developer guide | Microsoft Learn). These AMD 7040 series only support 10 TOPS, so it is unclear why these drivers are included in this driver pack.

The last driver is related to the Framework EC, and that is failing with the same error. As a reminder, these are from the 2.05 driver pack (since they were not updated in the 2.06 driver pack), so this isn’t a new issue. I look forward to hearing from you next week.

11

We have uploaded the package again to fix the WiFi/BT install issue.

1 Like
12

Aren’t there two sets of Microsoft Effects Drivers? One for each of the possible webcams you can have on a Framework 13?

AFAICS Microsoft Effects (blurred background etc.) are working fine on my Framework 13 with 7840U processor and 2nd gen webcam.

13

Hi Quin_Chou,

Did the SHA256 hash get updated on the website for the updated Driver Pack 2.06 file? I tried twice and the hash of the updated 2.06 file doesn’t match what is on the website. I won’t be able to test until we can confirm that the file is the correct one with hash validation. Please let me know.

14

Hi Brian,

The 3 MEP drivers that I listed in my post all failed to install with no additional data available. I did some digging and according to Microsoft their requirements for the Microsoft Effect Pack is for:

Prerequisites

  • Windows 11, version 22H2 or newer (Build 22623.885+).

  • Device must have a supported NPU and the hardware manufacturer must have opted in and installed the Windows Studio Effect driver on the system. (See the Copilot+ PCs supported by NPUs).

We have Windows 11 24H2 installed so that fulfills the first requirement. Since these drivers will not install on the Framework 13 AMD 7040, and the verification checks per Microsoft website indicate that the capability is not enabled. I was hasty in connecting this to having to have a Copilot+ PC, I apologize. That being said, I do not have any answers as to why these drivers do not install. Thoughts?

15

What message are you actually getting? For instance, maybe they’re not installing because they are already installed.

16

Hi Brian,

As posted above, the message doesn’t contain any additional information:

Processing inf : MicrosoftEffectPack.inf
Failed to install the driver : No more data is available.

This was on a fresh install of Windows 11 24H2 and no drivers had yet been installed.

17

Hi @Quin_Chou,

Thanks for this. I will try tomorrow and let you know what I find. I will say, though – please take it or leave it – but my opinion is that as this is now a different driver package, you should bump the number to 2.07 or something higher. Because as you’ve released 2.06 already, now you are going to have two 2.06’s floating around: one with this fix, and one without. I think this will cause unneeded confusion with your customers. Again, just my take.

18

Hi @Quin_Chou,

I just checked again, and the SHA256 hash of the new 2.06 listed in the downloads doesn’t match the actual SHA256 hash of the download. Please let me know.

19

I second this opinion @pundo_florm :slight_smile:.

20

Or at least call it 2.06a to distinguish it.

21

I check the SHA256 again, the file’s SHA256 is same to the SHA256 in forum. Could you show me your SHA256?