r/FlowZ13

▲ 13 r/FlowZ13

Make Asus acknowledge its own faulty BIOS

I made the mistake of updating the bios of my Asus ROG Flow Z13 from 311 to 314. Now, performance has severely degraded; FPS in any game is approx. 30% lower. I have discovered on reddit similar posts about this, but only from 4-5 people. So it is either a limited issue, happening to some devices, or people have just not noticed this yet. I mean, if you play a game having 90 FPS and with the new bios it goes to 60FPS, you might not notice it. My issue is that it is impossible to downgrade bios, and whenever I write to Asus, they just tell me to send the device to service. I cannot do this since I work on it.

My question to all of you is how do I make Asus acknowledge that they released a faulty bios and convince them to work on a fix? Right now, no one is taking this seriously and it is really frustrating.

reddit.com
u/FunAd7198 — 4 days ago
▲ 24 r/FlowZ13

Bloodborne "Windows port" is simply incredible 😍

Tested on my Z13 Flow AI 395 Max All Settings High FSR4 quality Native resolution Profile Performance Important:

u/darkfoxy38 — 4 days ago

Using the z13 as a monitor for Xbox/ps5

Is this possible. I'm planning on getting a console to play certain exclusives, could I use my z13 as monitor?

reddit.com
u/LOOMOOA40 — 4 days ago
▲ 0 r/FlowZ13+1 crossposts

Anyone know how to bypass the 395 ai max z13’s overclocking limits?

Flow z13 with the ai max 395.

If I try to use smokeless umaf to overclock the ram or cpu+gpu boost clock, I get a message to either abandon discard the overclock with no way to dismiss it.

Did anyone have any luck with this?

u/1010_lol — 4 days ago
▲ 43 r/FlowZ13

Case guy here, its the 9th and the store is live!

https://www.etsy.com/shop/NaviProfessorsStore

Hello! Case guy here again

its the 9th, and like i said, the store is live with MUCH more stock this time!

17 blue penless cases (15 V1.1, 2 1.0)

5 white penless cases (all V1.1)

And about 10 cases total of Bstock

V1.1 Cases are $40

V1.0 cases are $35

ALL bstock is $28.

Need one with a pen? let me know!

u/Navi_Professor — 6 days ago
▲ 86 r/FlowZ13

CachyOS + Gamescope on the ROG Flow Z13. You were all correct. I'm sold! 🔥

Well to all the people that have been praising to use CachyOS on this sub... CHEERS to you!

I pulled the trigger on the Rog Flow and decided to upgrade the hard drive and just go straight into CachyOS.... and man i am blown away by the experience. Better FPS, Better Productivity, Better Battery... with slightly more headache on configuration but nothing AI cant solve lol. ( Funny enough i have 10 years in Ubuntu... AWS Linux and more... and man cachyos has a learning curve )

The desktop experience is fantastic, and switching into Steam Gaming Mode makes this feel like the best of both worlds.

I have a bazzite home theater gaming console and i wanted the best of both worlds so this is
- CachyOS Desktop
- GameScope hot swap with power profiles

I wanted the quick boot into gaming experience of handheld mode but with the power of a desktop for vscoding and LLM sudios.

I ended up taking things a little further and building three custom KDE Plasma widgets specifically for the Flow Z13

🎮 Gaming HUD — Steam Gaming Mode launcher, controller connections and battery levels, recently played games, and power-profile selection.

⚡ Control HUD — Custom TDP profiles, undervolting, and keyboard/lightbar RGB controls through z13ctl.

📊 System HUD — Live CPU/GPU, temperatures, fan speeds, battery, memory, and power telemetry.

I'm loving everything about this! Anyway huge thanks to this community!

P.S - I decided to open-source the whole project so other Flow Z13 owners can use it too. There are prebuilt downloads for each widget or a complete bundle with a simple installer.

It might require some tweaking if you dont use a default cachyOS setup and a default gamescope setup ( default directories etc )

If required i will add more settings and configurations for random use cases

GitHub: https://github.com/kyrios-code/rog-flow-kde-widgets

P.S.S. - The widgets wouldn't be possible without the AMAZING z13ctl app. Big props to that application

u/kyriosyuudai — 6 days ago

Anyone running local LLMs on Flow 13 64gb?

Hi Everyone!

I'm considering the flow 13 64gb (they don't sell the 128gb where I live, or anywhere near for that matter). I'd be interested in running local text and image models, particularly Qwen 3.8 27b. I know Qwen 3.8 Flash won't run on 64gb, unfortunately.

Do any of you have this config, and how fast does it run? Is it usable? (>20tks/s)

reddit.com
u/ziogio998 — 5 days ago
▲ 39 r/FlowZ13

Custom Case Mod: 180-deg Flip Mount for 2025 Z13 using salvaged Dexnor metal plates in progress. so far.....

any suggestions?

my custom case mod project for the 2025 ROG Flow Z13 (Ryzen AI Max+ 395). I’m adapting it to work natively with a magnetic keyboard case stand, but the stock kickstand geometry makes standard mounting a pain.

To solve the airflow restrictions and clear the ports, I flipped the Z13 180 degrees (upside down, camera facing down). It keeps the top thermal exhaust completely unblocked by the stand, and the OEM keyboard can still fold over cleanly for transport.

For my initial test, I used thin Gorilla double-sided tape to attach the actual steel backing plate and rubber trim that I salvaged directly out of a Dexnor case (tore down the original backing and sanded it flush). It holds perfectly, but tape isn't a permanent solution.

Next step: I'm designing a 3D-printed snap-on clip sleeve on my Flashforge printer to slide over the stock Z13 kickstand panel. It will feature an internal recess pocket to trap the salvaged Dexnor steel plate completely inside a thin 0.4mm layer of plastic, creating a completely flush, clean mechanical interface without any messy glues or tape.

Has anyone designed custom structural slip-sleeves or tension clips for the Z13 kickstand? Would love to hear your thoughts on tolerances or wall thickness to keep the hinge tension smooth.

I have another photo of the backplate that I will be duplicating but I need to adjust the height so the kickstand can be used without the need to remove the plate.

u/Home_theater_dad — 6 days ago

Case and charging cable or smaller charger

What's everyone's recommended case? Can you buy a cable(not type c on both sides but with the proprietary cable end) that can be used with a 140w powerbank id like to be able to charge it through the charge port on the go or is there a smaller charger that anyone can recommend?

reddit.com
u/xtianmic — 6 days ago

Anyone struggling to play dota 2 with the flow z13?

Every other game runs smoothly, even newer unoptimized games like COE33, farcry 6, hitman WOA, spiderman 2, but surprisingly my 395+ 32gb model struggles with dota? 60fps on 2k external monitor during team fights and 100fps tops when farming peacefully. Any idea on how i could solve this?

My setup: -Turbo mode 85W -External 1440P monitor (set to display external monitor only) -150W slim-Q charger -Best looking settings -G-Helper only, 16GB vram

I also noticed memory utilization of around 97%? I only have steam discord and dota 2 open so i dont know whats taking up so much ram.

reddit.com
u/branded_steelpan — 5 days ago

RGB window on the back

Hi All
Loving my new z13, however I can’t seem to get pure white light from the RGB lighting on the back. There is a really strong purple hue to the light, in the picture it is set to R255 G255 B255 and you can see how purple it looks. Could anyone confirm if this is normal? I am using G-helper over armoury crate so could look at swapping to fix it if it is unique to my device.

u/nad302 — 6 days ago
▲ 151 r/FlowZ13+7 crossposts

LlamaStash 0.0.2 — a zero-overhead terminal launcher for llama.cpp (TUI + CLI + OpenAI-compatible proxy, Linux/macOS/Windows)

I built LlamaStash to scratch a personal itch: I run local models through llama.cpp on AMD Strix Halo and got tired of writing the same llama-server wrapper script for the tenth time.

Ollama and LM Studio both wrap llama.cpp but hide too much (and cost real performance). Raw llama-server is fast but tedious. LlamaStash is the middle ground.

What it does:

  • llamastash init — first-run wizard. Detects your hardware (CUDA / ROCm-HIP / Metal / Vulkan / CPU), installs llama-server, scans your existing HuggingFace / Ollama / LM Studio model caches, recommends a GGUF that fits your VRAM, downloads it, writes a tuned config, smoke-launches it.
  • TUI + CLI + daemon + OpenAI-compatible proxy in one Rust binary. The proxy at 127.0.0.1:11435/v1 lets OpenCode, Cline, the OpenAI SDKs, and llm-cli work as-is. There's also an opt-in --ollama-compat mode that takes port 11434 and answers the byte-exact "Ollama is running" handshake.
  • Multi-model concurrency with per-model port allocation, /health-probed state machine, intelligent context auto-fit (sidesteps llama.cpp's --fit collapse on Linux iGPUs).
  • Agent-friendly CLI: every TUI capability has a CLI subcommand, --json is a stable agent contract, documented exit codes per failure class.
  • In-TUI HuggingFace browser with search, sort, paginate, per-file hardware fit, download with cancel.

On performance — this is the part that matters for this sub.

LlamaStash spawns the unmodified upstream llama-server. So the wrapper should add zero overhead. I measured it. Across AMD APU (Ryzen AI Max+ 395), Apple Silicon, and NVIDIA, on four model sizes (small E2B Q4, mid 31B Q4, large 27B Q8, large MoE 35B-A3B Q8), every cell matches raw llama-server within ≤1%.

Cross-tool numbers on AMD APU (decode tok/s / TTFT ms on chat_turn):

Tool small mid large_dense large_moe
LlamaStash 86.9 / 51 9.8 / 467 7.4 / 417 42.6 / 181
raw llama-server 86.0 / 51 9.9 / 468 7.4 / 414 42.7 / 186
LM Studio 2.16.0 91.1 / 187 11.6 / 1477 7.9 / 1274 37.0 / 683
Ollama 0.24.0 50.4 / 223 4.8 / 1092 2.6 / 1745 12.1 / 476

LM Studio wins decode on small/mid/large_dense (their Vulkan path is well-tuned on gfx1151) but loses on the MoE and pays a 1-1.5s TTFT tax from its OpenAI shim. Ollama is consistently slower, and its RAG prefill is catastrophic (cold prefill every rep — 4 min on a 31B). Mac and NVIDIA tables are in the benchmarks page.

Methodology, variance gates, fairness rules, and per-cell JSONs are all checked in. The harness is reproducible: make bench-end-to-end. Tear it apart.

What it's not:

  • Not an Ollama fork or replacement (though --ollama-compat exists for tools that auto-detect Ollama).
  • Not a model hub.
  • Not a llama.cpp fork. Same upstream binary.
  • Not a hosted service. Loopback-only in 0.0.2. LAN + auth + TLS are on the roadmap.

Install:

curl -fsSL https://llamastash.dev/install.sh | sh   # macOS + Linux one-shot
irm https://llamastash.dev/install.ps1 | iex        # Windows 11 (PowerShell, no admin)
scoop bucket add llamastash https://github.com/llamastash/scoop-llamastash && scoop install llamastash
brew install llamastash/llamastash/llamastash       # Homebrew (macOS + Linuxbrew)
yay -S llamastash                                   # Arch Linux (AUR — source build)
yay -S llamastash-bin                               # Arch Linux (AUR — prebuilt binary)
yay -S llamastash-git                               # Arch Linux (AUR — main checkout)
cargo install llamastash                            # any Rust toolchain

Then llamastash init and you're up.

Platform: Linux (x86_64, aarch64), macOS (Intel, Apple Silicon), Windows 11 (x86_64). aarch64-pc-windows-msvc and Windows AMD GPU detection on the roadmap.

Honest tradeoffs: Single-author project. Bug reports especially welcome on hardware I don't own. The OpenAI-compat surface covers chat/completions, embeddings, rerank; Anthropic /v1/messages shim is coming.

Repo: https://github.com/llamastash/llamastash

Blog post with the full story: https://deepu.tech/introducing-llamastash

Benchmark methodology: https://deepu.tech/benchmarking-llamastash

Happy to answer questions in the thread.

u/deepu105 — 11 days ago
▲ 26 r/FlowZ13+1 crossposts

Tested Control Resonant on Z13, PX13, Lenovo Yoga 7i (Intel + 5060), and a desktop

I went down the nerd rabbit hole today. I really wanted to know how much faster the laptops I'm considering are for real world gaming. I ran the Lenovo Pro 7i Aura, the Asus Proart PX13, and the ROG Flow Z13 on Control Resonant. It's not a perfect test as I didn't try to run the exact same scenes, but it was all within the same level.

I was very surprised at the results. PX13 and Z13 both beat out the beefier GPU on the Lenovo. Claude thinks it's because the wimpy charger on the Lenovo just can't push enough power into the 5060 to make it worth it. The Lenovo does have a creator mode where the computer drains faster than the charger can keep up, but I think that's kind of cheating.

I was also surprised at how well the PX13 kept up with the Z123, given it's got a much thinner profile and less sophisticated cooling. I didn't even run it in "tent" mode. The fan was facing down on my desk.

I think the so what of all this is that PX13 and Z13 both do an amazing job of running games. The question is whether you want OLED at 60 hz (PX13) or IPS at >120hz (Z13). I still don't know the answer for me.

u/madderbear — 9 days ago
▲ 11 r/FlowZ13

Z13 in 2026 worth it ?

I’m having to down size my gaming pc so been looking at the z13 .
The model I can get in my budget is the 32gb model with the 8060s.
I’m also disabled so touch screen is a plus for input for basic windows use .

I do travel a lot upto 14 hours on a ferry (7 hours there 7 hours back)

How ever when at home I would like to put the z13 Ona stand and hook up my rtx 5060ti but use the z13 screen , I understand I’ll loose some performance using the internal screen.

My question is do you think this is for me , or should I look at something else ?

reddit.com
u/wobzomby86 — 12 days ago
▲ 57 r/FlowZ13+1 crossposts

ROG Flow Z13 2025 128GB - Qwen3.8 Flash-Next benchmarks with Halogen, Gufo and Rulith (60W vs 93W, up to 200K context)

Been playing around with the Strix Halo LLM projects that have been popping up lately, so I spent a few hours seeing how far I could push Qwen3.8 Flash-Next on my 128GB 2025 Flow Z13.

Tested Halogen, Gufo and Rulith at both 60W and 93W.

60W is what I actually consider usable day to day on the Z13. 93W is more of a "let's see what it can do" setting.

One thing before the numbers: this is not a strict apples-to-apples backend comparison. The model formats and MTP setups are different between them. I'm mostly comparing the setups I'd realistically use with each project right now, not trying to prove backend X is universally faster than backend Y.

https://preview.redd.it/s5mh8ryr24th1.png?width=1536&format=png&auto=webp&s=baf5a0cae8c53b9e6e64c4bd84b8a28f591fb8ae

Test setup

  • ROG Flow Z13 2025 — Ryzen AI MAX+ 395, 128GB
  • CachyOS KDE — kernel 7.2.8-2-cachyos, UMA 512MB, GTT 124GB, IOMMU off
  • Halogen 0.16.0 — Qwen3.8 Flash-Next v2 checkpoint, MTP depth 2
  • Gufo 0.5.0 — Qwen3.8 Flash-Next UD-Q4_K_XL, MTP Q8_0 draft 7, 262K context / 1 session
  • Windows 11 25H2 + Rulith 0.4.1 — 32GB RAM / 96GB VRAM, UD-IQ4_XS, MTP draft 3, 262K context

Halogen

Halogen was easily the fastest one for prompt processing/prefill in my testing.

93W

https://preview.redd.it/yhzarjny24th1.png?width=775&format=png&auto=webp&s=233f6e7c5c50fa9cd237dd915f3ec3f8e56eaa77

At 64K I got about 1722 tok/s PP.

At 200K it was still doing 1694 tok/s PP and 41.16 tok/s decode.

What surprised me more than the peak number was how little PP dropped with context size. Going from 64K to 200K was basically:

1722 -> 1694 tok/s

So for long context, this setup held up really well.

60W

https://preview.redd.it/47171lm134th1.png?width=771&format=png&auto=webp&s=2a2a201515dd1d94a42ada430b84e1f83121ead4

At 60W I got about 1573 PP / 45 tok/s decode at 64K, and 1509 PP / 35.4 tok/s at 200K.

This is probably the setting I'd actually use.

The fans calm down quite a bit and thermals are obviously easier to deal with, while prompt processing is still over 1500 tok/s at 200K.

60W feels like the sweet spot on this machine.

Gufo

Gufo was actually the one I was most curious about before doing this.

93W

https://preview.redd.it/nj6qrht234th1.png?width=782&format=png&auto=webp&s=deac5f98149869b594751f4ad911d250d2628de0

Around 1398 PP at 64K, and 1343 PP / 33.6 tok/s decode at 200K.

Still fast, but there's a pretty noticeable gap to Halogen with the configs I tested.

60W

https://preview.redd.it/ofd85gn334th1.png?width=759&format=png&auto=webp&s=de3476c119e77de783ef461877ced81a039f749b

Around 1238 PP at 64K, and 1156 PP / 33.0 tok/s at 200K.

Gufo seemed to care more about the power limit than the other two, at least for PP.

At 200K it went from roughly 1156 PP at 60W to 1343 at 93W, so about a 16% increase.

The project is moving pretty quickly though, so I'm definitely going to keep testing it. Right now, on my Z13 and with these settings, it isn't catching Halogen yet.

Rulith(old strix llama) / Windows

Rulith was interesting for a different reason.

https://preview.redd.it/qg8pjjs434th1.png?width=779&format=png&auto=webp&s=ad220831a38b83acf72aa0e03c194cfcc9e71d9b

At 93W I got about 1221 PP at 64K and 1170 PP / 32.55 tok/s at 200K.

So PP is clearly behind the Linux setups here.

But short-context decode is actually very fast. At 1K context I saw 54.7 tok/s.

The downside is that decode falls off pretty hard as context grows, ending up at about 32.55 tok/s at 200K.

So the pattern I saw was basically:

short context: Rulith is very fast
long context: Halogen holds its speed much better

Rulith at 60W

https://preview.redd.it/jhuiy0q734th1.png?width=775&format=png&auto=webp&s=f96742fd169d407a565efaad6e4236227b23ccf9

This is actually closest to how I normally use the Z13.

About 1138 PP at 64K, and 1070 PP / 31.29 tok/s at 200K.

I already have a dual CMP 170HX box running 24/7 as my headless LLM server, so the Z13 is more of a main PC for me.

I do have CachyOS set up as a dual boot, but switching back and forth is a little annoying because I have to change the memory allocation in BIOS depending on what I'm booting.

Because of that I end up leaving it in Windows most of the time, and Rulith is honestly pretty convenient for that.

All of them together

https://preview.redd.it/asubedz934th1.png?width=2380&format=png&auto=webp&s=6f3c96a6fc08a8ce7969d638bd8bc4041a6021aa

https://preview.redd.it/8qi9bqod34th1.png?width=2380&format=png&auto=webp&s=10ae19409fec901543ad61695947a450c9248a34

For PP, Halogen is pretty clearly ahead with the setups I tested.

At 200K:

Halogen 93W: 1694 PP
Halogen 60W: 1509 PP

Gufo 93W: 1343 PP
Gufo 60W: 1156 PP

Rulith 93W: 1170 PP
Rulith 60W: 1070 PP

https://preview.redd.it/2qwk29ag34th1.png?width=2380&format=png&auto=webp&s=be6d799eeaa9cac91484fad2a53ee18b22b1d59f

https://preview.redd.it/v3974j0i34th1.png?width=2380&format=png&auto=webp&s=262d1dfbaf83e7959a2e77df34431f4942fff7ad

Decode is more interesting.

Rulith starts out very fast at low context, but drops quite a bit as the context fills up.

Halogen is much flatter across the whole range.

So for normal short chats, Rulith can actually feel really good. For coding/agent stuff where the context keeps growing, I'd rather have Halogen.

Overall

For my current setups:

Halogen: best PP and best long-context behavior.

Rulith: slower PP, but very convenient if you actually want to use the Z13 as a Windows PC, and short-context decode is surprisingly good.

Gufo: not as fast as Halogen yet on my machine, but probably the one I'll keep watching because development seems pretty active.

Strix Halo 128GB is still kind of a weird niche, but I think that's also what makes it interesting.

If you want enough VRAM for models like Flash-Next on conventional consumer GPUs, the cost gets stupid pretty quickly. There are obviously more VRAM-efficient backends and free-token/offload tricks showing up now, so it's not a simple price comparison anymore.

Still, being able to run Qwen3.8 Flash-Next with a 200K context on what is basically a 13-inch tablet/laptop is pretty wild.

I paid about 3.2M KRW used($2400) for this Z13. New Z13s and the ProArt/PX13-type Strix Halo machines also occasionally show up below 4M KRW($3000) here, so for someone specifically interested in local LLMs, I think they're in a pretty unique spot.

Of course the actual problem is that I bought this thing for local LLMs and somehow ended up using it as a gaming machine more often.

https://preview.redd.it/pql3gc5u24th1.png?width=1536&format=png&auto=webp&s=8b77cff4a12b4ccb722f777ee60d1c20cf16b23c

reddit.com
u/Prudent_Appearance71 — 13 days ago
▲ 34 r/FlowZ13

One of the ways I use my flow z13

My wife and her twin are running in a race this morning. I offered to drop them off because parking can be a mess. I plugged my Silverado EV in at a charger and trying out Gears of War E-day on the device. So far so good.

u/clay-tri1 — 12 days ago

Best local AI

I am looking for the best local AI for my 128gb Z13. I need to be able to edit photos and design images with text. Would also like to create video from still images.

reddit.com
u/xHCICxSpyder — 12 days ago
▲ 19 r/FlowZ13

Case guy here again. i solved a quality issue on the cases. this fix will be standard going forward.

these pockmarked cases will likely have their own listing with a discount.

u/Navi_Professor — 12 days ago
▲ 15 r/FlowZ13

Case guy here again. Next case batch will be on on october 9th! + updates!

Hello! i am here to announce the next release of cases as Feedback has started to roll in as the shipping testers get their cases.

store link

Now, some updates. New price is $40. This is where the price is staying here on out.

Stock total! i am going to try and get 20 cases out this time around but there will be 15 at minimum!

Why 20? There will be 2 colors of cases, a blue bumper AND a white bumper! and my goal is 10 each.

https://preview.redd.it/8t735hh923th1.jpg?width=4000&format=pjpg&auto=webp&s=29b64059a84f78026cc6f8390eaec3bdcc00bb92

Now. this does lead me into some changes have been made that i have to be transparent over.

Print orientation has changed. This case is now being printed upside down instead of right side up, and it has some pros and cons

This has shortened print time dramatically from 16 hours per case to 9 hours per case, practically half the print time, which has enabled me to do multiple color selections.

The downside is that the outside finish simply isn't as good, and I am actively trying to find ways to improve it, but I don't think I will be able to match it.

Demand is far higher than I expected for this case, and what comes out to practically a case a day isn't enough.

Now. some actual improvements.

https://preview.redd.it/czpwqptk23th1.png?width=1829&format=png&auto=webp&s=1dfa7013c0a94fc98ceeb91c9ac25f0980fe9b08

A weak section of this case was the center bumpers on the old design. This section has been improved; the frame itself has been made thicker and wider, which should strengthen this area. All but 2 cases in my inventory still have this design. And will likely move to B stock.

Which finally, this brings me to "the cheaper option!"

There are now A and B stock cases. The printing process isn't perfect, and sometimes cases print badly, or I am a clutz and break them during cleanup.

Regardless, they're fine after being repaired properly (IE, anything that breaks gets physically welded back together)

And so, instead of creating more plastic waste and binning these cases, I would rather sell them to someone who isn't quite as keen on aesthetics.

These will be priced at $28. These don't make me any money, but it's better than wasting them.

and of course, leave feedback below.

-Navi

reddit.com
u/Navi_Professor — 13 days ago

Could vinyl sticker on the back affect productivity?

I would like to protect the back of my flowz13 with a vinyl sticker. Would itvaffect productivity or air flow?

reddit.com
u/Cute_but_depresso — 13 days ago