Larian Banner: Baldur's Gate Patch 9
Previous Thread
Next Thread
Print Thread
Joined: Jun 2019
stranger
OP Offline
stranger
Joined: Jun 2019
So I seem to be having my own version of the DE crash on launch that seems to be affecting a number of users. I have gotten a new computer that has been working excellent for just about everything I've put it through so far except that the DoS2:DE seems to not want to launch at all for some reason. Screen will go black for a couple seconds and then instantly crash out and leave a .dmp file behind in the exe folder.

Classic Edition works A-OK no problem whatsoever. Have loaded my last save game from classic and run around for a couple minutes and everything seems just fine.

Any ideas on what might be the culprit of this particular crash would be most helpful! Hopefully the crash dump means something to you. It would be nice to continue on with my DE campaign again when this is finally working!

I have attempted the following things already:

Launch from Divinity Original Sin 2\DefEd\bin\EoCApp.exe
Disable fullscreen optimizations
Disable all overlays (NVIDIA, Steam, Discord)
Compatibility mode for Windows 8/7
Run as Administrator
Verified Integrity of Game Cache
Full Reinstall
NVIDIA Drivers Up to Date
Windows Up to Date
Antivirus on/off makes no difference
gold.log has no content 0kb
Used low quality graphicSettings.lsx - no difference
Replaced entire %DOCUMENTS%\Larian Studios\Divinity Original Sin Enhanced Edition folder - no difference
Run the .NET Framework setup verification tool on all the installed packages:
https://blogs.msdn.microsoft.com/as...ork-setup-verification-tool-users-guide/
.NET Framework 2.0 SP2
.NET Framework 3.0 SP1
.NET Framework 3.0 SP2
.NET Framework 3.5 SP1
.NET Framework 4 Client
.NET Framework 4 Full
.NET Framework 4.5
.NET Framework 4.5.1
.NET Framework 4.5.2
.NET Framework 4.6
.NET Framework 4.6.1
.NET Framework 4.6.2
.NET Framework 4.7
.NET Framework 4.7.1
.NET Framework 4.7.2
All returned ok.

All crashes return the same dump file info. Dump file contents below. It refers to StreamMgr::SetFileLocationResolver function that seems to be the source of the error but I don't know what that means in this case.


*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*** WARNING: Unable to verify checksum for SDL2.dll

KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullClassPtr

Key : AV.Fault
Value: Write

Key : Timeline.Process.Start.DeltaSec
Value: 2


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start
Name: <blank>
Time: 2019-06-13T06:26:03.226Z
Diff: 29226 mSec

Timeline: Dump.Current
Name: <blank>
Time: 2019-06-13T06:25:34.0Z
Diff: 0 mSec

Timeline: Process.Start
Name: <blank>
Time: 2019-06-13T06:25:32.0Z
Diff: 2000 mSec


DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT: (.ecxr)
rax=0000000000000001 rbx=0000000000000001 rcx=00007ff47fd785c8
rdx=00007ff47fd785c8 rsi=00007ff47fd785c8 rdi=0000000000000000
rip=00007ff60f7f2dd4 rsp=0000005886cff460 rbp=00007ff47fd785c8
r8=0000000000000001 r9=0000000000000001 r10=00007ff47fd60000
r11=ffffffffffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
EoCApp!AK::StreamMgr::SetFileLocationResolver+0x1c0f74:
00007ff6`0f7f2dd4 f04c0fc14f20 lock xadd qword ptr [rdi+20h],r9 ds:00000000`00000020=????????????????
Resetting default scope

FAULTING_IP:
EoCApp!AK::StreamMgr::SetFileLocationResolver+1c0f74
00007ff6`0f7f2dd4 f04c0fc14f20 lock xadd qword ptr [rdi+20h],r9

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff60f7f2dd4 (EoCApp!AK::StreamMgr::SetFileLocationResolver+0x00000000001c0f74)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000020
Attempt to write to address 0000000000000020

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_WRITE

PROCESS_NAME: EoCApp.exe

FOLLOWUP_IP:
EoCApp!AK::StreamMgr::SetFileLocationResolver+1c0f74
00007ff6`0f7f2dd4 f04c0fc14f20 lock xadd qword ptr [rdi+20h],r9

WRITE_ADDRESS: 0000000000000020

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000020

WATSON_BKT_PROCSTAMP: 5c7dc8f2

WATSON_BKT_PROCVER: 3.6.37.7694

PROCESS_VER_PRODUCT: Divinity Original Sin 2

WATSON_BKT_MODULE: EoCApp.exe

WATSON_BKT_MODSTAMP: 5c7dc8f2

WATSON_BKT_MODOFFSET: 11b2dd4

WATSON_BKT_MODVER: 3.6.37.7694

MODULE_VER_PRODUCT: Divinity Original Sin 2

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

MODLIST_WITH_TSCHKSUM_HASH: 183565d0bc3839f1e301d2650f16505e7470769b

MODLIST_SHA1_HASH: 3643b27928b693dd597c38eeb640055afae47e23

DUMP_FLAGS: 2

DUMP_TYPE: 1

ANALYSIS_SESSION_HOST: XXXXXXXXX

ANALYSIS_SESSION_TIME: 06-12-2019 23:26:03.0226

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

THREAD_ATTRIBUTES:
BUGCHECK_STR: APPLICATION_FAULT_NULL_CLASS_PTR_WRITE_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_WRITE

PRIMARY_PROBLEM_CLASS: APPLICATION_FAULT

PROBLEM_CLASSES:

ID: [0n313]
Type: [@ACCESS_VIOLATION]
Class: Addendum
Scope: BUCKET_ID
Name: Omit
Data: Omit
PID: [Unspecified]
TID: [0x3bd4]
Frame: [0] : EoCApp!AK::StreamMgr::SetFileLocationResolver

ID: [0n286]
Type: [INVALID_POINTER_WRITE]
Class: Primary
Scope: BUCKET_ID
Name: Add
Data: Omit
PID: [Unspecified]
TID: [0x3bd4]
Frame: [0] : EoCApp!AK::StreamMgr::SetFileLocationResolver

ID: [0n309]
Type: [NULL_CLASS_PTR_DEREFERENCE]
Class: Primary
Scope: BUCKET_ID
Name: Add
Data: Omit
PID: [Unspecified]
TID: [0x3bd4]
Frame: [0] : EoCApp!AK::StreamMgr::SetFileLocationResolver

ID: [0n311]
Type: [NULL_CLASS_PTR_WRITE]
Class: Primary
Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
BUCKET_ID
Name: Add
Data: Omit
PID: [0x5388]
TID: [0x3bd4]
Frame: [0] : EoCApp!AK::StreamMgr::SetFileLocationResolver

LAST_CONTROL_TRANSFER: from 00007ff60f7c4864 to 00007ff60f7f2dd4

STACK_TEXT:
00000058`86cff460 00007ff6`0f7c4864 : 00007ff4`7fd785c8 00007ff4`82598900 00007ff4`82598940 00000000`00000000 : EoCApp!AK::StreamMgr::SetFileLocationResolver+0x1c0f74
00000058`86cff490 00007ff6`0f7f1425 : 00007ff4`82598a00 00007ff4`7fd632c0 000001fd`0d510000 00007ff6`0f7c49ef : EoCApp!AK::StreamMgr::SetFileLocationResolver+0x192a04
00000058`86cff4c0 00007ff6`0f7f237d : 00007ff4`8259d400 00007ff4`82598900 00000058`86cff6c0 00000000`00000000 : EoCApp!AK::StreamMgr::SetFileLocationResolver+0x1bf5c5
00000058`86cff500 00007ff6`0f93d55f : 00000058`86cff6c0 000001fd`0d510000 00000000`00000000 00000000`00000000 : EoCApp!AK::StreamMgr::SetFileLocationResolver+0x1c051d
00000058`86cff530 00007ff6`0f93d89c : 000001fd`65a9e9e0 00007ff4`825cca20 00000000`00000000 00000000`00000000 : EoCApp!AK::StreamMgr::SetFileLocationResolver+0x30b6ff
00000058`86cff560 00007ff6`0f89b94a : 00007ff4`82409950 00000000`00000000 00007ff6`00000000 00000000`00000000 : EoCApp!AK::StreamMgr::SetFileLocationResolver+0x30ba3c
00000058`86cff590 00007ff6`0f799520 : 00000000`00001000 000001fd`0d510000 00000000`00000000 000001fd`0d510000 : EoCApp!AK::StreamMgr::SetFileLocationResolver+0x269aea
00000058`86cff5c0 00007ff6`0f43f90f : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000000 : EoCApp!AK::StreamMgr::SetFileLocationResolver+0x1676c0
00000058`86cff8a0 00007fff`18677974 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : EoCApp!nv::cloth::ClothFabricCooker::operator=+0xbc29ff
00000058`86cff8e0 00007fff`190ea271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000058`86cff910 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


THREAD_SHA1_HASH_MOD_FUNC: c61887fb6834b04454568dea8807c141ab40d466

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d08cf53ef560b2927c52c1f289d98a76512a6330

THREAD_SHA1_HASH_MOD: e088e3e3e84cb75ca14302b63add275274267210

FAULT_INSTR_CODE: c10f4cf0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: EoCApp!AK::StreamMgr::SetFileLocationResolver+1c0f74

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: EoCApp

IMAGE_NAME: EoCApp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5c7dc8f2

STACK_COMMAND: ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID: NULL_CLASS_PTR_WRITE_c0000005_EoCApp.exe!AK::StreamMgr::SetFileLocationResolver

BUCKET_ID: APPLICATION_FAULT_NULL_CLASS_PTR_WRITE_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_WRITE_EoCApp!AK::StreamMgr::SetFileLocationResolver+1c0f74

FAILURE_EXCEPTION_CODE: c0000005

FAILURE_IMAGE_NAME: EoCApp.exe

BUCKET_ID_IMAGE_STR: EoCApp.exe

FAILURE_MODULE_NAME: EoCApp

BUCKET_ID_MODULE_STR: EoCApp

FAILURE_FUNCTION_NAME: AK::StreamMgr::SetFileLocationResolver

BUCKET_ID_FUNCTION_STR: AK::StreamMgr::SetFileLocationResolver

BUCKET_ID_OFFSET: 1c0f74

BUCKET_ID_MODTIMEDATESTAMP: 5c7dc8f2

BUCKET_ID_MODCHECKSUM: 2bf77e1

BUCKET_ID_MODVER_STR: 3.6.37.7694

BUCKET_ID_PREFIX_STR: APPLICATION_FAULT_NULL_CLASS_PTR_WRITE_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_WRITE_

FAILURE_PROBLEM_CLASS: APPLICATION_FAULT

FAILURE_SYMBOL_NAME: EoCApp.exe!AK::StreamMgr::SetFileLocationResolver

WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOn...c7dc8f2/c0000005/011b2dd4.htm?Retriage=1

TARGET_TIME: 2019-06-13T06:25:34.000Z

OSBUILD: 17763

OSSERVICEPACK: 475

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 256

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 1989-09-09 23:58:46

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: eec

ANALYSIS_SOURCE: UM

FAILURE_ID_HASH_STRING: um:null_class_ptr_write_c0000005_eocapp.exe!ak::streammgr::setfilelocationresolver

FAILURE_ID_HASH: {7efc41d5-42a8-f03f-6a2e-56b080adcbe3}

Followup: MachineOwner
---------

Last edited by vometia; 13/06/19 08:55 AM. Reason: Spoiler tags for brevity
Joined: Mar 2003
Location: Canada
Support
Offline
Support
Joined: Mar 2003
Location: Canada

Are you shutting down all non-essential programs (especially anti-virus) before starting the game? Firewalls can cause conflicts (generally on startup or loading screens) and overlays from graphics tweaking/monitoring programs or chat programs can also caused issues.

Try doing a clean boot and then test the game. For example, there is a known conflict with the Nahimic service used by two audio programs (SonicRadar and Sonic Studio) for certain motherboards which can cause the DE to crash after about a second of black screen, but the Classic release is ok. In that case, there may or may not be an event listed in the Event Viewer for NahimicService.exe, as well as the game executable (probably both 'RADAR_PRE_LEAK_64' events); this should be fixed with the latest updates for the Nahimic drivers and apps.
Click Start, or hit WinKey-R, type in msconfig and hit enter; in the General tab, click Selective Startup, uncheck Load startup items (if required) and leave Load system services and Use original boot configuration options checked. Next, click on the Services tab, check the box to Hide all Microsoft services, then click the Disable All button (maybe make a note of which are currently enabled/disabled), then click OK and reboot the computer.
Run msconfig again to switch back to the normal boot configuration.

Try changing the default audio output in Windows. A handful of people have reported crashes in the DE, but not Classic, that could be avoided that way (or in a couple cases fixed by changing, starting the game, exiting and switching back), some related to USB headsets.

Try browsing to the '..\Documents\Larian Studios' folder and rename the 'Divinity Original Sin 2 Definitive Edition' folder again, and try this replacement folder.


If that doesn't help, please email supportdos2@larian.com with a dxdiag report (WinKey-R, type in dxdiag and hit enter, then when it finishes loading click on the 'Save All Information...' button and save the report somewhere handy) and a link to this topic, and zip a few of the 'CrashDump' files together to include.

Joined: Jun 2019
stranger
OP Offline
stranger
Joined: Jun 2019
Hi Raze. Thanks for getting back to me with some extra things to try out.

I have just done some testing by shutting down everything running in the background - no dice. I do not have Sonic Radar/Sonic Studio or anything related to NahimicService.exe installed on my machine so you can rule that one out. Nothing has shown up in Event Viewer either.

I have tried unplugging all extra USB devices and my headset and changing the default audio output device without success also. You can rule those out.

I have done the folder replacement with the one you have provided and also no success.

I am going to give the email to support a go with the dxdiag report along with some of the crashdump files to see if they have any clues for me to check out.

Thanks for your assistance man, I appreciate your quick reply! We'll see what the support guys have to say.

Joined: Jun 2020
stranger
Offline
stranger
Joined: Jun 2020
Just wanted to chime in a year later here. I was having the same issues. The replacement folder suggested by Raze worked for me. Now I launch with no issues.

Joined: Mar 2023
L
stranger
Offline
stranger
L
Joined: Mar 2023
Although this post is 4 years old, I encountered the same issue today. I asked for help on Discord but no one responded, so I decided to solve the problem myself. I checked the Event Viewer and found that Definitive Edition was referencing the nvcuda64.dll module when starting up, but I haven't installed an NVIDIA graphics card. This driver module may have been left over from a previous graphics card, and the application error in the Event Viewer clearly indicated this. So I located nvcuda64.dll, stopped the service, and deleted it. Therefore, I suggest that friends who encounter the same problem can open the Event Viewer to see where the problem is.

Joined: May 2023
B
stranger
Offline
stranger
B
Joined: May 2023
Thanks. Your solution finally solved my issue.

By the way, did you switch recently from an NVidea to some other GPU? Because this was, I think, the reason why it happened to me as nvcuda64.dll is a NVidea drivers dll.
Cheerio

BlueInmotion


Moderated by  gbnf, Monodon 

Link Copied to Clipboard
Powered by UBB.threads™ PHP Forum Software 7.7.5