Has anyone been getting BSODs on Win 10, alder lake?

[TheVroomVroom]

I've been getting BSOD on Alder Lake, it used to be KMODE EXCEPTION and couple like that, after which I did fresh windows install, and past week I have gotten 2 BSODs so far, both KERNEL_SECUIRITY_CHECK FAILED.
I'm running 12700k on Gigabyte Z690 Elite AX DDR4, with 2x8GB Corsair Vengeance LPX 3200Mhz. No OCs at all except XMP on RAM, but I did 4 passes on Memtest and it was fine. I've often some DRM game running, and I was thinking if E/P cores could cause the PC to BSOD or something. Attaching my memory dump just in case.

070322-9078-01.dmp

[kirashi]

1 hour ago, TheVroomVroom said:

I've been getting BSOD on Alder Lake, it used to be KMODE EXCEPTION and couple like that, after which I did fresh windows install, and past week I have gotten 2 BSODs so far, both KERNEL_SECUIRITY_CHECK FAILED.
I'm running 12700k on Gigabyte Z690 Elite AX DDR4, with 2x8GB Corsair Vengeance LPX 3200Mhz. No OCs at all except XMP on RAM, but I did 4 passes on Memtest and it was fine. I've often some DRM game running, and I was thinking if E/P cores could cause the PC to BSOD or something. Attaching my memory dump just in case.

070322-9078-01.dmp 2.42 MB · 1 download

Based on a quick bugcheck analysis of your DMP file, it appears that BEService.exe contributed to the crash. I believe BEService.exe is related to BattleEye Anti-Cheat, so you'll want to contact BattleEye to ask why their software is crashing your system.

Quote

19: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000004, The thread's stack pointer was outside the legal stack
	extents for the thread.
Arg2: ffff998182bcd3b0, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffff998182bcd308, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------
KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2624
    Key  : Analysis.DebugAnalysisManager
    Value: Create
    Key  : Analysis.Elapsed.mSec
    Value: 21788
    Key  : Analysis.Init.CPU.mSec
    Value: 640
    Key  : Analysis.Init.Elapsed.mSec
    Value: 43417
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 87
    Key  : Bugcheck.Code.DumpHeader
    Value: 0x139
    Key  : Bugcheck.Code.Register
    Value: 0x139
    Key  : FailFast.Name
    Value: INCORRECT_STACK
    Key  : FailFast.Type
    Value: 4
    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:  070322-9078-01.dmp
BUGCHECK_CODE:  139
BUGCHECK_P1: 4
BUGCHECK_P2: ffff998182bcd3b0
BUGCHECK_P3: ffff998182bcd308
BUGCHECK_P4: 0

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

EXCEPTION_RECORD:  ffff998182bcd308 -- (.exr 0xffff998182bcd308)
ExceptionAddress: fffff8061925a2e5 (nt!RtlpGetStackLimitsEx+0x0000000000173895)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000004
Subcode: 0x4 FAST_FAIL_INCORRECT_STACK 
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  BEService.exe
ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_CODE_STR:  c0000409
EXCEPTION_PARAMETER1:  0000000000000004
EXCEPTION_STR:  0xc0000409

STACK_TEXT:  
ffff9981`82bcd088 fffff806`19209169     : 00000000`00000139 00000000`00000004 ffff9981`82bcd3b0 ffff9981`82bcd308 : nt!KeBugCheckEx
ffff9981`82bcd090 fffff806`19209590     : ffffe484`c804d6d0 fffff806`1900d9d7 00000048`041002f7 00000000`00000004 : nt!KiBugCheckDispatch+0x69
ffff9981`82bcd1d0 fffff806`19207923     : 00000000`00000000 00000000`00000000 ffffc886`e21344d0 fffff806`190aa133 : nt!KiFastFailDispatch+0xd0
ffff9981`82bcd3b0 fffff806`1925a2e5     : ffff9981`82bcd7c0 ffff9981`82bcdf88 ffff9981`82bcd5b0 ffffc886`ffb6a950 : nt!KiRaiseSecurityCheckFailure+0x323
ffff9981`82bcd540 fffff806`190e6c21     : ffff9981`82bcd7c0 00000000`00000000 ffffc886`e671a948 4be73050`00000003 : nt!RtlpGetStackLimitsEx+0x173895
ffff9981`82bcd570 fffff806`190e59d6     : ffff9981`82bcdf88 ffff9981`82bcdcc0 ffff9981`82bcdf88 00000000`00000060 : nt!RtlDispatchException+0xe1
ffff9981`82bcd790 fffff806`192092ac     : 00000000`00001000 ffff9981`82bce030 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
ffff9981`82bcde50 fffff806`19205443     : ffffc886`f08123b0 ffffc886`e8447770 ffffc886`e8447770 00000000`00000000 : nt!KiExceptionDispatch+0x12c
ffff9981`82bce030 00000000`00000002     : 00000000`00000000 00000000`00000000 fffff806`197804d0 00000000`00020000 : nt!KiPageFault+0x443
ffff9981`82bce1c8 00000000`00000000     : 00000000`00000000 fffff806`197804d0 00000000`00020000 00000000`00000001 : 0x2

SYMBOL_NAME:  nt!KiFastFailDispatch+d0
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
IMAGE_VERSION:  10.0.19041.1288
STACK_COMMAND:  .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET:  d0
FAILURE_BUCKET_ID:  0x139_MISSING_GSFRAME_nt!KiFastFailDispatch
OS_VERSION:  10.0.19041.1
BUILDLAB_STR:  vb_release
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {1971a9b0-b7ec-89bf-0a51-10ac52818da5}

 

[TheVroomVroom]

13 hours ago, kirashi said:

Based on a quick bugcheck analysis of your DMP file, it appears that BEService.exe contributed to the crash. I believe BEService.exe is related to BattleEye Anti-Cheat, so you'll want to contact BattleEye to ask why their software is crashing your system.

 

That's interesting, thanks for letting me know. Yup BEService.exe is definitely BattleEye service.

[TheVroomVroom]

On 7/3/2022 at 2:53 AM, kirashi said:

Based on a quick bugcheck analysis of your DMP file, it appears that BEService.exe contributed to the crash. I believe BEService.exe is related to BattleEye Anti-Cheat, so you'll want to contact BattleEye to ask why their software is crashing your system.

 

Hey man, still got couple BSODs, I did another fresh win install as well, and havent installed BattleEYE. Could you check this dump as well? Thank you!
Pattern is the same, BSOD names are quite simmilar as well  

070822-7687-01.dmp
 

070822-7703-01.dmp

[TheVroomVroom]

It still BSODs with XMP off.

Also I had MemTest running overnight (with XMP on) and after 20 passes it still had 0 errors.

Another dump here (with XMP off)

070922-7937-01.dmp

[kirashi]

4 hours ago, TheVroomVroom said:

Hey man, still got couple BSODs, I did another fresh win install as well, and havent installed BattleEYE. Could you check this dump as well? Thank you!
Pattern is the same, BSOD names are quite simmilar as well  

070822-7687-01.dmp 2.04 MB · 0 downloads
 

070822-7703-01.dmp 1.54 MB · 0 downloads

I don't have time to check on people's dumps all day long - I got paying IT clients to attend to. You can download the WinDBG (Preview) app for free from the Microsoft App Store if you want to analyze your own dump files to see what the possible cause might be.

https://apps.microsoft.com/store/detail/windbg-preview/9PGJGD53TN86

 

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools

 

Memtest is good, but can pass even though memory is bad. If the system continues bug checking (BSOD) after a fresh installation of Windows with only hardware drivers installed (before third party software), that usually points to a hardware problem of some kind.

 

The only thing I just noticed is that you're running an old version (OS_VERSION:  10.0.19041.1) of Windows 10. While this is technically still supported, I would highly advise you install an updated copy to rule out compatibility issues with this older Windows 10 build.

 

https://en.wikipedia.org/wiki/Windows_10_version_history

[TheVroomVroom]

Update:

 

Origin Web Helper Service is to blame. When enabled, driver verified fails Win32KFull.sys.

 

Damn you EA. Didn't expect that to cause THAT.