SER8 (R7 8745HS) Freezing / DPC_WATCHDOG_VIOLATION 0x133

Joo

Hi everyone,

I wanted to share a frustrating issue I’ve been dealing with on my Beelink SER8 and see if I’m the only one experiencing this. Starting yesterday, my mini PC began freezing completely. The symptoms were very specific:

It would freeze right on the Beelink boot logo
If I managed to get into Windows, it would freeze about 20 seconds after login.

Weirdest part: The mouse cursor would still move smoothly, but the entire Windows interface was completely frozen and unclickable. After about 20 seconds of hang, it would crash with a DPC_WATCHDOG_VIOLATION (0×133) BSOD.

I initially thought my internal NVMe SSD was dying or had a loose connection, but after some troubleshooting (and realizing it was a classic storage I/O hang), I traced it back to the recent AMD Chipset Drivers update - Version 8.05.04.516.

I managed to completely uninstall this specific chipset driver package, and the system immediately became stable again. I’m going to do a clean reinstall of Windows 11 tomorrow just to be completely safe and wipe any corrupted leftover files.

Has anyone else run into this issue with the 8.05.04.516 driver version?

I also made a post on reddit and other people are having the same issue, pls beelink team fix the issue.

EDIT: I just did a fresh win11 install without installing AMD adrenaline software and the chipset drivers and the pc is working fine, so i guess the culprit is really the chipset drivers

Beelink CS-June

Joo

Hello there,

Thanks for your reply~

Could you please send us a picture of SN code(two lines) at the bottom of machine?

Then we will sned you the system file.

Have a nice day~

Ashuramaru

Joo The chipset seems to be half of the issue, and triggers a compound issue with the most recent AMD GPIO Controller. The AMD Software itself is stable; it’s def the chipset update that’s the primary culprit, and only by resolving BOTH the GPIO Controller issue and the chipset driver issue can the SER8 8745HS be stabilized.

I’ve noticed a lot of ppl shredding their PC’s in the comments just trying to resolve the issue. Something about a bug repair in the newest chipset triggers a fault in the latest AMD GPIO Controller. Rolling back the chipset alone doesn’t resolve the issue either once it’s been triggered. Both need to be resolved to stabilize.

YOU DO NOT NEED TO UNINSTALL AMD ADRENALINE TO RESOLVE THIS ISSUE.
If you are able to login to Windows, then YOU DO NOT NEED TO ENTER THE RECOVERY ENVIRONMENT.

TO FIX FROM WINDOWS:
1. ROLL BACK THE AMD CHIPSET DRIVER TO VER 8.02.18.557, LOCATED HERE: AMD CHIPSET 8.02.18.557 RELEASE NOTES + LINK

DISABLE AMD CHIPSET AUTO-UPDATE
Open AMD Adrenaline Edition
Go To System –> Manage Updates ; You’ll see two AMD Update options, one for AMD Adrenaline Edition, the other for the AMD Chipset Driver. Check the driver version is 8.02.18.557 in the drop-down located next to the AMD Chipset Update (three bullet points in-line)
Disable Auto-Update via the switch on the top-right of the “Update” screen
ROLLBACK THE AMD GPIO CONTROLLER
Press Win +X to open shortcut menu and select “Device Manager”
Scroll down to “System Devices” and open the extended menu to display all system devices
Locate the “AMD GPIO Controller” and double-click ; select the “Driver” tab
IF THE DRIVER DATE IS 03/2026 VER 2.2.0.137, THEN YOU NEED TO ROLL BACK THE DRIVER BY SELECTING “Roll Back Driver”. To roll-back the driver Windows will need to restart and update; allow this
AFTER GPIO CONTROLLER DRIVER ROLLBACK, CONFIRM THE ROLLBACK VER IS 2.2.0.136, DATED 11/2025 ; This can be done by re-entering device manager and double-clicking on the AMD GPIO Controller and checking the “Driver” tab in Properties.

This should be it. After doing this the system should be stable again. Just make sure you do not inadvertently allow the GPIO Controller to be updated again before Beelink and AMD work out a fix with the chipset update.

IF YOU ARE UNABLE TO ENTER DEVICE MANAGER FROM WINDOWS AND NEED TO USE WinRE TO ROLL BACK THE AMD GPIO CONTROLLER, shulin was kind enough to post a fix:

*Get into WinRE: Troubleshoot → Advanced options → Command Prompt
*Find Windows drive letter (probablyD:)

diskpart
list volume
exit

*List drivers:dism /image:D:\ /get-drivers
*Find the most recentamdgpio2 driver. In my case, I found a driver amdgpio2.inf dated 3/22/2026 with Published Nameoem12.inf
*Remove the faulty driver using its Published Name. In my case, the command wasdism /image:D:\ /remove-driver /driver:oem12.inf
*Reboot. In Windows, disable AMD Software Auto-Update

The effective driver version for AMD GPIO Controller on my computer is now 2.2.0.136 dated 11/10/2025.

Fmtrx

I have the same issue, with the same message. PRoblem is located with the chipset driver that was installed on 20/5. Result is that my pc was so badly damaged that i cannot boot in recovery mode. I am in the middle of a project and AMD destroyed me.

JsonLim

Fmtrx I’m in same situation, and after I tried even to reinstall Windows(clean drive), my SSD got damaged, so I ordered a new SSD. So BAD!!!

mlmason75

OMG!!! 😳

I have 2 SER8 8845 computers and one of them automatically installed the buggy 8.05.04.516 chipset drivers. And now like everyone else my PC is locking up like crazy.

I am going to do a clean install tomorrow but this time only use the AMD display and chipset drivers from beelink.

Luckily my other SER8 8845 did not automatically install these buggy chipset drivers.

Hard Lesson learned. 😩

Fmtrx

i cannot believe these guys in AMD. They publish a buggy product without bothering testing it properly. . . at least you are lucky and have one machine. I went back to an old laptop and will have to install may things from scratch. Hopefully i saved source code to an external SSD before the major lockup . . .

Joo

Fmtrx i wrote a mail to amd support and they told me this:

Thank you for contacting AMD Support. I am so sorry to hear that your Beelink Mini PC froze and that you had to go through the hassle of completely reinstalling Windows 11 just to get it working again. I understand how incredibly frustrating that must have been, and I am here to help clarify exactly why this happened so you can avoid it in the future.

To explain what occurred: the chipset drivers offered directly on the AMD website and through the AMD Adrenalin software are designed specifically for standard desktop motherboards (such as AM4 and AM5 socket motherboards). However, your Beelink SER8 features a Ryzen 8745HS, which is a mobile processor built primarily for notebooks, all-in-one PCs, and mini-PCs.

Systems like yours use highly customized motherboard architectures. Because of this, the generic AMD chipset drivers are not compatible and can cause severe system conflicts.

To keep your system running safely and smoothly, the chipset and graphics drivers must be downloaded exclusively from the manufacturer. We highly recommend visiting Beelink’s official support website and downloading the specific drivers they provide for the SER8 model, as those have been tested and validated for your exact hardware configuration.

So basically they say its not their fault

Fmtrx

I call BS on this one. They have a special software manager called ‘Adrenaline’ which oughts to be smart enough to block updates of 780M when the driver is epicentered for the desktop chipset. Even if windows tried to install the driver silently, Adrenaline should be able to block if the driver was incompatible. I cannot accept their excuse.
Besides previous version of Adrenaline and chipset driver worked perfectly for the mini pc.

Naming the software ‘Adrenaline’ was the only wise move they did in AMD. Its main role is to raise the adrenaline of users after catastrophic failures.

Joo

Beelink CS-June

Could you please clarify what you mean by “system file”? If you are referring to a Beelink Windows image to reinstall the OS, I want to clarify that I do not need it. I have already performed a clean install of Windows 11 and my PC is currently working fine.

The reason I reached out is to report this severe bug.

I kindly ask you to escalate this specific driver conflict to your technical and engineering team. Many users on Reddit are suffering from these exact same random freezes after updating their AMD drivers. We need Beelink to investigate this compatibility issue with AMD so we can safely update our systems in the future without our PCs crashing.

Nazario

I agree with Joo , I spent hours to understand what happened and try to solve this big issue with AMD drivers and I have no more time to solve it alone. Please Beelink do something!!!!!

Nhawk

I had the same issue and I just tested it by installing the same update again. Within a minute of booting, the PC froze.
The fastest way out of the issue is to use a recent restore point. For now I disabled auto-update in AMD software manager.
This is the software that caused it: Chipset Drivers 8.05.04.516

Beelink CS-June

Nhawk and @Nazario and @jooli

Hello there,

We are very sorry for the inconvenience caused to you due to the machine failure.
At present, our R&D team has already become aware of the machine malfunction issues you have reported.

The problem you encountered is related to AMD chipset/graphic driver compatibility. Currently only the original factory driver is fully compatible with our devices. The latest official AMD drivers are not yet adapted for our models.
Our R&D team is in communication with AMD to optimize and match the newest drivers.
To fix the recurring startup failure without system reinstallation, please roll back to the original built-in graphic driver temporarily. This will stabilize your device startup performance.
We will keep you updated once the compatible new driver is released.

Have a nice day~

open_lot_0125

Beelink CS-June When can we expect a resolution of this flaw? It seems pretty unacceptable that such an error would be allowed to slip past.

fvogelmann

Beelink CS-June
Since I am also having this problem: How exactly can I “roll back the graphics driver”? A step-by-step solution would be very helpful, until you fix this problem. Thanks!

JsonLim

I have been struggling with same issue from 5/20/26. I did so many things to fix(Including deleting Adrenaline and Chipset, and restoring pc), but it was not working. So now I’m reinstalling Windows. Hopefully it will be working ok. It was so crazy happening this from AMD update…, I was about to buy new PC, not MiniPC any more.
Blaming AMD and Beelink

JsonLim

JsonLim Unfortunately, the exact same problem persists even after reinstalling, and I am feeling quite frustrated.

WillD

JsonLim I’d suggest disabling Windows Update while you’re repairing your system. It will install updates to what it considers ‘critical’ systems, particularly AMD drivers (!) without even notifying you or asking permission. I had that happen to me today - with this problem. I’ve now managed to rebuild my system [with help from DeepSeek AI] without losing everything or having to re-install Windows.

Destraler

Hi, same problem. I’m experiencing restarts and thought Windows startup was broken, so I tried a complete reinstall from scratch. However, it won’t let me disable Security Boot, and I can’t do anything beyond the BIOS settings. Now I have a useless brick.

albgr

Hi.

I have the same problem.

jerembeelink

Hi, i have the same problem

Beelink SER8 8745HS
BIOS: HPT.8xxx.SER8.V035.P8C0M0C15.14.Link
AMD Chipset Software: 8.05.04.516
Crash: DPC_WATCHDOG_VIOLATION 0×133

jerembeelink

Installing 8.02.18.557 AND disabling hyper v fixed it for me. Only installing the old driver did not

Beelink CS-June

Nickan

Hello there,

Thanks for your sharing.

Have a nice day~

fvogelmann

Hello there,

Here is the tutorial you need:

Right-click “This PC” → “Manage” → “Device Manager”
Expand “Display adapters”, find AMD Radeon 780M
Right-click → Properties → Driver tab → Click “Roll Back Driver”
Select the reason for rolling back → OK → Restart your computer

⚠ This method can only roll back to the previous version; you cannot select a specific version number.

Have a nice day~

open_lot_0125

Hello there,

We are very sorry that we have not received any notification from the R&D team regarding when there will be a solution to the SER8 AMD driver failure issue. Please wait patiently.

We are truly sorry for the inconvenience caused to you due to the machine failure.

Have a nice day~

Nickan

fvogelmann

Step by step solution:

https://www.amd.com/en/support/download/drivers.html This website -> BAD for now, becuase they have bugged driver for Chipset (GPIO). In versions after march 9.
You need stable driver version that released earlier like in march or feb 2026
I trust to this website and downloaded OLD driver from here: https://www.techpowerup.com/download/amd-ryzen-chipset-drivers/

Or you can download from official website here: https://www.amd.com/en/support/downloads/previous-drivers.html/chipsets/laptop-chipsets/amd-ryzen-and-athlon-mobile-chipset.html

Install it.
Open Adrenaline software (right click on desktop -> adrenaline) or search in Start menu. (if you never installed that -> install).
Find in Andrenaline menu about “check updates” or something like that (depends on the language) -> open window.
Turn off radiobox or checkbox for “automatically download and install updates”

Done
Restart PC

Nickan

Same here. The problem like guy said with amd chipset driver. Latest version of chipset on AMD website & that you get from adrenaline software automatically installed -> corrupted one, and makes crash.

How i found out that?
By enabling full memory dump & reading dump of crashed windows.
Its 100% crash of the driver in latest (by 18 may 2026) version of chipset.
Really sucks thing.

How to fix?
1.) go to website (or any alternative like that, i trust this one)
https://www.techpowerup.com/download/amd-ryzen-chipset-drivers/

Scroll down find:
8.02.18.557 (March 9th, 2026)

And download this version of chipset driver.
Install that, reboot PC.
In andrenaline software find option to turn off drivers update for chipset (in window where drivers updated)

Also few notes about the bug:
1.) i have c/c++ dev enveriopment on my pc, like visual studio 2026 community, a lot of libs (debug ones) and everything works perfectly fine without issues.
2.) But at the same time at PC near me at my wife i have crashes. On wifes PC zero software dev software.

I suspect the issue related to wrong linking or wrong enveriopment (debug one) released for “release” one for production consumer.
Because of that - crashes.

The only good solution -> roll back driver (not via windows device, it will not work, and will automatically roll back) via forcefully re-installing whole package and turning off option for autoupdate).

DO NOT reinstall windows or whatever, the problem 100% in this latest amd chipset drivers.
https://pcforum.amd.com/s/question/0D5Pd00001ZDWU2KAP/what-drivers-andor-chipsets-do-i-download-and-install-for-a-ryzen-7-8745hs-w-amd-radeon-780m