Posted September 17, 2017
Anyone experienced that? Any fixes?
heillon
New User
Registered: Apr 2012
From United Kingdom
Raze_Larian
Dragon Knight
Developer
Registered: Mar 2012
From Canada
Posted September 22, 2017
Install the 2015 Visual C++ Redistrubutable (update 3, 64bit)
https://www.microsoft.com/en-us/download/details.aspx?id=53840
EDIT: The Definitive Edition uses the 2017 Visual C++ redistributable.
https://go.microsoft.com/fwlink/?LinkId=746572 (direct download)
or https://support.microsoft.com/en-ca/help/2977003/the-latest-supported-visual-c-downloads
On Windows 7 or Windows 8.1, install the Microsoft Universal C Runtime (is already part of Win 10), downloaded below, or from Windows update.
https://support.microsoft.com/en-us/kb/2999226
.Net 3.5 [choose Microsoft .NET Framework 4 Client Profile (Web Installer)] - If the launcher starts, this should be fine.
https://www.microsoft.com/en-us/download/details.aspx?id=21
https://www.microsoft.com/en-us/download/details.aspx?id=53840
EDIT: The Definitive Edition uses the 2017 Visual C++ redistributable.
https://go.microsoft.com/fwlink/?LinkId=746572 (direct download)
or https://support.microsoft.com/en-ca/help/2977003/the-latest-supported-visual-c-downloads
On Windows 7 or Windows 8.1, install the Microsoft Universal C Runtime (is already part of Win 10), downloaded below, or from Windows update.
https://support.microsoft.com/en-us/kb/2999226
.Net 3.5 [choose Microsoft .NET Framework 4 Client Profile (Web Installer)] - If the launcher starts, this should be fine.
https://www.microsoft.com/en-us/download/details.aspx?id=21
Post edited July 01, 2019 by Raze_Larian
heillon
New User
Registered: Apr 2012
From United Kingdom
Posted September 22, 2017
Thank you for your detailed reply. I was trying lot of different things so I am not sure what worked in the end.
I did update directx, ran updates to .NET, installed newest graphics drivers, also windows update. I guess I hit the right combination by accident. Hopefully your reply Raze will help anyone who had the same problem! :)
Edit: I just realised I didn't mention I was running Win7x64, Radeon 6950, i5 5th gen.
I did update directx, ran updates to .NET, installed newest graphics drivers, also windows update. I guess I hit the right combination by accident. Hopefully your reply Raze will help anyone who had the same problem! :)
Edit: I just realised I didn't mention I was running Win7x64, Radeon 6950, i5 5th gen.
Post edited September 22, 2017 by heillon
Mart_nO8
New User
Registered: Mar 2019
From Colombia
Posted May 10, 2019
thats right solutión. !!! 100%.
Thanks Raze_Larian
Thanks Raze_Larian
Post edited May 10, 2019 by Mart_nO8
BreezyBadger
New User
Registered: Dec 2017
From Canada
Posted May 18, 2019
https://www.microsoft.com/en-us/download/details.aspx?id=53840
On Windows 7 or Windows 8.1, install the Microsoft Universal C Runtime (is already part of Win 10), downloaded below, or from Windows update.
https://support.microsoft.com/en-us/kb/2999226
.Net 3.5 [choose Microsoft .NET Framework 4 Client Profile (Web Installer)]
https://www.microsoft.com/en-us/download/details.aspx?id=21
A temporary fix is to uninstall the existing 2015 Visual C++ Redistrubutable and re-install the 2015 Visual C++ Redistrubutable (update 3, 64bit). Not repair, that doesn't work, re-install.
https://www.microsoft.com/en-us/download/details.aspx?id=53840
This is temporary because windows fixes itself with the most recent version (not the one that works with this game). Obviously, Larian is making use of some hack that has been patched out in the most recent version of the Visual Studio 2015 C++ redistributable, but they're too busy rolling in cash to care.
So Laian, fix your crash to desktop when trying to run definitive edition. What in Satan's name are you people doing with all the money you're milking from this cash cow? Can you please find it in your time, sometime after taking deep drags from the company blow pipe but before engaging in your usual bouts of vigorous wanking, to fix the crash to desktop that occurs almost every time I try and run definitive edition?
Dump Summary
------------
Dump File: CrashDump - 05-17-2019 23h 14m 14s.dmp : G:\GOG\Divinity - Original Sin 2\DefEd\bin\CrashDump - 05-17-2019 23h 14m 14s.dmp
Last Write Time: 5/17/2019 7:14:14 PM
Process Name: EoCApp.exe : G:\GOG\Divinity - Original Sin 2\DefEd\bin\EoCApp.exe
Process Architecture: x64
Exception Code: 0xC0000005
Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
Heap Information: Not Present
Bold text is a good hint where to start *actually* earning your pay, because right now I. and many more people, feel robbed.
Post edited May 18, 2019 by BreezyBadger
Raze_Larian
Dragon Knight
Developer
Registered: Mar 2012
From Canada
Posted May 18, 2019
Are you getting a 0xc000007b error?
The Definitive Edition uses the 2017 Visual C++ redistributable. Try doing a manual re-install of that, if you haven't already.
https://go.microsoft.com/fwlink/?LinkId=746572 (direct download)
or https://support.microsoft.com/en-ca/help/2977003/the-latest-supported-visual-c-downloads
Is there any difference exiting out of Galaxy, if applicable, and starting the game directly from the '..\Divinity Original Sin 2\DefEd\bin\EoCApp.exe' program file, by right clicking and running as administrator (or '..\Divinity Original Sin 2\Classic\EoCApp.exe' for the original release)?
Try doing a clean boot and then test the game. 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 checking your system files:
- click Start, type cmd into the search box, right click Command Prompt and select run as administrator.
- type the following command and hit Enter
sfc /scannow
When that is done, type exit and hit Enter, then reboot your computer.
For more details, see: https://support.microsoft.com/en-ca/kb/929833
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 quote or link to this topic. Also check the '..\Divinity Original Sin 2\DefEd\bin' folder for the gold.log file, and zip a few of the 'CrashDump' files together to include.
Post edited May 18, 2019 by Raze_Larian
Raze_Larian
Dragon Knight
Developer
Registered: Mar 2012
From Canada
Posted May 18, 2019
In general for the 0xc000007b error, usually just reinstalling the redistributables will fix it (VC, .Net Framework 4 [if the launcher starts, this should be fine] and on Win 7/8 the Microsoft Universal C Runtime).
Tom's Hardware has a guide for this (written for Win 7/8 but most should be applicable to Win 10, as well)
A post in a Win 10 forum reported fixing this by manually replacing some dll files (as does the guide above, as a last resort).
One person with this error reported that uninstalling Skype fixed it and (after installing the Microsoft Universal C Runtime to fix a dll error) got the game working. He had used the Dependency Walker program to look at the D:OS 2 executable, and found that for some reason the system was trying to access dll files in the Skype folder, rather than the system folders.
Another person with this error code that tried this found no such issues.
To check this, after starting the Dependency Walker program and opening the EoCApp.exe game executable, right click the window and select 'show full paths' (or hit F9), then check the list of dlls; most should be in C:\Windows\System32, possibly a video driver folder under c:\Windows, or the game's install folder.
Tom's Hardware has a guide for this (written for Win 7/8 but most should be applicable to Win 10, as well)
A post in a Win 10 forum reported fixing this by manually replacing some dll files (as does the guide above, as a last resort).
One person with this error reported that uninstalling Skype fixed it and (after installing the Microsoft Universal C Runtime to fix a dll error) got the game working. He had used the Dependency Walker program to look at the D:OS 2 executable, and found that for some reason the system was trying to access dll files in the Skype folder, rather than the system folders.
Another person with this error code that tried this found no such issues.
To check this, after starting the Dependency Walker program and opening the EoCApp.exe game executable, right click the window and select 'show full paths' (or hit F9), then check the list of dlls; most should be in C:\Windows\System32, possibly a video driver folder under c:\Windows, or the game's install folder.
BreezyBadger
New User
Registered: Dec 2017
From Canada
Posted May 18, 2019
My "Exception Code" is actually 0xC0000005
Already installed the MSVC++ Redist 2015-2019 from microsoft site & .Net runtimes. No dice.
SFC /scannow did nothing. Everyone seems to suggest this as a panacea but this tool has almost never fixed anyone's problem whenever I look through forums where it is recommended.
The game works the first time I start it, after a reboot, but not afterwards.
The Classic edition works fine.
I looked at all the DLLS that were run-time linked into the executable using the mini-dump generated on crash using VS C++.
In there I saw the following dlls were linked into the executable, that weren't System32, GOG, or Larian:
NahimicOSD.dll C:\ProgramData\A-Volute\A-Volute.28054DF1F58B4\Modules\ScheduledModules\x64\NahimicOSD.dll 1.2. 13.57414
A-Volute.SonicStudio3DevProps2.dll C:\ProgramData\A-Volute\A-Volute.SonicStudio3\Modules\ScheduledModules\x64\ A-Volute.SonicStudio3DevProps2.dll 2.1.2.56401
ProductInfo.dll C:\ProgramData\A-Volute\A-Volute.SonicStudio3\Modules\ScheduledModules\x64\ProductInfo.dll
I disabled the Audio "service" Nahimic.
After diabling the Nahimis servie, using "services.msc" It works now. I'm guessing this thing hooks into running executables. On a side note, I also see that some nVidia shit also hooks into the process, but it's not causing issues (I still don't like it).
So If your game is crashing to desktop:
1. Install Visual Studio Comunity edition VS C++ packages.
2. Open the .dmp file the game generates.
3. Look through the list of modules that were linked into the program image when it crashed.
4. Find out what is "hooked" into the executable and find some way to get rid of the software that owns the dlls not in C:\Windows, or GOG, or Divinity Original Sin folders. Other shit can go to hell. No company should hook into all running executables - that's basically a rootkit.
Already installed the MSVC++ Redist 2015-2019 from microsoft site & .Net runtimes. No dice.
SFC /scannow did nothing. Everyone seems to suggest this as a panacea but this tool has almost never fixed anyone's problem whenever I look through forums where it is recommended.
The game works the first time I start it, after a reboot, but not afterwards.
The Classic edition works fine.
I looked at all the DLLS that were run-time linked into the executable using the mini-dump generated on crash using VS C++.
In there I saw the following dlls were linked into the executable, that weren't System32, GOG, or Larian:
NahimicOSD.dll C:\ProgramData\A-Volute\A-Volute.28054DF1F58B4\Modules\ScheduledModules\x64\NahimicOSD.dll 1.2. 13.57414
A-Volute.SonicStudio3DevProps2.dll C:\ProgramData\A-Volute\A-Volute.SonicStudio3\Modules\ScheduledModules\x64\ A-Volute.SonicStudio3DevProps2.dll 2.1.2.56401
ProductInfo.dll C:\ProgramData\A-Volute\A-Volute.SonicStudio3\Modules\ScheduledModules\x64\ProductInfo.dll
I disabled the Audio "service" Nahimic.
After diabling the Nahimis servie, using "services.msc" It works now. I'm guessing this thing hooks into running executables. On a side note, I also see that some nVidia shit also hooks into the process, but it's not causing issues (I still don't like it).
So If your game is crashing to desktop:
1. Install Visual Studio Comunity edition VS C++ packages.
2. Open the .dmp file the game generates.
3. Look through the list of modules that were linked into the program image when it crashed.
4. Find out what is "hooked" into the executable and find some way to get rid of the software that owns the dlls not in C:\Windows, or GOG, or Divinity Original Sin folders. Other shit can go to hell. No company should hook into all running executables - that's basically a rootkit.
Post edited May 18, 2019 by BreezyBadger
Raze_Larian
Dragon Knight
Developer
Registered: Mar 2012
From Canada
Posted May 18, 2019
That's why I asked, to see if you were also getting the 07b error, or if you just posted in this topic in relation to the redistributables. This is a known issue, but I have not seen it reported to be temporarily fixed by reinstalling the VC redistribuable, or working once after a reboot (maybe the service loading was delayed, or set to load on demand). A couple of people with this issue have reported the game would work sometimes, though, so maybe it was the same situation, and they didn't realize the connection with rebooting (sometimes they ran another program first that got it loaded, and sometimes they didn't, etc).
The Nahimic service is used by two audio programs (SonicRadar and Sonic Studio) for certain motherboards. Generally it causes the DE to crash after about a second of black screen, but the Classic release is ok. This should be fixed with the latest updates for the Nahimic drivers and apps, though if you are not using the programs or Nahimic features, you can just leave the service disabled.
Anyway, I'm glad you finally got it working properly.
The Nahimic service is used by two audio programs (SonicRadar and Sonic Studio) for certain motherboards. Generally it causes the DE to crash after about a second of black screen, but the Classic release is ok. This should be fixed with the latest updates for the Nahimic drivers and apps, though if you are not using the programs or Nahimic features, you can just leave the service disabled.
Anyway, I'm glad you finally got it working properly.