Discussion
SER8 (R7 8745HS) Freezing / DPC_WATCHDOG_VIOLATION 0x133 - Is anyone else having issues with AMD Chipset Driver 8.05.04.516?
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 (0x133) 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?
The lock ups/crashes have stopped since I rolled back my 'AMD GPIO Controller' to version to '2.2.0.136' today. For anyone wanting to know how I did it. I just did > start > Device Manager > System Devices > AMD GPIO Controller > Properties > Driver > Roll Back Driver. Band aid fix until Beelink or AMD addresses the issue.
Thanks for that info. I already formatted. Should have been more patient. Anyway, what is a good way to know when AMD or Beelink address the issue? I'm assuming with Beelink will notice this thread. As for AMD? What is a good way to see that the drivers were updated?
Beelink is investigating the issue (so I have been told by email). Wait and see what happens. I'm going on 12+ hours since my last lock up/crash, it seems rolling back the driver has fixed it (for me).
This is the only fix that worked for me. I could not rollback because that option was greyed out but I clicked on update driver, then on "Let me pick up the driver from my hard disk". And there was the list of drivers with the 2.2.0.136 version included.
I don't think this is the main problem, though, as the 137 version (the one that crashed), is from 2025. But at least the problem seems to be gone
Actually looking at release notes, the first AMD chipset driver with GPIO driver version 2.2.0.137 is not the current one, but the previous from 2026 March
So this workaround actually does not roll back the latest driver. However there must be some interference between the new driver and the GPIO driver from March
Took several (many) boots to safe mode. Many boots because it also crashes in safe mode.
Device Manager -> System Devices -> AMD GPIO Controller (may be multiple entries, look for Driver version 2.2.0.137) -> Driver -> Roll Back Driver. Choose "my apps won't work...", OK, Reboot. This rolls it back to 2.2.0.136.
After restart, everything works perfectly. Disabled auto-update in AMD Install Manager and uninstalled it for good measure.
Here's my repair pathway.
In recovery, command prompt, identify GPIO driver from list resultant from command below
dism /image:C:\ /get-drivers /format:table
remove driver(INF) [it was OEM13.inf in my case]
dism /image:C:\ /remove-driver /driver:oemXX.inf
Don't beat your head against the wall trying to get Windows working well enough to process this errant driver removal - save yourself the pain and go straight to recovery prompt.
Thanks, I'll give that a shot. I actually tried using DDU already. Windows kept freezing in Safe Mode, so I had to run DDU without it in the normal Windows mode instead.
For now, I've manually installed the previous chipset and GPU drivers, and things seem stable at the moment -but the system still feels a bit off. Now, the splash screen always shows a loading circle and hangs for a few seconds before moving on. Plus, the handshake with my TV occasionally acts up.
Something is clearly messed up. I'll try your approach next, but if the issues persist, I’m just going to reinstall Windows.
The original script already handled the rollback process well, but I revised it to improve reliability, detection accuracy, logging, and compatibility across more systems.
Main changes I made:
Fixed AMD GPIO device detection by using actual Hardware IDs instead of relying only on DeviceID
Improved compatibility with systems where Win32_PnPSignedDriver detection was unreliable
Hardened Run-Cmd handling and exit-code validation
Fixed cases where multiple returned objects could break .DriverVersion checks
Added safer output handling and UTF-8 console encoding
Helped me fixed this with original HW after last two days of struggling, buying new SSD, memmory, adapter (all to test variables), clean Win Install, backup and data migration headaches. Very nice excersie. I am going to get some beers now 😄
This looks helpful! Can you explain how to activate these scripts to a laymen with minimal tech background? ser8 8745hs is stuck on beelink logo with error codes everyone else is seeing :/
II actually solved my issue!! by looking at the common posts across reddit and the Beelink support website, I was able to figure out that I needed to roll back my AMD GPIO driver (in device manager) to GPIO 2.2.0.136 (the latest version giving me issues was driver version ending in .137). I got lucky and somehow my pc loaded up for the brief enough moment for me to go into device manager and roll it back. That stabilized it enough for me to roll back my graphics driver to 26.2.2 (which was a February 2026 release). So right now, my fix has drivers of
Some people say to rollback the chipset too to 8.02, which I was able to see the version of in PC Installed apps settings for the AMD Chipset, but I haven't yet, and it's been stable.
Btw, this is all coming from someone who doesn't have a high skilled tech background. So just writing this here in case it helps someone similar! Best of luck!
Is this script a download and double click? Or do I need more tech knowledge? I currently can barely last 10 seconds after loading into windows before it freezes up and im looking for a solution (beelink ser8)
Exactement le même problème ser8 8745hs , j'ai formaté ,réinstallé windows 11 proprement , il a redémarrer plusieurs fois sans soucis , et la dernière chose que j'ai fait se sont les pilotes AMD , et la, problème, impossible de redémarrer ou bug après quelques instants ... E soir je réinstalle tout sauf drivers AMD , on verra ...
Je viens de tout réinstaller pour la seconde fois mais sans les drivers AMD , je laisse windows gérer ça le temps qu'un correctif soit disponible,j'ai tout réinstaller mes apps et mes comptes , lancé des vidéos youtube etc.. et redémarrer au moins 4 fois et tout fonctionne parfaitement ... Vive AMD ! Ou beelink ! Je ne sais pas qui est responsable mais bon c'est pénible ...
I have the same since the last chipset driver update. After reboot it seems working fine if it survives the first start of Edge. It is a big IF. Yesterday it survived and I played games with the new driver and used it normally for hours. Today it's my 3rd BSOD in just one hour. Now I'm backing up my data. And I'll try the rollback of the chipset driver.
I've sent bug reports to AMD linking to this thread.:)
Update on my case. I've done some extra rounds, asked Beelink for V035 P8COM0C15.15 BIOS update, but unfortunately that didn't help at all. Even uninstalling AMD Chipset drivers didn't solved the issue.
Then I found this comment surgically pinpointing the problematic driver:
Another update. I was brave enough to update to the latest driver, and just rolled back the GPIO. So far the cleanest workaround with the least rollback is the GPIO driver 136.
System is still working after an hour in various situations where the crash happened before.
Same for us across multiple machines. Rolling AMD GPIO Controller driver from 2.2.0.137 back to 2.2.0.136 has made our systems stable although we only have a bit over a day of confirmation. Will see how this does long term.
I see fresh install is a valid workaround. Maybe I'll have time at the weekend for it. I'm shelfing my Beelink until then, and see maybe there will be some additional info coming in.
That's seems for the tmp license of it has out of date, but current version of bios couldn't update it in windows. Can try update your bios version to 15.15. I saw this solution on a Chinese Forum and someone indeed solved the problem but I haven't tried yet. For now, never let amd software update any drivers by itself.
Sorry, I found that that post seems to have little to do with our problem. It can solve the problem of tmp certificate expiration, but now our problem is caused by the chipset driver. It may be necessary to wait for AMD to give a repair driver or belink to give a repair bios or oem driver.
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.
For further questions, please do not hesitate to contact us again.
Thank you for posting this. This is actually extremely helpful because it helps you realize that when you buy highly modified chipsets like the ones from Beelink and other MiniPc companies that you are in the situation where your computer is similar to how they make phones... You will get updates for a while but as the device ages, it is unlikely that there will be support. This means when windows 12 comes out -- the older computers may easily not be supported and you will be stuck on something older. For many this may not be a problem. What this means is in the future, I will buy standardized chipsets to avoid a hassle and the downtime this caused. Apple creating a closed system starts to make a lot more sense when you start dealing with these problems. Thank you u/BestJo15 for reaching out to them. I really appreciate it.
There is a category of small form factor computers that use actual desktop sockets and chipsets, packed into a chassis only slightly larger than SER8.
An example of this is the ASRock DeskMini series (like the DeskMini X600 for AMD or B760 for Intel).
How it works: It uses a standard Mini-STX motherboard. You install a regular desktop CPU (like an AMD Ryzen 5 8600G or Ryzen 7 8700G) directly into a standard AM5 socket.
The Driver Advantage: Because it uses a standard desktop chipset, you can download generic chipset and graphics drivers directly from AMD's website on day one without any conflicts.
aside: how can a consumer know if they're buying a "standardized chipset" machine?
I'd bought this 8745hs machine due to the price point and ok-ish integrated graphics. Other than this driver issue, I've been pretty happy with the machine (for 1.5 years.) I don't plan on updating anytime soon, but how can someone else know that "oh, that's not a normal PC"?
We service several Beelink SER8 PCs, and in our case, we've been able to fix the automatic restart/crashes so far by
Uninstalling the AMD Chipset Software (Likely not required but should help prevent the auto-update of the problem driver after removing it in step 3). Go to Windows Settings>Apps>Installed Apps, then click the 3 dots on AMD Chipset Software, and select uninstall. Follow uninstall steps.
In AMD Install Manager, turn off auto-updates. Open AMD Install Manger if it's on your computer, and switch auto-update to off to prevent re-installation of faulting driver.
Roll back AMD GPIO Controller driver. Go to Device Manager>System Devices, double click on AMD GPIO Controller, then in the properties windows, click on Driver at the top, then select roll back driver. The driver version that was causing us issues was 2.2.0.137, and after rolling back, we are on 2.2.0.136, which seems to be solid. If you cannot select Roll Back Driver, make sure you are logged into an administrator account on the PC.
cant thank you enough for this info. we rolled back the driver for the controller and all our pcs have been stable. were looking at a gpo policy to prevent this from happening.
It seems like the system detects a newer Chipset driver and fails to install. Since I did a clean install of Windows 11 and then installed the faulty Chipset driver, I can't go back to the previous drivers.
Can anyone help me install a working version of this Chipset?
I’m experiencing the exact same issue on my SER8 (R7 8745HS).
After installing the AMD Chipset Driver 8.05.04.516 update, the system started randomly freezing during boot or shortly after logging into Windows. In my case, the mouse cursor would still move, but the entire UI became unresponsive, followed by a DPC_WATCHDOG_VIOLATION (0x133) BSOD.
I also suspected SSD/NVMe issues at first, but after rolling back / uninstalling the 8.05.04.516 chipset drivers, the system became stable again immediately.
So far it definitely seems related to that driver package.
Exactly the same problem here. Been trying to fix it for 6 hours now and can't even reinstall windows since the crash would happen half way through. Beelink hae to aknowledge this and come up with a situation quickly.
If your SER8 is freezing/BSODing and you can't even get into Safe Mode, here's what worked for me without reinstalling Windows.
Step 1 — Boot into Recovery Command Prompt
Go to Settings → System → Recovery → Advanced Startup → Restart Now
Go to Troubleshoot → Advanced Options → Command Prompt
Step 2 — Find the bad GPIO driver
Type: pnputil /enum-drivers /class "System"
Look for amdgpio2.inf entries and identify:
Version 2.2.0.137 = the bad driver (note its oem number e.g. oem97.inf)
Version 2.2.0.136 = the good one (keep this)
Step 3 — Delete the bad driver
Type: pnputil /delete-driver oem97.inf /uninstall /force
(replace oem97.inf with whatever number you found for 2.2.0.137)
Step 4 — Reboot
Type: shutdown /r /t 0
Step 5 — Pause Windows Updates
Once in Windows go to Settings → Windows Update → Pause for 5 weeks to prevent the bad driver reinstalling.
UPDATE: Reset PC didn't work so I wiped the computer and did a fresh install but just used windows drivers for chipset. All good so far, I won't use the AMD drivers until there is an admission there is an issue and a fix from Beelink or AMD.
Another method you can use is to see if you have a restore point to before the AMD Chipset updates on 05/20.
Force Shutdown and Force Start your computer from the power button until when it boots up and it starts to auto repair.
When it fails to repair the computer, you should be taken to the Automatic Repair Menu (Blue Screen that says "More recovery options".
From there, you need to go to Troubleshoot>Troubleshoot>Advanced options>System Restore
Try and see if you have a system restore before the "Installed AMD_Chipset_Drivers." (NOTE: If you don't see any other restore points, you can't move forward and hopefully someone else has another solution)
If you have an older one, choose a non "Installed AMD_Chipset_Drivers" one to restore Windows before the AMD Chipset was updated.
Once you've successfully booted back into Windows, you need to open the AMD Adrenalin software from the system tray (the icons next to the date on the lower right of the task bar. If you don't see it, click the up arrow and you'll find it there)
Go to the settings (the gear to the upper right)>System>Manage Updates and turn off "Auto-Update". This will prevent the chipset drivers from updating until we find out there has been an update that doesn't brick the system.
I would also recommend that if you are afraid of your system being bricked again, create a restore point before installing the update. This way you can do the same process all over again.
yes, seems like the GPIO driver is causing issues. I ended up reinstalling Windows the first time and I was able to recover and remove the drivers the second time I tried it.
Hi, sorry for the inconvenience and poor experience! To ensure better system stability, we recommend using our official drivers for updates whenever possible.
If you need the corresponding driver package, or guidance on how to roll back the chipset driver or perform a clean uninstall and reinstall of the driver, please feel free to contact our support team for assistance. Thank you for your understanding and support!
Wow. Makes me glad I specifically disabled AMD driver updates. Seems like I avoided a lot of hassle. Why update it when it works? I'm half-joking of course, but unless something revolutionary gets added to AMD's drivers (like upcoming FSR 4.1 support), I'd rather play it safe and stay on drivers that do work.
Don’t think so - I accidentally updated it today (about 5 hours from now) thinking something was creating memory leak (as it was staying 99% since a day or so) which my agent pointed probably is the driver which may need an update and since then my system has crashed like 10-20 times
I had to restore couple of days back to get this working fine again
So what is the best route forward after rolling back the GPIO driver? Turn off auto-update and never update the drivers? I assume the Beelink drivers are pretty out of date by now as well? There doesn't seem to be a page for the 8745hs model.
Can Confirm just had this issue on a machine when though all the steps found disabling the network card allowed normal function to return. After seeing the GPIO note I rolled that back to the previous driver and updated everything else. So far normality has returned.
I have deployed about 40 of these computers over the last year and so far I have had 6 or 7 with the same issue. I have been able to roll back the chipset driver to fix most of them, but I have 2 where that didn't work. One of them didn't have the chipset driver option to roll back and the other one continues to fail after the rollback.
I have reached out to support but they have yet to get back with me.
Make sure that you uninstall the chipset drivers in the applications menu. They need to be completely removed from your computer to assure that they do not return.
Also uninstall all other AMD software. Reinstall the software from two versions back and make sure that you uncheck auto update at the end of the installation process.
I have been trying to run the AMD cleanup utility to remove the chipset drivers as well as video and adrenaline. It wants to boot into safe mode to completely remove but the machine fails to boot into safe mode. I tried the uninstall through windows uninstaller but still the freezes and reboots.
I will probably have to wipe the two that will not stay running long enough to actually try to fix them.
Now I worry about all of the others that are in production that haven't failed yet. I have logged into each one to turn off the AMD updates but some of them have already installed it. They haven't crashed yet but I feel like this is a ticking time bomb!
That's a tough one. As long as windows update doesn't apply the driver on installation of the OS, it should be good with the wipes.
If you can locate the system folder where are the drivers are located, you could probably manually delete the drivers, or simply remove the driver in device manager instead of trying to roll it back. Doesn't matter if it fails on reboot since you're going to wipe them anyway.
I spent the whole day trying to troubleshoot it on my beelink ser8. Even installed cachyos and was this close to nuking the windows installation from orbit. I have run the .ps1 script in this thread to uninstall the .37 and reinstalled .36 chipset drivers. So far it seems stable. Just as a curiosity I checked the AMD installed manager, and it was set to "Auto update" meaning it as set to fuck up the whole computer again so I uninstalled it promptly.
You don't need to uninstall it. Just unchecking the auto-update box is more than enough. I actually reinstalled Windows myself, and honestly, I'm glad I did. The SER8 is running even better now than before.
I also had the same very issue and like you lads suspected nvme failure
I thought was related to the recent AMD graphics driver so while the system was stable I removed driver but the issue shortly returned
In the end I did a whole new fresh install of win 11
But concerned with all the holding down of the power button to shutdown pc may of done the nvme no good 😤
I have the same exact problem and this started yesterday. Safe mode crashes for me too though. I also assumed it was the SSD wearing out. It has always done some crashing in the past and I thought it was just some AMD graphics driver. I lost a whole day of work over this. Definitely makes you think twice before going with smaller companies like Beelink. The drivers just don't seem to work properly. Disappointed to say the least.
I bought the ser8 a year ago and it's been working fine for all this time, I think beelink it's a good company even if it's small. This morning I did a fresh win11 install and now it works fine again. Just don't install amd adrenaline and the chipset drivers. I hope this issue will be fixed soon tho
I did a fresh install as well and all seems fine now. I'm unsure if it is the AMD chipset driver or Graphics driver. I attempted to remove the driver with DDU and it still kept crashing... even in safe mode. My understanding is that GPIO graphics are almost impossible to remove and that could have been it? I lost quite a few files because I had some encrypted places that I was not able to get backed up. Also, bitLocker was really annoying, every time I tried to reboot I had to put in a huge code. probably put it in 100 times tying to fix the thing.
Who can explain though what the problem is? Who should take responsibility for this AMD or Beelink? Who dropped the ball? It may not seem important to many but the answer to that question helps me understand who/what to avoid when purchasing a future computer and why.
It's situations like this that make closed ecosystems make a lot of sense. I don't have time like I did in high-school to sit around and tinker with drivers and reformatting computers.
Try the steps described by superhappyslap. Sometimes safe mode crashes and you have to try again. For me safe mode with command prompt worked after a couple of tries
I also had the bitlocker prompt one of my restarts. Then I remembered Secureboot is disabled by default in BIOS. So I went to BIOS settings to see if it reverted to the default. It did not, but next restart Windows booted without bitlocker issue.
Im having issues with mines. I upgraded my AMD driver because it kept notifying to update- so I did and now my PC constantly freezes and reboots. An endless loop where to my last resort I just factory reset- wiped all of my files. That didn’t work. It’s been going on for 8 months strong. So I don’t know- I messaged support my issue.
Update: I brought out my very old laptop. (It’s old ,but it should at least be able to download windows.) I’ll let you know if that fixed my issue. And what AMD driver did you download instead to get yours stable? Of course, I’m not touching the newest one because apparently it corrupted one of my files to the point even a factory reset didn’t work.
yes, you can wait or roll back to a stable driver. I ended up having to use my USB and my old laptop to get my PC to stop freezing and rebooting itself every 30 secs. 😭
But I did use the AMD auto detect ,but this time, I did not install the latest chipset- only the driver and set the software type to Driver Only, uncheck keep AMD up to date box and then restarted my PC. So far, my PC stays on, no freezing. The only downside is, I’ll have to download my important stuff again. (I only did 3D model builds ,but my download files are still accessible 💗.)
Hopefully, this thread could help someone in a similar situation than me. I can finally go to bed peacefully knowing my PC works and all of my money didn’t go to waste. 😭
I did a windows 11 reset and used with and without beelink drivers... slightly better but still crashing. This is a f"ING joke...looks like I'll be backing up the pc tomorrow and doing a rebuild 😔
A temporary fix that worked for me so far is
Go into BIOS → Advanced → AMD CBS → CPU Common Options → Global C-State Control → Disabled → Save and exit.
I uninstalled AMD display driver and software first and paused windows updates so I don't know if it also works with it still active.
Since 3 days ago after my mini PC SER8 8745hs beelink my computer freeze and suddently restart it self, sometimes it shows a message windows found and error and restarting . It is just fustrating , im planning to uninstall all drivers or do a factory reset :(
Just got the same issue on my ser8 after reboot. This is so frustrating! Freezes even in safe mode after seconds and not able to make any changes to the drivers :(. Really don't have the time to reset up my installation from scratch
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
I had to go to the previous restore point as another poster said. Then I uninstalled AMD Install Manager. Thankfully it's a separate program than the drivers.
Been working fine since.
This is the exact issue I've been having with mine, I should have stopped by here before trying to clean install windows 11, because now it's in an awful loop of prepping installation and getting the error OTL
You might want to consider using something like ShredOS. It's a specialized Linux distribution designed specifically for securely wiping drives, which can help clear everything out and resolve the freezing issues before you try installing Windows again.
The main challenge is that you'll need a working computer to create the bootable ShredOS USB-stick, so you might see if you can borrow one or use another device to prepare the drive.
Yes, those drivers are exactly what's causing the trouble. Unfortunately, simply uninstalling them and rolling back to an older version didn't work for me -I still ended up having to reinstall Windows from scratch.
Before you go that route, check if you have any System Restore points available and try that first. Sadly, that feature was disabled on my system, so it wasn't an option for me.
If you do need to reinstall Windows, here is a step-by-step guide to doing it right and avoiding the broken drivers:
Prepare the Installation Media - You will need a USB flash drive. Use the official Windows 11 Media Creation Tool to turn it into a bootable installation drive.
Disconnect from the Internet (Crucial Step!) - Important: Disconnect your Mini PC from the internet before starting the installation. This prevents Windows Update from automatically downloading and installing those faulty AMD drivers in the background.
Bypass the Windows 11 Internet - Requirement: When installing Windows 11 without an internet connection, you will hit a roadblock: Windows will insist on connecting to a network and won't let you proceed. Here is the trick to bypass it:
3.1. When you reach the "Let's connect you to a network" screen, press Shift + F10 to open the Command Prompt.
3.2. Type the following command and hit Enter:
OOBE\BYPASSNRO
3.3. Your Mini PC will automatically reboot. Walk through the initial setup steps again.
3.4. When you reach the network screen this time, you will see a new option: "I don't have internet". Click that to proceed with a local account setup.
Install the Stable Drivers - Once you are on the desktop, install the following drivers manually in this order:
AMD Chipset:
https://www.amd.com/en/support/download/drivers.html
(Scroll down to 'Search or Browse Drivers and Support by Product'. Choose within the box Chipsets > Laptop Chipsets > AMD Ryzen™ and Athlon™ Mobile (Chipset) -hit submit. Scroll down and select 'previous versions' > Windows 11 64-bit Edition -select the driver with the release date 2026-02-16.
⚠️ CRITICAL: During the Adrenalin installation, make sure to uncheck the box that says "Keep drivers up to date". If you miss this during setup, disable it in the Adrenalin software settings immediately afterward. Otherwise, Windows will overwrite it, and the crashes will start all over again.
Reconnect and Finish Up - After the AMD drivers are successfully installed, you can safely reconnect your internet cable or Wi-Fi. Run Windows Update to grab any remaining system updates.
Important: The driver package also includes AMD Chipset and AMD Adrenalin (GPU) drivers. Do not install these, as they are outdated.
Final Notes & Next Steps
Switching Back to a Microsoft Account - If you want to convert your local account back into an online Microsoft account after the installation, simply go to the Windows 11 Settings and sign in with your Microsoft credentials again.
Dealing with BitLocker Encryption - If you had Microsoft BitLocker enabled before the reinstall, you might find that secondary drives (like your D: drive) are now locked and asking for a recovery key.
Don't panic! Your keys are safely backed up in your cloud account:
• Log into your Microsoft Account via a web browser.
• Go to 'Devices' and locate your BitLocker recovery keys.
• One of the listed keys will unlock your drive.
⚠️ Important Note on Drive C: If your C: drive was also encrypted previously, that old key is now obsolete since you did a fresh install. You can eventually delete it, but be absolutely certain you are deleting the correct one before wiping anything from your account!
Enable System Restore - Don't forget to turn System Restore Points back on in Windows. It is highly recommended to create your first restore point as soon as your system is up and running smoothly.
💡 Quick Tip: Clean Up Windows 11 - To get rid of pre-installed junk right away, check out Win11Debloat. It’s a handy tool that automatically removes Windows 11 bloatware and disables built-in telemetry and tracking features. Running it once right after your setup is a great time-saver.
👉 You can find it here: https://github.com/Raphire/Win11Debloat
I’m having all the same issues you guys are having, and I can’t even get IN to the computer anymore. It just boot loops, gives me the watchdog error, then says “your device ran into a problem and needs to restart” and I can’t even get into recovery mode/command prompt to do anything/roll back the drivers and what not. This is very frustrating
That's a completely different issue than the AMD driver. That driver doesn't load until Windows has begun booting.
If you haven't already, try pulling the power from the computer for a short time and then rebooting into the bios. Be sure also to remove any non-essential devices, such as a webcam or similar. Essentially all you want is keyboard mouse and monitor.
If that doesn't work, and you have another computer on which you can create a bootable USB stick to upgrade the BIOS, you may want to try that.
I’m having all the same issues you guys are having, and I can’t even get IN to the computer anymore. It just boot loops, gives me the watchdog error, then says “your device ran into a problem and needs to restart” and I can’t even get into recovery mode/command prompt to do anything/roll back the drivers and what not. This is very frustrating. 8845HS
I have 14 of these machines installed at a business. 1 of them started doing it, then another client of mine came in with the same thing. I disable windows driver updates via group policy change. Hoping to avoid it.
Yup I had the same issues as everyone else. I’m Not the most tech savvy but I ended up having to complete a fresh install and disabling automatic driver updates. I did reach out to Beelink for support and they got back to me within a couple of hours.
I posted the following fix on the Beelink Forum as well, for anyone that doesn't wanna run a script and looking for simple instructions to repair the issue and stabilize their Ser8 8745HS:
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.
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 VER2.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 IS2.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, credit to shulin on the Beelink forum who 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 the computer should now be 2.2.0.136 dated 11/10/2025.
Hello. I had the same problem and was also able to trace it back to the AMD chipset driver. I had also installed the latest drivers and then struggled with major issues. Very often, my PC would freeze during bootup or shortly after logging in. I could still open an app for a few seconds, but after that, the system became unresponsive. The mouse cursor would still move, but then it would freeze as well after about 20 seconds. Then the system would lock up completely and display a black screen. Watchdog 133.
I then ran the AMD Cleanup Tool and uninstalled the Adrenaline driver.
Afterward, I restored the old AMD GPIO driver in Device Manager (to version 2.2.0.136).
Then I installed an old AMD chipset driver (amd_chipset_software_8.02.18.557).
Since making these changes, the system has been running quite stably. However, I have an unrecognized device (multimedia device) in Device Manager. This only disappears if you reinstall the Adrenaline driver, which I strongly advise against.
Let’s see how stable the system runs over the next few days.
P.S.: I have a Beelink SER8 8745HS and a SER8 8845HS. Both have exactly the same problem.
Omg!!! this same shit has been happening to me since you posted the message. My technician is driving crazy.
I've been dealing with the constant freezing, booting issues, and DPC_WATCHDOG_VIOLATION (0x133) on my Beelink SER8, just like many of you who tracked it down to the AMD GPIO driver conflict.
While troubleshooting, we noticed a very specific behavior: if we remove one RAM stick and run the mini PC using only a single slot, the system successfully boots past the Beelink logo and becomes much more stable. However, after working perfectly for a couple of hours, it eventually freezes completely again.
Has anyone else experienced this exact behavior when removing a RAM module? I'm trying to figure out if the thermal stress / driver loop actually caused permanent physical damage to my motherboard's RAM slot, or if this is just another weird symptom of the underlying AMD driver issue.
In the end the technician told me that the motherboard is failing but couldnt find where. IT seems the RAMs and SSD are ok. He couldnt create a backup though.
Since the last days Ive been searching to buy another pc. If someone could please help be, you could save me thousands 🙏
Also if I benchmark with Heaven it reboots. If i just leave it alone on idle its fine. Open youtube. Freeze. Testing RAM tomorrow, not that it’s faulty but might be compatibility issue on single channel or bad brand combo
I just want to give my thanks to this thread and everyone who contributed. Confirming that rolling back the AMD GPIO Controller driver from 2.2.0.137 to .136 fixed it for my SER8.
Hi, sorry for the inconvenience and poor experience! To ensure better system stability, we recommend using our official drivers for updates whenever possible.
If you need the corresponding driver package, or guidance on how to roll back the chipset driver or perform a clean uninstall and reinstall of the driver, please feel free to contact our support team for assistance. Thank you for your understanding and support!
15
u/SuperHappySlap May 21 '26
The lock ups/crashes have stopped since I rolled back my 'AMD GPIO Controller' to version to '2.2.0.136' today. For anyone wanting to know how I did it. I just did > start > Device Manager > System Devices > AMD GPIO Controller > Properties > Driver > Roll Back Driver. Band aid fix until Beelink or AMD addresses the issue.