Requesting your help to test the AMD Public Graphics Driver on Framework Laptop 16

We are planning to implement the AMD public graphics driver across all AMD products. We have a long-standing relationship with AMD and ask for your help in testing the driver to ensure there are no critical issues before we begin using it. Please feel free to send us any feedback. We will work with AMD to address it.

We will prepare a driver bundle with the latest version in the coming weeks. Until then, you can download the driver directly from the AMD website. This driver is compatible with the Framework Laptop 16 Ryzen 7040 series.

Download Link:
https://www.amd.com/en/support/downloads/drivers.html/processors/ryzen-pro/ryzen-ai-max-pro-300-series/amd-ryzen-ai-max-plus-pro-395.html

7 Likes

I have some small glitches with the latest 25.8.1 in windows 11 (latest update), FW 16 7940HS with out dGPU:

  1. it looks like driver restart it takes 1-2 seconds. screen freeze , go blacks and then everything is OK. it didn’t happen with adrenalin 25.6.1 (driver install only)
  2. I saw strange artefact on lock screen. I’m not sure if it is Windows or AMD Driver issue, but I have seen part of the Excel formula field on the lock screen, when computer woke up from hibernate. Execel was opened but it was minimized when I hibernated my FW16

part of the lock screen

relevant part of the Excel which was minimized. location on the screen does not match

GPU and chipset version

The current amd drivers seems to cause a kernel panic.

For context, I heavily use Maya and 24.30.74 works well enough but updating to 25.8.1 and running Maya or even a web browser causes a black screen (possibly a kernel panic).

Some debug info I’ve gonna (Windows 11)

SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a system service routine.

Arguments:

Arg1: 00000000c0000005, Exception code that caused the BugCheck

Arg2: fffff800431cdb86, Address of the instruction which caused the BugCheck

Arg3: ffff8282ea8fd640, Address of the context record for the exception that caused the BugCheck

Arg4: 0000000000000000, zero.

Debugging Details:

------------------

*** WARNING: Unable to verify timestamp for amdkmdag.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec

Value: 1312

Key : Analysis.Elapsed.mSec

Value: 4551

Key : Analysis.IO.Other.Mb

Value: 0

Key : Analysis.IO.Read.Mb

Value: 1

Key : Analysis.IO.Write.Mb

Value: 0

Key : Analysis.Init.CPU.mSec

Value: 1140

Key : Analysis.Init.Elapsed.mSec

Value: 16553

Key : Analysis.Memory.CommitPeak.Mb

Value: 109

Key : Analysis.Version.DbgEng

Value: 10.0.27871.1001

Key : Analysis.Version.Description

Value: 10.2505.01.02 amd64fre

Key : Analysis.Version.Ext

Value: 1.2505.1.2

Key : Bugcheck.Code.LegacyAPI

Value: 0x3b

Key : Bugcheck.Code.TargetModel

Value: 0x3b

Key : Dump.Attributes.AsUlong

Value: 0x21808

Key : Dump.Attributes.DiagDataWrittenToHeader

Value: 1

Key : Dump.Attributes.ErrorCode

Value: 0x0

Key : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

Key : Dump.Attributes.LastLine

Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage

Value: 0

Key : Failure.Bucket

Value: AV_amdkmdag!unknown_function

Key : Failure.Exception.IP.Address

Value: 0xfffff800431cdb86

Key : Failure.Exception.IP.Module

Value: amdkmdag

Key : Failure.Exception.IP.Offset

Value: 0x6db86

Key : Failure.Hash

Value: {c753a2f9-94a6-448f-1d0e-e079b3442215}

Key : Hypervisor.Enlightenments.ValueHex

Value: 0x7497cf94

Key : Hypervisor.Flags.AnyHypervisorPresent

Value: 1

Key : Hypervisor.Flags.ApicEnlightened

Value: 1

Key : Hypervisor.Flags.ApicVirtualizationAvailable

Value: 0

Key : Hypervisor.Flags.AsyncMemoryHint

Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested

Value: 0

Key : Hypervisor.Flags.CpuManager

Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi

Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled

Value: 1

Key : Hypervisor.Flags.Epf

Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks

Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable

Value: 1

Key : Hypervisor.Flags.MaxBankNumber

Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl

Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush

Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing

Value: 1

Key : Hypervisor.Flags.Phase0InitDone

Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos

Value: 0

Key : Hypervisor.Flags.RootScheduler

Value: 0

Key : Hypervisor.Flags.SynicAvailable

Value: 1

Key : Hypervisor.Flags.UseQpcBias

Value: 0

Key : Hypervisor.Flags.Value

Value: 38408431

Key : Hypervisor.Flags.ValueHex

Value: 0x24a10ef

Key : Hypervisor.Flags.VpAssistPage

Value: 1

Key : Hypervisor.Flags.VsmAvailable

Value: 1

Key : Hypervisor.RootFlags.AccessStats

Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened

Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor

Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading

Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync

Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled

Value: 0

Key : Hypervisor.RootFlags.IsHyperV

Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened

Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt

Value: 1

Key : Hypervisor.RootFlags.MceEnlightened

Value: 1

Key : Hypervisor.RootFlags.Nested

Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor

Value: 1

Key : Hypervisor.RootFlags.Value

Value: 1015

Key : Hypervisor.RootFlags.ValueHex

Value: 0x3f7

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff800431cdb86

BUGCHECK_P3: ffff8282ea8fd640

BUGCHECK_P4: 0

FILE_IN_CAB: 082825-15984-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x21808

Kernel Generated Triage Dump

FAULTING_THREAD: ffffe58f632990c0

CONTEXT: ffff8282ea8fd640 – (.cxr 0xffff8282ea8fd640)

rax=0000000000021c04 rbx=ffffe58f68be8020 rcx=fffff800442ee360

rdx=0000000000000000 rsi=0000000000000000 rdi=ffff88032ea1a910

rip=fffff800431cdb86 rsp=ffff8282ea8fe090 rbp=ffffe58f4e2670a0

r8=00000000000084e2 r9=fffff8004430f613 r10=0000000000009e7d

r11=0000000000000010 r12=ffffe58f68a0e601 r13=ffffe58f54a779b0

r14=0000000000000000 r15=ffff88032ea1acd0

iopl=0 nv up ei pl zr na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246

amdkmdag+0x6db86:

fffff800`431cdb86 418906 mov dword ptr [r14],eax ds:002b:00000000`00000000=???

Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

STACK_TEXT:

ffff8282`ea8fe090 ffffe58f`68be8020 : 00000000`00021c05 ffffe58f`4e2670a0 ffff8282`00021c04 ffffe58f`54a77901 : amdkmdag+0x6db86

ffff8282`ea8fe098 00000000`00021c05 : ffffe58f`4e2670a0 ffff8282`00021c04 ffffe58f`54a77901 00000000`c0000000 : 0xffffe58f`68be8020

ffff8282`ea8fe0a0 ffffe58f`4e2670a0 : ffff8282`00021c04 ffffe58f`54a77901 00000000`c0000000 ffff8282`ea8fe338 : 0x21c05

ffff8282`ea8fe0a8 ffff8282`00021c04 : ffffe58f`54a77901 00000000`c0000000 ffff8282`ea8fe338 00000000`00000000 : 0xffffe58f`4e2670a0

ffff8282`ea8fe0b0 ffffe58f`54a77901 : 00000000`c0000000 ffff8282`ea8fe338 00000000`00000000 ffffe58f`68870100 : 0xffff8282`00021c04

ffff8282`ea8fe0b8 00000000`c0000000 : ffff8282`ea8fe338 00000000`00000000 ffffe58f`68870100 fffff800`432ebfb7 : 0xffffe58f`54a77901

ffff8282`ea8fe0c0 ffff8282`ea8fe338 : 00000000`00000000 ffffe58f`68870100 fffff800`432ebfb7 ffffe58f`4e2670a0 : 0xc0000000

ffff8282`ea8fe0c8 00000000`00000000 : ffffe58f`68870100 fffff800`432ebfb7 ffffe58f`4e2670a0 ffff8282`ea8fe470 : 0xffff8282`ea8fe338

SYMBOL_NAME: amdkmdag+6db86

MODULE_NAME: amdkmdag

IMAGE_NAME: amdkmdag.sys

STACK_COMMAND: .cxr 0xffff8282ea8fd640 ; kb

BUCKET_ID_FUNC_OFFSET: 6db86

FAILURE_BUCKET_ID: AV_amdkmdag!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c753a2f9-94a6-448f-1d0e-e079b3442215}

When you install the driver, do you check the checkbox of factory default? It does the clean install if you check the checkbox of factory default.

Do you have dGPU on the system?

Yes, i do. The dgpu was running when i get this crash

I’ve been having this issue for a while now, and I haven’t seen any posts about it yet. For some reason, after a while, when I play any moderately graphically demanding game, the system will just shut down and then reboot. When the system boots back up, I get a pop-up from AMD Adrenalin saying there was an error and to send a crash report. I’ve sent them many times, but it’s been several driver updates since it started, and nothing is working to fix it. I know it’s not thermals because when I run a stress test, the hotspot only ever reaches 76C. The only solution I’ve found to fix the issue is rolling back the drivers to a much older version by installing the Framework Driver Bundle. The games I mainly play are Minecraft with mods and Liftoff drone simulator. I never had issues before with using the latest graphics drivers, but I feel like this issue is just something AMD will have to fix.

here are my laptop’s specs too.
CPU: Ryzen 7 7840HS
GPU: Radeon 7700S
RAM: 32GB Crucial 5600 MT/s
Storage: 1TB NVMe
OS: Windows 11 Pro (latest version)

I don’t have a problem if I have to use the graphics driver version that comes with the driver bundle, but it’d be nice if I could use the latest drivers.

I did find this Windows minidump, but I’m not sure how much it helps.

Thanks for feedback! We are checking this with AMD. Do you still have this dump file that can share to us?

Yes, I still have it. How would you like me to share it, since I can’t directly upload it to my reply. Google drive also doesn’t work. I tried uploading it but it says it’s not a supported file type.

Zip it up, then upload :slight_smile:

Been having constant hard freezes forcing me to hold the power button to recover, this happens very soon after starting Sea of Thieves and usually takes only a few minutes. I’m downgrading the drivers back to the 2.06 bundle because this is even less stable than before

I just tried it and it didn’t work :confused:

I’m also getting a BSOD similar to @zachary_stout (amdkmdag+6db86), I can reliably reproduce it by playing a game like SOT that starts up the dedicated GPU, then closing the lid. It will either immediately BSOD, or BSOD when I open the lid. This only happens with the updated drivers, not the version included in the 2.06 driver bundle.

Note: The crash can happen without closing the lid or attempting sleep mode, the above is just an easy way to reproduce it

1 Like

Hi,

I am getting the same issues with a similar system to the above (R9 and Kingston RAM)

Freezes when playing some games.

1 Like

how about zip it with password?

Running 3.07 with 25.9.2 driver only no issues. The only time I’ve had issues with the public drivers seemed to be when I tried to use the Radeon adrenaline software.

I have to walk this back somewhat. I’ve found recently that in some titles, in this case avatar frontier of Pandora, on the public driver release my GPU will not activate at all, leaving the Apu to shoulder the full load. Returning to the proprietary drivers fixes this issue, but no other fixes(such as altering power profiles, installing adrenaline or changing Windows display settings) provided any relief.

For my FW16, after updating to BIOS 3.0.7 and utilizing AMD public graphics drivers for RX 7700S (25.9.1), I’ve noticed that the battery drain issue while plugged in has returned after BIOS 3.0.6 fixed it for me. Playing Battlefield 6 led to a drain of approximately 30% per hour playing for 2 hours even when the power profile is set to “Balanced”. I am unsure as to whether this was due to the BIOS update or an issue of incompatibility with the drivers.