Crashing in The Division | Forums

[Fist-.]

I had same problem that most of you are currently having with instant crashing while trying to log in. I tried all the other recommended options and nothing worked. After one crash sent me BSOD I was way mad.
I suspected the game at first, then I began to question my hardware.

Win 10 Pro
i5 4690k
GTX 970
z97 mobo
16 GB RAM

At one point I did manage to log in only to crash 3 min later, I never moved just was checking setting options. Everything was High or ultra. Did not get to see all since I crashed.
Any how I suspected unstable OC in GPU or CPU.

My work around; default cpu and gpu disconnect all usb not needed (printer, wireless headset, so on) disconnected HDD back up drive and SSD temp storage drive.
only drive running was my 500 gig SSD main drive.
Game booted up and logged me in, some what slower then I am use to, but I got in no crashes after 30 min of play. FYI settings defaulted to medium.

I logged out and now I will try connecting USB and drives one at a time then resetting after each one and logging into game. after all is online and game logs and runs for at least 30 min, I will then try OC cpu but at 50% of what my original OC was. Same with GPU. I will update later with what happens.

Time consuming I know but I must find out if it was due to OC or hardware. Maybe not the answer you guys where looking for but it worked for me "so far".

Time consuming I know but I must find out if it was due to OC or hardware. Maybe not the answer you guys where looking for but it worked for me "so far".

[Zakuaz]

So as I searched around in hopes of a fix I stumbled upon a WatchDogs thread that was about the game crashing on startup. In there the conditions appeared to be identical to my situation blah blah blah:

The culprit for me was the Overlay64.dll, it's located in the games Ubisoft folder C/programfilesx86/Ubisoft/Ubisoft game launcher.

I renamed mine to overlay64.dll.old and just played the game for the first time (3 hour session, maybe more)

To find out if your issue is related to the overlay64.dll run msinfo32 and painstakingly scroll to todays date and look for any "application crash" related to "The Division" - highlight that line and if the "Faulting Module" is in fact "Overlay64.dll" well then go the folder I mentioned above and rename that file to overlay64.dll.old


Not a fix but it worked...I'll assume/hope UBI can squash some of these issue for launch.
GL n HF!

[jlh221]

Looks like I am primarily getting video driver errors, which either result in the game crashing, or my computer freezing and being forced to restart. I have not had this issue with any other game or application. Have tried playing fullscreen and windowed fullscreen. In both cases will encounter the error within a minute of entering a game.

MSI MS-7919
Intel core i7-4790K
RAM 32GB
NVIDIA GTX 770 - 361.91 (also tried on 361.75 which is labeled as optimized for The Division Beta, still crashes)
Windows 7 Pro - 6.1.7601

I am seeing this error a lot.

2/19/2016 11:50 PM Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20150128-0016.dmp
C:\Windows\Temp\WER-806665928-0.sysdata.xml
C:\Windows\Temp\WERBF16.tmp.WERInternalMetadata.xm l

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\K ernel_0_0_cab_7390bf16

Analysis symbol:
Rechecking for solution: 0
Report Id: 22c8b811-a6b5-11e4-9bd2-448a5ba58f04
Report Status: 0

edit: for detail accuracy

[FunkyTowel]

Every fix is comming from players and not Devs so why not pay the players half

[PabPicass]

GPU: AMD R9 390x
CPU: i5 - 6600k OC @ 4.5
16GB RAM @ 3000
MSI z170 CHIPSET



2/20/2016 1:13 AM Application Error Faulting application name: TheDivision.exe, version: 1.0.0.0, time stamp: 0x56bb5f28
Faulting module name: d3dcompiler_46.dll, version: 9.30.960.9200, time stamp: 0x5010a64d
Exception code: 0xc0000005
Fault offset: 0x00000000001df6f8
Faulting process id: 0x12d0
Faulting application start time: 0x01d16b744b16d9d8
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Tom Clancy's The Division - Beta\TheDivision.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Tom Clancy's The Division - Beta\d3dcompiler_46.dll
Report Id: 1837885c-2c30-4db7-97e0-d7420d8e5c60
Faulting package full name: 
Faulting package-relative application ID:

[PattonHe]

i am changing res from 4k to 2k, the game crash everytime.

my spec:

i7 4960X CPU
3 ways titan X GPU
the game installed in ssd
win 10

[LvJasper420]

Problem signature:
P1: thedivision.exe
P2: 1.0.0.0
P3: 56bb5f28
P4: 763a
P5: 134217728

running an i5-4670k
8gb ram
GTX 960
windows 10

have tried workaround but none seem to work

[Nullsec23]

So as I searched around in hopes of a fix I stumbled upon a WatchDogs thread that was about the game crashing on startup. In there the conditions appeared to be identical to my situation blah blah blah:

The culprit for me was the Overlay64.dll, it's located in the games Ubisoft folder C/programfilesx86/Ubisoft/Ubisoft game launcher.

I renamed mine to overlay64.dll.old and just played the game for the first time (3 hour session, maybe more)

To find out if your issue is related to the overlay64.dll run msinfo32 and painstakingly scroll to todays date and look for any "application crash" related to "The Division" - highlight that line and if the "Faulting Module" is in fact "Overlay64.dll" well then go the folder I mentioned above and rename that file to overlay64.dll.old


Not a fix but it worked...I'll assume/hope UBI can squash some of these issue for launch.
GL n HF!

I basically did this, except my file was intelocl64.dll - I renamed it to intelocl64.dll.old
It was located in C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64 -- No clue why it worked but it did.

Find the faulting Module "file" via the Windows Error Reporting log in msinfo32.exe, rename whatever is causing the issue.

Thanks to Zakuaz for the tip.

[Monkeysuit]

Followed all the steps in OP. Still crashing on launch. But uninstalling C++ had the added benefit of leaving me without explorer.exe working properly. Love having to operate computers from task manager.

20/02/2016 2:38 AM Application Error Faulting application name: TheDivision.exe, version: 1.0.0.0, time stamp: 0x56bb5f28
Faulting module name: TheDivision.exe, version: 1.0.0.0, time stamp: 0x56bb5f28
Exception code: 0xc0000005
Fault offset: 0x000000000000ccab
Faulting process id: 0xb8c
Faulting application start time: 0x01d16b87b24a5a8d
Faulting application path: D:\Steam\steamapps\common\Tom Clancy's The Division - Beta\TheDivision.exe
Faulting module path: D:\Steam\steamapps\common\Tom Clancy's The Division - Beta\TheDivision.exe
Report Id: 4c94f834-aa91-41c8-87cf-fd48376c0c03
Faulting package full name: 
Faulting package-relative application ID:


CPU: Processor Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz, 3201 Mhz, 2 Core(s), 4 Logical Processor(s)
GPU: NVIDIA GeForce GTX 650
RAM: 16.0 GB
Motherboard model: Acer Veriton M680G
OS Name Microsoft Windows 10 Pro
Version 10.0.10586 Build 10586

[Ironeyes-]

Ubigames all suffer from the same problem, they do not play well on factory overclocked Nvidea cards(no idea about ATI cards). The only way I can play without freezing and CTD is to underclock my video card.