Siege Is Already Installed and Its Telling Me It Needs to Install 24gb Again

Hi,

Few weeks agone i decided to play this astonishing game over again after a long break. Equally many of you, for the commencement 20minutes of gameplay i faced this CTD result, fabricated most impossible to play this game so i decided to "gear up" it or at to the lowest degree investigate what causes the outcome.

Kickoff things get-go, my post is written in timestamp, things i tried in lodge.
Second.., all of the tests and results are made in DX11 fashion .
3rd.., from the very first moment, i tried the mentioned methods without any ingame overlay (uconnect, RTSS OSD etc) and considering i had no inkling at all at the first, i removed my CPU and RAM OC, too didnt utilise my dVGA undervolt profile, but the base clocks and speed on everything.

This mail will exist long for a reason, i only want yous to salvage your time boyfriend players.

My config:

i7 9700K
16GB of RAM (XMP 3200)
1080Ti
Win10 on NVMe SSD (950Pro), Division2 is on a separate one (860 EVO).

Then.., where should i starts. Well for first, only like many of you i thought it must be a driver (NV) problem, so i tried half-dozen ( Vi!! ) dissimilar NV drivers, from the newest (466.77) to the oldest (442.59 - 2020.03.10) without whatever result.
The moment i experienced my 2-3rd CTD with the sixth NV commuter, i did start to ask my clanmates nearly their VGA'due south and drivers, information technology gave me an instant upshot, this outcome has no contact with whatsoever VGA or CPU manufacturers (AMD, Intel or NV), considering two of them had the very same issue, one with second gen Ryzen & RX 580, another config is newest Ryzen with 6800XT. NV'southward users had 2060, 2x 3060 Ti, reported the very same issue.
And then.., event ane: ignore and/or skip

every

VGA driver version or driver setting advice from

anyone

, came from offical source (this site & forum) or from unoffical source, its simply doesnt affair, bullsh1t.

Since the moment i decided to play Partitioning 2 again was the adjacent day i did install a clean Win10 (2021 H1) with MCT, my second suspect was the operating organisation itself.

I had an idea to cheque the Win10 Event Director, maybe i find something useful there and ohhh ladies and gents, i did..!
Every single ****ing CTD of the past days had the very aforementioned ID: 0xc0000005

Its a retentivity access violation code.

I tin guarentee.., 90% of you get the very aforementioned error code after CTD, how practise i know? Well allow me continue..
(remaining 10% shares on hw & unstable OC etc.. errors)

You all know EAC.., the thing that doesnt let u.s. change the game priority to High without regedit usage, simply at least its worthless as an anticheat, its but in that location in the background process list to make our life harder.
Well.., in the "operating system investigation" line, my outset pace was to disable every single built-in Win10 security "features" from Defender across firewall, DEP and other program behavior "analyzers" that tin molest EAC and/or Division2 & uconnect (exe's and folders), i thought the problem came from here, possibly any of them insult these the game files while nosotros playing.. NO. Turning them off changed naught, just i kept them OFF to maintain the pace-by-step method.

(To keep alive the main reason i write this postal service i can tell y'all, in that location are many, i mean MANY solutions on the spider web how to "fix" this error code, NONE of them works for Div2, i tried them all..)

After i realized i get this very aforementioned code every ****ing time, i asked the aforementioned clanmates who did share their config and driver version infos with me, to cheque their logs, what error code they recieve when/later CTD occurs..?!
Well dear readers, i hope all of you sit down, they recieve the VERY Aforementioned. c0000005.

Okay.., i thought its a progress anyways so i fabricated a bigger step, i did clean install TWO other, older Win10 versions, 1909 (19H2) and 1809 (Redstone) with NV drivers from the same era.., hell, time throw out of window. No positive effect, same CTD frequently, same mistake code.

Please note.., at this betoken, nosotros are easely can divide/lock-out two main factors, hardware (& their drivers) and Win10 from the possible suspects list.

Whats left..?! Well, software anomalies and the Memory itself (RAM or whole virtual.., i wasnt sure at this point.).

To keep,, i did clean install the 2021H1 Windows ten back and made a quick cheque what software dependencies the game has.
I find out, when nosotros install Div2 it uses & install a chip onetime Visual Studio versions, and then i took them off and replaced them with the newest ones of each (2012 & 2015).
Likewise installed NET Framework iii.5 next to the already installed newest one.
Result.., aye.., for now you can guess..

And then i turn my attending to the folders the game concur its files, installation dir and the one in D&S/Username/Mygames and the rules/permission & ownership settings of those dirs, no upshot at all.
After this point.., i felt i ran out of ideas..

I made a bootable USB bulldoze with Memtest86, ran a 4phase full retention exam & scan, it took nigh 3 hours, nothing, zero error, my 2x8 kit is perfect.

Ok, then turned my attention to the page file, and ****ing finally, here starts the story..
So my showtime step with the page file was to took it out of windows "manage" hands and i did prepare it manually to set 24GB (min-max 24).

The frequence of the CTD'south seems slowed down a bit, sometimes i was able to play 30-40 mins in a row (dont you lot dare to laugh..! ).

I felt im on the right runway, my next motility was to minimize the page file size, so i did gear up information technology to 1GB and jesus christ, the next 60 minutes gave me the long waited "heureka" moment.
Yes-yes, believe or non, from this moment i could reproduce the CTD and the same fault code ANYTIME i desire..!!!!

How..?! Uncomplicated.., OSD with RAM usage. The game crashed everytime i reached 60-62% of RAM usage, god damn, its a memory leak!

Google is our best friend they say.., so the Div2 & pagefile search leads me to this thread, back to January:
https://forums.ubisoft.com/showthread.php/2316158-Division-2-retentivity-leak-issue

A player.., AltairCreation discovered this issue nigh a year ago.

(Btw.., no matter of how much RAM you accept, sixteen or 32GB, you can test it with this method above anytime y'all desire.)

Then here we are, at the by few months you tin can read different promises and balderdash****s hither, request you to send dxdiags and other reports to help "investigate" the problem, all of you can be

absolutely sure

, there is Nothing to investigate.
Its only interim for the reason to become some fourth dimension, why?! Well, I retrieve i started to understand this one also..

This memory leak in the game code introduced itself in January.., then at some indicate they patched it.., how the hell could it came back?
Remember what happend not too long ago, when Massive restarted the seasons, "to give us the opportunity to play it again" they said?!
It started with a hell of a lot bugs, fifty-fifty the maintenances had their own mainteneces #two sometimes #three at the same days, they had a very difficult time to keep the game on its legs, and here comes the matter!!
Information technology was the very same time, when the game version in the card went from numbers to "unoffical".., recollect ?!

Whatever this "unoffical" version is really, an before dev & tester version or just a modded version to be able to replay the seasons, the base of the code it operates has the retentiveness leak issue and once over again, you can exist 100% sure they knew and know it !
They just merely cannot exercise anything with it, maybe fixing again doesnt worth the time (to them^^) or who knows, but they know if the season ends (soon) they can render to the last offical version & release, and aforementioned moment the "unoffical" version will disappear from all of us, last (patched) version of the game will stand for again, and this CTD madness due to the retention leak volition disappear aswell. I cant wait to read that "patchnote" where they will proudly tell the CTD matter has been fixed, lol..

--------------------------------------------------------

If yous read my post to this bespeak, i accept skillful news too.., until they restore the game version from this crap, i take a "semi-solution" to prevent a memory leak hit & CTD, sometimes for hours, few things:

Due to the nature of the memory leak, you lot accept to minimize the game RAM consumption, there is one simple way to accomplish this, extra streaming altitude in the graph menu, set information technology to 0, it has

huge

and instant touch on to extend the time between CTD's..

Earlier i decided to make this post i read many others and some of you seems like think "everything is okay" when y'all able to play Height for example to an hour.
The game's memory consumption is the

everyman

in Summit, most of usa can play it long plenty but.., for example if you get dorsum to Washington and start to exercise

anything

in OpenWorld, CP'south and other activities, the game RAM usage will skyrocket and you lot will hit your desktop very soon also.
Another proficient exmple is the RAIDs, very low memory consumption compared to OpenWorld, just those tin CTD while playing RAIDs who has other RAM hungry background processes running at the same fourth dimension, similar browsers with open ~YT tabs, etc.., and then keep these things in mind.

Set your pagefile to fix value, at least 24GB (SSD), and search for the Win10 setting where you lot tin ready every restart or shutdown delete your page file (type "secpol" in start menu).

(Information technology takes virtually 30-60sec to delete, not a drama..)

Finally, there is a great and well known third party software called IntelligentStandbyListCleaner

These are my settings

The cardinal setting is the "free memory is lower than.." it helps yous to forestall the arrangement & game pass the game's retentivity leak erogen zone and keeps you lot (hopefully long enough) nether ~60% of RAM usage.
For peoples with 32GB RAM.., i would say 12000-14000 instead of my 6144 value with 16GB, some of my clanmates already use these values.

So.., with Extra Streaming Distance setting to zero (ingame), stock-still and big plenty pagefile size (& auto delete when restart) and ISLC with proper values can profoundly heave the time windows between CTDs, i can play Openworld activities oftentimes for hours!! Give it a effort..

Things you tin ignore/forget/skip bcos zero connection to the game's retention leak (0xc0000005):

VGA driver change & settings
Win10 reinstall & update
Sectionalization 2 reinstall
Verify game files/integrity
DirectX refresh/diag
Any Overlays (UConnect, RTSS etc, utilize them calmly)
Discord

etc.., the listing of the balderdash****due south are long, whoever mentioning these.., he/she just acting similar she/he knows whats shes/hes talking well-nigh. They dont.

degregorioapid1982.blogspot.com

Source: https://discussions.ubisoft.com/post/614219

Share this post