Need help with Ryzen AI 7 350 performance?

General
1

I’m looking for help with a Ryzen AI 7 350 issue. After setting up my system, I noticed performance and stability problems during everyday use and light workloads. I’m not sure if this is a driver, BIOS, or compatibility problem, and I need advice on troubleshooting steps and possible fixes.

2

Start with the boring stuff first.

Update BIOS from your board vendor, not from Windows tools. Early AGESA on new Ryzen mobile parts is often messy. If your BIOS is old, stability goes bad fast, even on light loads.

Then do a clean driver pass.

  1. AMD chipset driver from AMD.
  2. iGPU driver from AMD or your laptop/vendor page if it is a prebuilt.
  3. Remove old display drivers with DDU if you already swapped versions a few times.
  4. Update Windows fully, including optional driver fixes once.

Check memory next. A lot of random stutter and app hangs come from RAM settings.

  1. If EXPO is on, turn it off and test stock.
  2. Run MemTest86 or Karhu overnight.
  3. If you use mixed RAM kits, stop. That causes dumb issues all the time.

Watch temps and clocks with HWiNFO. On light workloads, if the chip spikes to high temp, then drops clocks hard, you might have a bad power plan, bad paste job, or vendor firmware issue. Idle temp bouncing is normal. Constant 90C on browser stuff is not.

Also disable this stuff for testing.

  1. Core isolation, memory integrity.
  2. Third party RGB and motherboard apps.
  3. Any auto OC or PBO preset.

If you want useful data, post BIOS version, RAM kit, SSD model, Windows build, and what ‘stability problems’ means. Reboots, WHEA errors, freezes, driver timeout, all point to diff stuff. Ryzen issues are often fixable, but the exact symtoms matter a lot.

3

I’d split it into two buckets: software jank vs hardware/power behavior.

@sonhadordobosque already covered the usual BIOS/driver/memory side, so I’d look at the stuff people skip:

  • Event Viewer and Reliability Monitor. If you’re getting LiveKernelEvent, WHEA-Logger, display resets, or appcrash patterns, that narrows it down fast.
  • SSD firmware + storage driver. A weirdly unstable “CPU” system is sometimes just the NVMe hitching or timing out.
  • Power profile from the laptop vendor. I actually kinda disagree with the “just use AMD drivers” advice if this is a laptop. OEM-tuned graphics/power packages can matter more than the newest generic one.
  • Hardware acceleration. Test with it off in browser, Discord, Steam, etc. Light workload stutter is often GPU/video decode weirdness.
  • USB/peripheral nonsense. Hubs, docks, RGB junk, even bad wireless dongles can cause random freezes. Strip it down and test bare minimum.

Also check if virtualization is enabled in BIOS/Windows. Sometimes VBS/Hyper-V tanks responsiveness more than people expect.

If this is happening at stock settings with a clean Windows install, that’s when I’d start suspecting immature firmware or a dud unit tbh. Post exact laptop/model, error logs, and whether it happens on battery, plugged in, or both.

4

I’d add one angle that @sonhadordobosque only brushed past: thermals and scheduler behavior.

Ryzen AI chips can feel “unstable” when they’re actually bouncing clocks too aggressively. Check:

  • HWiNFO for CPU temp, skin temp, PPT/TDC/EDC limits
  • whether the laptop is silently capping wattage on USB-C charging
  • core parking and Windows 11 scheduler weirdness after sleep/hibernate

A quick test is this:

  1. Disable Fast Startup
  2. Turn off modern standby if your OEM allows it
  3. Set minimum processor state to 5 percent, not 100
  4. Test in a local admin account with all startup apps disabled

I also would not immediately blame RAM compatibility unless you upgraded it yourself. A lot of these newer systems ship with shaky OEM firmware long before the memory is actually the issue.

Pros for the ‘’: can improve readability if you’re organizing your troubleshooting notes or benchmark results.
Cons for the ‘’: not really relevant unless you’re documenting the issue for others.

If responsiveness is worse after waking from sleep, that points more to BIOS/ACPI than raw driver problems. If it happens only under browser/video use, test different browsers, because some builds handle AMD decode paths better than others.