In my experience, I think The Battle Eye itself is flawed, causing crashes on many users' computers. So my advice is to reinstall the game, then perform a clean boot to rule out the influence of the software. Please refer to this article: https://support.microsoft.com/en-us/topic/how-t...
bluedeath
Hi All,
I had a few bluedeath when I played escape from tarkov and I checked the memory.dmp file and here is the result:
Can you help me what can I do with that issue ?
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff801`5e600000 PsLoadedModuleList = 0xfffff801`5f22a230
Debug session time: Sat Apr 23 23:11:27.883 2022 (UTC + 8:00)
System Uptime: 0 days 1:18:06.716
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`5e9f78a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffde8e`c8d367b0=000000000000013a
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_HEAP_CORRUPTION (13a)
The kernel mode heap manager has detected corruption in a heap.
Arguments:
Arg1: 0000000000000011, Type of corruption detected
Arg2: ffffa30f6ae02100, Address of the heap that reported the corruption
Arg3: ffffa30f84c826f0, Address at which the corruption was detected
Arg4: 0000000000000000
Debugging Details:
------------------
fffff8015f2fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
HeapDbgInitExtension Failed
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3108
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 14729
Key : Analysis.Init.CPU.mSec
Value: 390
Key : Analysis.Init.Elapsed.mSec
Value: 55552
Key : Analysis.Memory.CommitPeak.Mb
Value: 93
FILE_IN_CAB: 042322-10296-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 13a
BUGCHECK_P1: 11
BUGCHECK_P2: ffffa30f6ae02100
BUGCHECK_P3: ffffa30f84c826f0
BUGCHECK_P4: 0
POOL_ADDRESS: Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffa30f84c826f0
FREED_POOL_TAG: BE__
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: UnityCrashHand
STACK_TEXT:
ffffde8e`c8d367a8 fffff801`5eb8ec58 : 00000000`0000013a 00000000`00000011 ffffa30f`6ae02100 ffffa30f`84c826f0 : nt!KeBugCheckEx
ffffde8e`c8d367b0 fffff801`5eb8ecb8 : 00000000`00000011 00000000`00000000 ffffa30f`6ae02100 ffffde8e`c8d36a28 : nt!RtlpHeapHandleError+0x40
ffffde8e`c8d367f0 fffff801`5eb8e8e5 : 00000000`00000030 ffffa30f`84c7f000 ffffa30f`88c6c000 00000000`00000000 : nt!RtlpHpHeapHandleError+0x58
ffffde8e`c8d36820 fffff801`5ea51bfc : ffff908c`187e0770 fffff801`5e88ae8c 00000000`00000001 ffffde8e`c8d36ac8 : nt!RtlpLogHeapFailure+0x45
ffffde8e`c8d36850 fffff801`5e8893f2 : ffffa30f`6ae02340 ffff908c`14742bff ffff908c`188e95f0 ffffde8e`00000000 : nt!RtlpHpLfhSubsegmentFreeBlock+0x18659c
ffffde8e`c8d36900 fffff801`5efb2149 : 00000000`00000000 ffffde8e`c8d36b68 00000000`000023c4 01000000`00100000 : nt!ExFreeHeapPool+0x362
ffffde8e`c8d369e0 fffff801`b9385907 : fffff801`b90751d8 ffffde8e`00000000 00000000`00000000 00000000`00000000 : nt!ExFreePool+0x9
ffffde8e`c8d36a10 fffff801`b90751d8 : ffffde8e`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : BEDaisy+0x325907
ffffde8e`c8d36a18 ffffde8e`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : BEDaisy+0x151d8
ffffde8e`c8d36a20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 61724379`74696e55 : 0xffffde8e`00000000
SYMBOL_NAME: BEDaisy+325907
MODULE_NAME: BEDaisy
IMAGE_NAME: BEDaisy.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 325907
FAILURE_BUCKET_ID: 0x13a_11_BE___BEDaisy!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {6a85b8ad-f8a7-b71c-b9d1-e9d62252af2e}
Followup: MachineOwner
---------
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
3 answers
Sort by: Most helpful
-
Anonymous
2022-04-24T13:05:40+00:00 Yep, the blue screen only happens when I run this game, so I'm wonderring that if the BattleEye has a conflict with my graphic driver, but this wrong can't be fixed via reintalling graphic driver.
-
Sakiko 39,240 Reputation points Independent Advisor2022-04-23T16:25:12+00:00 Hello, I'm A&K, here to help.
The information you provided shows that BattleEye has created a blue screen.
Try temporarily uninstalling the game to see if that helps.