this happens when im actively opening many software like after effect and photoshop, I suspect it run out of memory? here is s memory dump looks like its a vram issue? is it because my vram is too low?
CPU: 3700x
CPU cooler: aio
Motherboard: gigabyte
Ram: 32gb
SSD/HDD: nvme m.2
GPU:2080s+2070s
PSU: 750w
OS:win10
memory dump:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000017, Unexpected system command failure.
Arg2: ffffffffc000000d
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3078
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 3121
Key : Analysis.IO.Other.Mb
Value: 6
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 21
Key : Analysis.Init.CPU.mSec
Value: 1671
Key : Analysis.Init.Elapsed.mSec
Value: 21142
Key : Analysis.Memory.CommitPeak.Mb
Value: 94
Key : Bugcheck.Code.DumpHeader
Value: 0x10e
Key : Bugcheck.Code.KiBugCheckData
Value: 0x10e
Key : Bugcheck.Code.Register
Value: 0x10e
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: 10e
BUGCHECK_P1: 17
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffffc881`f95de8a8 fffff802`6c4e3ad0 : 00000000`0000010e 00000000`00000017 ffffffff`c000000d 00000000`00000000 : nt!KeBugCheckEx
ffffc881`f95de8b0 fffff802`6d96a5fb : ffffb889`1dae20a0 ffffb889`209ef7b8 ffffdf08`00000000 ffffb889`209ef7b8 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffc881`f95de8f0 fffff802`6d96abd4 : ffffb889`1dae2000 00000000`00000000 ffffb889`209ef7b8 ffffc881`f95de9c0 : dxgmms2!VIDMM_WORKER_THREAD::FlushEvictQueue+0x133
ffffc881`f95de940 fffff802`6d96a942 : ffffdf08`2a361c60 ffffdf08`2a361c60 00000000`00000000 ffffb889`1dae2010 : dxgmms2!VIDMM_WORKER_THREAD:😛rocessEvictQueues+0xcc
ffffc881`f95de970 fffff802`6d955b73 : fffff802`6d8f4301 fffff802`6d8f4394 00000000`00000000 ffffdf08`31a18900 : dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+0xf6
ffffc881`f95dea00 fffff802`6d946759 : ffffb889`1dae2010 ffffdf08`2a26b301 00000000`00000001 00000000`0679c501 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1a463
ffffc881`f95debe0 fffff802`60917e85 : ffffdf08`2a26b380 fffff802`6d946750 ffffb889`1dae2010 000f8067`b4bbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffc881`f95dec10 fffff802`609fd498 : ffff8781`e0c80180 ffffdf08`2a26b380 fffff802`60917e30 00106b76`ffffffd8 : nt!PspSystemThreadStartup+0x55
ffffc881`f95dec60 00000000`00000000 : ffffc881`f95df000 ffffc881`f95d9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VIDMM_WORKER_THREAD::FlushEvictQueue+133
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.906
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 133
FAILURE_BUCKET_ID: 0x10e_17_dxgmms2!VIDMM_WORKER_THREAD::FlushEvictQueue
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8b70aac8-c9b8-15d4-254c-a3e0828fa53b}
Followup: MachineOwner
CPU: 3700x
CPU cooler: aio
Motherboard: gigabyte
Ram: 32gb
SSD/HDD: nvme m.2
GPU:2080s+2070s
PSU: 750w
OS:win10
memory dump:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000017, Unexpected system command failure.
Arg2: ffffffffc000000d
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3078
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 3121
Key : Analysis.IO.Other.Mb
Value: 6
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 21
Key : Analysis.Init.CPU.mSec
Value: 1671
Key : Analysis.Init.Elapsed.mSec
Value: 21142
Key : Analysis.Memory.CommitPeak.Mb
Value: 94
Key : Bugcheck.Code.DumpHeader
Value: 0x10e
Key : Bugcheck.Code.KiBugCheckData
Value: 0x10e
Key : Bugcheck.Code.Register
Value: 0x10e
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: 10e
BUGCHECK_P1: 17
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffffc881`f95de8a8 fffff802`6c4e3ad0 : 00000000`0000010e 00000000`00000017 ffffffff`c000000d 00000000`00000000 : nt!KeBugCheckEx
ffffc881`f95de8b0 fffff802`6d96a5fb : ffffb889`1dae20a0 ffffb889`209ef7b8 ffffdf08`00000000 ffffb889`209ef7b8 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffc881`f95de8f0 fffff802`6d96abd4 : ffffb889`1dae2000 00000000`00000000 ffffb889`209ef7b8 ffffc881`f95de9c0 : dxgmms2!VIDMM_WORKER_THREAD::FlushEvictQueue+0x133
ffffc881`f95de940 fffff802`6d96a942 : ffffdf08`2a361c60 ffffdf08`2a361c60 00000000`00000000 ffffb889`1dae2010 : dxgmms2!VIDMM_WORKER_THREAD:😛rocessEvictQueues+0xcc
ffffc881`f95de970 fffff802`6d955b73 : fffff802`6d8f4301 fffff802`6d8f4394 00000000`00000000 ffffdf08`31a18900 : dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+0xf6
ffffc881`f95dea00 fffff802`6d946759 : ffffb889`1dae2010 ffffdf08`2a26b301 00000000`00000001 00000000`0679c501 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1a463
ffffc881`f95debe0 fffff802`60917e85 : ffffdf08`2a26b380 fffff802`6d946750 ffffb889`1dae2010 000f8067`b4bbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffc881`f95dec10 fffff802`609fd498 : ffff8781`e0c80180 ffffdf08`2a26b380 fffff802`60917e30 00106b76`ffffffd8 : nt!PspSystemThreadStartup+0x55
ffffc881`f95dec60 00000000`00000000 : ffffc881`f95df000 ffffc881`f95d9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VIDMM_WORKER_THREAD::FlushEvictQueue+133
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.906
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 133
FAILURE_BUCKET_ID: 0x10e_17_dxgmms2!VIDMM_WORKER_THREAD::FlushEvictQueue
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8b70aac8-c9b8-15d4-254c-a3e0828fa53b}
Followup: MachineOwner
Last edited: