I'm having the same issue also, tried all the suggestions and still no luck. It can crash every few minutes and other times I can play for an hour or more before it crashes. I've played Div 2 for a long time now but this has only been happening in recent months and it's getting to the point that i don't want play it any more because i know I'll just get frustrated with it. I would really hope this is fixed, along with the graphical bug (https://discussions.ubisoft.com/topic/99978/graphics-glitch/19?lang=en-US), prior to the new content being deployed. Fix the existing issues before making new content otherwise people are not going to buy the new content if they can't play it reliably.

You see: all of the aforementioned 7 app crashes share only 2 unique exception offset addresses. Those being either fault offset address "0x000000000035f3c4" or "0x00000000004df7e4".

So tl;dr: There probably is something within the game code that tries to access memory that doesn't exist..
If anybody wants to check if this is the cause for their game crash, open "Event Viewer" -> "Windows Logs" -> "Application" and look out for error events with source "Application Error" and an "Event ID" of 1000. If it says "Faulting application name: TheDivision2.exe" and "Exception code: 0xc0000005" under the "General" tab, it's this issue.

So I get the same 35f3c4 fault offset address as described by @GrannyMist. I decided to take the plunge and flatten my system and then installed Win11 hoping that may help. Obviously that meant reinstalling Ubi Connect and i uninstalled and reinstalled Div2. Did it help? Did it work? Did it hell, it still CTD :(, yet everything else works fine.

Come on Ubi, get this fixed or you're going to lose players who are losing faith in your products!

@hralex1951 I have installed the latest driver but I'm unable to play Div2 long enough to verify it has resolved the glitching for me as i keep getting the CTD issues still under investigation by Ubi.

@paulpc_ro Yeah, i lost my HC character because of the issues which has made me reluctant to try HC again.

@hralex1951 I have installed the latest driver but I'm unable to play Div2 long enough to verify it has resolved the glitching for me as i keep getting the CTD issues still under investigation by Ubi.

You see: all of the aforementioned 7 app crashes share only 2 unique exception offset addresses. Those being either fault offset address "0x000000000035f3c4" or "0x00000000004df7e4".

So tl;dr: There probably is something within the game code that tries to access memory that doesn't exist..
If anybody wants to check if this is the cause for their game crash, open "Event Viewer" -> "Windows Logs" -> "Application" and look out for error events with source "Application Error" and an "Event ID" of 1000. If it says "Faulting application name: TheDivision2.exe" and "Exception code: 0xc0000005" under the "General" tab, it's this issue.

So I get the same 35f3c4 fault offset address as described by @GrannyMist. I decided to take the plunge and flatten my system and then installed Win11 hoping that may help. Obviously that meant reinstalling Ubi Connect and i uninstalled and reinstalled Div2. Did it help? Did it work? Did it hell, it still CTD :(, yet everything else works fine.

Come on Ubi, get this fixed or you're going to lose players who are losing faith in your products!

I'm having the same issue also, tried all the suggestions and still no luck. It can crash every few minutes and other times I can play for an hour or more before it crashes. I've played Div 2 for a long time now but this has only been happening in recent months and it's getting to the point that i don't want play it any more because i know I'll just get frustrated with it. I would really hope this is fixed, along with the graphical bug (https://discussions.ubisoft.com/topic/99978/graphics-glitch/19?lang=en-US), prior to the new content being deployed. Fix the existing issues before making new content otherwise people are not going to buy the new content if they can't play it reliably.

Same issue here on 3080Ti so please get this fixed ASAP as i really dont want to keep rolling back drivers.