This appears to have gotten worse with the recent hotfix.
As of tonight, with another player on our coop realm, I CTD effectively ever 2-3 minutes. This is completely unplayable.
I’ve additionally tried the following to no avail now: Reinstalling the game fully (on multiple SSDs). A fresh install of windows. Error message for windows event viewer remains unchanged.
Does a reinstall of your game drivers help? (I understand it’s a big ask). Someone in the Discord reported that helped them immensly.
Silas
The team need to add the same Volumetric slider Last Epoch did and allow us to go through all 5 levels including complete disable.
It’s the only setting in Unity that actually has any real impact and the only one that does anything in Last Epoch too.
I would like to +1 this.
I have 130 hours in game before the co-op update, and just started a real with a friend and I’m getting this super irritating slow-down, speed-up effect. It makes it impossible to play. I’ve tinkered with all graphics settings to the point where I now have no idea what else to try.
Getting a range of 40-50 fps most of the time, with it dropping to 30 in areas like lowland meadows and sacrament at times, as well as other areas.
I am playing co-op with 2-3 total players, including me, at a time.
Specs below if that helps:
AMD Ryzen 5 5600X 6-Core Processor
32 GB Ram
SSD (idk if the other specs for this matter)
NVIDIA GeForce RTX 3060 Ti
Would love to see some performance patches after this update that can help a ton.
Would you have some files for us Dpdp03?
See: How to Properly Report Bugs!
I appreciate it!
If you have other specific locations that trigger this, please let us know. Thank you for your report!
Silas
Hey Silas!
Could you provide me a link to the discord post? I want to make sure I understand here, but if im not mistaken we’re just talking about Nvidia drivers?
As a test this morning, I’ve completed a clean install of the latest of my GPU drivers (DDU uninstall of previous including wiping registry, 591.44 as previous, installing that latest 591.86).
This change did not produce any results - the crash remained consistent.
With that in mind I also wanted to give it a try to the last (in my opinion) stable set of drivers Nvidia provided for the 4 series card. I keep a copy of the 566.36, the last-ish of the pre-5 series slop drivers Nvidia has been putting out. I followed a similar path using DDU to wipe 591.86 from my system, and installed 566.36.
This did result in some changes in behavior. Instead of crashing almost immediately, I was able to continue a session in my group’s shared realm for approximately 42 minutes. When I crash with 566.36 installed, it does not generate a windows event viewer error for the application.
I’ve attached both of the crash logs files from the driver changes here, along with the player.log, player-prev.log, and datastore folder again) for the tests using the changed drivers: 566.36 Test - Google Drive
As a note, I typically run studio drivers, but have swapped to nvidia game drivers in this testing context. I also do not install Nvidia’s application, just the driver and control panel. As a disclaimer as well, I would typically not recommend downgrading so far back in terms of drivers. Many newer titles require specific newer driver versions to even launch, so downgrading may cause issues outside of No Rest for the Wicked.
did a fresh reinstall just now, no changes
Hey Selei, it was just a comment from a player in passing, saying it worked for him 
Here is the source: discord comment
Thanks for the extensive testing you’ve done, that is appreciated!
Silas
Hi everyone here,
I’ve been instructed to spread the word about a potential issue due to a windows update affecting Nvidia GPU’s. More here: https://overclock3d.net/news/software/new-windows-update-ruins-nvidia-geforce-gpu-performance-reports-claim/
If you suspect this might be affecting you, either restoring a point before this update or exercising patience until Microsoft fixes this on their side is your only recourse.
In that case, we ask you to hold of on reporting performance issues until the previous mentioned update can we ruled out.
Silas
Interesting! This is a great find!
I actually see a Jan26 update available for my windows machines - KB5078127. I’ll run that update and see if I can ping any differences in operation!
If that has no appreciable effect, I’ll see if I can restore point prior to KB5074109.
Summary
Full system shutdown during game startup after latest update. No BSOD, no crash dialog. Happens consistently during startup sequence, after FSR3 initialization.
Yes, the bug is 100% reproducible.
It occurs every time the game is launched after the latest update.
During game startup, after:
successful Unity initialization
successful Steam login
FSR3 upscaler initialization
just before / during intro sequence
I have not found an identical report describing a full system shutdown (not a crash or freeze) during startup related to FSR3 and ultrawide resolution.
The game should continue to the main menu after startup.
The system hangs briefly and then powers off completely.
This is not a Windows crash or BSOD, and no dump is generated.
I have uploaded the following files and included links below:
Player.log
Player-prev.log
DataStore folder (zipped as DataStore.zip)
%USERPROFILE%\AppData\LocalLow\Moon Studios\NoRestForTheWickeddxdiag.txt
Note about crash reports:
There are no files in
%USERPROFILE%\AppData\LocalLow\Moon Studios\NoRestForTheWicked\backtrace\crashpad\reports
because the system powers off and the game does not generate a crash dump.
CPU: AMD Ryzen 9 5900X (stock, PBO disabled)
GPU: AMD Radeon RX 9070 XT (stock, no OC / no undervolt)
RAM: 32 GB
Resolution: 3440×1440 (ultrawide)
OS: Windows
Graphics API: Direct3D11
AMD Driver: 32.0.23017.1001
The game worked perfectly before the update (9h play session, no issues).
Other demanding games (e.g. Battlefield 6 at Ultra) are fully stable.
GPU drivers were clean-installed using DDU.
Disabling CPU/GPU tuning does not change the behavior.
Based on logs, the shutdown happens shortly after FSR3 upscaler initialization, which suggests a possible issue with FSR3 on ultrawide resolutions during startup.
DxDiag and player logs.
Did you try this already - I have the same update available and am giving it a download now. Will report back.
Hey!
I did! I’ve been running a few variations of test to see how far I could push things.
The short is, it does seem in some capacity to help, though I dont think it fully solves the issue yet.
Updating to KB5078127 and keeping driver version 566.36 resulted in a surprising increase in stability! I was able to complete a full 90 minute session (about 20 minutes AFK in Sacrament, followed by going through The Shallows and Lowland Meadows killing enemies plus a full crucible run) without any issues!
I just finished re-updating to the latest Nvidia drivers to see how consistent this experience might be. The unfortunate news there is that while this does appear to resolve the windows event still, the latest drivers crashed in a similar fashion after approximately 25 minutes, 10 of which was AFK in sacrament and the rest spent in Lowland Meadows fighting.
These are just initial impressions though. I’m going to run a few more sessions with the latest drivers, then downgrade again to validate my initial experience again to make sure it wasnt a fluke.
So, mine appears to be fixed - he says hopefully. I played for about 15 minutes on my online realm just now, and it was back to normal.
The long version:
I actually just did the Windows update myself. So, last night I couldn’t really play because the performance was yo-yo’ing and stuttering, almost as if I was thermally throttled. So my friend and I played something else and I put my PC to sleep. This morning I woke it up, booted Wicked and it was much better, no yo-yo’ing or stutters - I had done nothing/no changes though. Very confusing. I then found this thread, and the info about various issues with Windows updates and needing new Nvidia drivers. I had already done the new drivers last night to no avail, so did the Windows update and the performance is actually better.
My theory: I have a feeling that on max-everything settings, @ 3440x1440 and HDR, the game was dipping in and out of acceptable framerate ranges. So, I would periodically see 100fps, and then 40fps. Now that shouldn’t matter in regards to tearing etc as I use G-sync, however I think the radical lows and highs were resulting in that yo-yo effect I mentioned. After applying the update my lows never go down that far anymore.
I’m still a little perplexed though as I have a friend with a 3080 and he runs Wicked on his ultra widescreen at 5120x1440, and reports the same/better FPS than me with my 4090 at a lower res. I do feel there is something sus happening. 
That’s great news!
Probably my last contribution for the time being 
On the latest drivers, I continued to crash in ~8-10 minutes. For 10 attempts, I loaded in with my character in the shared realm at the Lumber Yard Whisper and let the game run until it decided to close. Post windows version update, I no longer see the event error 0xc0000409, though it appears the latest GPU drivers may still have a related crash of some kind. The behavior was consistent on all attempts.
I’ve once again downgraded back to 566.36 and seem relatively stable. It’ll be a few days until I can gather up a few of our realm folks to play a session together, to see if that stability is retained as more players are on the realm participating. Here’s to hoping!
A quick summary of things that, i’ll say allegedly helped here:
Appreciate the back and forth so far everyone! Good hunting!
I’m on win 10, not win 11, but downgrading nvidia drivers to 566.36 seems to improve situation noticeably
maybe hotfix 5 did something as well
Hey guys, I’ve been experiencing a lot of performance issues recently. My specs are 32GB 3200MHz RAM, a Ryzen 7 5700X3D, and an RTX 5070.
Even with this setup, I’m getting around 40–60 FPS in most areas of the map. I play at 1440p with the Quality Preset set to Performance, DLSS on Performance (CNN model), and I’ve tested multiple configurations to compare results. Surprisingly, there’s barely any difference — even switching from the highest settings to the lowest doesn’t improve performance in a meaningful way.
I’ve already updated my NVIDIA drivers, made sure Windows is up to date, and ran benchmarks on 3DMark. Everything points to the issue being related specifically to No Rest for the Wicked.
Playing in single-player reduces the problem significantly, but I still drop to around 60 FPS in some areas, which feels quite low considering my hardware.
I am also getting performance issues similar to Gus_dev. When I am in Sacrament or other areas my fps drops to 40 sometimes as low as 28. I am playing at 1440p, AMD FSRAA AMD FSR 3.1.5
Specs are: AMD Radeon RX 9070 XT, AMD Ryzen 7 5700G, and I am also using windows 11
Changing any of these settings and lowering the resolution doesn’t seem to change performance in the slightest. When I am wandering in certain areas like sacrament and nameless pass the fps will tank from 60 to 28 then go up to 40 when not moving.
I updated my drivers to the latest and did a clean install before installing the new drivers. I am not really sure if there is anything else I can do on my end.
Edit: The Shallows I experience no performance issues.
I just booted up the game after the new patch, and even in town I’m getting terrible fps, stuttering and screen tearing…