PC Graphics

[pogosoco]

I don't even know where to start by typing this up ... it's been A pure nightmare and hell ... so I built 2 new pcs like 30 days ago exactly , the specs for both pc's are matching parts

CPUs - Ryzen 5 3600X / AFM Cooler = Noctua NH-D15
GPUs - Sapphire Nitro + RGB Edition  RX5700XT

MOBOs - Asus X470-F ROG Strix
RAMs - G.Skill RipJaws F4-3200C14D-16GVK 16GB 2x8
PSU - Seasonic FOCUS Plus 750 Gold SSR-750FX 750W
HD/SSD -  SAMSuNG 970 EVO NVMe M.2 SSD 1TB
Windows 10 PRO oh yeahhhhh soooooo proooooooooooooooooooooo allllll i doooooooo issss crashhhhhhhhhhhhhhhhhhhh

pc's & parts are Brand New , No previous video drivers or models were installed , Factory fresh builds/installs
Both suffering same issues , Current date 5/27/2020 @ driver versions 20.4.2 made the pcs become unusable and now even rolling back to older drivers I.E 20.2.2 // 19.12.1 or any driver , instant crashes and black screens when entering any game or doing anything , moving my mouse now causes the driver to restart ... even installing driver through Device Manager VIA skipping addrenaline install ofcourse running DDU in safe mode first etc / restart with internet off doing everything right . this is flat out AMD driver / card sided , nothing else in our PCS can be causing this .. so many people are plagued by issues with these amd cards right now and it really honestly feels like nothing at all is being done , I can't even contact newegg to get help or anybody for help .. I can't even return the card to newegg because it says it's 1day past return date ... and I can't call them to tell them I only waited 1 more day to see if this bs driver fixed anything but all it did was make our pcs 100x worse than yesterday  like no joke I can't do anything now .. reinstalling old drivers do no good for me anymore .. im crashing on everything and anything I Really don't know what to do other than just throew the card in the trash I mean I'm not A rich person or can afford to do that but I really don't know what else to do I don't even know how to get help or if there really is any help .. there obviously isn't any help , this is just so sad This was the first ATI card I ever purchased and I have been playing pc games for 20 years since I was 12 , my first good Nvidia card was A Nvidia 6800GT back in the AGP card days .. and sadly I really think that card was better than this $450 x 2 = 900 + tax @  soon to be paper weights.. Is there even any real workerss on this forum to help ?? where can I get actual help

Black screens / crashes / hanging / bs / failing drivers all drivers and bunk where can i get help or A replacement what do I DOOOOO

[morelock]

I'm not normally a "jump ship" kind of guy, but that said.
You've got a very nice/desirable 5700xt (Nitro+rgb) - sell it, you shouldn't have any issue getting a buyer currently. Buy the best Nvidia GPU can for whatever $ you get out of it.
I know that's not an ideal solution, you bought the 5700xt for a reason. Still... at a certain point (by the way your post was worded it sounds like you've found that point) you really start disliking the card, and likely even if every issue was fixed tomorrow, you'd still question / second guess / resent it in the future. Sometimes it really is best just to cut your losses and try another route. 

Whatever you choose, I wish you luck. Frustrating when a new build doesn't work right.

[blitz]

5700xt is the worst card i have ever owned and i been gaming for 20 years

[pogosoco]

UPDATE / AFter running DDU multiple times as well as AMDutility and ridding of the new plagued driver 20.4.2 (WHQL) and going back to 20.2.2 (WHQL) I am able to play WoW again and set my fan settings in ATi driver without causing crash or errors , before I would run 5 feet in wow or so and the driver crash would trigger on the new driver .. I was fine just last night with 20.2.2 and went to 20.4.2 and that's when all the issues surfaced again.. I really hope they get this ffixed soon... like officially please do more testing and fixes for my components and games . The performance in league of legends is still Crap tbh..

[pogosoco]

Please just forreal AMD if anyone reads this post / thread please get these issues fixed , I'm gonna hold onto the card and remain on 20.2.2 until I forsure know things are working .. I will wait patiently for A fix just please do it

[Anonymous]

Mir geht es genauso, ich hatte mehr NVidea von der 200er, die Radeon HD7750, die 770er bis zur 970er und nie solche Probleme wie jetzt. Wobei die Radeon 7750 HD ein sehr gutes Preis-Leistungs-Verhältnis hatte wie meine anderen übrigens auch. 

[pogosoco]

Update 3 .. crashed again and keeps coming back ... confirmed problems came after installation of new driver released yesterday..now can't get rly any driver to remain stable

[Earnhardt]

Sorry to hear,I have had the STRIX 5700XT OC since October and have never had a crash or black screen on any drivers to date.Hope you get your system figured out.

[_y_]

I feel your pain ... have a 5700XT, for compatibility reasons I combined it with all AMD hw ... x570 chipset, amd ryzen. I even bought same brands (Gigabyte AORUS series). And still ... crash crash.

PC was assembled around january 2020, started off with Battlefield randomly crashing, rebooting etc. Went back to the 19.12.1 drivers which solved my issues ... until I started playing Warzone. It crashed constantly, I also experiences black screens with Starcraft 2. Warzone is stable on the 20.4.1 drivers (Battlefield still crashing).

Now installing 20.5.1, hope I can play both with the same driver set :-)

I dont expect much since this is still in the known issues list:

Some users may still experience black screen or system hang issues during extended periods of gameplay. AMD will continue to monitor and investigate reports of these issues closely.

[Anonymous]

Leider ist das bei 20.11.2 und 5700XT immer noch so. Ich habe auch alles von Gigabyte Aorus , bis auf die CPU  (Ryzen Threadripper 1900X 8Core) natürlich und das seit November 2020

[flashback_tr]

You are right to say about rx 5700xt. I have also Sapphire rx 5700xt nitro+ and have same problems. I tried everything mainboard bios update, chipset driver update and every gpu driver from 19.12.1 to 20.5.1. I can play BF5 and WWZ but can not play warzone with 19.12.1..But when i updated driver, i can not play any games. Even i rolled back the driver i cant play most of the games. Besides, i started to see some strange random points and artifact on the windows screen also with latest driver. I decided to send the graphic card to sapphire service. If i have i change to take my money, i will never ever buy radeon graphic card.

[rj2736]

It started out OK. For about 2 days.

Now this piece pof brand new all-AMD crap crashes multiple times a day.

RX 5700 XT

 AMD Ryzen 5 3600

NEVER NEVER NEVER buy crap from AMD.

Unreliable, noisy utter **bleep** crap.

Rot in hell AMD. Blasted thieves.

[rj2736]

What if any, is the reason this piece of **bleep** fails to resume from sleep. What is the problem Mr. A f**king MD ?

n 12 11:35:01 zen CRON[4950]: pam_unix(cron:session): session opened for user root by (uid=0)
jan 12 11:35:01 zen CRON[4952]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
jan 12 11:35:01 zen CRON[4950]: pam_unix(cron:session): session closed for user root
jan 12 11:45:01 zen CRON[5067]: pam_unix(cron:session): session opened for user root by (uid=0)
jan 12 11:45:01 zen CRON[5068]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
jan 12 11:45:01 zen CRON[5067]: pam_unix(cron:session): session closed for user root
jan 12 11:48:42 zen NetworkManager[879]: <info> [1610448522.1342] manager: sleep: sleep requested (sleeping: no enabled: yes)
jan 12 11:48:42 zen NetworkManager[879]: <info> [1610448522.1343] manager: NetworkManager state is now ASLEEP
jan 12 11:48:42 zen NetworkManager[879]: <info> [1610448522.1346] device (enp37s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
jan 12 11:48:42 zen whoopsie[1347]: [11:48:42] offline
jan 12 11:48:42 zen dbus-daemon[878]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=879 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
jan 12 11:48:42 zen systemd[1]: Starting Network Manager Script Dispatcher Service...
jan 12 11:48:42 zen dbus-daemon[878]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
jan 12 11:48:42 zen systemd[1]: Started Network Manager Script Dispatcher Service.
jan 12 11:48:42 zen NetworkManager[879]: <info> [1610448522.1636] device (enp37s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
jan 12 11:48:42 zen avahi-daemon[872]: Withdrawing address record for 10.1.1.2 on enp37s0.
jan 12 11:48:42 zen avahi-daemon[872]: Leaving mDNS multicast group on interface enp37s0.IPv4 with address 10.1.1.2.
jan 12 11:48:42 zen avahi-daemon[872]: Interface enp37s0.IPv4 no longer relevant for mDNS.
jan 12 11:48:42 zen NetworkManager[879]: <info> [1610448522.1877] device (enp37s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
jan 12 11:48:42 zen kernel: r8169 0000:25:00.0 enp37s0: Link is Down
jan 12 11:48:42 zen dnsmasq[1156]: reading /etc/resolv.conf
jan 12 11:48:42 zen nm-dispatcher[5119]: run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory
jan 12 11:48:42 zen dnsmasq[1156]: using nameserver 127.0.0.53#53
jan 12 11:48:42 zen dnsmasq[1156]: reading /etc/resolv.conf
jan 12 11:48:42 zen dnsmasq[1156]: using nameserver 127.0.0.53#53
jan 12 11:48:52 zen systemd[1]: NetworkManager-dispatcher.service: Succeeded.
jan 12 11:49:12 zen systemd-logind[915]: Delay lock is active (UID 10020/rj, PID 2168/xfce4-screensav) but inhibitor timeout is reached.
jan 12 11:49:12 zen systemd[1]: Reached target Sleep.
jan 12 11:49:12 zen systemd[1]: Starting Suspend...
jan 12 11:49:12 zen systemd-sleep[5138]: Suspending system...
jan 12 11:49:12 zen kernel: PM: suspend entry (deep)
-- Reboot --
jan 12 15:12:30 zen kernel: Linux version 5.4.0-60-generic (buildd@lgw01-amd64-001) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #67-Ubuntu SMP Tue Jan 5 18:31:36 UTC 2021 (Ubuntu 5.4.0-60.67-generic 5.4.78)
jan 12 15:12:30 zen kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-60-generic root=UUID=830cddc1-febd-4d3d-943f-b4fb1afe82bd ro noquiet nosplash amdgpu.ppfeaturemask=0xffffffff
jan 12 15:12:30 zen kernel: KERNEL supported cpus:
jan 12 15:12:30 zen kernel: Intel GenuineIntel
jan 12 15:12:30 zen kernel: AMD AuthenticAMD
jan 12 15:12:30 zen kernel: Hygon HygonGenuine
jan 12 15:12:30 zen kernel: Centaur CentaurHauls
jan 12 15:12:30 zen kernel: zhaoxin Shanghai
jan 12 15:12:30 zen kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
jan 12 15:12:30 zen kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
jan 12 15:12:30 zen kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'

Please analyse tyhe above **bleep** and point out the e xact error for me. I cant find it ...

ASSWIPE CRAP COMPANY

[rj2736]

Yet another AMD bleep up an 17 09:50:00 zen NetworkManager[918]: [1610873400.0451] manager: sleep: sleep requested (sleeping: no enabled: yes) jan 17 09:50:00 zen NetworkManager[918]: [1610873400.0452] manager: NetworkManager state is now ASLEEP jan 17 09:50:00 zen NetworkManager[918]: [1610873400.0454] device (enp37s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') jan 17 09:50:00 zen whoopsie[1700]: [09:50:00] offline jan 17 09:50:00 zen dbus-daemon[917]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=918 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") jan 17 09:50:00 zen systemd[1]: Starting Network Manager Script Dispatcher Service... jan 17 09:50:00 zen dbus-daemon[917]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' jan 17 09:50:00 zen systemd[1]: Started Network Manager Script Dispatcher Service. jan 17 09:50:00 zen NetworkManager[918]: [1610873400.0832] device (enp37s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') jan 17 09:50:00 zen avahi-daemon[911]: Withdrawing address record for 10.1.1.2 on enp37s0. jan 17 09:50:00 zen avahi-daemon[911]: Leaving mDNS multicast group on interface enp37s0.IPv4 with address 10.1.1.2. jan 17 09:50:00 zen avahi-daemon[911]: Interface enp37s0.IPv4 no longer relevant for mDNS. jan 17 09:50:00 zen NetworkManager[918]: [1610873400.1089] device (enp37s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') jan 17 09:50:00 zen dnsmasq[1189]: reading /etc/resolv.conf jan 17 09:50:00 zen nm-dispatcher[32053]: run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory jan 17 09:50:00 zen kernel: r8169 0000:25:00.0 enp37s0: Link is Down jan 17 09:50:00 zen dnsmasq[1189]: using nameserver 127.0.0.53#53 jan 17 09:50:00 zen dnsmasq[1189]: reading /etc/resolv.conf jan 17 09:50:00 zen dnsmasq[1189]: using nameserver 127.0.0.53#53 jan 17 09:50:10 zen systemd[1]: NetworkManager-dispatcher.service: Succeeded. jan 17 09:50:30 zen systemd-logind[944]: Delay lock is active (UID 10020/rj, PID 1929/xfce4-screensav) but inhibitor timeout is reached. jan 17 09:50:30 zen systemd[1]: Reached target Sleep. jan 17 09:50:30 zen systemd[1]: Starting Suspend... jan 17 09:50:30 zen systemd-sleep[32074]: Suspending system... jan 17 09:50:30 zen kernel: PM: suspend entry (deep) -- Reboot -- jan 17 12:52:34 zen kernel: Linux version 5.4.0-62-generic (buildd@lgw01-amd64-045) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #70-Ubuntu SMP Tue Jan 12 12:45:47 UTC 2021 (Ubuntu 5.4.0-62.70-generic 5.4.78) jan 17 12:52:34 zen kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-62-generic root=UUID=830cddc1-febd-4d3d-943f-b4fb1afe82bd ro noquiet nosplash amdgpu.ppfeaturemask=0xffffffff jan 17 12:52:34 zen kernel: KERNEL supported cpus: jan 17 12:52:34 zen kernel: Intel GenuineIntel jan 17 12:52:34 zen kernel: AMD AuthenticAMD jan 17 12:52:34 zen kernel: Hygon HygonGenuine jan 17 12:52:34 zen kernel: Centaur CentaurHauls jan 17 12:52:34 zen kernel: zhaoxin Shanghai jan 17 12:52:34 zen kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' jan 17 12:52:34 zen kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' jan 17 12:52:34 zen kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' jan 17 12:52:34 zen kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 jan 17 12:52:34 zen kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format. jan 17 12:52:34 zen kernel: BIOS-provided physical RAM map: jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009d81fff] usable jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x0000000009d82000-0x0000000009ffffff] reserved jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20bfff] ACPI NVS jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x000000000a20c000-0x000000000affffff] usable jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000eb7fdfff] usable jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x00000000eb7fe000-0x00000000eb947fff] reserved jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x00000000eb948000-0x00000000ebdc8fff] usable jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x00000000ebdc9000-0x00000000ebedafff] ACPI NVS jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x00000000ebedb000-0x00000000ecb10fff] reserved jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x00000000ecb11000-0x00000000eeffffff] usable jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x00000000ef000000-0x00000000efffffff] reserved jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000ffffffff] reserved jan 17 12:52:34 zen kernel: BIOS-e820: [mem 0x0000000100000000-0x000000080f37ffff] usable jan 17 12:52:34 zen kernel: NX (Execute Disable) protection: active jan 17 12:52:34 zen kernel: e820: update [mem 0xe7c24018-0xe7c32057] usable ==> usable jan 17 12:52:34 zen kernel: e820: update [mem 0xe7c24018-0xe7c32057] usable ==> usable jan 17 12:52:34 zen kernel: e820: update [mem 0xe7c0a018-0xe7c23457] usable ==> usable jan 17 12:52:34 zen kernel: e820: update [mem 0xe7c0a018-0xe7c23457] usable ==> usable jan 17 12:52:34 zen kernel: extended physical RAM map: jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x0000000000100000-0x0000000009d81fff] usable jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x0000000009d82000-0x0000000009ffffff] reserved jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x000000000a000000-0x000000000a1fffff] usable jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x000000000a200000-0x000000000a20bfff] ACPI NVS jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x000000000a20c000-0x000000000affffff] usable jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x000000000b000000-0x000000000b01ffff] reserved jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x000000000b020000-0x00000000e7c0a017] usable jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x00000000e7c0a018-0x00000000e7c23457] usable jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x00000000e7c23458-0x00000000e7c24017] usable jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x00000000e7c24018-0x00000000e7c32057] usable jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x00000000e7c32058-0x00000000eb7fdfff] usable jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x00000000eb7fe000-0x00000000eb947fff] reserved jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x00000000eb948000-0x00000000ebdc8fff] usable jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x00000000ebdc9000-0x00000000ebedafff] ACPI NVS jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x00000000ebedb000-0x00000000ecb10fff] reserved jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x00000000ecb11000-0x00000000eeffffff] usable jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x00000000ef000000-0x00000000efffffff] reserved jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x00000000f8000000-0x00000000fbffffff] reserved jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x00000000fd000000-0x00000000ffffffff] reserved jan 17 12:52:34 zen kernel: reserve setup_data: [mem 0x0000000100000000-0x000000080f37ffff] usable jan 17 12:52:34 zen kernel: efi: EFI v2.70 by American Megatrends jan 17 12:52:34 zen kernel: efi: ACPI 2.0=0xebe58000 ACPI=0xebe58000 SMBIOS=0xec955000 MEMATTR=0xe94fe698 ESRT=0xe94fff98 jan 17 12:52:34 zen kernel: secureboot: Secure boot disabled jan 17 12:52:34 zen kernel: SMBIOS 2.8 present. jan 17 12:52:34 zen kernel: DMI: Micro-Star International Co., Ltd. MS-7C52/B450M-A PRO MAX (MS-7C52), BIOS 3.40 01/22/2020 jan 17 12:52:34 zen kernel: tsc: Fast TSC calibration using PIT jan 17 12:52:34 zen kernel: tsc: Detected 3600.111 MHz processor jan 17 12:52:34 zen kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved jan 17 12:52:34 zen kernel: e820: remove [mem 0x000a0000-0x000fffff] usable jan 17 12:52:34 zen kernel: last_pfn = 0x80f380 max_arch_pfn = 0x400000000 jan 17 12:52:34 zen kernel: MTRR default type: uncachable jan 17 12:52:34 zen kernel: MTRR fixed ranges enabled: jan 17 12:52:34 zen kernel: 00000-9FFFF write-back jan 17 12:52:34 zen kernel: A0000-BFFFF write-through jan 17 12:52:34 zen kernel: C0000-DFFFF uncachable jan 17 12:52:34 zen kernel: E0000-FFFFF write-protect jan 17 12:52:34 zen kernel: MTRR variable ranges enabled: jan 17 12:52:34 zen kernel: 0 base 000000000000 mask FFFF80000000 write-back jan 17 12:52:34 zen kernel: 1 base 000080000000 mask FFFFC0000000 write-back jan 17 12:52:34 zen kernel: 2 base 0000C0000000 mask FFFFE0000000 write-back jan 17 12:52:34 zen kernel: 3 base 0000E0000000 mask FFFFF0000000 write-back jan 17 12:52:34 zen kernel: 4 base 0000EC260000 mask FFFFFFFF0000 uncachable jan 17 12:52:34 zen kernel: 5 disabled jan 17 12:52:34 zen kernel: 6 disabled jan 17 12:52:34 zen kernel: 7 disabled jan 17 12:52:34 zen kernel: TOM2: 0000000810000000 aka 33024M jan 17 12:52:34 zen kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT jan 17 12:52:34 zen kernel: total RAM covered: 3839M jan 17 12:52:34 zen kernel: Found optimal setting for mtrr clean up jan 17 12:52:34 zen kernel: gran_size: 64K chunk_size: 64M num_reg: 5 lose cover RAM: 0G jan 17 12:52:34 zen kernel: e820: update [mem 0xec260000-0xec26ffff] usable ==> reserved jan 17 12:52:34 zen kernel: e820: update [mem 0xf0000000-0xffffffff] usable ==> reserved jan 17 12:52:34 zen kernel: last_pfn = 0xef000 max_arch_pfn = 0x400000000 jan 17 12:52:34 zen kernel: esrt: Reserving ESRT space from 0x00000000e94fff98 to 0x00000000e94fffd0. jan 17 12:52:34 zen kernel: e820: update [mem 0xe94ff000-0xe94fffff] usable ==> reserved jan 17 12:52:34 zen kernel: check: Scanning 1 areas for low memory corruption jan 17 12:52:34 zen kernel: Using GB pages for direct mapping jan 17 12:52:34 zen kernel: secureboot: Secure boot disabled jan 17 12:52:34 zen kernel: RAMDISK: [mem 0x3a0e0000-0x3d48ffff] jan 17 12:52:34 zen kernel: ACPI: Early table checksum verification disabled jan 17 12:52:34 zen kernel: ACPI: RSDP 0x00000000EBE58000 000024 (v02 ALASKA) jan 17 12:52:34 zen kernel: ACPI: XSDT 0x00000000EBE580A0 0000BC (v01 ALASKA A M I 01072009 AMI 00010013) jan 17 12:52:34 zen kernel: ACPI: FACP 0x00000000EBE5FBB0 000114 (v06 ALASKA A M I 01072009 AMI 00010013) jan 17 12:52:34 zen kernel: ACPI: DSDT 0x00000000EBE581F0 0079BB (v02 ALASKA A M I 01072009 INTL 20120913) jan 17 12:52:34 zen kernel: ACPI: FACS 0x00000000EBEC4E00 000040 jan 17 12:52:34 zen kernel: ACPI: APIC 0x00000000EBE5FCC8 00015E (v03 ALASKA A M I 01072009 AMI 00010013) jan 17 12:52:34 zen kernel: ACPI: FPDT 0x00000000EBE5FE28 000044 (v01 ALASKA A M I 01072009 AMI 00010013) jan 17 12:52:34 zen kernel: ACPI: FIDT 0x00000000EBE5FE70 00009C (v01 ALASKA A M I 01072009 AMI 00010013) jan 17 12:52:34 zen kernel: ACPI: SSDT 0x00000000EBE5FF10 0000C8 (v02 ALASKA CPUSSDT 01072009 AMI 01072009) jan 17 12:52:34 zen kernel: ACPI: SSDT 0x00000000EBE5FFD8 008C98 (v02 AMD AMD ALIB 00000002 MSFT 04000000) jan 17 12:52:34 zen kernel: ACPI: SSDT 0x00000000EBE68C70 00366B (v01 AMD AMD AOD 00000001 INTL 20120913) jan 17 12:52:34 zen kernel: ACPI: MCFG 0x00000000EBE6C2E0 00003C (v01 ALASKA A M I 01072009 MSFT 00010013) jan 17 12:52:34 zen kernel: ACPI: HPET 0x00000000EBE6C320 000038 (v01 ALASKA A M I 01072009 AMI 00000005) jan 17 12:52:34 zen kernel: ACPI: UEFI 0x00000000EBE6C358 000042 (v01 ALASKA A M I 00000002 01000013) jan 17 12:52:34 zen kernel: ACPI: VFCT 0x00000000EBE6C3A0 00E884 (v01 ALASKA A M I 00000001 AMD 31504F47) jan 17 12:52:34 zen kernel: ACPI: IVRS 0x00000000EBE7AC28 0000D0 (v02 AMD AMD IVRS 00000001 AMD 00000000) jan 17 12:52:34 zen kernel: ACPI: PCCT 0x00000000EBE7ACF8 00006E (v01 AMD AMD PCCT 00000001 AMD 00000000) jan 17 12:52:34 zen kernel: ACPI: SSDT 0x00000000EBE7AD68 002F29 (v01 AMD AMD CPU 00000001 AMD 00000001) jan 17 12:52:34 zen kernel: ACPI: CRAT 0x00000000EBE7DC98 000B58 (v01 AMD AMD CRAT 00000001 AMD 00000001) jan 17 12:52:34 zen kernel: ACPI: CDIT 0x00000000EBE7E7F0 000029 (v01 AMD AMD CDIT 00000001 AMD 00000001) jan 17 12:52:34 zen kernel: ACPI: SSDT 0x00000000EBE7E820 001D4A (v01 AMD AmdTable 00000001 INTL 20120913) jan 17 12:52:34 zen kernel: ACPI: SSDT 0x00000000EBE80570 0000BF (v01 AMD AMD PT 00001000 INTL 20120913) jan 17 12:52:34 zen kernel: ACPI: WSMT 0x00000000EBE80630 000028 (v01 ALASKA A M I 01072009 AMI 00010013) jan 17 12:52:34 zen kernel: ACPI: Local APIC address 0xfee00000 jan 17 12:52:34 zen kernel: No NUMA configuration found jan 17 12:52:34 zen kernel: Faking a node at [mem 0x0000000000000000-0x000000080f37ffff] jan 17 12:52:34 zen kernel: NODE_DATA(0) allocated [mem 0x80f355000-0x80f37ffff] jan 17 12:52:34 zen kernel: Zone ranges: jan 17 12:52:34 zen kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff] jan 17 12:52:34 zen kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff] jan 17 12:52:34 zen kernel: Normal [mem 0x0000000100000000-0x000000080f37ffff] jan 17 12:52:34 zen kernel: Device empty jan 17 12:52:34 zen kernel: Movable zone start for each node jan 17 12:52:34 zen kernel: Early memory node ranges jan 17 12:52:34 zen kernel: node 0: [mem 0x0000000000001000-0x000000000009ffff] jan 17 12:52:34 zen kernel: node 0: [mem 0x0000000000100000-0x0000000009d81fff] jan 17 12:52:34 zen kernel: node 0: [mem 0x000000000a000000-0x000000000a1fffff] jan 17 12:52:34 zen kernel: node 0: [mem 0x000000000a20c000-0x000000000affffff] jan 17 12:52:34 zen kernel: node 0: [mem 0x000000000b020000-0x00000000eb7fdfff] jan 17 12:52:34 zen kernel: node 0: [mem 0x00000000eb948000-0x00000000ebdc8fff] jan 17 12:52:34 zen kernel: node 0: [mem 0x00000000ecb11000-0x00000000eeffffff] jan 17 12:52:34 zen kernel: node 0: [mem 0x0000000100000000-0x000000080f37ffff] jan 17 12:52:34 zen kernel: Zeroed struct page in unavailable ranges: 11805 pages jan 17 12:52:34 zen kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000080f37ffff] jan 17 12:52:34 zen kernel: On node 0 totalpages: 8376803 jan 17 12:52:34 zen kernel: DMA zone: 64 pages used for memmap jan 17 12:52:34 zen kernel: DMA zone: 26 pages reserved jan 17 12:52:34 zen kernel: DMA zone: 3999 pages, LIFO batch:0 jan 17 12:52:34 zen kernel:

[Anonymous]

Nicht ganz so krass habe ich schon vor Ärger gepostet, bei den Preisen tut AMD so, als ob denen die Probleme nichts angeht. GaGa!!!

[Anonymous]

Hallo, ich habe eine Problemlösung gegoogelt:https://www.reddit.com/r/Amd/comments/cf111o/fixes_propably_a_lot_of_issues_with_rx_5700_rx/

und folgendes gemacht 

1.Im Bios den PCI Express der Grafikkarte von Auto auf GEN 3 gestellt.

2.Freesync, Anti-Lag deaktiviert in der Radeon Software und 3.Die Framerate habe ich begrenzt

Das Hauptproblem ist wohl das Windows nicht mit dem PCI Express 4 richtig was mit anfangen kann!

Seitdem kein Absturz mehr !!!

[rj2736]

Is anybody at AMD actually still looking into this. It seems this is not a new card. It is a three year old card that still fails. Is this yet another MAJOR AMERICAN MICRO**bleep** **bleep**UP ???

YES .. IT IS ..

THIS CARD WILL NEVER WORK AND AMD KNOWS IT..

**bleep**ING AMERICAN BASTARDS !!! **bleep** YOU ALL OVER

**bleep**BAGS

**bleep** YOU

**bleep** YOU

[rj2736]

Any chance that this three year old piece of junk will actually work wothout locking up for longer than a single day ... ant time in the future ??

Deart AMD, please advise on which card I need to replace this piece of hopelessly broken junk: AMD RX 5700 GPU

[Matrixx]

Dear, can I ask you how you have configured the memories? At what speed do you have them configured? Do you have the XMP profile enabled? I have opened a post today called RX5700XT + Drivers, read it and tell me. a greeting

[rj2736]

I haven't configured anything. No overclocking etc. I'm afraid I don't know what XMP is in this context. Just put system in suspend and every other resume it something fails. This morning's failure:

an 29 09:12:12 zen kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=3926517, emitted seq=3926519
jan 29 09:12:12 zen kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0
jan 29 09:12:12 zen kernel: amdgpu 0000:2b:00.0: amdgpu: GPU reset begin!
jan 29 09:12:17 zen systemd[1]: NetworkManager-dispatcher.service: Succeeded.
jan 29 09:12:17 zen systemd-resolved[851]: Using degraded feature set (UDP) for DNS server 10.1.1.1.
jan 29 09:12:17 zen kernel: general protection fault: 0000 [#1] SMP NOPTI
jan 29 09:12:17 zen kernel: CPU: 4 PID: 25853 Comm: kworker/4:0 Tainted: G OE 5.4.0-65-generic #73-Ubuntu
jan 29 09:12:17 zen kernel: Hardware name: Micro-Star International Co., Ltd. MS-7C52/B450M-A PRO MAX (MS-7C52), BIOS 3.40 01/22/2020
jan 29 09:12:17 zen kernel: Workqueue: events drm_sched_job_timedout [amd_sched]
jan 29 09:12:17 zen kernel: RIP: 0010:mutex_lock+0x1e/0x40
jan 29 09:12:17 zen kernel: Code: c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 49 89 fc e8 8d de ff ff 31 c0 65 48 8b 14 25 c0 6b 01 00 <f0> 49 0f b1 14 24 74 08 4c 89 e7 e8 b2 ff ff ff 41 5c 5d c3 66 66
jan 29 09:12:17 zen kernel: RSP: 0018:ffffafee48427c88 EFLAGS: 00010246
jan 29 09:12:17 zen kernel: RAX: 0000000000000000 RBX: 87e828cdf86bc547 RCX: 0000000000000000
jan 29 09:12:17 zen kernel: RDX: ffff99410f629740 RSI: 0000000000000004 RDI: ffff9941ee92adc0
jan 29 09:12:17 zen kernel: RBP: ffffafee48427c90 R08: 0000000000000085 R09: 0000000002e64586
jan 29 09:12:17 zen kernel: R10: 0000000002e64586 R11: 0000000000000000 R12: 87e828cdf86bc6b7
jan 29 09:12:17 zen kernel: R13: 87e828cdf86bc6b7 R14: ffff9941e2d00000 R15: ffff9941ea0d50b0
jan 29 09:12:17 zen kernel: FS: 0000000000000000(0000) GS:ffff9941ee900000(0000) knlGS:0000000000000000
jan 29 09:12:17 zen kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
jan 29 09:12:17 zen kernel: CR2: 000055aaa371f010 CR3: 00000007b5e28000 CR4: 0000000000340ee0
jan 29 09:12:17 zen kernel: Call Trace:
jan 29 09:12:17 zen kernel: kfd_gtt_sa_free+0x2d/0x90 [amdgpu]
jan 29 09:12:17 zen kernel: kernel_queue_uninit+0x4e/0x100 [amdgpu]
jan 29 09:12:17 zen kernel: pm_uninit+0x16/0x20 [amdgpu]
jan 29 09:12:17 zen kernel: stop_cpsch+0xa7/0xd0 [amdgpu]
jan 29 09:12:17 zen kernel: kgd2kfd_suspend.part.0+0x35/0x50 [amdgpu]
jan 29 09:12:17 zen kernel: kgd2kfd_pre_reset+0x47/0x60 [amdgpu]
jan 29 09:12:17 zen kernel: amdgpu_amdkfd_pre_reset+0x1a/0x20 [amdgpu]
jan 29 09:12:17 zen kernel: amdgpu_device_gpu_recover.cold+0x352/0x96d [amdgpu]
jan 29 09:12:17 zen kernel: amdgpu_job_timedout+0x123/0x150 [amdgpu]
jan 29 09:12:17 zen kernel: drm_sched_job_timedout+0x72/0xc0 [amd_sched]
jan 29 09:12:17 zen kernel: process_one_work+0x1eb/0x3b0
jan 29 09:12:17 zen kernel: worker_thread+0x4d/0x400
jan 29 09:12:17 zen kernel: kthread+0x104/0x140
jan 29 09:12:17 zen kernel: ? process_one_work+0x3b0/0x3b0
jan 29 09:12:17 zen kernel: ? kthread_park+0x90/0x90
jan 29 09:12:17 zen kernel: ret_from_fork+0x22/0x40
jan 29 09:12:17 zen kernel: Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs f2fs btrfs xor zstd_compress raid6_pq dm_crypt vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_recent xt_CHECKSUM xt_MASQUERADE ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_tables nfnetlink bridge stp llc binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic amdgpu(OE) ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm amd_iommu_v2 amd_sched(OE) snd_seq_midi input_leds joydev snd_seq_midi_event amdttm(OE) edac_mce_amd snd_rawmidi snd_seq kvm_amd crct10dif_pclmul snd_seq_device amdkcl(OE) ghash_clmulni_intel aesni_intel nls_iso8859_1 crypto_simd cryptd glue_helper wmi_bmof snd_timer drm_kms_helper i2c_algo_bit k10temp snd fb_sys_fops syscopyarea sysfillrect sysimgblt soundcore ccp mac_hid sch_fq_codel nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit kvm xt_addrtype
jan 29 09:12:17 zen kernel: xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nct6775 nf_defrag_ipv4 libcrc32c hwmon_vid ip6table_filter parport_pc ip6_tables ppdev iptable_filter bpfilter lp parport drm nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 hid_generic usbhid hid uas usb_storage crc32_pclmul i2c_piix4 r8169 nvme ahci realtek nvme_core libahci wmi gpio_amdpt gpio_generic
jan 29 09:12:17 zen kernel: ---[ end trace 3c4079192320e109 ]---
jan 29 09:12:17 zen kernel: RIP: 0010:mutex_lock+0x1e/0x40
jan 29 09:12:17 zen kernel: Code: c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 49 89 fc e8 8d de ff ff 31 c0 65 48 8b 14 25 c0 6b 01 00 <f0> 49 0f b1 14 24 74 08 4c 89 e7 e8 b2 ff ff ff 41 5c 5d c3 66 66
jan 29 09:12:17 zen kernel: RSP: 0018:ffffafee48427c88 EFLAGS: 00010246
jan 29 09:12:17 zen kernel: RAX: 0000000000000000 RBX: 87e828cdf86bc547 RCX: 0000000000000000
jan 29 09:12:17 zen kernel: RDX: ffff99410f629740 RSI: 0000000000000004 RDI: ffff9941ee92adc0
jan 29 09:12:17 zen kernel: RBP: ffffafee48427c90 R08: 0000000000000085 R09: 0000000002e64586
jan 29 09:12:17 zen kernel: R10: 0000000002e64586 R11: 0000000000000000 R12: 87e828cdf86bc6b7
jan 29 09:12:17 zen kernel: R13: 87e828cdf86bc6b7 R14: ffff9941e2d00000 R15: ffff9941ea0d50b0
jan 29 09:12:17 zen kernel: FS: 0000000000000000(0000) GS:ffff9941ee900000(0000) knlGS:0000000000000000
jan 29 09:12:17 zen kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
jan 29 09:12:17 zen kernel: CR2: 000055aaa371f010 CR3: 00000007b5e28000 CR4: 0000000000340ee0
jan 29 09:12:18 zen CRON[26228]: pam_unix(cron:session): session opened for user root by (uid=0)
jan 29 09:12:18 zen CRON[26230]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)

[Matrixx]

I advise you the following, download the program, it is free "Who Crashed" and the MemTest64. You run the Mem under windows for at least 20 minutes to see if the system crashes. If that happens, you start windows in Safe Mode and do the Test again, to see what happens.