🛈 Announcement
Greetings! The Division forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game
  1. #121
    tbh after seeing so many posts and configs, its clearly not a problem with the players, we tried every possible troubleshooting fix. why does it work for some and not for others? idk, without any proper scientific reasoning :P we wont know. At the end of the day, its something that i feel only Massive can fix. We do not know the contents of the crash reports we been sending, perhaps if massive could share a few of the contents so to see is there anything that could shed light and help us understand the problem better
    Share this post

  2. #122
    After 2+ hours and opening ticket with my xdiag and msinfo to ubi i think i solved this thanks to the support guyss (Luis you rock)

    In my case, i have win10 updated + Nvidia drivers, still there was something wrong with .net runtime libraries.. This is the ubi message translated, in case it helps someone...

    After analyzing them, we can inform you that the incident you are experiencing may have to do with a failure in the Windows library. For some reason, the ntdll.dll file is failing in your operating system. We recommend that you try to reinstall some libraries, to try to repair that ntdll.dll.

    First, you should go to Control Panel> Programs and Features and uninstall all programs that start with the name "Microsoft Visual C ++" and "Microsoft Net Framework." Afterwards, you would have to install the following Windows components:

    Microsoft Visual C ++ 2005: https://www.microsoft.com/en-us/down....aspx?id=21254
    Microsoft Visual C ++ 2008: http://www.microsoft.com/en-us/downl...ils.aspx?id=29
    Microsoft Visual C ++ 2010: http://www.microsoft.com/en-gb/downl....aspx?id=14632
    Microsoft Visual C ++ 2012: http://www.microsoft.com/en-us/downl....aspx?id=30679
    Microsoft Visual C ++ 2013: https://www.microsoft.com/en-us/down....aspx?id=40784
    Microsoft Visual C ++ 2015: https://www.microsoft.com/en-us/down....aspx?id=48145

    Microsoft Net Framework: https://www.microsoft.com/es-es/down....aspx?id=30653

    Once you have downloaded and installed all these components, you should restart the PC. Then try the game, and if you still continue with the incident, the only remaining option would be to reinstall the operating system, because that is where the root of the incident lies. Regarding this issue, we attach the link to Microsoft's support so that they can guide you if you wish to carry out that process: https://support.microsoft.com/es-es

    Finally we are going to ask you to follow these tips to optimize your PC correctly:

    - Check that you have the updated Windows: https://support.microsoft.com/es-es/...ows-update-faq
    - Update the Nvidia drivers in case there is a new one or do a clean installation of the latest drivers: http://www.nvidia.es/Download/index.aspx?lang=en
    - Perform a file check in Windows: https://support.microsoft.com/es-es/...rrupted-system
    - Make a clean start in windows: https://support.microsoft.com/es-es/...oot-in-windows
    - Launches Uplay as administrator.
    - Check the game files inside Uplay.
    - Disable the following programs: Deluge, Bittorrent, MSI programs, any verlay you can have active and the RivaRuner

    If you have any other questions, do not hesitate to contact us again.
    Share this post

  3. #123
    Lens00140's Avatar Senior Member
    Join Date
    Feb 2019
    Location
    Straya
    Posts
    2,092
    If only everybody tried updating their Visual C++ half of the posts would not be here on the forums

    Great to hear you found a solution tuiputui plus giving cred where it's due
    Share this post

  4. #124
    Game's still crashing as usual despite the provided possible fix. Hoping this gets fixed soon, sucks crashing the end of mission and having everything lost.
    Share this post

  5. #125
    having same issue. this is not a fix but what I do to decrease my crashing is I disable my uplay overlay then go into the files and launch the game through the EAClaunch application and not the thedivision2 application. I get about 1-3 hours before crashing, I don't know why this way works better but if I launch the game normally I crash every 5-30mins
    Share this post

  6. #126
    Crashes just about stopped for me after doing the following:

    1. Uninstalled C++ 2017 in control panel and installed 2015 found in the game files
    2. Disabled Shader Cache in nvidia control panel

    Might help someone.
    Share this post

  7. #127

    Easy Anti-Cheat

    I was having nonstop crashes. I would be 5 mins in the game and it would instantly crash. So far, the only solution that has allowed me to play 3+ hours was to "reinstall" Easy Anti-Cheat program. You can find it in your Division 2 install folder. Good luck to everyone else.

    (The game will still crash but I would take 3+ hours of playing over 5 mins)
    Share this post

  8. #128
    Some really good info here, was wondering about the stutter that im getting and a few of the suggestions that others supplied have fixed the stuttering. Thanks
    Share this post

  9. #129
    Originally Posted by Pandah Go to original post
    I was having nonstop crashes. I would be 5 mins in the game and it would instantly crash. So far, the only solution that has allowed me to play 3+ hours was to "reinstall" Easy Anti-Cheat program. You can find it in your Division 2 install folder. Good luck to everyone else.

    (The game will still crash but I would take 3+ hours of playing over 5 mins)
    glad that worked for u, but it didn't for me. I think the problem is, theres like a multitude of reasons why one's game would crash, hence one solution might work for one but not for other. At least thats what I'm observing and that adds to the frustration, we see a potential solution, we hope it works, we get disappointed. Rinse & repeat makes for insanity
    Share this post

  10. #130
    Originally Posted by tuiputui Go to original post
    After 2+ hours and opening ticket with my xdiag and msinfo to ubi i think i solved this thanks to the support guyss (Luis you rock)

    In my case, i have win10 updated + Nvidia drivers, still there was something wrong with .net runtime libraries.. This is the ubi message translated, in case it helps someone...
    Question, this solution was given to you after they analyzed your DxDiag and MsConfig files that you uploaded to the ticket? Because in my case, this was not a suggested solution.
    Share this post