A fix for the Division 2 Game 100% CPU crash | Forums

[Hideookino]

First off im playing on my Asus Rog GL752VW. This fix worked for me and it may not work for you.

I played beta with 0 issues, but for some reason on release I couldn't even get past the first explosion.

I had no sound, everything felt choppy, benchmarks were either stopped in the first phase or crashed on the last.

I tried everything that was posted in the past week and even tried some of the division 1 fixes. Everything from no overlays, changing all video/graphic settings to raise gpu and lower cpu, re validating, re installing, priority changing, nothing.

THE ONLY THING THAT ACTUALLY WORKED...was plugging my headphones in.

I replicated the crash and the fix 5 times in total with 100% success rate. I've played a total of 3 hours and 10mins (not counting the 36mins spent configuring and failing) with 0 crashes.

Windows audio device graph isolation was apparently the problem. (No it was not a virus, enhancements were turned off)
Every time Division 2 crashed and when the few times task manager actually worked i saw windows audio device graph isolation show up as one of the top processes under CPU usage. Since i plugged in my headphones it really seems to behave.

Windows audio graph isolation was using 15-20% CPU while it was running without headphones. With them plugged in, it dropped to .6-2%.

I hope this works for some of you guys.

[Lens00140]

THE ONLY THING THAT ACTUALLY WORKED...was plugging my headphones in.

That is the strangest fix I have heard yet!

Anyways what ever does it for you must be a good thing, Enjoy the game!

[blaQ-]

What did you actually do? Replace your speakera with a headphone?

[Hideookino]

All i did was plug in my turtle beach headphones into the usb port and start the game up.

[Lens00140]

and it's still working alright?

Also read on another website about one of the beta's and crashing, some people figured out that to have less issues, stop game play about ever hour and close uPlay and restart. Probably the memory issue

[dbgager]

That would have no effect on anything. Its just a coincidence. ALso if its crashing its not because the CPU is a t 100%.

[Lens00140]

dbgager, I've come across some really really strange things over the years building and repairing pc's and it's not out of the question, plugging in a usb device and do some strange things to computers.

I'm sure you've seen some strange stuff in your travels as well dbgager

I'm going to suggest that Hideookino doesn't post this in the tech section tho, not after what someone replied to me when speaking with another agent about a poss fix for them
here's the linky https://forums.ubi.com/showthread.ph...p-on-PC/page19

Scroll down to my response then go back a couple of pages

[dbgager]

Not going to happen. That's an output device. Its not going to have any effect on a program.

[Hideookino]

The thing is still working with 0 crashes and no auditory/graphic issues.

Well, if you don't count the few skill bugs, everything is perfect at 13 hours in.

@Dbgager

Windows audio graph isolation was using 15-20% CPU while it was running without headphones. With them plugged in, it dropped to .6-2%.

I just plugged in my apple corded earbuds and the game works fine too. When I took them out and restarted the game, I lasted 5 seconds before I had to manually restart my laptop.

So maybe it does have to do with Windows audio graph isolation process?
(tried ending the process, funny thing about WAGI is that is likes to run and ending will just cause it to start back up again)

All i know is there have been countless errors/posts about Windows Audio Graph Isolation when it comes to music/games with/out headphones. And most if not all of the issues are about high cpu usage.

You are also right, technically its not a crash, it just takes 10-20 minutes to see any response after it hits 100% and my laptop heats up. Because of this and potential damage I'd call it a crash and reset everything.

@Lensoo14o

I thought it was a memory issue too.

[tcarlisle2012]

Anything is possible. I've seen games where if you launch the game with a controller attached, it raises the chance that the game will suffer a memory leak. But if you disconnect the controller and launch the game, then plug in the controller it is stable. That was Just Cause 3.

That said, I am pretty confident this game doesn't have memory leaks, because if it did I'd see symptoms playing it literally 12 hrs continuously. And I have played while capturing performance and resource usage metrics, and upon review I saw nothing concerning.

What is probably at play here, is the audio device driver. Windows 10 doesn't always give you the latest driver. It isn't uncommon to have to find the latest driver and install it.

Windows audio device graph isolation specifically exists so that audio device vendors can add their own audio enhancements to the audio stack. If that is causing problems, then it points to the audio device driver being problematic. So really, this sounds like a hardware device issue and beyond the games control to resolve.

Just like the logitech headset problem where those folks are having tons of audio issues and expecting the game to fix.... never mind the logitech 933 seems to trigger audio issues in a lot of games. So my money is on that the issue resides completely on Logitech's side and their driver or audio enhancements.