Random crashes in The Division....anyone got any ideas?

StevieP · 7 Jan 2019 at 23:54

I'm really enjoying The Division again but since putting together a new spec PC I'm getting random crashes and I can't figure out why!

I got a couple of crashes recently but my new Ryzen 2600 was getting very toasty in a badly ventilated case and with an awful thermal paste job on the stock cooler so I put it down to the temps getting up as high as 90°C :eek:

as the reason for the crashes!

Anyway, this evening I've put a new cooler on the CPU and put everything in a new case and so far the temps are massively improved (56.6°C max while playing!) so surely it can't be that!

I've tried verifying the game data through uPlay and it did find some errors and corrected them but it is still crashing (nothing in event viewer!)

The game was copied from another drive following a recent full OS reinstall to save having to re-download but can this be the problem since it's re-verified the game data OK??

Any help or things to try will be appreciated!

Malevolence · 8 Jan 2019 at 05:38

I had random blue screen crashes on The Division when I installed it on my newly built PC, a 2600X build for me. Turned out it was the motherboard's Intel Gigabit LAN drivers that were causing the problem. Simply updated them and voila, no more crashes. Are you sure there's nothing in the Event Viewer?

StevieP · 8 Jan 2019 at 07:28

Malevolence said:
I had random blue screen crashes on The Division when I installed it on my newly built PC, a 2600X build for me. Turned out it was the motherboard's Intel Gigabit LAN drivers that were causing the problem. Simply updated them and voila, no more crashes. Are you sure there's nothing in the Event Viewer?

Nothing at all in there for the time of the crash - bearing in mind though that they aren't blue screen crashes but rather just crashes to the desktop where it pops up with the message to send the crash report off!

What's really frustrating is that I've played it a lot recently without issue (albeit with the side off my old case because of the cooling issue) and the only changes yesterday was switching to the new case and putting a better CPU cooler on there! (ie. no tangible changes to the system hardware itself!)

Rroff · 8 Jan 2019 at 07:29

Make sure GPU is properly seated, etc.

Been any Windows 10 (assuming you are running it) updates since the crashing started? the game doesn't seem to run the best on that OS.

StevieP · 8 Jan 2019 at 07:44

It's a relatively new install of W10 (maybe a week or two) so update-wise it should be fine!

I'll check the GPU but with it being a new case install I was very careful to be honest!

So frustrating that it worked the day before yesterday and all I did yesterday was fit a new CPU cooler and shove it all in a new case!?!?

zola25 · 8 Jan 2019 at 09:28

When I had a 1st Gen Ryzen system running the 8 Pack DDR4 at XMP speed caused the Division to constantly CTD, I had to set the memory at 2666MHz or lower to get stability in games despite it passing every memory test I could throw at it. I'd imagine your 2600 will be more tolerant of memory, but could be worth a try.

StevieP · 8 Jan 2019 at 10:52

zola25 said:
When I had a 1st Gen Ryzen system running the 8 Pack DDR4 at XMP speed caused the Division to constantly CTD, I had to set the memory at 2666MHz or lower to get stability in games despite it passing every memory test I could throw at it. I'd imagine your 2600 will be more tolerant of memory, but could be worth a try.

Thanks for the suggestion, I'll give it a try!

The thing I just can't get my head around is that it's been working just fine for the last week or so (alveit with the side off my old case) and then all of a sudden a new case and CPU cooler seems to have affected it somehow!

I might try a full re-download or possibly even a W10 re-install to see if that helps!

wordy · 8 Jan 2019 at 13:13

Been getting these a lot over the last few days.

StevieP · 8 Jan 2019 at 20:57

Quick update on this - I deleted the game from within uPlay & deleted the various folders and re-downloaded the game - so far tonight no crashes to desktop at all! (played for roughly 2 hours!)

I'm not gonna say it's fixed....but it's been nice to get through a go without constant crashing!

Thanks to everyone that chipped in!

wordy · 9 Jan 2019 at 20:12

StevieP said:
Quick update on this - I deleted the game from within uPlay & deleted the various folders and re-downloaded the game - so far tonight no crashes to desktop at all! (played for roughly 2 hours!)

I'm not gonna say it's fixed....but it's been nice to get through a go without constant crashing!

Thanks to everyone that chipped in!

You’re welcome. I will of course take full credit for resolving your problem.

StevieP · 9 Jan 2019 at 20:24

wordy said:
You’re welcome. I will of course take full credit for resolving your problem.

Gotta be honest - I think it was your post that made the difference!

StevieP · 12 Jan 2019 at 16:20

Yeah.....the crashing is back! :confused:

I've just tried taking the advice of @zola25 above and set my memory frequency to 2666MHz in the BIOS but HWiNFO is reporting the "memory clock" as being 1197.4MHz (which I presume is rounded up to 1200MHz and running in dual channel making 2400MHz??

Any other suggestions?

zola25 · 12 Jan 2019 at 17:57

^That'd be my guess, although I would have thought 2666 would be a standard divider, unsure why it's defaulting to 2400Mhz (2 channels x 1200)

StevieP · 12 Jan 2019 at 18:15

zola25 said:
^That'd be my guess, although I would have thought 2666 would be a standard divider, unsure why it's defaulting to 2400Mhz (2 channels x 1200)

Well I've just played The Division for a good 2 hours with no crashes with the memory running at 2400MHz (although that isn't actually proof the game is more stable at that speed as it worked a couple of nights ago for that length of time while on the full 3200MHz!)

Regards the memory, should I be enabling the XMP setting and then overtyping to get it at 2666 or should I have it at "disabled" and still overtyping the speed?

zola25 · 12 Jan 2019 at 19:12

I'd be tempted to set XMP and then 2666. That way you'll at least get the timings and voltage you should have at XMP speeds. That's just my opinion though, it may not be the best solution.

As you've said this may not resolve your issue, but only time will tell. Out of interest did it impact performance much?

StevieP · 12 Jan 2019 at 20:19

zola25 said:
Out of interest did it impact performance much?

To be fair it didn't seem to impact The Division at all - in fact, and this makes no sense at all, whenever I glanced up at the FPS within uPlay I never noticed it drop below 110 whereas before I remember it dipping to the low 90's!?!? (this could just be down to the action on screen tho!)

What will bug me however is paying all that money for super-duper RAM and then not having it run at full tilt - even if it makes no difference to performance at all!

Undesirable · 12 Jan 2019 at 23:02

Ryzen's fussy about memory and according to DRAM Calculator by 1usmus the only difference between 1st gen and + gen is the SOC doesn't need as much voltage with the + chip you've got.

Here's a couple of configurations you can try in order to get the full 3200MHz but perhaps slacker timings than 8Pack mem should be capable of (enter all values manually in BIOS). If the first doesn't work, try the second:

Oh, and to optimize further towards games rather than synthetics, you'll want to switch BGS alt (bank group swap alt) from Enabled to Disabled, which is hidden somewhere in the BIOS (CBS settings or something).

Need more? Here's the advanced page:

Still not working? You're in for more "fun"; take a look at this flowchart to help improve stability yourself:

StevieP · 13 Jan 2019 at 12:31

Undesirable said:
Ryzen's fussy about memory and according to DRAM Calculator by 1usmus the only difference between 1st gen and + gen is the SOC doesn't need as much voltage with the + chip you've got.

Here's a couple of configurations you can try in order to get the full 3200MHz but perhaps slacker timings than 8Pack mem should be capable of (enter all values manually in BIOS). If the first doesn't work, try the second:

Oh, and to optimize further towards games rather than synthetics, you'll want to switch BGS alt (bank group swap alt) from Enabled to Disabled, which is hidden somewhere in the BIOS (CBS settings or something).

Need more? Here's the advanced page:

Still not working? You're in for more "fun"; take a look at this flowchart to help improve stability yourself:

Wow! I really appreciate the effort - I mean it's all waaaaay over my head but I will have a proper read and see what's what!

Thanks again...

Supr3me · 24 Jan 2019 at 09:07

Hey Steve,

Like you I've been jumping on the Division recently and was getting crashes to desktop every now and then. After searching through some threads on the Ubisoft forums, one of the things recommended is to disable DX12 in the in-game settings. Its under options > Video.

I done this last night and game seemed to run slightly better for a couple of hours without any crashes.

Not sure if you have tried this but if not worth a go.

Also if you fancy teaming up with someone let me know, would be good to run through the game with someone. I'm about 50% through main campaign.

StevieP · 24 Jan 2019 at 09:38

Supr3me said:
Hey Steve,

Like you I've been jumping on the Division recently and was getting crashes to desktop every now and then. After searching through some threads on the Ubisoft forums, one of the things recommended is to disable DX12 in the in-game settings. Its under options > Video.

I done this last night and game seemed to run slightly better for a couple of hours without any crashes.

Not sure if you have tried this but if not worth a go.

Also if you fancy teaming up with someone let me know, would be good to run through the game with someone. I'm about 50% through main campaign.

Thanks for the suggestion but I don't think mine was ever set to DX12 - to be honest in the end I've ended up just leaving my RAM running at 2400MHz rather than using the XMP setting to run at 3200MHz!

Since leaving the RAM at stock I've not had a single crash in The Division or any other game and truth be told it doesn't seem to have affected the performance at all! (Bit annoying but if I'm not seeing any drop in performance outside benchmarks then I'll probably just end up living with it!)

One day I will give @Undesirable 's RAM settings a go but I've never been to confident messing around with voltages and timings etc!

Happy to have a run through with you though - just need to find out what my username is on uPlay!