AMD drivers crashes

[SuraPututya]

Does anyone have the same problem with new AMD Adrenalin Edition 25.3.2 drivers?
Here’s what I’ve tried so far:

Uninstalled and reinstalled the new driver.

Tried lowering in-game settings to see if that helps, but it still crashes.

Reverted back to the previous driver (everything works fine again).

Checked for updates to Windows and the game — all are up to date.

AMD RX 6700 XT 12 GB
AMD Ryzen 5 2600 Six-Core Processor
32 RAM
WIn 11


************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 44

Microsoft (R) Windows Debugger Version 10.0.27829.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\surar\OneDrive\Documentos\The Last of Us Part II\The Last of Us Part II-v1.3.10430.0406 2025-05-01-23-05-06.mdmp]
Comment: ''
User Mini Dump File: Only registers, stack and portions of memory are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 26100 MP (12 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
Edition build lab: 26100.1.amd64fre.ge_release.240331-1435
Debug session time: Thu May 1 23:05:06.000 2025 (UTC + 3:00)
System Uptime: 0 days 1:28:18.652
Process Uptime: 0 days 0:02:44.000
................................................................
................................................................
.............................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr
(1268.2a60): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007ffe`8fa5df14 c3 ret
0:085> !analyze -v
................................................................
................................................................
.............................
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************


KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullPtr

Key : AV.Type
Value: Write

Key : Analysis.CPU.mSec
Value: 531

Key : Analysis.Elapsed.mSec
Value: 595

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 250

Key : Analysis.Init.Elapsed.mSec
Value: 2942

Key : Analysis.Memory.CommitPeak.Mb
Value: 252

Key : Analysis.Version.DbgEng
Value: 10.0.27829.1001

Key : Analysis.Version.Description
Value: 10.2503.24.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2503.24.1

Key : Failure.Bucket
Value: INVALID_POINTER_WRITE_c0000005_tlou-ii.exe!Unknown

Key : Failure.Exception.Code
Value: 0xc0000005

Key : Failure.Exception.IP.Address
Value: 0x7ff7351bc8a0

Key : Failure.Exception.IP.Module
Value: tlou_ii

Key : Failure.Exception.IP.Offset
Value: 0x19cc8a0

Key : Failure.Hash
Value: {d37c73c3-64f2-f712-746b-0ca2af790601}

Key : Failure.ProblemClass.Primary
Value: INVALID_POINTER_WRITE

Key : Timeline.OS.Boot.DeltaSec
Value: 5298

Key : Timeline.Process.Start.DeltaSec
Value: 164

Key : WER.OS.Branch
Value: ge_release

Key : WER.OS.Version
Value: 10.0.26100.1

Key : WER.Process.Version
Value: 1.3.10430.406


FILE_IN_CAB: The Last of Us Part II-v1.3.10430.0406 2025-05-01-23-05-06.mdmp

COMMENT:

CONTEXT: (.ecxr)
rax=00007ff7366c67e0 rbx=000000f7fbe7f3a0 rcx=000003f2c6274800
rdx=000000000000000f rsi=00000000887a0006 rdi=000003f2c6274800
rip=00007ff7351bc8a0 rsp=000000f7fbe7f348 rbp=000000f7fbe7f450
r8=7ffffffffffffffc r9=0000000000000000 r10=0000000000000000
r11=000000f7fbe7f190 r12=000003f2c6274988 r13=00000000ffffffff
r14=0000000000000043 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
tlou_ii!ctlWaitForPropertyChange+0x168f80:
00007ff7`351bc8a0 c704250000000006007a88 mov dword ptr [0],887A0006h ds:00000000`00000000=????????
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff7351bc8a0 (tlou_ii!ctlWaitForPropertyChange+0x0000000000168f80)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

PROCESS_NAME: tlou-ii.exe

WRITE_ADDRESS: 0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000000

STACK_TEXT:
000000f7`fbe7f348 00007ff7`351b85cd : ffffffff`fffffffe 00007ff7`362fa4ac 00007ff7`366c6e50 00000000`887a0006 : tlou_ii!ctlWaitForPropertyChange+0x168f80
000000f7`fbe7f350 00007ff7`34ae4fa5 : ffffffff`fffffffe 00007ff7`3b81d060 ffffffff`fffffffe 00000000`887a0006 : tlou_ii!ctlWaitForPropertyChange+0x164cad
000000f7`fbe7f860 00007ff7`34aedb00 : ffffffff`fffffffe 00007ff7`3b81d060 00000000`00000000 00007ffe`8ccacdcf : tlou_ii+0x12f4fa5
000000f7`fbe7f900 00007ff7`34aebbb6 : 00007ff7`3b81e090 00007ff7`3b81e090 00000000`00000000 00000000`00000000 : tlou_ii+0x12fdb00
000000f7`fbe7f9c0 00007ff7`360a5c9c : 000002c5`8423fe80 00000000`00000000 00000000`00000000 00000000`00000000 : tlou_ii+0x12fbbb6
000000f7`fbe7f9f0 00007ffe`8eeae8d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tlou_ii!NVSDK_NGX_UpdateFeature+0xa019c
000000f7`fbe7fa20 00007ffe`8f9b14fc : 00000000`00000000 00000000`00000000 000004f0`fffffb30 000004d0`fffffb30 : kernel32!BaseThreadInitThunk+0x17
000000f7`fbe7fa50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2c


SYMBOL_NAME: tlou_ii+168f80

MODULE_NAME: tlou_ii

IMAGE_NAME: tlou-ii.exe

STACK_COMMAND: ~85s; .ecxr ; kb

FAILURE_BUCKET_ID: INVALID_POINTER_WRITE_c0000005_tlou-ii.exe!Unknown

OS_VERSION: 10.0.26100.1

BUILDLAB_STR: ge_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 1.3.10430.406

FAILURE_ID_HASH: {d37c73c3-64f2-f712-746b-0ca2af790601}

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

[animal_PLANET]

AMD has listed this as a known issue. Hopefully it wont be long for AMD to patch. Try an earlier driver and see if it helps.

https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-25-4-1.html

Originally posted by AMD:

Intermittent application crash or driver timeout may be observed while playing The Last of Us Part 2.

[👁️‍🗨antiparti]

There's a newer optional driver on amd website, I never trust adrenaline anymore to give me the latest optionals.

[TM2P]

25.4.1 optional drivers works so far for me. On a 6700xt

[UGX Rorke]

Originally posted by TM2P:

25.4.1 optional drivers works so far for me. On a 6700xt

so far yeah but just note it's still on the issues list for the new driver

[SuraPututya]

Originally posted by UGX Rorke:

Originally posted by TM2P:

25.4.1 optional drivers works so far for me. On a 6700xt

so far yeah but just note it's still on the issues list for the new driver

new drivers dont help me and i`ve got crashes anyway..i`m gonna cry..

[UGX Rorke]

Originally posted by SuraPututya:

Originally posted by UGX Rorke:

so far yeah but just note it's still on the issues list for the new driver

new drivers dont help me and i`ve got crashes anyway..i`m gonna cry..

if you are on the new drivers try going back 2 driver versions OP said "Reverted back to the previous driver (everything works fine again)." but failed to tell us what driver version he is running so maybe try that?

[SuraPututya]

Originally posted by UGX Rorke:

Originally posted by SuraPututya:

new drivers dont help me and i`ve got crashes anyway..i`m gonna cry..

if you are on the new drivers try going back 2 driver versions OP said "Reverted back to the previous driver (everything works fine again)." but failed to tell us what driver version he is running so maybe try that?

i`m gonna do it again, but when i use old drivers, i cant play other games, they are crashing every time and it is said to update drivers

[UGX Rorke]

Originally posted by SuraPututya:

Originally posted by UGX Rorke:

if you are on the new drivers try going back 2 driver versions OP said "Reverted back to the previous driver (everything works fine again)." but failed to tell us what driver version he is running so maybe try that?

i`m gonna do it again, but when i use old drivers, i cant play other games, they are crashing every time and it is said to update drivers

thats the only problem when reverting back to older drivers you loose game support

[TM2P]

Originally posted by SuraPututya:

Originally posted by UGX Rorke:

so far yeah but just note it's still on the issues list for the new driver

new drivers dont help me and i`ve got crashes anyway..i`m gonna cry..

Seeing the error code you posted, definitely a driver issue. Try using DDU to completely erase the current drivers and reinstall while disconnecting your internet to prevent windows from downloading its crappy drivers.

Also install the chipset drivers too just to be safe. Currently in the last chapter and no crashes.

[sinephase]

try using DDU and set it to delete old AMD remnants as well as disable automatic driver install for when you launch windows again
EDIT: always make sure you're using the most up to date version of DDU

[UGX Rorke]

Originally posted by sinephase:

try using DDU and set it to delete old AMD remnants as well as disable automatic driver install for when you launch windows again
EDIT: always make sure you're using the most up to date version of DDU

that will help because?

you do realise AMD have stated it's a driver issue right? so rolling back will fix the issue with his game but his other games probibly wont work as intended due to loss of game support

[TM2P]

Originally posted by UGX Rorke:

Originally posted by sinephase:

try using DDU and set it to delete old AMD remnants as well as disable automatic driver install for when you launch windows again
EDIT: always make sure you're using the most up to date version of DDU

that will help because?

you do realise AMD have stated it's a driver issue right? so rolling back will fix the issue with his game but his other games probibly wont work as intended due to loss of game support

It will remove all traces of the problematic driver and a clean install can be done.

[UGX Rorke]

Originally posted by TM2P:

Originally posted by UGX Rorke:

that will help because?

you do realise AMD have stated it's a driver issue right? so rolling back will fix the issue with his game but his other games probibly wont work as intended due to loss of game support

It will remove all traces of the problematic driver and a clean install can be done.

but again that wont help tho will it because it's not a corupt driver it's a DRIVER problem that AMD knows about rolling back to 2 drivers ago will help

[sinephase]

Originally posted by UGX Rorke:

Originally posted by sinephase:

try using DDU and set it to delete old AMD remnants as well as disable automatic driver install for when you launch windows again
EDIT: always make sure you're using the most up to date version of DDU

that will help because?

you do realise AMD have stated it's a driver issue right? so rolling back will fix the issue with his game but his other games probibly wont work as intended due to loss of game support

yet it doesn't happen to everyone. I wonder why that is?
Did AMD admit it's an issue, or just say it's a "reported" issue?
It's worth the try.

[animal_PLANET]

Originally posted by sinephase:

Did AMD admit it's an issue

Yes, see my reply. Comment #1.