- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm looking for help in trying to get Black Desert running stably on my system. The game will crash to desktop with no apparent trigger. One of its dmp files follows:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToV8JsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 41
Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Delete Me\Documents\Black Desert\Dump\r471677_0x00000000000000A6_736324_5992f81d.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 22631 MP (32 procs) Free x64
Product: WinNt, suite: SingleUserTS
Edition build lab: 10.0.22621.3374 (WinBuild.160101.0800)
Debug session time: Sat Jun 22 13:08:08.000 2024 (UTC + 1:00)
System Uptime: not available
Process Uptime: 0 days 0:08:08.000
................................................................
................................................................
............................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(540c.163c): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007ffb`e8211eb4 c3 ret
0:333> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Execute
Key : Analysis.CPU.mSec
Value: 202
Key : Analysis.Elapsed.mSec
Value: 18260
Key : Analysis.IO.Other.Mb
Value: 19
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 38
Key : Analysis.Init.CPU.mSec
Value: 62
Key : Analysis.Init.Elapsed.mSec
Value: 8024
Key : Analysis.Memory.CommitPeak.Mb
Value: 202
Key : Failure.Bucket
Value: SOFTWARE_NX_FAULT_CODE_c0000005_nvgpucomp64.dll!Unknown
Key : Failure.Hash
Value: {5aa55cec-3aa1-506c-e384-3fd2350fba85}
Key : Timeline.Process.Start.DeltaSec
Value: 488
FILE_IN_CAB: r471677_0x00000000000000A6_736324_5992f81d.dmp
CONTEXT: (.ecxr)
rax=0000000000000801 rbx=00000000000014f4 rcx=0000000000000042
rdx=000000015a49ffe0 rsi=000000010000000c rdi=0000000100000001
rip=00000000000000a6 rsp=00000000e969ec40 rbp=0000000123da0738
r8=0000000000000000 r9=0000000000000000 r10=00007ffbd4fdbf40
r11=0000000123da0738 r12=0000000123c826f8 r13=000000011d6cfff0
r14=0000000000000040 r15=0000000123da0738
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
00000000`000000a6 ?? ???
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00000000000000a6
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000008
Parameter[1]: 00000000000000a6
Attempt to execute non-executable address 00000000000000a6
PROCESS_NAME: blackdesert64.exe
EXECUTE_ADDRESS: a6
FAILED_INSTRUCTION_ADDRESS:
+0
00000000`000000a6 ?? ???
ERROR_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: 0000000000000008
EXCEPTION_PARAMETER2: 00000000000000a6
STACK_TEXT:
00000000`e969ec40 00000000`00000086 : 00000001`23cecb38 00000001`23da0738 00000001`23c826f8 00000001`23da0738 : 0xa6
00000000`e969ec48 00000001`23cecb38 : 00000001`23da0738 00000001`23c826f8 00000001`23da0738 00007ffb`d4fd5831 : 0x86
00000000`e969ec50 00000001`23da0738 : 00000001`23c826f8 00000001`23da0738 00007ffb`d4fd5831 00000001`00000000 : 0x00000001`23cecb38
00000000`e969ec58 00000001`23c826f8 : 00000001`23da0738 00007ffb`d4fd5831 00000001`00000000 00000001`00000000 : 0x00000001`23da0738
00000000`e969ec60 00000001`23da0738 : 00007ffb`d4fd5831 00000001`00000000 00000001`00000000 00000001`23cecb38 : 0x00000001`23c826f8
00000000`e969ec68 00007ffb`d4fd5831 : 00000001`00000000 00000001`00000000 00000001`23cecb38 00007ffb`d4ead0f0 : 0x00000001`23da0738
00000000`e969ec70 00007ffb`d4fdeb38 : 00000001`23cecb38 00000001`1d6d9130 00000001`23cecb38 00000001`1d6cfff0 : nvgpucomp64!destroyFinalizer+0xaa77b1
00000000`e969eca0 00007ffb`d4fffd88 : 00000000`00000086 00000000`0000005c 00000001`23cecb38 00000001`23cecb38 : nvgpucomp64!destroyFinalizer+0xab0ab8
00000000`e969ecd0 00007ffb`d4eb0b51 : 00000000`e969eef0 00000000`00000000 00000001`23cecb38 00000001`1d6fddc0 : nvgpucomp64!destroyFinalizer+0xad1d08
00000000`e969ed00 00007ffb`d50dfec6 : 00000001`23c59708 00007ffb`d5d5ac50 00000001`1d683fb8 00000000`00000000 : nvgpucomp64!destroyFinalizer+0x982ad1
00000000`e969ed40 00007ffb`d4ea135a : 00000000`000014f4 00000001`1d683fb8 00000001`1d688ce0 00000000`e969f260 : nvgpucomp64!destroyFinalizer+0xbb1e46
00000000`e969f030 00007ffb`d4ea16e0 : 00000001`1d684620 00000000`000011eb 00007ffb`d59df040 00000001`23c596f0 : nvgpucomp64!destroyFinalizer+0x9732da
00000000`e969f060 00007ffb`d4ea17c7 : 00007ffb`d5d48b08 00000000`e969f1f0 00000000`e969f260 00007ffb`d59defe0 : nvgpucomp64!destroyFinalizer+0x973660
00000000`e969f0f0 00007ffb`d4cfde99 : 00000001`1d6a3e48 00000000`e969f2c9 00000001`1d683fb8 00007ffb`d474b3c1 : nvgpucomp64!destroyFinalizer+0x973747
00000000`e969f220 00007ffb`d4cfdf65 : 00000001`0008001f 00000001`1d683fb8 00000001`1d683fb8 00000000`e969f4b0 : nvgpucomp64!destroyFinalizer+0x7cfe19
00000000`e969f300 00007ffb`d475d940 : 00000000`e969f4a8 00000000`e969f4a8 00000000`b7e9e100 00000000`b7e9e100 : nvgpucomp64!destroyFinalizer+0x7cfee5
00000000`e969f330 00007ffb`d475e38b : 00000001`1d678680 00000000`e969f490 00000001`1d678520 00000000`00000000 : nvgpucomp64!destroyFinalizer+0x22f8c0
00000000`e969f390 00007ffb`d474ad98 : 00000000`e969f848 00000000`e969f810 00000000`00000000 ffffffff`ffffffff : nvgpucomp64!destroyFinalizer+0x23030b
00000000`e969f6b0 00007ffb`d474af30 : 00000000`00000000 00000000`00000000 00000000`00000000 00000001`25180160 : nvgpucomp64!destroyFinalizer+0x21cd18
00000000`e969f6f0 00007ffb`cd5a9d31 : 2b3fba2a`23e07944 00000001`6d25cfb0 00000000`00000000 00007ffb`ce407202 : nvgpucomp64!destroyFinalizer+0x21ceb0
00000000`e969f720 00007ffb`cddec94f : 00000000`00000000 2b3fba2a`23e07944 00000000`00000001 d1fa9a05`14c91a68 : nvwgf2umx+0x89d31
00000000`e969f790 00007ffb`cd91bea3 : 00000000`00000000 00000000`00000000 00000000`ffffffff 00000000`e969f8c9 : nvwgf2umx!NVDEV_Thunk+0x4b53f
00000000`e969f810 00007ffb`cd77dbd3 : 00000001`6d339080 00000001`6d25cc30 00000001`6d25cc30 00007ffb`cd77b7fd : nvwgf2umx!NVAPI_Thunk+0x1cc4e3
00000000`e969f910 00007ffb`cd73ffa9 : 00000000`e969fcf0 00000000`00000000 00000001`26b9e7c8 00000001`26b9e7c8 : nvwgf2umx!NVAPI_Thunk+0x2e213
00000000`e969f9b0 00007ffb`cd5e9a61 : 00000002`1699cb40 00000000`00000000 00000000`e969fae0 00000000`00000000 : nvwgf2umx!NVENCODEAPI_Thunk+0x59389
00000000`e969f9e0 00007ffb`cde2c58a : 00000000`00000000 00000002`1699f6c0 00000000`7b76f480 00000000`00000000 : nvwgf2umx!NVAPI_DirectMethods+0x29e51
00000000`e969fcc0 00007ffb`cde2c2a8 : 00000000`00000000 00000000`7b76f480 00000000`00000000 00000000`7b81b1b8 : nvwgf2umx!NVDEV_Thunk+0x8b17a
00000000`e969fdd0 00007ffb`cdda0f73 : 00000000`00000000 00000000`00000000 00000000`d0608b60 00000000`00000000 : nvwgf2umx!NVDEV_Thunk+0x8ae98
00000000`e969fe80 00007ffb`cdda0e6f : 00000000`00000000 00000001`34de2ba0 00000000`00000000 00000000`00000000 : nvwgf2umx!OpenAdapter12+0x1210e3
00000000`e969fed0 00007ffb`ce40e1fe : 00000001`34de2ba0 00000000`00000000 00000000`00000000 00000000`00000000 : nvwgf2umx!OpenAdapter12+0x120fdf
00000000`e969ff00 00007ffb`e690257d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvwgf2umx!SetDependencyInfo+0x43ad5e
00000000`e969ff30 00007ffb`e81caf28 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1d
00000000`e969ff60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28
SYMBOL_NAME: nvgpucomp64+aa77b1
MODULE_NAME: nvgpucomp64
IMAGE_NAME: nvgpucomp64.dll
STACK_COMMAND: ~333s; .ecxr ; kb
FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_CODE_c0000005_nvgpucomp64.dll!Unknown
BUCKET_ID_MODPRIVATE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 32.0.15.5599
FAILURE_ID_HASH: {5aa55cec-3aa1-506c-e384-3fd2350fba85}
Followup: MachineOwner
---------
0:333> .ecxr
rax=0000000000000801 rbx=00000000000014f4 rcx=0000000000000042
rdx=000000015a49ffe0 rsi=000000010000000c rdi=0000000100000001
rip=00000000000000a6 rsp=00000000e969ec40 rbp=0000000123da0738
r8=0000000000000000 r9=0000000000000000 r10=00007ffbd4fdbf40
r11=0000000123da0738 r12=0000000123c826f8 r13=000000011d6cfff0
r14=0000000000000040 r15=0000000123da0738
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
00000000`000000a6 ?? ???
I have just reinstalled Windows 11 and have installed all the recent drivers for my hardware I could find.
As I am running a 14900KS, I have already gone into the BIOS and confirmed that the Intel limits are being enforced.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Realist_Ego,
As you might already know, the issue you are experiencing is most probably the known issue about 13th&14th Gen i9 processors being unstable, specially, if you are seeing crashes on other applications like the explorer, your browser, Discord, or even BSODs.
There is an investigation on-going by intel on this issue: https://community.intel.com/t5/Processors/June-2024-Guidance-regarding-Intel-Core-13th-and-14th-Gen-K-KF/m-p/1607807
If you have already update your BIOS to the latest one, and verified/set the following power supply parameters:
- PL1: 125W-320W
- PL2: 253-320W
- IccMax: 307A-400A
* Note PL1 <= PL2
And it's not stable, definetly, go for an RMA.
And as a personal recommendation, 14900KS is the best consumer chip right now and Intel is advertising their performance with the following power supply parameters:
- PL1 = PL2 = 320W
- IccMax: 400A
If you make it work with anything that is below those parameters, you'll be giving up performance for a CPU that's not precisely cheap, so in that case I'd recommend you go for the RMA.
Also, note that even if it seems to be stable, it might fail over the next months, since the CPU has already degraded at some level.
I also had this issue and it was mostly no crashes until lately where I am having crashes by the hour.
/SpaceTurtle

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page