BSODs happening whenever playing the game "New World".

Question

Analyzed a dmp file from a recent Kmode Exception not Handled BSOD and this is what I got. I have also been frequently getting Memory Management BSOD after a few minutes playing the game.

System Info:
Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz, 3601 Mhz, 4 Core(s), 8 Logical Processor(s)
Installed Physical Memory (RAM) 32.0 GB
GPU GTX 1080

I recently replaced my RAM completely so it can't be a problem with that. I have updated all drivers, ran mdsched.exe, and installed all windows updates. Nothing has been helping.

Here is the dmp file analysis:

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 4140

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 17556

Key  : Analysis.Init.CPU.mSec
Value: 859

Key  : Analysis.Init.Elapsed.mSec
Value: 41333

Key  : Analysis.Memory.CommitPeak.Mb
Value: 82

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: 112021-6531-01.dmp

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8034c6d99de

BUGCHECK_P3: 0

BUGCHECK_P4: 28

READ_ADDRESS: fffff8034cafb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000028

EXCEPTION_PARAMETER2: 0000000000000028

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
ffffb903ceb0fb98 fffff8034c259fcb : 000000000000001e ffffffffc0000005 fffff8034c6d99de 0000000000000000 : nt!KeBugCheckEx
ffffb903ceb0fba0 fffff8034c2093ac : 0000000000001000 ffffb903ceb10440 ffff800000000000 0000000000000000 : nt!KiDispatchException+0x17477b
ffffb903ceb10260 fffff8034c205543 : ffff8b000b995250 fffff8034c1f9305 0000000000003708 0000000000000009 : nt!KiExceptionDispatch+0x12c
ffffb903ceb10440 fffff8034c6d99de : fffff8034c749861 000000000000044c 0000000000000000 ffffd40e00000000 : nt!KiPageFault+0x443
ffffb903ceb105d8 fffff8034c749861 : 000000000000044c 0000000000000000 ffffd40e00000000 fffff8034c01bbc2 : nt!ObpCaptureHandleInformation+0xae
ffffb903ceb105e0 fffff8034c6d98b5 : fffff8034c6d9930 ffff8b000d1f7b58 ffffd40e00200000 ffffb903ceb10720 : nt!ExpSnapShotHandleTables+0x131
ffffb903ceb10670 fffff8034c746ee1 : ffffb903ceb10720 00000000000e04f8 0000000000200000 0000000000000000 : nt!ObGetHandleInformation+0x39
ffffb903ceb106b0 fffff8034c49041f : ffffd40ee6cf0010 0000000000000000 ffffcc7aa9400010 ffffd40eedff4000 : nt!ExpGetHandleInformation+0x5d
ffffb903ceb106f0 fffff8034c48f1a7 : fffff8034c48f100 fffff8034db86e29 ffffd40eebd54040 ffffb903ceb10af8 : nt!ExpQuerySystemInformation+0x112f
ffffb903ceb10a30 fffff8034db7278d : ffffd40eebd50000 ffffb903ceb10af8 0000000000000000 0000000000200010 : nt!NtQuerySystemInformation+0x37
ffffb903ceb10a70 ffffd40eebd50000 : ffffb903ceb10af8 0000000000000000 0000000000200010 0000000000000010 : EasyAntiCheat+0x3278d
ffffb903ceb10a78 ffffb903ceb10af8 : 0000000000000000 0000000000200010 0000000000000010 00000000c0000004 : 0xffffd40eebd50000 ffffb903ceb10a80 0000000000000000 : 0000000000200010 0000000000000010 00000000c0000004 00000000000000c0 : 0xffffb903ceb10af8

SYMBOL_NAME: EasyAntiCheat+3278d

MODULE_NAME: EasyAntiCheat

IMAGE_NAME: EasyAntiCheat.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 3278d

FAILURE_BUCKET_ID: 0x1E_c0000005_R_EasyAntiCheat!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ce59a4f8-3172-1959-b169-6e22d4ca6bb1}

UPDATE: Another recent BSOD dmp analysis.

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3561

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 6528

Key  : Analysis.Init.CPU.mSec
Value: 499

Key  : Analysis.Init.Elapsed.mSec
Value: 3110

Key  : Analysis.Memory.CommitPeak.Mb
Value: 79

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: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80667ef836e

BUGCHECK_P3: ffffef8128fef180

BUGCHECK_P4: 0

CONTEXT: ffffef8128fef180 -- (.cxr 0xffffef8128fef180)
rax=000000000000000b rbx=ffff840943fcc180 rcx=0000000000000064
rdx=0000000000000010 rsi=ffffef8128ff0190 rdi=3066744e03030000
rip=fffff80667ef836e rsp=ffffef8128fefb80 rbp=0000000000000008
r8=00000000082e2c64 r9=ffff840943fcd4f0 r10=0000000000000000
r11=ffffef8128fefca8 r12=0000000000000640 r13=ffff840943fcd548
r14=ffffef8128fefef0 r15=ffffb70514a86800
iopl=0 nv up ei pl nz ac pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010212
Ntfs+0xe836e:
fffff80667ef836e 44394710 cmp dword ptr [rdi+10h],r8d ds:002b:3066744e03030010=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: MsMpEng.exe

STACK_TEXT:
ffffef8128fefb80 fffff80667ef903c : ffff84096675f528 ffff840943fcd4f0 ffffb70514a86800 0000000000000001 : Ntfs+0xe836e
ffffef8128fefcb0 fffff80667efa0e0 : ffff84096675f528 ffff8409683b2010 0000000000000000 ffffef8128feff50 : Ntfs+0xe903c
ffffef8128fefda0 fffff80667ef661b : ffff8409683b2010 ffffef8128ff0190 ffff8409683b2010 0000000000000000 : Ntfs+0xea0e0
ffffef8128ff0080 fffff8066368f6f5 : ffff840943fcc030 ffff8409683b2010 ffffef8128ff0300 ffff84098f9767c0 : Ntfs+0xe661b
ffffef8128ff0300 fffff80661176c5f : ffff84098f976800 0000000000000000 ffffef8128ff03f9 fffff80661175c55 : nt!IofCallDriver+0x55
ffffef8128ff0340 fffff806611ac284 : ffffef8128ff03f0 ffff84098f976818 0000000000000000 0000000000000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f
ffffef8128ff03b0 fffff8066368f6f5 : 0000000000000000 ffff840943f77c40 0000000000000000 0000000000000000 : FLTMGR!FltpCreate+0x324
ffffef8128ff0460 fffff80663690ce4 : 0000000000000003 ffff8409683b2010 ffff84096d4e6f49 fffff80663690913 : nt!IofCallDriver+0x55
ffffef8128ff04a0 fffff80663a7717d : ffffef8128ff0760 ffff840943f77c40 ffff84098f976858 0000000000000000 : nt!IoCallDriverWithTracing+0x34
ffffef8128ff04f0 fffff806639f23ee : ffff840943f77c40 000000000000007c ffff84096c183a30 ffff84096c183a01 : nt!IopParseDevice+0x117d
ffffef8128ff0660 fffff80663a948aa : ffff84096c183a00 ffffef8128ff08c8 0000000000000040 ffff840942cfd7a0 : nt!ObpLookupObjectName+0x3fe
ffffef8128ff0830 fffff80663a1608f : 0000000000000000 000000e79157eca0 0000000000000000 0000000000000001 : nt!ObOpenObjectByNameEx+0x1fa
ffffef8128ff0960 fffff80663a15c69 : 000000e79157ec68 0000000000000001 000000e79157eca0 000000e79157ec90 : nt!IopCreateFile+0x40f
ffffef8128ff0a00 fffff80663808cb8 : ffff8409600e4080 000000e79157ec88 ffffef8128ff0aa8 0000000000000001 : nt!NtCreateFile+0x79
ffffef8128ff0a90 00007ffcfd30d814 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000e79157ebf8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffc`fd30d814

SYMBOL_NAME: Ntfs+e836e

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

IMAGE_VERSION: 10.0.19041.1348

STACK_COMMAND: .cxr 0xffffef8128fef180 ; kb

BUCKET_ID_FUNC_OFFSET: e836e

FAILURE_BUCKET_ID: 0x3B_c0000005_Ntfs!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {295ea5f8-4818-74e6-5ff2-8c3321f15313}

Answer 1

Try report this issue to the game manufacturer.
Open start and search for feedback and open the Feedback Hub app and report this issue and make sure include dump files too.
Try uninstall your graphic card driver and see if the problem persist.

Answer 2

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive:

https://www.windowsq.com/t/bsod-posting-instructions.17/
https://www.windowsq.com/resources/v2-log-collector.8/
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

.
.
.
.
.

Answer 3

Hi there,

The best way would be to share this as a feedback to the Game maker and make sure it is not something that has been caused by the game itself.

Kmode Exception Not Handled is a system crash. The crash happens when a Kernel Mode Program is causing an exception, which the error handler is not able to identify.

Before the feedback make sure you have tried these out

-Turn off fast startup
-Run Windows Memory Diagnostics
-Update device drivers & BIOS.

---

--If the reply is helpful, please Upvote and Accept it as an answer--