Tom Clancy's The Division

Tom Clancy's The Division

View Stats:
Øuantum3 Feb 9, 2019 @ 1:54pm
The Division Crashes / Close to Desktop
Hi there,

Since the two latest patches (1.8 and 1.9) the game became unplayable because it crashes and/or get closed to desktop. I have many hours played in this game, but since these 2 patches can't play it anymore. Each time the game is launched, after loading the latest save and playing some minutes, the game crashes.
--

I would like to know if someone else is having the same issue and if you bought the game around these days or not. That will help me to understand if there is a problem with the updates or not.
--

Already tried all the steps to solve this issue but none of them solved the problem. Please, address to the question. If you have some solution which is not found in google, pleaese, let me know.


Thank you in advance.
< >
Showing 1-15 of 16 comments
Frodonator Feb 10, 2019 @ 2:20am 
I pre-ordered it and have had that problem and still have that problem.
I also have it with division 2 and wildland's, but no other game.
The game crash's and I get the message to send a report.

All I found to help is to set graphic's to lowest and full screen windowed and it cut the crash's down lot's.

I could play all week with no problems, then one day I get it lots.
Reborn Feb 10, 2019 @ 3:18am 
if i may ask are you using windows 10? if so go to the settings snd turn off dx12
Frodonator Feb 10, 2019 @ 3:26am 
Not using DX12.
N3XU5. Feb 10, 2019 @ 5:06am 
I have this same problem on DX12 W10.
FraJos Feb 12, 2019 @ 12:05pm 
Same problem on Win10 and DX12 OFF.!!!
N3XU5. Feb 12, 2019 @ 2:04pm 
Ubisoft support help me with this. Translate this from polish to english.

1. Proszę odnaleźć plik .exe dla UplayPC (znajduje się on domyślnie w folderze C:\Program Files\Ubisoft\Ubisoft Game Launcher, plik Uplay.exe) a następnie proszę kliknąć na pliku .exe prawym przyciskiem myszy i wybrać opcję Właściwości. Następnie proszę o przejście do zakładki Tryb Zgodności i zaznaczenie opcji 'Uruchom jako administrator'. Proszę kliknąć na Zastosuj i OK.

2. Proszę wyłączyć wszystkie aplikacje z autostartu.

3. Proszę również uruchomić grę przy wyłączonej funkcji nakładki aplikacji Uplay (Overlay). Proszę kliknąć na ikonę z trzema poprzecznymi paskami w lewej górnej części ekranu aplikacji Uplay, i przejść do Ustawień. Należy odznaczyć "Włącz nakładkę wewnątrz gry dla zgodnych gier" i zaakceptować klikając na "Zapisz". Następnie proszę zrestartować klienta Uplay i spróbować uruchomić grę.

4. Proszę o wyłączenie wszystkich nieużywanych w grze urządzeń USB. Pozwoli to wykluczyć ewentualny konflikt.

5. Proszę upewnić się, że podczas uruchomienia żadne dodatkowe oprogramowanie nie próbuje uzyskać dostępu do plików gry. Dotyczy to również programów antywirusowych i dobrze jest dodać poniższą lokalizację do wyjątków programu antywirusowego.

C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher

Następnie proszę zweryfikować pliki gry oraz usunąć folder z plikiem konfiguracyjnym gry. W ten sposób zostaną przywrócone jej ustawienia domyślne. Plik można znaleźć w poniższej lokalizacji:

C:\Users\[Username]\Documents\My Games\Tom Clancy's The Division\State.cfg
racdavies Feb 12, 2019 @ 4:09pm 
They seem to have fixed the green flickering but not the ctd`s, well with D2 on the horizon why would they bother fixing the first game now
Øuantum3 Feb 12, 2019 @ 5:24pm 
Hey people, yes; it was the DX12 thing... can't believe it because I've played lot of hours with DX12 on without any problem till these updates came in. It seems that UbiSoft won't solve this.
the citizens Feb 12, 2019 @ 7:46pm 
DX12 on or off doesn't fix it for me , ive had enough wasting my time with this B/S ubisoft fix it ASAP
Player 2 Feb 12, 2019 @ 9:53pm 
Originally posted by Bio-Break:
I pre-ordered it and have had that problem and still have that problem.
I also have it with division 2 and wildland's, but no other game.
The game crash's and I get the message to send a report.

All I found to help is to set graphic's to lowest and full screen windowed and it cut the crash's down lot's.

I could play all week with no problems, then one day I get it lots.
This. i do everything and i tho i fix it already but no its still got ctd constantly. the only thing i can do is just use default setting and windowed mode. its reduce ctd chance. even i got constant 60fps in the benchmark after increasing graphic setting, i got ctd immediately ingame.

i just get the game btw. and most of my playtime is just watching connecting screen:(

oh and i have no problem with wildlands
Last edited by Player 2; Feb 12, 2019 @ 9:54pm
Avalanche Feb 12, 2019 @ 10:02pm 
Well, i had the same problem, turned off DX12 and it stopped, but it happens between the Ubisoft logo and the loading animation.....if it crashes for me at all, it will be before i can choose my character.
Øuantum3 Feb 13, 2019 @ 4:43am 
Originally posted by Lithari:
Well, i had the same problem, turned off DX12 and it stopped, but it happens between the Ubisoft logo and the loading animation.....if it crashes for me at all, it will be before i can choose my character.

That happened to me also; after the screens with the brands and such, the game closed to desktop or froze the computer (with DX12 on).

I also found that playing in windows mode is more probably to not occur a sudden crash (with DX12 on).

I have not played The Division for some time, but for the latest updates the problem was, each launch of the game, more often.

In DX11 I have found no problems at all but the game supports DX12 and DX12 is much better than DX11.

Ubisoft MUST fix this. And probably, because The Division is for nVidia and The Division 2 is for AMD I think they're not using the same API since AMD uses Vulkan and that's why I think they won't fix this problem.

Btw, The Division 2 sucks. It's more of the same with more elements on screen and better God Rays (they're the same than usual but with a layer of blur with low opacity, kind of bloom effect on it). Game play is exactly the same than in The Division 1. They have improved nothing but made a bigger and clustered map.
Last edited by Øuantum3; Feb 13, 2019 @ 4:47am
Secret Squirrel Feb 13, 2019 @ 7:44am 
I can play all day long on Windows 10 and the game set to DirectX 12. I know that because I did that yesterday.... and the day before. LOL.

Sorry to hear your experience is not the same. I usually recommend a few things as the standard starting points. Use Display Driver Uninstaller (DDU) to remove the GPU driver completely. Use the best mode which requires boot into safe mode -- that is the best way to ensure all pieces are removed. Then re-install the drivers using the latest.

Shut down all processes that may be hooking into video, like riva tnt server, game overalys (except uplay of course), turn off game capture things like NVidia shadow play, steam stream server, etc.

Validate local files, in steam by going to properties of the game and "local files".

A lot f times, weird issues are often fixed by going to the game executable in file explorer, right clicking, and the "compatibility" tab turn off "High DPI Scaling"

Also, within the games graphics settings, turn off HBAO+ from the ambient occlusion setting. When I have this on, it doesn't crash but there are areas and lighting that cause the frame rate to drop into the single digits. Seems to be a bug here.
Last edited by Secret Squirrel; Feb 13, 2019 @ 7:47am
Secret Squirrel Feb 13, 2019 @ 10:34am 
Apologies, I thought I was on DX12 because I did set it that way, but checking again it isn't.... and as soon as I select DX12 and restart, it crashes. I recall finding that unstable a couple years ago when I bought this game. So yes, I'd say it is bugged and best to avoid DX12, because otherwise I find the game very stable.

The good news is, when I beta tested The Division 2, I definately had DX12 enabled and am sure it took, and was stable. But I wouldn't expect a patch here since this game is pretty much out of major support.
Last edited by Secret Squirrel; Feb 13, 2019 @ 10:35am
Øuantum3 Feb 17, 2019 @ 5:56am 
Originally posted by Secret Squirrel:
Apologies, I thought I was on DX12 because I did set it that way, but checking again it isn't.... and as soon as I select DX12 and restart, it crashes. I recall finding that unstable a couple years ago when I bought this game. So yes, I'd say it is bugged and best to avoid DX12, because otherwise I find the game very stable.

The good news is, when I beta tested The Division 2, I definately had DX12 enabled and am sure it took, and was stable. But I wouldn't expect a patch here since this game is pretty much out of major support.

Hey no problem... It was the DX12 thing. You know, I've played a lot this game before the 1.8 update, always with DX12 on and never had a problem. Even with the update 1.8 had no problems but it seems that Ubisoft did something before the patch 1.9 that made the game crashing with some regularity; then, with the 1.9 patch the game crashes when loading the game.

I assume that is because The Division 2 was linked to the Division 1. The Division 1 works with nVidia and the Division 2 works with AMD. You know nVidia uses DX12 natively if you own a PCIe 3.0 motherboard and video card of same characteristic while AMD uses Vulkan for all the rendering; so that's why I think that DX12 isn't working anymore in The Division 1. I guess that change from nVidia to AMD resulted in some incompatibility regarding the graphics drivers nd the cross plataform thing.

AMD and nVidia uses different APIs, as said above, AMD emulates DX12, so it isn't true DX12 and The Division 2 isn't also. It's just an emulation. nVidia is also emulating DX12. All games you see that say are compatible with DX12 is just a lie; there are only few native DX12 games in the market; all the others are emulated. You can check in Internet the difference between Vulkan, emulated DX12 and native DX12. I assume that game companies are squizing the emulation of DX12 since it gives very good results. Doom was done for Vulkan, for example, which allows cross plataform since Vulkan will be used (if not already) in cellphones, tablets, notebooks (Play Station uses Vulkan) and it supports even Windows XP while the True Native DX12 is only supported by PC and Microsoft XboX (but, XboX uses a diminished version of DX12 but much better than Vulkan).

Vulkan is the AMD attempt to win the videogames market againts nVidia/Microsoft DX12 by supporting any plattaform, but Vulkan is far far far away to provide all the features that True Native DX12 has.

As for Ghost Reacon Wildlands, I have no problems with DX12.

Hope this help and also, the extra information.

Have a good day :)
Last edited by Øuantum3; Feb 17, 2019 @ 5:59am
< >
Showing 1-15 of 16 comments
Per page: 1530 50

Date Posted: Feb 9, 2019 @ 1:54pm
Posts: 16