BSOD on Exit {STACK-OVERFLOW}

[Afterlife, Ghost Groping]

i didnt have this issue during any of the betas but for some reason its happening now. Nexon y'all need to fix this.

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: 0000000000000002, Stack cookie instrumentation code detected a stack-based
buffer overrun.
Arg2: fffff304f2366730, Address of the trap frame for the exception that caused the BugCheck
Arg3: fffff304f2366688, 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: 1562

Key : Analysis.Elapsed.mSec
Value: 2351

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x139

Key : Bugcheck.Code.TargetModel
Value: 0x139

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : FailFast.Name
Value: STACK_COOKIE_CHECK_FAILURE

Key : FailFast.Type
Value: 2

Key : Failure.Bucket
Value: 0x139_MISSING_GSFRAME_nt!KiFastFailDispatch

Key : Failure.Hash
Value: {1971a9b0-b7ec-89bf-0a51-10ac52818da5}


BUGCHECK_CODE: 139

BUGCHECK_P1: 2

BUGCHECK_P2: fffff304f2366730

BUGCHECK_P3: fffff304f2366688

BUGCHECK_P4: 0

FILE_IN_CAB: 070824-10390-02.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

TRAP_FRAME: fffff304f2366730 -- (.trap 0xfffff304f2366730)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000003f rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80640a46c25 rsp=fffff304f23668c8 rbp=ffffc80e7b2b41b0
r8=0000000000000000 r9=7ffffffffffffffc r10=fffff8063b04bce0
r11=fffff304f2366860 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
Ntfs!_report_gsfailure+0x5:
fffff806`40a46c25 cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: fffff304f2366688 -- (.exr 0xfffff304f2366688)
ExceptionAddress: fffff80640a46c25 (Ntfs!_report_gsfailure+0x0000000000000005)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000002
Subcode: 0x2 FAST_FAIL_STACK_COOKIE_CHECK_FAILURE

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 2

PROCESS_NAME: M1-Win64-Shipp

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: 0000000000000002

EXCEPTION_STR: 0xc0000409

STACK_TEXT:
fffff304`f2366408 fffff806`3b230129 : 00000000`00000139 00000000`00000002 fffff304`f2366730 fffff304`f2366688 : nt!KeBugCheckEx
fffff304`f2366410 fffff806`3b2306f2 : ffffa600`e86d5a8a 00000000`000000e1 fffff304`f2366e01 fffff304`f2366e50 : nt!KiBugCheckDispatch+0x69
fffff304`f2366550 fffff806`3b22e3db : ffffc80e`79508ba0 fffff806`3b086404 00000000`00000003 00000000`00000020 : nt!KiFastFailDispatch+0xb2
fffff304`f2366730 fffff806`40a46c25 : fffff806`40c18bdf ffffdb0e`c31517a8 ffffc80e`00000001 ffffc80e`f0339190 : nt!KiRaiseSecurityCheckFailure+0x35b
fffff304`f23668c8 fffff806`40c18bdf : ffffdb0e`c31517a8 ffffc80e`00000001 ffffc80e`f0339190 ffffdb0e`c31517a8 : Ntfs!_report_gsfailure+0x5
fffff304`f23668d0 fffff806`40b29119 : fffff304`f2366e50 ffffdb0e`c31515e0 ffffc80e`f0339190 fffff806`00000001 : Ntfs!NtfsBypassIoDisableCore+0x127
fffff304`f2366950 fffff806`40b3ad5c : 00000000`00000000 fffff304`f2366e28 00000000`00000000 ffffc80e`ef66e960 : Ntfs!NtfsCommonCleanup+0x609
fffff304`f2366dc0 fffff806`3b049b05 : ffffc80e`effe97a0 fffff806`3fd28049 ffffc80e`754c2520 ffffc80e`ef66eeb0 : Ntfs!NtfsFsdCleanup+0x1ec
fffff304`f2367130 fffff806`3fd2a1fb : 00000000`00000000 ffffc80e`effe97a0 00000000`00000001 00000000`00000000 : nt!IofCallDriver+0x55
fffff304`f2367170 fffff806`3fd27e43 : fffff304`f2367200 00000000`00000000 00000000`00000000 ffffc80e`754c2520 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x15b
fffff304`f23671e0 fffff806`3b049b05 : ffffc80e`f0339190 fffff806`3b048298 ffffc80e`ef9600c0 fffff806`3b131d57 : FLTMGR!FltpDispatch+0xa3
fffff304`f2367240 fffff806`3b4ae17f : ffffc80e`f0339190 ffffc80e`754c2520 ffffc80e`ef9600c0 ffffc80e`ef66e960 : nt!IofCallDriver+0x55
fffff304`f2367280 fffff806`3b4c9cb3 : fffff304`f23673c9 fffff304`00000000 00000000`00000414 00000000`00000001 : nt!IopCloseFile+0x18f
fffff304`f2367310 fffff806`3b4c6819 : 00000000`45948d10 00000000`01b34000 00000000`00000414 00000002`35c282d8 : nt!ObpCloseHandle+0x313
fffff304`f2367430 fffff806`3b22f808 : ffffc80e`effa70c0 ffffc80e`effa70c0 00007ffa`e9fb7088 00000000`00000000 : nt!NtClose+0x39
fffff304`f2367460 00007ffb`6be70184 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`00f7f5a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`6be70184

[Afterlife, Ghost Groping]

still no update on this...

[Sir Meowthius]

Originally posted by Afterlife, Ghost Groping:

still no update on this...

Youll want to check your RAM. Search MEMTest86 and put that on a thumb drive and have your UEFI boot to that to run a test on your RAM. Its possible it could be failing or on its way out.

[Afterlife, Ghost Groping]

Originally posted by Sir Meowthius:

Originally posted by Afterlife, Ghost Groping:

still no update on this...

Youll want to check your RAM. Search MEMTest86 and put that on a thumb drive and have your UEFI boot to that to run a test on your RAM. Its possible it could be failing or on its way out.

ran Memtest86+ last night, Passed.

[Sir Meowthius]

Originally posted by Afterlife, Ghost Groping:

Originally posted by Sir Meowthius:

Youll want to check your RAM. Search MEMTest86 and put that on a thumb drive and have your UEFI boot to that to run a test on your RAM. Its possible it could be failing or on its way out.

ram Memtest86+ last night, Passed.

Looked into the Primary Error Code and its a bit general, but it refers to Hardware, Memory or possible software creating a corrupted or broken string resulting in a fatal error creating the BSOD.

Did you try doing a Boot Time Scan Disk? Its the only other option other than either Re-installing the game, or doing a Re-install of your OS if its an Operating System File that has gotten corrupted.

[Afterlife, Ghost Groping]

Originally posted by Sir Meowthius:

Originally posted by Afterlife, Ghost Groping:

ram Memtest86+ last night, Passed.

Looked into the Primary Error Code and its a bit general, but it refers to Hardware, Memory or possible software creating a corrupted or broken string resulting in a fatal error creating the BSOD.

Did you try doing a Boot Time Scan Disk? Its the only other option other than either Re-installing the game, or doing a Re-install of your OS if its an Operating System File that has gotten corrupted.

both SFC and DISM check out, no corruption or errors found :/

[KetoRay]

I've got the same problem here. That's the main reason why I've stopped playing till they fix this. I also did all the scans and tests and all passed.

[Nikusui 😗]

Then, it's probably a software writing to a stack frame exceeding it's allocated space. Win 11?

[Afterlife, Ghost Groping]

Originally posted by Nikusui 😗:

Then, it's probably a software writing to a stack frame exceeding it's allocated space. Win 11?

yea its W11 Pro, but im not sure if Nexon fixed the issue, or my PBO settings which are stable in every single title ive played, that was causing the issue.

i disabled my PBO (Precision Boost Overdrive) settings in BIOS and the problem has stopped... could just be coincidence but theres that.

[Afterlife, Ghost Groping]

Originally posted by KetoRay:

I've got the same problem here. That's the main reason why I've stopped playing till they fix this. I also did all the scans and tests and all passed.

any overclocks of any type? im not sure if its coincidence but i disabled my PBO settings and only left my RAM at EXPO 1 in bios and its been fine so far. unaware if Nexon did a hotfix or not.

[Rogue]

3rd party anti-virus? Or any background tasks/software running messing with system operations, either legit or malware...

[Afterlife, Ghost Groping]

Originally posted by Rogue:

3rd party anti-virus? Or any background tasks/software running messing with system operations, either legit or malware...

nah, im a PC tech so everything here is licensed and all that jazz

[_Atr4Mør5]

Originally posted by Sir Meowthius:

Originally posted by Afterlife, Ghost Groping:

still no update on this...

Youll want to check your RAM. Search MEMTest86 and put that on a thumb drive and have your UEFI boot to that to run a test on your RAM. Its possible it could be failing or on its way out.

MemTest86 is trash

MemTest5 + Anta777 Extreme config
https://github.com/CoolCmd/TestMem5

[_Atr4Mør5]

Originally posted by Afterlife, Ghost Groping:

Originally posted by Nikusui 😗:

Then, it's probably a software writing to a stack frame exceeding it's allocated space. Win 11?

yea its W11 Pro, but im not sure if Nexon fixed the issue, or my PBO settings which are stable in every single title ive played, that was causing the issue.

i disabled my PBO (Precision Boost Overdrive) settings in BIOS and the problem has stopped... could just be coincidence but theres that.

If so, play with LLC