cancel
Showing results for 
Search instead for 
Did you mean: 

PC Drivers & Software

lzq
Journeyman III

Can't play League of Legends

google translate:

I play League of Legends, click "Start Game", there may be a black screen within 3~10 seconds after entering the game room, then the display shows "No Signal". After the state lasted for about 10~15 seconds, the display resumed the signal. At the bottom of the Radeon Settings, there is a notification saying: "Default Radeon WattMan settings have been restored due to an unexpected system failure", while the desktop wallpaper becomes a mosaic. The display can't make any sound, the interface of the window program can't be fully rendered, and 80% of the place is black. Everything returned to normal after restarting the computer, but running the League of Legends again and entering the game room still has a 50% chance of experiencing the symptoms described earlier. The current driver version is 19.8.2, and the 19.8.1 driver does not have the symptoms described earlier.

Windows 10 1903
Radeon Software Adrenalin 2019 Edition 19.8.2
AMD Ryzen 7 3700X, Not overclocked
AMD Radeon RX 5700 XT 50th Anniversary, Default setting, Not overclocked
Corsair 3200Mhz 16G DDR4 (CMK32GX4M2B3200C16)
ASUS Prime X570 Pro, Latest version of BIOS

original:

我玩英雄联盟,点击“开始游戏”,进入游戏房间后的3~10秒之内有可能出现黑屏,接着显示器显示“无信号”。这种状态持续大约10~15秒后,显示器恢复了信号,Radeon Settings的底部有一条通知说:Default Radeon WattMan settings have been restored due to an unexpected system failure”,与此同时桌面壁纸变成了马赛克,显示器无法发出任何声音,窗口程序的界面也无法完全渲染,80%的地方都是黑色。重新启动计算机后一切恢复正常,但是再次运行英雄联盟并进入游戏房间依然有50%的几率出现前面描述症状。当前驱动程序版本是19.8.2,19.8.1版本驱动程序中没有前面所描述症状。

Windows 10 1903
Radeon™ Software Adrenalin 2019 Edition 19.8.2
AMD Ryzen™ 7 3700X,未超频
AMD Radeon™ RX 5700 XT 50th Anniversary,默认设置,未超频
海盗船 3200Mhz 16G DDR4(CMK32GX4M2B3200C16)
华硕Prime X570 Pro,最新版本的bios

0 Likes
2 Replies
vbueno
Journeyman III

I have de same problem... Has anyone helped you or had an answer from amd?

0 Likes
lzq
Journeyman III

google translate:

This problem did not recur after upgrading to 19.10.1

original:

升级到19.10.1后没有再出现这种问题

0 Likes