cancel
Showing results for 
Search instead for 
Did you mean: 

Drivers & Software

andrulko
Adept II

Black screen on the first Windows boot (Nitro+ RX 5700 XT)

My system specification:

  • AMD Graphics Card
    • SAPPHIRE NITRO+ RX 5700XT 8G GDDR6 (no overclocking, Adrenalin's tuning settings are set to "Automatic")
  • Desktop
  • Operating System
    • Windows 10 Pro 64bit (v2004 build 19041.208) 
  • Driver version installed
    • Adrenalin 2020 Edition 20.4.2
  • Display Devices
    • Samsung Curved C32HG70 (LC32HG70QQIXCI) 2560x1440 @144Hz DP (the same issue happens on HDMI)
  • Motherboard + Bios Revision
    • Gigabyte Z170-HD3 DDR3 (F21f BIOS, latest)
  • CPU/APU
    • Intel Core i5-6500 @3.20 GHz (no overclocking)
  • Power Supply Unit  Make, Model & Wattage
    • Chieftec Chieftronic Powerplay Gold GPU-750FC 750W (GPU is connected by 2 separate 6+2 pin cables, the same issue occurs with a single cable connected)
  • RAM
    • DIMM1: Kingston HyperX KHX1866C10D3/4G
    • DIMM2: Kingston HyperX KHX1866C10D3/4G
    • DIMM3: Kingston HyperX KHX1866C10D3/4G
    • DIMM4: Kingston HyperX KHX1866C10D3/4G
    • Total RAM: 16GB

 

Issue description:

I truly hope AMD team will spot this thread (contacting support directly doesn't work, they say black screens are fixed and it is my issue). So, starting from Adrenalin 20 I have black screens on first Windows boot in 95% cases. If there is no black screen, it will occur if I run Chrome for example (hardware acceleration is disabled, but even if I enable it the same thing will happen). Consequently, I have to reset PC and the 2nd boot takes 2-3 minutes, then everything works whole day. I don't play at this time, it's mostly work (Chrome/Skype/Slack/Zoom/OBS Studio 1440p demo recordings etc.).

I did not have similar issues with Adrenalin 19 but I don't want to revert since those random black screens make me crazy. I'm very happy with 20.4.2 driver, it's definitely a small win but it doesn't help with Windows first boot issue.

I'm very certain it is driver issue. Why? Because in the morning (~7:30am) I have uninstalled driver completelely using DDU. I have turned on PC in 8 hours and it has simply turned on and I'm writing this question. Basic driver is used currently (sorry, it's Ukrainian):

pastedImage_4.png

 

Because of GPU, I have already replaced PSU (I was using pretty good Aerocool VX-750, it's not the cheapest one), so it's definitely not a hardware issue and I truly believe (and hope ) my GPU doesn't have defects + again, no black screens on the first Windows boot on Adrenalin 19 (e.g 19.12.1).

My mobo is not very fresh so probably it's somehow linked with UEFI (I do have and use it) but it's not that easy to replace it as you may know, since I need to have new CPU + DDR4 RAM too

Am I the only person experiencing this issue? I was on Windows 10 (1909) but swtiched to 2004 to see whether it makes any difference. But no, black screen on boot is here too.

Will gladly answer any questions

1 Solution

Clearly your RX5700XT GPU choice was an easy upgrade and proved cheaper than just buying a 2070 Super.

View solution in original post

25 Replies
andrulko
Adept II

A quick update on the topic, I'm not sure what has helped exactly, but I'll describe all actions I did:

1) Turned off Freesync  in monitor settings (was using "Ultimate Engine" setting, switching to "Standard Engine" didn't make big difference;

pastedImage_1.png

2) Uninstalled Adrenalin 20.4.2 via DDU in safe mode;

3) Installed Radeon™ Pro Software for Enterprise 20.Q1.2 (it had ended with some error, display driver was installed and AMD Radeon Settings are working too

pastedImage_2.png

pastedImage_3.png

I turned off PC yesterday and turned it on in 4-5 hours. The first boot was successful, good! Today's morning, I've turned on PC again and it has launched successfully on the first boot too! I didn't try gaming (and seeems this revision is not intended for gaming) but at least I can work on PC.

If the PC will be running fine till Friday, I'll close this question.

Black screen has occurred today in the morning on the first boot with the following record in Event Viewer:

Log Name: System
Source: Service Control Manager
Date: 29.04.2020 9:49:51
Event ID: 7000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-PPKCC7R
Description:
Не вдалося запустити службу AMD External Events Utility через таку помилку:
The service did not respond to the start or control request in a timely fashion.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2020-04-29T06:49:51.8341264Z" />
<EventRecordID>3720</EventRecordID>
<Correlation />
<Execution ProcessID="896" ThreadID="940" />
<Channel>System</Channel>
<Computer>DESKTOP-PPKCC7R</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">AMD External Events Utility</Data>
<Data Name="param2">%%1053</Data>
<Binary>41004D0044002000450078007400650072006E0061006C0020004500760065006E007400730020005500740069006C006900740079000000</Binary>
</EventData>
</Event>

This is probably the first time Enterprise driver has crashed. I'll keep monitoring. It was a bit different black screen comparing to 20.4.2 driver. It was not instant, I've seen Windows log on screen, then monitor has blinked about 5 times and then I had to reset PC. Already working around 10 hours near PC without any crashes (Chrome/VPN/Zoom/Steam/OBS Studio). 

0 Likes
andrulko
Adept II

I have disabled PC around 12am yesterday and enabled it at 1:23PM. It took around 3 minutes to boot Windows (usually it happens after I reset PC on the first boot when black screen occurs). But I didn't have any issues with shutdown at night, thus I think that probably issue is linked more with shutdown rather than startup.

After Windows has loaded, I've opened Chrome and within a ~1 minutes screen was becoming black/white/green fast (it was flickering) for 20 secs, then black screen occured and I've reset the PC again. It is working now.

Extracted all events logs for today, so full picture of events is below:

KeywordsDate and TimeSourceEvent IDTask Category
Classic02.05.2020 13:31:22Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:31:22Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:31:22Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.SecurityAppBroker
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:29:29Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscCloudBackupProvider
and APPID
Unavailable
to the user DESKTOP-PPKCC7R\andru SID (S-1-5-21-550369304-1544700656-2868597353-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
02.05.2020 13:29:20Microsoft-Windows-DriverFrameworks-UserMode10111User-mode Driver problems.The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.
02.05.2020 13:29:20Microsoft-Windows-DriverFrameworks-UserMode10110User-mode Driver problems.A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.
Classic02.05.2020 13:29:07Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
to the user DESKTOP-PPKCC7R\andru SID (S-1-5-21-550369304-1544700656-2868597353-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:29:07Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
to the user DESKTOP-PPKCC7R\andru SID (S-1-5-21-550369304-1544700656-2868597353-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:29:07Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
to the user DESKTOP-PPKCC7R\andru SID (S-1-5-21-550369304-1544700656-2868597353-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:29:07Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
to the user DESKTOP-PPKCC7R\andru SID (S-1-5-21-550369304-1544700656-2868597353-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:29:06Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{21B896BF-008D-4D01-A27B-26061B960DD7}
and APPID
{03E09F3B-DCE4-44FE-A9CF-82D050827E1C}
to the user DESKTOP-PPKCC7R\andru SID (S-1-5-21-550369304-1544700656-2868597353-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:29:06Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:29:06Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:29:05Service Control Manager7000NoneНе вдалося запустити службу AMD External Events Utility через таку помилку:
The service did not respond to the start or control request in a timely fashion.
Classic02.05.2020 13:29:05Service Control Manager7009NoneВичерпано час очікування (45000 мс) для встановлення підключення служби AMD External Events Utility.
Classic02.05.2020 13:28:17BTHUSB34NoneЛокальний адаптер не підтримує важливий стан контролера низького енергоспоживання та не може забезпечувати роботу в режимі периферійних пристроїв. Мінімальна необхідна маска підтримуваних станів – 0x2491f7fffff, отримано 0x1fffffff. Функція ролі периферійних пристроїв низького енергоспоживання не буде доступна.
02.05.2020 13:28:17Microsoft-Windows-Kernel-PnP219(212)The driver \Driver\WudfRd failed to load for the device HID\VID_045E&PID_077F&MI_03&Col02\7&28633bd2&0&0001.
(70368744177664),(2)02.05.2020 13:28:14Microsoft-Windows-Kernel-Power41(63)The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Classic02.05.2020 13:28:14volmgr161NoneDump file creation failed due to error during dump creation.
Classic02.05.2020 13:28:20EventLog6008NoneThe previous system shutdown at 13:24:25 on ‎02.‎05.‎2020 was unexpected.
Classic02.05.2020 13:25:37Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscCloudBackupProvider
and APPID
Unavailable
to the user DESKTOP-PPKCC7R\andru SID (S-1-5-21-550369304-1544700656-2868597353-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
02.05.2020 13:25:25Microsoft-Windows-DriverFrameworks-UserMode10111User-mode Driver problems.The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem.
02.05.2020 13:25:25Microsoft-Windows-DriverFrameworks-UserMode10110User-mode Driver problems.A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.
Classic02.05.2020 13:25:21Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-PPKCC7R\andru SID (S-1-5-21-550369304-1544700656-2868597353-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:25:12Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
to the user DESKTOP-PPKCC7R\andru SID (S-1-5-21-550369304-1544700656-2868597353-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:25:12Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
to the user DESKTOP-PPKCC7R\andru SID (S-1-5-21-550369304-1544700656-2868597353-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:25:11Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
to the user DESKTOP-PPKCC7R\andru SID (S-1-5-21-550369304-1544700656-2868597353-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:25:11Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
to the user DESKTOP-PPKCC7R\andru SID (S-1-5-21-550369304-1544700656-2868597353-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:25:10Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{21B896BF-008D-4D01-A27B-26061B960DD7}
and APPID
{03E09F3B-DCE4-44FE-A9CF-82D050827E1C}
to the user DESKTOP-PPKCC7R\andru SID (S-1-5-21-550369304-1544700656-2868597353-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:25:10Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:25:10Microsoft-Windows-DistributedCOM10016NoneThe application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Classic02.05.2020 13:25:10Service Control Manager7000NoneНе вдалося запустити службу AMD External Events Utility через таку помилку:
The service did not respond to the start or control request in a timely fashion.
Classic02.05.2020 13:25:10Service Control Manager7009NoneВичерпано час очікування (45000 мс) для встановлення підключення служби AMD External Events Utility.
02.05.2020 13:24:23Microsoft-Windows-DriverFrameworks-UserMode10111User-mode Driver problems.The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.
02.05.2020 13:24:23Microsoft-Windows-DriverFrameworks-UserMode10110User-mode Driver problems.A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.
02.05.2020 13:23:19Microsoft-Windows-Kernel-PnP219(212)The driver \Driver\WudfRd failed to load for the device HID\VID_045E&PID_077F&MI_03&Col02\7&28633bd2&0&0001.
Classic02.05.2020 13:23:19BTHUSB34NoneЛокальний адаптер не підтримує важливий стан контролера низького енергоспоживання та не може забезпечувати роботу в режимі периферійних пристроїв. Мінімальна необхідна маска підтримуваних станів – 0x2491f7fffff, отримано 0x1fffffff. Функція ролі периферійних пристроїв низького енергоспоживання не буде доступна.
(70368744177664),(2)02.05.2020 13:23:17Microsoft-Windows-Kernel-Power41(63)The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Classic02.05.2020 13:24:25EventLog6008NoneThe previous system shutdown at 1:07:41 on ‎02.‎05.‎2020 was unexpected.
nordvargr
Adept III

Having similar issue from time to time, it only happens on cold boot, and to fix it I have to replug the DP cable and turn off/on my monitor, because otherwise I'm unable to chose my monitor's native resolution (2540x1440).

Will this ever be fixed? I doubt it. I guess we will have to learn to live with this - any many other - issues that are plaguing the "RDNA" infrastructure since its release...

Hmm, I didn't try replugging DP cable. I confirm, it's only about cold boot. My resolution is the same, running at 144Hz.

I truly hope that yes, since Enterprise drivers have already brought a way more stability for me (20.4.2 are pretty good but I get black screen on cold boot in 99% cases).

Ordered good-quaity DP 1.4, I think it will be delivered next week and I'll see how it goes. Replacing the cable has helped someone. Hardware is ok, I've been running Gigabyte PCI-Ex GeForce GT 1030 OC 2GB GDDR5 (64bit) (1265/6008) (DVI, HDMI) (GV-N1030OC-2GI) for 2 days without any issues but I wish working/playing on 5700XT.

It happened to me today - basically my PC cold-booted right into black screen. Then after I restarted the PC manually I couldn't chose my monitor's native resolution in Windows (2540x1440 was no showing up on the list) untill I replugged DP cable and turned off/on my monitor. Actually this is a very old issue, I have seen this in many prior Adrenalin revisions.

0 Likes

Hi,

How about Adrenalin 2019 12.2.1 GUI/UI + Adrenlin 2020 20.4.2. drivers updated in Windows device manager?

That is what I am running now.

It seems stable whereas Adrenalin 2020 20.4.2 crashes, and Relive Recording does not work properly either.

Thanks.

0 Likes

Do you mean 19.12.1? Just to make sure:

1) Uninstall everything using DDU;

2) Install Adrenalin 2019 19.12.1 + driver as usual;

3) Update display+audio driver via device manager manually, using drivers stored in C:\AMD\Win10-Radeon-Software-Adrenalin-2020-Edition-20.4.2-Apr23\Packages\Drivers ?


Since I've noticed that system behaves a bit different, I have just uninstalled Enterprise driver and installed 20.4.2 GUI + Driver back. If that fails to run on a cold boot in the morning, I'll try your kind suggestion, thanks!

I'm starting thinking it's somehow related with monitor (it was working good on R9 380 though for almost 1 month via HDMI). Let's see what DP 1.4 cable will do, can't wait to get it soon (most likely, it will be delivered this week finally)

Correct. I would reboot after 2) and make sure that Adrenalin 19.12.1 drivers seem to be working correctly firts, and then do 3) as you said above. 
Just in case anything goes wrong, make sure you run a full windows 7 type backup first and make sure you know how to boot into save mode on your PC just in case you get a black screen at boot.

I have been running well on RX Vega 64 Liquid now for a few days using Adrenalin 2019 19.12.1 GUI/UI and Adrenalin 2020 20.4.2 drivers.
OK?
I wish you luck.   

0 Likes
spartakus109
Journeyman III

This guy has the answer https://community.amd.com/thread/252387 

0 Likes

I'm running 5700XT since November. I didn't notice so many black screens earlier, they were random and not frequent. I remember that I've even finished Shadow of the Tomb Raider without any crashes, spending 4-5 hours in the game per day. But since quarantine, since I spend whole day near PC + AMD has delivered Adrenalin 20, these black screens became a disaster, especially when you have a videocall with customer (it's ok on the other hand, since you have 2-3 minutes to drink some water ).

I see many positive feedbacks on RX5700XT in the online store where it was bought, many people say everything is ok. It is everything about other hardware which interacts with GPU I think (motherboard first of all). On YouTube, you will also find many "solutions" but almost each consists of "disable this, enable this etc.", only few people resolved it by replacing PSU or cable, for example. All we want just to plug in GPU and work/play, of course.

 Thanks to 5700XT, my PC have experienced real evolution, so I truly believe AMD willl fix everything soon.

I had to ruin PC case, it was my first experience with 5700...

pastedImage_9.png

Decided to replace the case and PC cooler to achive better temps

pastedImage_11.png

Switched to another PSU

pastedImage_12.png

Finally, added more RAM (current setup)

pastedImage_13.png

Because of so many efforts and expenses, I won't give up yet. But after DP cable replacement, the only thing which is left if that won't work - hoping that AMD will make drivers better soon

Clearly your RX5700XT GPU choice was an easy upgrade and proved cheaper than just buying a 2070 Super.

You are completely right. I have saved probably $100 buying RX5700XT and have spent a bit more than $200 trying to make AMD thing work without big success!

Directed by Robert B. Weide

P.S. Connected my second old 23" monitor (LG D2342P) via HDMI. PC was off for over 4 hours and it is working for over 1 hour without any black screens! I don't plan keeping it though, one monitor is enough for me.

P.P.S. I wish AMD displaying black screen above instead of just black screen...

0 Likes
christiang
Adept III

Same problem with "radeon pro software"

0 Likes
andrulko
Adept II

Morning my time. First cold boot. The 2nd monitor is connected via HDMI and I'm using 20.4.2 driver. It works!

Opened Chrome, playing YouTube music on one screen and writing this message on another. No critical errors on boot according to Event Viewer.

Any ideas? Probably, 5700XT needs more load? Now I think that new DP 1.4 cable I'm waiting for won't help. On the other hand, I didn't try isolating pin 20 in current DP cable, so probably it's somehow linked with power.

What a crazy world!

0 Likes
andrulko
Adept II

It still works good on cold boot with 2 monitors connected. What I've noticed is that coolers are turning on more frequently (e.g. each 10 mins at ~1300RPM) but that's expected.

Also, when 1 monitor was connected VRAM was at ~300MHz mark and it was increasing when you watch video/play game/run videocall. Here is old screenshot:

pastedImage_2.png

Now it's at 1750MHz almost all the time:

pastedImage_3.png

I'll try it later when 2nd monitor will be disconnected but probably setting VRAM to 1750MHz manually will solve the problem with 1 monitor. We were looking at GPU clock all the time.

Also, it may be indeed DP-cable related issue.

UPD May 5th: Running just great, without single crash since morning. I don't need 2nd monitor for everyday usage but it's helpful during online work on quarantine. Patiently waiting for the next driver update + I'll raise another ticket to AMD asking why it works with 2 monitors. I've got impression that 5700XT simply needs heavy loads  Tomorrow, I'll try enabling Freesync (Ultimate Engine) to see whether it makes any difference and causes black screens

saulfernandez
Adept II

I have investigated about the serious situation that many present, black screen, audio video, not being able to install the software, not detecting gpu, etc. What I see completely feasible right now is to wait for the big windows update plus a week or two for the amd team to get familiar with it and get a new software update, drivers or whatever is necessary and thus be able to obtain a solution to all the big problems we have, this will take possibly 1 month from now, but it is the most viable and safe for amd to solve your problem, the key is the great update of windows, not our components that worked perfectly fine previously.

0 Likes
dimazda
Journeyman III

I don’t know if you solved the problem or not, but here is how I solved it.
It's not about the drivers, but in Windows.
Go to the Control Panel (Large Icons) -> Power Options -> Activate Power Buttons -> Change Settings That Are Not Available Now -> Uncheck "Enable Quick Launch"
It helped me !

---------------------------------------------------------------------------------

Я не знаю решил ли ты проблему или нет, но вот как решил ее я.
Дело не в драйверах, а в Виндовс.
Заходишь в Панель управления (Крупные значки) -> Электропитание -> Действие кнопок питания -> Изменение параметров которые сейчас не доступны -> Убрать галочку "Включить быстрый запуск"
Мне помогло!

I've read about such solution earlier, but I don't have such option unfortunately:

pastedImage_1.png

Most likely, that's because my motherboard is not so fresh. Fast boot is disabled on BIOS level but it did not make any difference.

---------------

Благодарю, но у меня такой опции нет. А вот с двумя экранами работает все, я еще заметил кое-что, опишу отдельным постом.

0 Likes

Uncheck "Enable Quick Launch" it worked on first boot. Thank you! (Radeon Pro Software)
0 Likes
andrulko
Adept II

I have finally reproduced good old black screen again! But on one monitor only, fortunately I did not have to reset PC during a videocall.

So, I have enabled Ultimate Engine for Freesync in monitor settings in the morning. It worked pretty fine for around 2 hours, then I had a meeting + 1140p recording at a time and after ~10 minutes I've encountered black screen on monitor with Freesync enabled. My 2nd old LG monitor doesn't support Freesync and I could still talk with another person, I could still work on LG monitor.

I have disabled Freesync in Samsung's monitor settings and within few seconds it started to work. I had another 3 meetings without any issues later on.

There is definitely some Freesync issue in 20.4.2 driver or just not the best compatibility with my monitor. I'll try "Standard Engine" monitor Freesync setting tomorrow.

andrulko
Adept II

In general, my system was very stable these days. I've managed to play some DOOM on Sunday, no crashes. No crashes on cold boot anymore, I don't even need to turn 2nd monitor on when starting PC, it's loading in any case. Main monitor is running in "Standard Engine" Freesync mode, I didn't have black screens.

But around 15 minutes ago, when lots of Chrome tabs were opened BSOD has occurred. Here are details:

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffc503613772c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80791750818, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\u0354308.inf_amd64_48534036afa0f0d8\B354265\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** WARNING: Unable to verify checksum for win32k.sys

BUGCHECK_CODE: 116

BUGCHECK_P1: ffffc503613772c0

BUGCHECK_P2: fffff80791750818

BUGCHECK_P3: ffffffffc0000001

BUGCHECK_P4: 3

PROCESS_NAME: System

SYMBOL_NAME: atikmpag+10818

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

FAILURE_ID_HASH: {e300aa8c-6915-3f37-7957-d2e4fc30a6fd}

Followup: MachineOwner
---------

I didn't encounter it for weeks, now it's here. Hope it's just one-time thing and I won't see it again. Probably, that's even somehow linked with Windows 10 2004 build, I think they already got a report from me

0 Likes

Здравствуйте! Можете сказать как решили? Я как понимаю у меня такая же проблема. Устанавливаю драйвер и все идет на ура. Как только перезагрузишься все ж*па полная. Зависает на загрузке,удаление драйвера помогает. 

Hello! Can you tell me how you decided? I understand that I have the same problem. I install the driver and everything goes off with a bang. As soon as you reboot, everyone has arrived. Hangs on loading, uninstalling the driver helps.

0 Likes

Привет! Я даже сам не знаю, что именно помогло, но наверное апрейд до Windows 10 2004 (Insider Preview) и подключение второго монитора. Ради интереса, когда компьютер будет "холодный" завтра с утра, попробую включить его без второго монитора и посмотрю, заработает ли. Я часто стартую даже без включения второго монитора (но он по HDMI подключен), поэтому может даже какой-то недавний апдейт Windows решил основную проблему с запуском и стабильностью. 28 мая ждем официальный релиз 2004 версии Windows, тогда установлю систему с нуля. Посмотрите также посты выше, я заметил что с 2 мониторами частота памяти автоматически увеличилась.

Hey! I think that Windows 10 2004 + 2nd monitor have solved cold boot and stability issue. I'll try running PC without 2nd monitor connected tomorrow. I don't even need to turn 2nd monitor on, it works in any case. Windows 10 2004 should be released officially after May 28th 2020, I'll install fresh copy and quit Insider Preview.

0 Likes

Hi guys! 

Did anyone manage to solve this issue yet?

My system worked fine for months, and all the sudden this happened. Out of nowhere, first boot of the day.

Going into safe mode and uninstalling the drivers, "fixes" the problem. But as soon as I install any version of the drivers, it goes black at the end of installation (before restart).

I only have one monitor. And my Windows is not version 2004.

Please help me if you found a solution, anyone.

0 Likes