1. Already have latest drivers.
2. I'll do that when I get home
3. Temps are fine. Being winter they go up to 80°C
4. Will have to fiddle with that to see what's what. Doubt it has anything to do with that. I play more graphically intense games like Alan Wake 2 that don't have the crashing problem.
6. Working on that.
7. I've submitted a ticket to AMD. I'll submit one to Hello Games when I get home.
I've disabled Riva Tuner, MSI Afterburner and MPO. I played for an hour last night and no crashes. I'll have to try and play for three hours to see what happens. Usually it occurs at the two hour mark. I suspect that it was probably Riva Tuner causing it.
I do have a second monitor and I can see the AMD error report tab in the taskbar but I can't access it as the window is on my main monitor. Is there anyway I could move it with shortcut keys?
2. Check Game Files: Verify the integrity of the game files through Steam or the respective platform you're using. Corrupted files can cause crashes.
Did that. All files are verified. No problems with them.
5. Event Viewer: Windows Event Viewer can be helpful to identify what happened just before the crash. Look under Windows Logs > System and Application for any critical errors around the time of the crash.
It happened again last night. I still have MPO, Riva Tuner and MSI Afterburner disabled. I am using Adrenaline Overlay now and it works ok. I don't think it caused the crash.
This time when I rebooted and loaded up the game the graphics were reset to defaults. 1920x1080 and everything on lowest. So the display driver didn't recover properly I'm guessing.
Here is the log entry from last night:
Level | Date and Time | Source | Event ID | Task Category |
Warning | 1/08/2024 10:02:34 PM | Display | 4101 | Display driver amduw23g stopped responding and has successfully recovered. |
This is what my main monitor looks like if a game crashes.
It also sometimes happens on bootup and the only way I can get out of it is to reboot and hope that it loads both monitors properly. They are both connected by a display port cable.
Here's an entry from event viewer from the 28th of July (which was Sunday when I posted this topic):
Level | Date and Time | Source | Event ID | Task Category | |
Error | 28/07/2024 7:58:25 PM | Application Error | 1000 | Application Crashing Events |
Faulting module name: ntdll.dll, version: 10.0.22621.3374, time stamp: 0xeae8eecc
Exception code: 0xc0000409
Fault offset: 0x000000000008ebdf
Faulting process id: 0x0x4134
Faulting application start time: 0x0x1DAE0D8BA2184D5
Faulting application path: C:\Program Files (x86)\DisplayFusion\DisplayFusion.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: 51fce995-ac6f-4d68-af48-88d1cf1cd58a
Faulting package full name:
Faulting package-relative application ID: "
I'm not sure if its related but maybe DisplayFusion could have maybe caused it?
I think because the display driver crashed it also affected DisplayFusion?
Yea, looks like it.
I haven't played two hours straight, more like 1 hour. But no problems for me with 7900 xtx. You might check the event viewer to find the crash reason. Perhaps running out of memory due to slight memory leak would be my first wild guess.
I have 32GB of RAM and 24GB of VRAM. Most games don't even use 10GB VRAM.
I'm not running out of RAM lol.
Ok an update. It just happened again when I was summoning my freighter. This time I was able to access my desktop on my main monitor.
I submitted a crash report to AMD.
Here is what happened:
I don't believe what it says about not enough VRAM. I have 24GB. I don't know how much it was using. Is there a way I can find out?
That's the exact same error I'm having at the moment. I'm running with Ryzen 7800X3D, Radeon 7900XTX & 64GB of RAM.
Did you ever fix the issue?