Twice I've tried to raid Meldeburne. First time, part way through the raid the game crashed to desktop. Restarted the computer and restarted the game to re-try. Didn't crash to desktop, but the game froze and couldn't get it to respond. Had to force quit through task manager.

8 months later, game bought just last week, same problem raiding Meldeburn, consistently crashing at the exact same place.

@scad94 Also having issues. If I go in the top left building the game crashes. Even if I just open the door and don't go inside after it will crash after a few seconds.

Just by reaching near this building the game CTD, even in exploration without raiding, @Scad94 I'm in the same boat as you, just bought this game and now can't refund this bugged mess, after 8 months without a fix Ubisoft already gave up on fixing

Here is a fix that worked for me:

Update: If the game still crashes for you try lowering this setting further.

Two crashes just after raiding Meldeburne

Computer Specs:

• CPU: AMD Ryzen 5600x
• GPU: Nvidia 3700 RTX
• RAM: 32 GB
• Motherboard: TUF GAMING B550M-PLUS
• Storage: 1TB SSD
• Monitor: LG 34GP83A-B 34 Inch

Game Experience:
Frequent crashes in England map, especially when raiding the monastery. Going to specific areas, mostly around or inside the monastery consistently crashes the game to desktop without any option to report error/crash.

Temporary Fix:
This thread suggested a potential fix by lowering the World Detail setting to Very High: https://www.reddit.com/r/ACValhalla/comments/o4rj8y/crashing_at_meldeburne/.
That did not fix my problem. Instead, I reduced my screen resolution from 3440x1440 to 2560x1440 and I am no longer experiencing the same crashes.

Expected Behavior:
Game should be able to support ultrawide screen resolution without crashes.

Edit*

I still managed to crash the game by going up the ladder to rescue the prisoners in the Meldeburne monastery or by opening the large chest in the other monastery. It seems like the game crashes every time there is a monastery involved or when there are priests performing rituals together...

Reducing the resolution and world detail setting helped reduce the frequency of crashes, but these monastery raid areas are still beyond playable.

I am not overclocking my GPU/CPU. And the temps are normal.

hey my Pc was crashing in ac valhalla but only when i got close to a church in Meldeburne.
I tried reinstalling the game cause i thought that it was not installed correctly. That didn`t help.
After that i screwed around with my in game graphics and reallised, that it`s only crashing when i`m playing with "environment textures" set on "very high".
i can have the textures on higher or lower then that but it only crashes on the setting "very high". i`m just hoping to help other people here.

Im running the game on radeon rx 5700 xt graphics card, windows 10, AMD Ryzen 5 2600 Six-Core Processor  3.40 GHz and 16 gigabyte of RAM

Played the game thru Norway starting area and the first few England raids with no issues. Then when I did the Meldeburne Raid (still in L20 area) the game just spluttered and crashed to desktop. Reloaded, same thing. 4 times until I lowered settings and I managed to complete it. (1 crash was outside, the other 3 were indoors near one of the Wealth chests).

Then I just now attacked the northern fortress for the first time and on the 3rd section breaking down the gates it did it again.

No error codes, game just quickly splutters and quits.

My rig should be able to handle Ultra particularly at 1440p! I checked my CPU and GPU temps as it crashed and CPU was low 60s, GPU mid 50s so well within their operating temps.

I raised a ticket but Chat is the only means for support on the website and the chat window had no response after half an hour. Both @Assassins Creed and @Ubisoft Support on Twitter have so far ignored me.

The Windows build below is a brand new install with all updates completed. Ubisoft Connect was also downloaded fresh, and I have verified the files already.

Windows 10 19042.110, AMD 5900x (16 core), Nvidia 3080, Aorus x570 Master, 32GB Corsair ram @3200. Everything at default speeds - no overclocking.

@nomadski I know this isn't what you are going to want to hear but there is nothing you can do about this issue on your end .... It's been a persistent problem since the 1.1.0 update back in December and no one has a solution as far as I can tell ..... About the only advice I can give you is to keep your fingers crossed and hope the upcoming update finally fixes this persistent systemic problem

See: https://discussions.ubisoft.com/topic/78181/pc-i-am-experiencing-frequent-crashes-freezes-in-game-post-here?lang=en-US&_=1626421338794

@ubi-smash The issue is persisting.

I am going to do a clean install one more time of the game but after that, it would be nice if Ubisoft looked at their game with a view that the problem MIGHT just be with the game code, and not with the users PC.

I see in the other thread this has been an issue for some time, could you at the very least confirm with the tech team that they are looking into this? Meldeburne seems to be coming up often, and seems to be a trigger for more crashing afterwards.

I know this isn't directly Medleburne, but I'm getting frequent crashing during and SINCE Meldeburne. It seems to be the trigger for my crashing.

Latest crash was last night, by the River Soar. Called for Longship, dived into water, CTD.

Tried to restart game and Ubisoft Connect crashed with a runtime error.



Then played the remaining main Ledecestreshire (?) main missions for 3.5 hours without crashing whilst recording with Shadowplay.

Complete frustrating and random.

Game keeps crashing around Meldeburne area sic point after 1.3.0. this happing to anyone else??