[SOLVED] 'A problem has occurred with your display driver...'

[EASY BOT Elmer]

"A problem has occurred with your display driver. This can be caused by out of date drivers, using game settings higher than your GPU can handle, an overheating GPU, or an error with the game. Please try updating your graphics drivers, or lowering your in-game settings. Current GPU and graphics driver: NVIDIA GeForce RTX 4090, 552.44."

(0x887A002B: UNKNOWN)

In-game Settings: Max Preset, XeGTAO, DLSS Quality, FSR Frame Generation, V-Sync: On. Exclusive Fullscreen.
NVIDIA Settings: Prefer Maximum Performance, all else driver default
Resolution: 3840x2160 @ 120Hz (G-Sync Enabled)

1.0 -- Relevant System Specs --

CPU: i9 10900k @ 5.2GHz (Temperatures During Session: 65-72°C)
GPU: Asus ROG Strix RTX 4090 (Temperatures During Session: 48-57°C)
RAM: 64GB @ 3200MHz
PSU: 1200W

2.0 -- Extra Commentary --

The game runs perfectly smooth at most of the times over 100 FPS, I thought I needed to limit FPS in order for G-Sync to kick in but it seems to do fine like this. Same smoothness could not be achieved with NVIDIA's Frame Generation or by keeping V-Sync off. I have been changing some Display/Graphical settings during this session that ultimately led to a crash.

- All crashes seem to happen during or starting dialogue/cutscenes.
- Problem occurs randomly and is unrelated to session time.
- Problem does NOT seem to be related to either or both V-Sync and G-Sync.
- Problem may be related to memory allocation.
- Problem could be related to sudden FPS spikes.

Would appreciate help if you've found a fix yourself.

3.0 -- Possible Fix (Subject to updates) --

NOTICE: NVIDIA driver version 555.85 does NOT fix this issue, and has been reported that it may make things worse. Impossible to be certain since they happen at random, but there is no need to update your drivers unless you need it for other games (F1 24, Senua's Saga: Hellblade II, Serum and XDefiant)

After doing some more research in the driver, it appears more people are experiencing this issue even with other games. Rolling back the driver to the previous one solved it for them. (e.g. Hogwarts Legacy, Star Wars: Jedi - Survivor, Horizon Forbidden West)

Fortunately I always keep several previous drivers at hand, but a lot of people do not. If you want to give it a shot you can find older NVIDIA drivers here: https://www.nvidia.com/Download/Find.aspx

Remember to fully uninstall your current GPU drivers first with Display Driver Uninstaller while in Safe Mode, restart the system and install the previous drivers.

- Reducing memory clock speed has been reported to work for one user.
- Undervolting the GPU has been reported to work for one user.
- Changing Anti-Aliasing to XeSS + FSR3 has been reported to work for one user.

4.0 -- Fix That Worked For Me --

For me it may have turned out to be a CPU priority issue. I fixed it by downloading Anti-Stutter - High CPU Priority by ChemBoy1. People may have seen others recommend making this change in the registry keys manually, ChemBoy1 just made it easier and wrote two scripts that would install the key and one to uninstall the key at will without having to add/remove the keys manually.

Link: https://www.nexusmods.com/ghostoftsushima/mods/16

[Plague Doctor]

Why are you running frame generation on and vsync on?
Gsync doesn't work when vsync is enabled so turn vsync off, you then shouldn't get tearing if Gsync is running.
Turning on frame generation with a 4090 in a game like this should not be required at all.

[EASY BOT Elmer]

Originally posted by Plague Doctor:

Why are you running frame generation on and vsync on?

Because I still notice tearing.

[EASY BOT Elmer]

Originally posted by Plague Doctor:

Why are you running frame generation on and vsync on?
Gsync doesn't work when vsync is enabled for a start so turn vsync off.
Turning on frame generation with a 4090 in a game like this should not be required at all.

Do you have anything helpful to say about this error? Don't waste my time. I don't do these things for no reason.

[Plague Doctor]

Ok enjoy your crashing

[Spy]

Same issue but I don't use v-sync or g-sync, so that's a dead-end.
I ran into some cutscenes where the game would consistently crash with this error, and the only way I got through was by reducing memory clock, which seems more like a temporary fix.

[C0nnIptions]

I just dealt with this pop-up and turning off frame generation fixed it for me i believe. Spent the last 30 minutes trying everything to no avail. Turning that off somehow got it to work.

[Peter Imperator]

Same. I don't use FSR 3 but it just crashed with the same error for no reason.

[Mis'Bah]

Anyone found fix for this I'm getting the exact same thing

[[User Deleted]]

Turn OFF frame generation. It is bugged and broken at the moment and is what's causing this specific error.

[AE Labs]

I was running into this issue a lot and finally after seeing a comment about overlays I turned off my RTSS overlay and FSR 3 stopped crashing. Also running in administrator mode. So turn off all overlays and run in admin mode. My crashes were instant though a few moments after starting the game compared to your 4 hour session. Lotta edits first time commenting on steam ever and yeah the moment i turned on RTSS it crashes.

[Aya]

I played for a few hours and was quite satisfied. However, I just experienced a direct black screen during a cutscene, and I couldn't get any response from any key presses, so I had to restart my computer.
My computer: 13900K + 4090, 64GB. All drivers are updated to the latest version. It's very strange, maybe a patch is needed. The game itself is very good, but it seems the port still has some bugs.

[Seifer Leonheart]

Same Issue I'm having, also a 4090 (5800x3D CPU), temps on the lower side, performance is above 100 at all times, not using reflex, framegen, res scaling or v-sync, just DLSS on quality.

Happened twice in around 10h.

[Shirakani]

XeGTAO for me is the guaranteed crash.

[Frid]

Originally posted by EASY BOT Elmer:

Originally posted by Plague Doctor:

Why are you running frame generation on and vsync on?
Gsync doesn't work when vsync is enabled for a start so turn vsync off.
Turning on frame generation with a 4090 in a game like this should not be required at all.

Do you have anything helpful to say about this error? Don't waste my time. I don't do these things for no reason.

Dude literally gave advice.

[ShadowSkill11]

Can't help but notice the first thing the error told you was to update your video drivers. Did you?