• Beelink Official

  • SER8 8745HS game stuttering on Windows 11, but on Windows 10 not

I have a Ser8 8745HS, with two identical NVMe SSD. On the first one a dual boot system: Windows 10 and Windows 11. On the second one: games. Windows 10: everything working fine, including games. Windows 11: everything working fine, exept games. On Windows 11 i have moderate video, and serious audio stuttering. A little additive: i’m playing with a controller with bluetooth connection, and when the game stutters, the controller is also barely responsive. /It’s not bluetooth that’s causing the stuttering, I’ve tried/. All possible Windows settings are the same on Windows 10 and 11, drivers too. I’ve searched the internet, and i’ve tried all possible solutions, nothing worked. What is the difference between the two operating systems that cause the stuttering?

    dltmchn Hi there, what games are you playing ?
    Some games are more stable on windows 10 than windows 11.
    And is the windows 11 preinstalled one ？

      No. It’s a barebone machine, i bought RAM /Crucial, 2X16 GB Kit/ and NVMe SSD /Apacer, 2×1 TB/ for it. I installed both systems with identical method: Media Creation Tool, from official Microsoft site.

      “Some games are more stable on windows 10 than windows 11.” Yes. But not all of them.

        I’ve already gone through these basic things. I made it. I uninstalled the driver with DDU, and reinstalled the driver you linked above, and the latest one from AMD official site too. Oldest driver, latest driver, it doesn’t matter. It doesn’t work. Stuttering remained. Oh, you edited the other question. “Hi there, what games are you playing ?” Doom Eternal, Rise of the Tomb Raider, Jedi Survivor. All games working fine on Windows 10. On Windows 11 i have problems with all of them, especially Jedi Survivor. Audio stuttering is insane. Sometimes the games runs fine for 20-30 seconds, and then the stuttering returns.

        [unknown] The latest one, from the Beelink Download Center: V29_15_13.

        [unknown] Yes, i tested it before, and an hour ago again /just for curiosity/. Nothing changes. Old driver, new driver, same problem. But again /just for the record/: under Windows 10 everything is fine. The problem only occurs under Windows 11. Especially under 24H2. Interestingly: under 23H2, no audio stuttering, just video stutters. What is changing in the Windows code that is making the situation worse? I have tried countless things. I’m starting to give up.

          support1
          Already done, weeks ago. But the BIOS settings apply to both operating systems, so why would that make a difference?

              dltmchn It is weird. Could you please send us a picture of the SN on the bottom of the PC ?

                  support1
                  What does the “零刻 brand” mean?
                  Anyway, I’ve already tried Windows 11 from the source you linked. The end result is the same. Stuttering remained.

                      dltmchn
                      Okay, UPDATE:
                      I replaced by Windows 11 24H2 with Windows 11 21H2. Just for testing.
                      Windows 11 21H2: no game stuttering. At all. Games working like under Windows 10.
                      Windows 11 24H2: stuttering. What am i missing?

                      UPDATE 2:
                      The latest Windows 11 Canary Insider Preview 27842.1000 build is working. No stuttering.
                      Interesting. 🤔
                      Then there is something in 24H2 that conflicts with my system. Of course, this did not reveal what it is, but at least I know that the situation is not hopeless. I only have to wait until 26H2 and I will have playable Windows 11. Provided they don’t put in what makes 24H2 unplayable for me by then. 😁

                          dltmchn 零刻 is for domestic market in China, Beelink is for oversea markets.

                            dltmchn Thanks for the updates. The root cause is almost certainly a Windows 11 24H2-specific bug in how the OS handles gaming workloads, audio, or Bluetooth input. The fact that older (21H2) and newer (Canary) builds work confirms it’s not a hardware or driver issue. Microsoft is likely aware of such bugs in preview releases and will address them in future updates (e.g., 25H2 or 26H2). Until then, using Windows 10 or 21H2 is a viable workaround, or staying on the Canary build for testing.