🛈 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. #11
    Originally Posted by Ubi-Redbeard Go to original post
    Hey folks,

    Sorry to hear this issue is still persisting.

    If you're still experiencing this issue - please create a case on the support website and submit your DxDiag and MsInfo files for further investigation?

    Once you have created your case, please provide us with your case number so we can look into this for you.

    Thanks.
    Thanks for responding to this thread.
    I'm a bit puzzled because I've seen some people don't have this issue at all on DX12 with pretty similar if not the same hardware, drivers, windows and updates.
    It's very strange. Last night I had two crashes in 30mins and after that almost 2h of playtime without any crash. I would like to know what's causing this kind of random problem behavior.
     1 people found this helpful
    Share this post

  2. #12
    SuspiciousPixel's Avatar Senior Member
    Join Date
    Apr 2012
    Location
    Chasing Keener
    Posts
    1,740
    Originally Posted by Ubi-Redbeard Go to original post
    Hey folks,

    Sorry to hear this issue is still persisting.

    If you're still experiencing this issue - please create a case on the support website and submit your DxDiag and MsInfo files for further investigation?

    Once you have created your case, please provide us with your case number so we can look into this for you.

    Thanks.
    Why are you still giving a generic response to DX12 issues?

    This has been on-going since release. The threads created on this issue which had several hundred replies were closed and no resolution was found from your "on-going investigations".

    Whether DX12 works seemed to be hardware dependant, so I beg you stop giving people false hope that something will be done about it and whilst I am here, the 100% CPU usage issue too.
     11 people found this helpful
    Share this post

  3. #13
    I check about the CPU usage.
    It comes from 46% to 99% all the time, then for some reason, i leave the character standing inside the main base.

    Again, CPU jumping like crazy for some reason and i dont know and understant why this is happening.

    I dont blame DX 12, I think is something else that is making trouble inside the game.

    The graphics seems to be volatile, many places where are just white walls, cubic cars, even no floor in the city.
     1 people found this helpful
    Share this post

  4. #14
    Hmm, I run the game on DX12 with way less issues than described here - except i've seen these CTDs a few times too and MAY have found a solution:

    So far, Afterburner seems to be the "issue". Division (and Div1 + FC5) never liked anything related to OC - so my pitch here is this: Try playing Division - in DX12 - without ANY Rivatuner/MSI Afterburner/EVGA-whateveritscalled and minimize overlay usage (not uplay, RTSS and steam plus the games bar from Win10 ontop of each other. Choose ONE and run with it). Just for testing - an make sure to run your card at stock everything and see what happens.

    I could largely mitigate this CTD behavior for Div2 - even if this is the only game that exhibits this touchy behavior (stress-tested any over/underclock for hours before, so it's rock solid elsewhere).

    My Specs are 3600X, 32GB DDR4 3000Mhz, GTX 1080 and the game runs from an NVMe drive.
     1 people found this helpful
    Share this post

  5. #15
    Fr33w8's Avatar Junior Member
    Join Date
    Mar 2019
    Posts
    13
    Are you by any chance also running an overclock on your GPU?
    I had a lot of DX12 crashes, since around the TU7 update. Especially in the inventory, when the background goes dark. This should be easier for the graphics card, but consistently crashed mine. I had to dial the overclock on chip and memory way down for it to run stable again. In DX11 there are no issues with regular overclock.
    Share this post

  6. #16
    I had this problem before, with disabling full screen optimization in win10 solved the crash issue for me but not 100% CPU usage!
    Share this post

  7. #17
    I'm also having a crash because of DX12, I like DX12 'cause it boosts my fps and less stutters unlike DX11, it crashes after few hours of playing or after an hour, I had a 3rd party program that keeps it crashing every 30mins or so but I remove it every time I play but it still crashes. Did everything I could to remove the crash but it's still there.
    Share this post

  8. #18
    Like I implied earlier, I found a correlation between tools that change your GPU behavior (over- AND underclocks) and the CTD issue in DX12 with these games. But to answer your question directly: No, I had my 1080 undervolted (firestrike stress-test, not just reruns, stable =).

    I've tried the "disable fullscreen optimizations" workaround BAlDBOlD suggested - but since the game has the DELTA-3 issue right now (ubi seems to be working on it right now) I cannot test it ;D
     1 people found this helpful
    Share this post

  9. #19
    I just can't believe that they still have the nuts to ask for people's money for DLC and yet not fixing this damn DX12 crashing!!!!! WTF is wrong with you at Massive/Ubisoft? So many people have this problem and you're silent??? Get your **** together developers and fix this or you will be fired and you guys vote with your wallet next time.
     3 people found this helpful
    Share this post

  10. #20
    OS: Windows 10
    CPU: i7-3930k (OC'ed to 4.2GHz)
    RAM: 32GB 1600MHz (quad-channel)
    GPU: EGVA 1060 6GB SSC

    I'm running quite happily with DX12 and butter-smooth performance on near-max settings.

    Average CPU usage is around 60-70% when playing.
    Share this post