cancel
Showing results for 
Search instead for 
Did you mean: 

Drivers & Software

AMD Radeon 5700 RX Adrenaline 19.9.2 bricks windows boot

Jump to solution

Hello AMD peeps,

I need some help with a weird issue i have since yesterday (19 oct 2019). 

Shutdown pc normally, on bootup 20 oct, boot did not move past the Windows 10 logo with the spinning circle. Tried restore points, startup repair, even safe mode boot, nothing worked. Eventually resorted to a clean install of Windows 10. 

Upon installing the Adrenaline 19.9.2 Driver (on this 100% clean windows install, AMD Drivers were the first thing i did) the computer just shut down in the middle of the installation process. When trying to reboot, you guessed it, giving the same problem as it all started with (no boot). I repeated this process 2 times, even got it caught on camera the second time.

Pc is 1 month old, no problems so far, using a ROG B450-i Gaming Mobo, AMD Ryzen 2600X, never OCed, XMP off, all bios settings auto/default. 

Since this is my first pc build ever, i dont really know what to do or where to go for answers. I can do everything normally with the stock driver. But ofcourse i dont want to brick my windows (again) when trying future installs of Adrenaline software.

Hope you guys can help!

Thanks in advance

0 Kudos
1 Solution

Accepted Solutions

Re: AMD Radeon 5700 RX Adrenaline 19.9.2 bricks windows boot

Jump to solution

Fixed the problem - The GPU had a faulty screw tap where it is supposed to be fit to the casing. This caused the card to shift within the casing, resulting in a bad connection.

View solution in original post

0 Kudos
2 Replies

Re: AMD Radeon 5700 RX Adrenaline 19.9.2 bricks windows boot

Jump to solution

Update; tried the following Adrenalin drivers;

19.9.3

19.9.2

19.8.2

19.7.5

All still bricking my windows.

No idea how to fix this

0 Kudos

Re: AMD Radeon 5700 RX Adrenaline 19.9.2 bricks windows boot

Jump to solution

Fixed the problem - The GPU had a faulty screw tap where it is supposed to be fit to the casing. This caused the card to shift within the casing, resulting in a bad connection.

View solution in original post

0 Kudos