Larian Studios Forums Divinity: Original Sin 2 Divinity - Original Sin 2 - Bugs & Technical Problems System freezes and I've to reboot my system

Hello,

I've tried to fix this myself and with the help of others over on the steam forums. I even contacted Swen and to my surprise he replied to me and tried to provide help but since twitter is bad for discussing potential fixes I've decided to make a forum post. I'm not the only one who experiences this behaviour (I'm actually not sure that this is a bug) although only a few people seem to be affected by it.

Here are some of the steam discussions which talk about this issue:

Discussion 1
Discussion 2
Discussion 3

I've got either one or two issues since there are two types of crashes:

1: A crash back to desktop:
If this happens a crashdump file is generated and I can send a bug report through the provided tool. I've looked inside the crashdump file and the reason it crashes seems to be that the game tries to access an address without having the permission to do so.

2: A crash which kills my rig:
This happens most of the time after I select the difficulty and the game switches to a loading screen. During that screen the mouse starts to stutter and the music begins to loop. I can't do anything from that point and after a while everything freezes. A restart is the only option I've got after this. Because of that no crashdump file is generated and I can't provide the support with one.

On a side note: The farthest I've made it was finishing character creation. It killed my rig during the loading screen that followed it ;(

What I've tried:

Drive updates, run as admin, deleting the DOS folder under documents as well as downloading the provided one from the troubleshooting thread Swen provided, selective startup, removing xbox controller as well as other not necessary usb devices, verifying local files several times, a memtest86 (only 4 passes which took 2hrs) since the problem hinted at a memory one and I thought my RAM might be faulty.

The strange thing is that the ea version worked for me. I tried some things in the ea version a few hours before the full release and everything worked fine.

System specs:

OS: Windows 10 Pro
CPU: i7-2600k @ 3.4ghz
Graphics Card: Geforce 580GTX
RAM: 8gb

I would add my dxdiag and the two recent crashdump files but I can't find an option to attach those. If needed I can upload those somewhere.

@vometia

No idea why those links were broken since in the preview they worked. Only reason might be because my account was new and had to be approved.

Try and play it in windowed mode and see what your system does. How is the CPU/GPU/VRAM/RAM usage etc, pay attention to sudden spikes or a gradual but steady increase.

So. There're no spikes. CPU is around 15-20% and RAM around 55% but this time I opened the ressource monitor in addition and this game generates a huge amount of hard faults/page faults per second (up to 127/s). Tried it 3 times. During the first one I got over 100 faults per second and the game crashed back to desktop. During my second try 3 faults per second were displayed and my rig froze and I had to reboot. On my third attempt the game had 127 faults per second before my rig froze again. I've tried to adjust the virtual memory but this didn't help.

Edit:
So, I read up on it and page faults aren't neccessarily bad but it might be connected to my crashes since when I crash back to my desktop the crashdump file states that it tried to access (write or read) a virtual address without having permission (can't look up the exact wording now since sending a report removes those files >.<).

So, since I can't play D:OS2 I thought it would be a nice idea to replay D:OS1 and try out the EE version since I played and finished only the classic one. After clearing the tutorial dungeon and reaching the bridge with the 2 guards the game started crashing as well. The error provided is createTexture2d failed. Reason: device removed. The classic version runs without any issues.

To try to eliminate problems with the directx 11 drivers I ran a benchmark (Heaven Benchmark) and had no issues. Some assistance from one of the tech guys from Larian (after the more pressing issues have been fixed) would be great since I'd really like to eventually be able to play D:OS2 and maybe even D:OS1 EE as well

99% its GPU driver related. Download DDU and run it so you boot into safe mode. Remove GPU drivers and reboot. Install newest drivers and see how that goes.

Didn't help. Today I did manage to get past character creation after I changed my graphics settings to very low but it crashed shortly after that. Other attempts with very low settings failed during the usual times. Therefore I don't think the graphic settings (very low, low etc.) have an impact on this issue. Especially since it crashes while still being in menues. I guess I'll just wait for a few weeks and come back then. Maybe it's fixed then.

The crashdump file which is created when the game just crashes (not killing my rig) states the following:

"Der Thread hat versucht,von einer virtuellen Adresse, für die er nicht über die entsprechenden Zugriffsrechte verfügt, zu lesen oder in diese Adresse zu schreiben."

Which translates to something along the lines of:

"The thread tried to read from a virtual address without having the appropiate access rights or to write something into it."

I disabled texture streaming inside the graphicSettings.lsx file but the error still occured.

Ok, I got something which might be related to the crash to desktop but probably? isn't related to the freeze issue. I ran another memtest86 with 10 passes which took 5h21m. During that test I got 4 errors out of 10 runs from test 10.

[Data Error] Test: 10, CPU: 0, Address: 61AE3B8C, Expected: 00000000, Actual: 20000000

So, I thought: Probably one RAM-Module is faulty. I tried to play the game with each module but the freezes kept happening with both modules. So, I don't think the freezes are related to my RAM but are probably related to the crash to desktop one since the error message tipped me into checking my RAM. I'm going to try to find the faulty module over the next few days but I don't think it will fix the freezes >,<

Edit: On a side note: I found the issue of the crashes in D:OS EE or at least a workaround. I disabled shadows in the graphicSettings.lsx file. Since then the crashes (createTexture2d failed. Reason: device removed.) stopped.

Not sure if it actually did something but before I did the above (strikethrough text) D:OS EE crashed every time at the start of the game at the bridge with that error. Now it just happens from time to time >.< So no fix but maybe a bandaid? ;/