AMD issues.

Swinny

Bronze Level Poster
is it 4.7.21 if I remember????

The latest one.

I never used to but when I started having these issues I used DDU to clean wipe and start again
 

ubuysa

The BSOD Doctor
IMHO, the crash defender is not the issue, the issue is why it's crashing, as it works absolutely fine throughout 99% of systems. There will be something conflicting with it causing the driver timeouts.
You know more about this stuff than I, but the 'it works on other systems' is true for just about every driver failure I've ever seen. The dumps all very strongly point at amdfendr.sys and it would be most wise to remove the AMD Crash Detection System from the equation, by disabling it, and then see what happens. Once we've confirmed that it is the crash detection system causing the failures we can move on to look at why.

The dumps show clearly what happened, though I didn't post this detail earlier. The failure happened at amdfenr+0x534D8...
Rich (BB code):
12: kd> k
 # Child-SP          RetAddr               Call Site
00 ffffb688`e9f2e6d0 ffff938c`70c84440  amdfendr+0x534d8
01 ffffb688`e9f2e6d8 00000000`00000001     0xffff938c`70c84440
02 ffffb688`e9f2e6e0 00000000`00000000     0x1
Be examining the details of that stack frame we can see exactly where the failure happened....
Rich (BB code):
12: kd> .frame /r 0
00 ffffb688`e9f2e6d0 ffff938c`70c84440     amdfendr+0x534d8
rax=ffffe30bcd1e3d60 rbx=ffff938c70c84440 rcx=ffffb688e9f2e720
rdx=ffff938c695f55e0 rsi=0000000000000001 rdi=0000000000000000
rip=fffff804c16c34d8 rsp=ffffb688e9f2e6d0 rbp=ffffb688e9f2e7d0
 r8=ffff938c695f55e0  r9=0000000000000000 r10=0000000000000000
r11=ffffb688e9f2e520 r12=0000000000000000 r13=ffff938c559a2d18
r14=00000000a1000005 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040202
amdfendr+0x534d8:
fffff804`c16c34d8 0f1f440000      nop     dword ptr [rax+rax]
The failure was detected at that NOP (no operation) instruction, these are typically used for alignment. What we want to know is what led up to this instruction. We can do that by disassembling the code backwards from that NOP...
Rich (BB code):
amdfendr+0x534b0:
fffff804`c16c34b0 b905000000      mov     ecx,5
fffff804`c16c34b5 48ff154caefeff  call    qword ptr [amdfendr+0x3e308 (fffff804`c16ae308)]
fffff804`c16c34bc 0f1f440000      nop     dword ptr [rax+rax]
fffff804`c16c34c1 eb60            jmp     amdfendr+0x53523 (fffff804`c16c3523)
fffff804`c16c34c3 488b442448      mov     rax,qword ptr [rsp+48h]
fffff804`c16c34c8 488d4c2450      lea     rcx,[rsp+50h]
fffff804`c16c34cd 48894360        mov     qword ptr [rbx+60h],rax
fffff804`c16c34d1 48ff15e8aefeff  call    qword ptr [amdfendr+0x3e3c0 (fffff804`c16ae3c0)]
fffff804`c16c34d8 0f1f440000      nop     dword ptr [rax+rax]
The last instruction there is the NOP where the failure was detected. Immediately prior is CALL instruction calling another amdfendr.sys function at offset 0x3E3C0, the dump shows us the address of this call; 0xFFFFF804 C16AE3C0. If we now disassemble this function we get...
Code:
12: kd> u fffff804`c16ae3c0
amdfendr+0x3e3c0:
fffff804`c16ae3c0 ??              ???
                          ^ Memory access error in 'u fffff804`c16ae3c0'
The function doesn't exist in memory. We can confirm this by displaying the bytes at this address...
Code:
12: kd> db fffff804`c16ae3c0
fffff804`c16ae3c0  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae3d0  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae3e0  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae3f0  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae400  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae410  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae420  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae430  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
The amdfendr.sys driver has attempted to call a function within itself that doesn't exist in memory and whilst potentially that could be a conflict with something else it seems unlikely.
 

SpyderTracks

We love you Ukraine
You know more about this stuff than I, but the dump very strongly points at amdfendr.sys and it would be most wise to remove the AMD Crash Detection System from the equation, by disabling it, and then see what happens. Once we've confirmed that it is the crash detection system causing the failures we can move on to look at why.

The dumps show clearly what happened, though I didn't post this detail earlier. The failure happened at amdfenr+0x534D8...
Rich (BB code):
12: kd> k
 # Child-SP          RetAddr               Call Site
00 ffffb688`e9f2e6d0 ffff938c`70c84440  amdfendr+0x534d8
01 ffffb688`e9f2e6d8 00000000`00000001     0xffff938c`70c84440
02 ffffb688`e9f2e6e0 00000000`00000000     0x1
Be examining the details of that stack frame we can see exactly where the failure happened....
Code:
12: kd> .frame /r 0
00 ffffb688`e9f2e6d0 ffff938c`70c84440     amdfendr+0x534d8
rax=ffffe30bcd1e3d60 rbx=ffff938c70c84440 rcx=ffffb688e9f2e720
rdx=ffff938c695f55e0 rsi=0000000000000001 rdi=0000000000000000
rip=fffff804c16c34d8 rsp=ffffb688e9f2e6d0 rbp=ffffb688e9f2e7d0
 r8=ffff938c695f55e0  r9=0000000000000000 r10=0000000000000000
r11=ffffb688e9f2e520 r12=0000000000000000 r13=ffff938c559a2d18
r14=00000000a1000005 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040202
amdfendr+0x534d8:
fffff804`c16c34d8 0f1f440000      nop     dword ptr [rax+rax]
The failure was detected at that NOP (no operation) instruction, these are typically used for alignment. What we want to know is what led up to this instruction. We can do that by disassembling the code backwards from that NOP...
Code:
amdfendr+0x534b0:
fffff804`c16c34b0 b905000000      mov     ecx,5
fffff804`c16c34b5 48ff154caefeff  call    qword ptr [amdfendr+0x3e308 (fffff804`c16ae308)]
fffff804`c16c34bc 0f1f440000      nop     dword ptr [rax+rax]
fffff804`c16c34c1 eb60            jmp     amdfendr+0x53523 (fffff804`c16c3523)
fffff804`c16c34c3 488b442448      mov     rax,qword ptr [rsp+48h]
fffff804`c16c34c8 488d4c2450      lea     rcx,[rsp+50h]
fffff804`c16c34cd 48894360        mov     qword ptr [rbx+60h],rax
fffff804`c16c34d1 48ff15e8aefeff  call    qword ptr [amdfendr+0x3e3c0 (fffff804`c16ae3c0)]
fffff804`c16c34d8 0f1f440000      nop     dword ptr [rax+rax]
The instruction at the bottom there is the NOP, these are typically used for alignment purposes. What we want to know is what code led up to this NOP and by disassembling backwards from the NOP we can find out...
Code:
12: kd> ub fffff804`c16c34d8
amdfendr+0x534b0:
fffff804`c16c34b0 b905000000      mov     ecx,5
fffff804`c16c34b5 48ff154caefeff  call    qword ptr [amdfendr+0x3e308 (fffff804`c16ae308)]
fffff804`c16c34bc 0f1f440000      nop     dword ptr [rax+rax]
fffff804`c16c34c1 eb60            jmp     amdfendr+0x53523 (fffff804`c16c3523)
fffff804`c16c34c3 488b442448      mov     rax,qword ptr [rsp+48h]
fffff804`c16c34c8 488d4c2450      lea     rcx,[rsp+50h]
fffff804`c16c34cd 48894360        mov     qword ptr [rbx+60h],rax
fffff804`c16c34d1 48ff15e8aefeff  call    qword ptr [amdfendr+0x3e3c0 (fffff804`c16ae3c0)]
fffff804`c16c34d8 0f1f440000      nop     dword ptr [rax+rax]
The last instruction there is the NOP where the failure was detected. Immediately prior is CALL instruction calling another amdfendr.sys function at offset 0x3E3C0, the dump shows us the address of this call; 0xFFFFF804 C16AE3C0. If we now disassemble this function we get...
Code:
12: kd> u fffff804`c16ae3c0
amdfendr+0x3e3c0:
fffff804`c16ae3c0 ??              ???
                          ^ Memory access error in 'u fffff804`c16ae3c0'
The function doesn't exist in memory. We can confirm this by displaying the bytes at this address...
Code:
12: kd> db fffff804`c16ae3c0
fffff804`c16ae3c0  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae3d0  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae3e0  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae3f0  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae400  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae410  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae420  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
fffff804`c16ae430  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
The amdfendr.sys driver has attempted to call a function within itself that doesn't exist in memory and whilst potentially that could be a conflict with something else it seems unlikely.
Driver timeouts are really common with Adrenaline, but it’s almost always a software incompatibility.

A workaround if finding the cause is not possible is to install just the display drivers without adrenaline, but fairly confident we can avoid that because despite some dodgy coding, adrenaline is actually very good, far better than the current nvidia control panel (although the new GeForce beta app looks to equal it finally after about 20 years of customers clamoring for it!)
 

SpyderTracks

We love you Ukraine
Hi all.

I bought a custom build pc from here a couple months back and alls been great.

However lately when playing FF14 out of the blue my pc screens go black - after about 30 seconds I get the error message

AMD Software detected that a driver timeout has occurred.

I’ve uninstalled and reinstalled the drivers I’ve cleared cache and sometime that will stop it for a day or so but then it just comes back and happens again.

Any ideas how to resolve this please.

Full pc specs below

Case


CORSAIR 5000D AIRFLOW TEMPERED GLASS GAMING CASE - WHITE


Promotional Item


Get a discount code for 20% off select peripherals at Corsair.com


Processor (CPU)


AMD Ryzen 9 7950X3D 16 Core CPU (4.2GHz-5.7GHz/144MB w/3D V-CACHE/AM5)


Motherboard


ASUS® ROG STRIX X670E-A GAMING WIFI (AM5, DDR5, PCIe 5.0, Wi-Fi 6E)


Memory (RAM)


32GB Corsair DOMINATOR TITANIUM DDR5 6400MHz (2 x 16GB) KIT


Graphics Card


24GB ASUS TUF GAMING RADEON™ RX 7900 XTX OC - HDMI, DP - DX® 12


Graphics Card Support Bracket


NONE (BRACKET INCLUDED AS STANDARD ON 4070 Ti / RX 7700 XT AND ABOVE)


1st M.2 SSD Drive


500GB SAMSUNG 980 PRO M.2, PCIe NVMe (up to 6900MB/R, 5000MB/W)


1st M.2 SSD Drive


2TB SAMSUNG 990 PRO M.2, PCIe 4.0 NVMe (up to 7450MB/R, 6900MB/W)


1st Storage Drive


2TB SEAGATE BARRACUDA SATA-III 3.5" HDD, 6GB/s, 7200RPM, 256MB CACHE


Power Supply


CORSAIR 850W RMx SERIES™ MODULAR 80 PLUS® GOLD, ULTRA QUIET


Power Cable


1 x 1.5 Metre UK Power Cable (Kettle Lead, 1.0mm Core)


Processor Cooling


CORSAIR iCUE H150i ELITE CAPELLIX XT RGB High Performance CPU Cooler - WHITE


Thermal Paste


ARCTIC MX-4 EXTREME THERMAL CONDUCTIVITY COMPOUND


Extra Case Fans


5 x Corsair AF120 RGB ELITE PWM Fan + Controller Kit


Sound Card


ONBOARD 6 CHANNEL (5.1) HIGH DEF AUDIO (AS STANDARD)


Network Card


ONBOARD 2.5Gbe LAN PORT


USB/Thunderbolt Options


2 PORT (2 x TYPE A) USB 3.0 PCI-E CARD + STANDARD USB PORTS


Operating System


Windows 11 Home 64 Bit - inc. Single Licence


Operating System Language


United Kingdom - English Language


Windows Recovery Media


Windows 10/11 Multi-Language Recovery Image - Unlimited Downloads from Online Account


Office Software


FREE 30 Day Trial of Microsoft 365® (Operating System Required)


Anti-Virus


NO ANTI-VIRUS SOFTWARE


Browser


Firefox™


Warranty


3 Year Silver Warranty (1 Year Collect & Return, 1 Year Parts, 3 Year Labour)


Delivery


STANDARD INSURED DELIVERY TO UK MAINLAND (MON-FRI)


Build Time


Standard Build - Approximately 3 to 5 working days


Miscellaneous


PCSpecialist 2023 Keyring


Welcome Book


PCSpecialist Welcome Book


Logo Branding


PCSpecialist Logo


Packaging


PCS Corsair Carton Upright


Price: £0.00 including VAT and Delivery


Unique URL to re-configure: https://www.pcspecialist.co.uk/saved-configurations/amd-am5-pc/ggC97rrf4F/
Hmmm, I have also seen that the recommended PSU for that card (according to Asus own documents) is recommended at 1000w if paired with a Ryzen 9 CPU


That's the other consideration is this could be related to transient spikes, those are an absolute pain to troubleshoot and really require specialist hardware monitoring nodes attached to the system for some concrete proof. But symptoms for those can be from odd program crashes, through to full BSODS or even just power cut out.

Not saying that's any cause, just raising as the PSU is below recommendations.
 

Swinny

Bronze Level Poster
Hmmm, I have also seen that the recommended PSU for that card (according to Asus own documents) is recommended at 1000w if paired with a Ryzen 9 CPU


That's the other consideration is this could be related to transient spikes, those are an absolute pain to troubleshoot and really require specialist hardware monitoring nodes attached to the system for some concrete proof. But symptoms for those can be from odd program crashes, through to full BSODS or even just power cut out.

Not saying that's any cause, just raising as the PSU is below recommendations.
1724596851023.png


As you can see here i did change the PSU from a 850w to a 1000w - my bad thought i had added this.
 

SpyderTracks

We love you Ukraine
Just posting this as is an easy thing to try although is from about a year ago, so may be related to outdated drivers

"I know this is an older topic now, but I was struggling with this same issue with constant crashes.

I tried a lot of tips that people have put in here, and I wanted to try to work out exactly what was causing the crash for me in the Adrenalin software over the standard driver.

For me, it actually turned out to be the Instant Replay function. I can reliably and repeatably replicate the crash with that function on/off. If it is on, I crash in games after 2-10 minutes. With the function off I have never had a driver or GPU crash.

I have spent days trying to work this out, so hopefully for some other people struggling with the 7900 XT(X) cards, this can help you if you still want to keep other functionality of the cards beyond just the base driver install."


There's various things to try in that reddit thread.
 

Swinny

Bronze Level Poster
Just posting this as is an easy thing to try although is from about a year ago, so may be related to outdated drivers

"I know this is an older topic now, but I was struggling with this same issue with constant crashes.

I tried a lot of tips that people have put in here, and I wanted to try to work out exactly what was causing the crash for me in the Adrenalin software over the standard driver.

For me, it actually turned out to be the Instant Replay function. I can reliably and repeatably replicate the crash with that function on/off. If it is on, I crash in games after 2-10 minutes. With the function off I have never had a driver or GPU crash.

I have spent days trying to work this out, so hopefully for some other people struggling with the 7900 XT(X) cards, this can help you if you still want to keep other functionality of the cards beyond just the base driver install."


There's various things to try in that reddit thread.
Thank you. However its always been disabled :)

So far so good on turning off the defender.
 

Swinny

Bronze Level Poster
Hi all - Really need some help with this - Starting to think something is wrong with the actual PC.

So today - The above happened again - However when i restarted my PC it wouldn't but and i had to load it into Safe mode however it then worked after another reboot - Really starting to become quite concerned especially given how much this cost and how new it is .......

@ubuysa @SpyderTracks

And then it done it again within 5 minutes of reloading it.
 
Last edited:

SpyderTracks

We love you Ukraine
Hi all - Really need some help with this - Starting to think something is wrong with the actual PC.

So today - The above happened again - However when i restarted my PC it wouldn't but and i had to load it into Safe mode however it then worked after another reboot - Really starting to become quite concerned especially given how much this cost and how new it is .......

@ubuysa @SpyderTracks

And then it done it again within 5 minutes of reloading it.
Did you go through the solutions in the previous link?
 

SpyderTracks

We love you Ukraine
Oh really sorry I may have missed that then as there’s been quite a bit of info in here
You'd need to use DDU to fully clean the driver in safe mode, then there are guides on youtube on how to just install the driver without adrenalin
 

Swinny

Bronze Level Poster
You'd need to use DDU to fully clean the driver in safe mode, then there are guides on youtube on how to just install the driver without adrenalin
Far from savvy on this but will give it a shot.

Thank you.

Update - ok seems to have worked - Ill keep you posted on what its now like
 
Last edited:
Top