Updating to or installing manually 25.3.1 causes BSOD on Bee-link SER9 computer running with Windows 11 24H2.
Rebooting leads to system crash.
I have to roll back to 24.12.1 in Safe Mode to get my computer back to its feet again.
Detailed informations:
Device name: DESKTOP-SER9
Processor: AMD Ryzen AI 9 HX 370 w/ Radeon 890M
Installed RAM: 32.0 GB (27.6 GB usable)
Device ID: E2BE0E23-B5B6-4312-9C35-744E65BB4537
Product ID: 00331-20315-18211-AA511
System type: 64-bit operating system, x64-based processor
Pen and touch: No pen or touch input is available for this display
Errors in system logs:
The AMD User Experience Program Data Uploader service terminated unexpectedly. It has done this 1 time(s).
The AMDRyzenMasterDriverV27 service failed to start due to the following error:
The system cannot fi...
I am not a technician and I am not sure if those infomation above are helpful. After those errors quoted above, there came a TON of errors in later logs.
I am willing to provide more details to help if more are needed to investigate.
I am also facing same bsod issue on Ryzen ai 9 hx 370, 890m , after display driver update on 25-2-24, and i saw on reddit many users are facing same plz tell the solution
Also experience the bsod DPC_WATCHDOG_VIOLATION after installation of 25.3.1
HX 370 with 890M
25.4.1 is not much better, wont boot ;(
Have you updated the BIOS on the SER9 to the latest version?
I know this post is about the Adrenaline 25.3.1 driver causing a BSOD, but I just wanted to add that while I may not get the BSOD, my computer will hard lock sometime overnight after having the driver updated. I have 5 mini dumps in the last week that all points to the same watchdog problem.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8059c5c33b0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
This only happens with this driver.
I back revved to 24.12.1 but it keeps getting updated even though I have the auto update off. I had it where it would download the driver but not install the driver yet it keeps getting updated period. Now I'm going to turn off the auto download feature.
Also the 25.3 .1 driver also has another problem where it changes the desktop context sensitive menu improperly. One is that the Adrenaline driver option is not available in the menu whether you go on the main menu or "Show more options". The other issue is that when you click on Display Settings, it will change the desktop icons to large instead of opening up the system settings at the "Display Settings". It also has that problem where the Personalize menu option doesn't open up the system settings menu either. I have to go to "Show more options" to get to the Display Setting and Personalize options to work.
I have the exact same issue.
Beelink SER9 with an AMD Ryzen AI 9 HX370, Windows 11 24H2 (26100.3624)
When I install 25.3.1 it causes the system to completely hang, it won't even boot into Windows.
I have to boot into Safe Mode manually and restore/revert the system to 24.12.1 for it to work again.
Can just join you the last 2 weeks i had more bsod`s than 2024 in complete.
But even more annyoing this install manager i prevered the old system or at least an option dont show me updates when i dont want it privacy view 😄
I was able to install 25.3.1 without issue today after updating the SER9 to the latest firmware.
There must be a conflict between older firmware and current AMD drivers.
Do you mean the BIOS update published on 12/26/2024?
thanks.
I installed version V103_15_73 and my serial number starts with a Y.
If you jump on the Beelink support forums they can provide you with a direct link to the firmware you need - that's what I did.