@jutzukan I already made a topic on this, no replies ofcourse.

Its not you though, so dont worry, i had a similar issue.
It seems rare, a sudden CTD, checking the eventviewer at first will only talk about display driver crash/reset.

Looking a little further in the applications logs, you'll most likely see 4 windows error report messages.
2 will be about D3DDRED2 and 2 will be additional logs about 'livekernel 141', which is a very generic code for saying 'something went wrong' lol.

Anyway the "DRED2" part is basically DX12.
So this either a GPU driver problem, which is possible if i look at the complaints on nividia forum about 457.30, it seems to cause alot of issues especially with the latest games it was released for in the first place.
OR its a AC Valhalla issue, which i personally suspect because the game is mentioned in the DRED2 logs. (you'll see a list of p1 to 8, with GPU code ie VEN10D or somesuch, windows 10 code and program name causing the crash)

So, something in relation to the GPU and DX12 causes a driver crash caused by something Valhalla does, which could be a memory leak but can also be faulty coding somewhere.

@johnweakaimbot I also got some "amd user" replies on Reddit with the same issue.

So im going to agree its very likely not the drivers perse, but something wrong with Valhalla.

Either way, its DX12 related and the devs will have to start there.
I should note the same thing happened for a while for Legions but also The Division 2.
Unless im mistaken, certainly TD2 got a patch eventually for the CTD's, so they ought to know in what direction to look for a solution by now.

Not sure about the saving part, but whenever i touch my mouse, it switches to KB/M as controls right? Okay, but it will stutter for a moment and the sound drops.
Same happens when i now touch my (normal microsoft xbox one for PC) controller, sound drops for a moment and the game stutters.

It seems to stay smooth as long as i dont switch around like that, but its not normal behaviour.
I think it may also happen when the game auto saves, but i cant be sure on that because it might just be my accidentally bumping into my table or maybe my mouse moves, it happens, so that might be nothing.

But please look into this.

Basically as title says, its on a shelf in a house behind Walden, it cannot be picked up.
There simply isnt a pickup prompt even though the HUD shows its something you should be able to pick up.

@cavveman Hi thanks for replying, but no it have not been to Walden before.

I tend to, as a pure autistic gamer :P, go 1 by 1 to every "thing" on the map.
So i know i didnt pick it up yet, as i hadnt travelled to that side of the map yet.

Anyway its simply bugged.

The D3DDRED2 crashes are becoming more frequent for some reason.

At first i thought it was the videocard, but no problem can i discover in terms of technical issues with it.
It could still be the driver but as i have no reason to roll back (due to everything else working fine) im going to leave the drivers as-is.

For me though, reading the eventviewer logs, it remains clear its Valhalla that causes the crashes.
It even froze while triggering that error, normally it would just CTD.

Its just way to similar to what AMD and nvidia users alike are experiencing.
Keep in mind, the error code is a direct reference to the dx12 api, thats got nothing to do with drivers (in rare cases, maybe) but almost always in relation to the app using the api.

@ubi-woofer
Considering the game can trigger CTD / D3DDRED2 errors (which is directly related to DX12 but possibly also the latest drivers from nvidia.. however on AMD the same thing happens) i really wouldnt recommend updating GPU drivers.

You have a game side issue that causes DX12 related issues, probably a memory leak of sorts.

@ubi-spud I have (and made a topic) the same issue, exactly the same.

Havent uploaded any photos or even used photomode, that aint it.
As you can trigger the same stutter when you start the game from desktop and the intro's, touch the controller and stutter/sound drops for a moment.

Any switching between KB/M and any controller, triggers it.

Sounds like a cloud save sync issue.

Because i see from several posts that other untouched (manual) saves people have also get corrupted, not just the latest save file, which is pretty weird and impossible as the state of the game in previous save files should be different.
So its nothing happening in your current save file state that causes the corruption, so it has to come from "outside", as the only fix i've seen is close the game, disconnect from internet, reconnect and restart the game.

So something is out of sync with ubisoft servers.

Anybody using a hdmi 2.0 monitor with amd freesync (premium)?
And does that make any difference at all?

I see most people here use a TV without VRR or Freesync who get tearing, so im wondering if you'd still get tearing on a monitor with freesync hdmi 2.0 or perhaps 2.1 if you have a monitor with that.

It should be noted that Sony already provided a full dev kit for the ps5 consoles back in 2019, where as microsoft only provided an incomplete dev kit beginning / mid 2020. (also called a basic dev kit)

It could easily explain why you see such an appaling difference on the XsX versus the ps5.
Got nothing to do with 'teraflops' or power, just lazy programming and software from both Ubisoft (look at the legions mess) and lazy microsoft who need to get their software in order.

This is a thing since launch by the way, I and many others made topics on this, never been addressed by ubisoft.

Now im lucky enough to only rarely get this crash, it’s non critical and windows might seem to report it as hardware failure, but that’s nonsense.
Its dx12 failure due to Valhalla in some way. (D3ddred2 = fancy code talk for dx12 so naturally it causes a driver crash/reset)

Keep in mind I can play the play the buggiest game released that everyone knows, ending in “2077” without a single crash or issue, on ultra settings for well over 80 hours now.

Nothing wrong with my hardware or system, thank you very much.

This is very much a Valhalla problem the devs need to look at already.

@b00msie yeh that’s basically the gpu drivers crashing due to dx12 crashing.
Same thing happens, still, on PC save the complete reboot, but the series X might require the reboot to load/reset drivers.

Can confirm the chest literally isn’t even there in ledecestrecire.

First I thought maybe I picked it up as all mysteries etc are flagged as completed for that area.
So i checked my ship schematics, the snake bite shield schematics are not present, so that’s not it either.

Bugged.

@qc_godlike819 i have not seen it so far since the latest update to the game.

I do feel sorry for the series X people, wanted to get one myself and even preordered the xbox ultimate edition (which cannot be cancelled apparently).

Plays, relatively, fine here on 60 fps / high settings PC on 1080p with the odd crash though that seems to be less since the patch 1.04.

Its really appalling and i blame both ubisoft and microsoft, ubisoft for their hasty releases with the connect update that caused a ton of issues, legion right after, valhalla right after that.. what were they thinking? All this to beat the fiscal year ..

And microsoft for providing really a lousy dev kit far too late and way to barebones, which is a big part of the problem for a few games out now and soon to be released.

The D3DDRED2 crashes are becoming more frequent for some reason.

At first i thought it was the videocard, but no problem can i discover in terms of technical issues with it.
It could still be the driver but as i have no reason to roll back (due to everything else working fine) im going to leave the drivers as-is.

For me though, reading the eventviewer logs, it remains clear its Valhalla that causes the crashes.
It even froze while triggering that error, normally it would just CTD.

Its just way to similar to what AMD and nvidia users alike are experiencing.
Keep in mind, the error code is a direct reference to the dx12 api, thats got nothing to do with drivers (in rare cases, maybe) but almost always in relation to the app using the api.

@ibetterrun fact you have it locked on 60hz/FPS means it’s got nothing to do with your monitor or for those with whatever TV they might use for either ps5 or XsX.

this happens less on ps5 apparently but you are not the first I’ve seen talk about this.
its a known issue on the Xbox though also on Xbox one.


I think ubisoft made a mistake releasing 2 big games so soon after one another.

Anybody using a hdmi 2.0 monitor with amd freesync (premium)?
And does that make any difference at all?

I see most people here use a TV without VRR or Freesync who get tearing, so im wondering if you'd still get tearing on a monitor with freesync hdmi 2.0 or perhaps 2.1 if you have a monitor with that.

It should be noted that Sony already provided a full dev kit for the ps5 consoles back in 2019, where as microsoft only provided an incomplete dev kit beginning / mid 2020. (also called a basic dev kit)

It could easily explain why you see such an appaling difference on the XsX versus the ps5.
Got nothing to do with 'teraflops' or power, just lazy programming and software from both Ubisoft (look at the legions mess) and lazy microsoft who need to get their software in order.

Sounds like a cloud save sync issue.

Because i see from several posts that other untouched (manual) saves people have also get corrupted, not just the latest save file, which is pretty weird and impossible as the state of the game in previous save files should be different.
So its nothing happening in your current save file state that causes the corruption, so it has to come from "outside", as the only fix i've seen is close the game, disconnect from internet, reconnect and restart the game.

So something is out of sync with ubisoft servers.

Normally it should have green lit eyes and i guess flames coming from them.
The flames never work, but the green 'light' does work, looks similar to the gloves.
Also they can go inverted for the light.

So to sum it up.
1 : the flames dont work, they do for the weapon, shield and horse and bird, so its not a graphical settings thing.
2 : Im not sure what triggers this but sometimes even the green light goes away from the eyes and they sort of invert, dark on the inside of the eyes but brighter around it.

Again i think number 2 gets triggered by certain cutscenes, simply walking around and jumping/running/doing whatever, seems to at least keep them normally lighted up. (still without flames though)

If i look at the character in the inventory screen, everything does show correctly.(and a simple dont show helmet/do show helmet can reset the eye thing at least)
This could also be the character LOD thing acting up as some people have reported, where the LOD of the character itself works kinda strangely, no ingame setting can change this.

Oh and Edit : the bird eyes can get in the way when you zoom in as the bird, the flames dance infront of the screen.. pretty sure that aint supposed to happen.