Frequent BSODs When Launching Fortnite – KERNEL_SECURITY_CHECK_FAILURE / CLOCK_WATCHDOG_TIMEOUT

[DeineBadewanne]

Hello,

I'm experiencing frequent BSODs when launching Fortnite, specifically with the error codes KERNEL_SECURITY_CHECK_FAILURE or CLOCK_WATCHDOG_TIMEOUT. This issue occurs exclusively with Fortnite—no other games on my system trigger these crashes.

System Specs:

CPU: AMD Ryzen 5 5600

GPU: NVIDIA GTX 1660 Super

RAM: Corsair Vengeance 32GB (3200 MHz)

Troubleshooting Steps Taken:

Updated Windows to the latest version

Updated GPU drivers

Updated CPU drivers

Updated BIOS to the latest version

Scanned for viruses/malware

Disabled XMP profile

Disabled third-party overlays (NVIDIA Overlay, RivaTuner)

Reinstalled and verified Fortnite files

Ran sfc /scannow

Used DISM tool to check and repair system integrity

Newly added RAM a few weeks ago but its compatable and it's stable in all other games, CPU also not overclocked and has good enough temp.

What could be the problem?

[HIVEmind]

honey pot violation

[Crashed]

Doesn't Fortnite have EAC? You might want to uninstall and reinstall it.

[_I_]

where did you get the drivers from?
windows update only gives generic drivers

grab the correct ones from the mobo mfg site

[MonkehMaster]

Crashed původně napsal:

Doesn't Fortnite have EAC? You might want to uninstall and reinstall it.

this seems to be what's found searching Google for issue and the game, it's the likely suspect.

beyond that, didn't see OP mention checking for dx or runtime, missing/corrupt/outdated, which is about all I can think of atm.

that said, to bad the game doesn't have a forum to ask that type of stuff.

also noting, no mention of os, or mention of looking into the dump file for the error code numbers, which would help.

[Crashed]

MonkehMaster původně napsal:

Crashed původně napsal:

Doesn't Fortnite have EAC? You might want to uninstall and reinstall it.

this seems to be what's found searching Google for issue and the game, it's the likely suspect.

beyond that, didn't see OP mention checking for dx or runtime, missing/corrupt/outdated, which is about all I can think of atm.

that said, to bad the game doesn't have a forum to ask that type of stuff.

also noting, no mention of os, or mention of looking into the dump file for the error code numbers, which would help.

If OP is running an Insider Preview OS then it can definitely crash EAC.

[ˢᵈˣ FatCat]

turn on or off secure boot perhaps, but that is a looong shot

[DeineBadewanne]

Well i am running Windows 10 as of right now, it worked about 2 weeks ago with the exact same settings, i have reinstalled EAC, i reinstalled my drivers with DDU, downloaded them from the nvidia website and amd for chipset/cpu and will get the error code numbers soon, can't test right now

[A&A]

AC or some bug checking or illegal (???) parameter in the kernel is causing the crash.

Or the Driver verifier fails for some reason.

[Midnight Aurais]

check your windows folder for the minidump folder if there is one download windbg from microsoft store open one of the dumps in it then click the analyze! highlighted text and copy paste results here

if you know what you are doing you can set break points in windbg and can see live what happened during the crash

[DeineBadewanne]

Midnight Aurais původně napsal:

check your windows folder for the minidump folder if there is one download windbg from microsoft store open one of the dumps in it then click the analyze! highlighted text and copy paste results here

if you know what you are doing you can set break points in windbg and can see live what happened during the crash

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffbd8011106180, The PRCB address of the hung processor.
Arg4: 000000000000000a, The index of the hung processor.

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for EasyAntiCheat_EOS.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1453

Key : Analysis.Elapsed.mSec
Value: 6784

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27793.1000

Key : Analysis.Version.Description
Value: 10.2410.02.02 amd64fre

Key : Analysis.Version.Ext
Value: 1.2410.2.2

Key : Bugcheck.Code.LegacyAPI
Value: 0x101

Key : Bugcheck.Code.TargetModel
Value: 0x101

Key : Failure.Bucket
Value: CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_EasyAntiCheat_EOS!unknown_function

Key : Failure.Hash
Value: {66663eff-c7cb-3b29-1135-c652fb10a94b}

Key : Stack.Pointer
Value: ISR

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 101

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffffbd8011106180

BUGCHECK_P4: a

FILE_IN_CAB: 031225-11562-01.dmp

FAULTING_THREAD: ffffce0829ea0080

FAULTING_PROCESSOR: a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Discord.exe

STACK_TEXT:
ffffb601`cadfeb68 fffff802`3d065dc0 : 00000000`0000001a 01000000`00000002 00000000`00000000 ffffad56`8090bc08 : nt!HalpTscQueryCounterOrdered+0x3
ffffb601`cadfeb70 fffff802`3d31ec10 : 00000000`0007a120 00000000`00000000 ffffb601`cadff400 00000000`0001e956 : nt!KeStallExecutionProcessor+0x120
ffffb601`cadfebf0 fffff802`3d7ba095 : 00000000`00000000 00000000`00000000 ffffb601`cadff4e0 ffffb601`cadff6c0 : nt!KeFreezeExecution+0x110
ffffb601`cadfed20 fffff802`3d312d08 : ffffb601`cadfee50 ffffb601`cadff350 ffffb601`cadfee50 00000000`00000000 : nt!KdEnterDebugger+0x6d
ffffb601`cadfed50 fffff802`3d7bdb80 : ffffb601`cadfee50 ffffb601`cadff350 ffffb601`cadfee50 00000000`0000003c : nt!KdpReport+0x74
ffffb601`cadfed90 fffff802`3d109fe9 : ffffb601`cadff618 00000000`00000000 00000000`00000000 fffff802`3ce02198 : nt!KdpTrap+0x160
ffffb601`cadfede0 fffff802`3d109bd7 : ffffb601`cadff618 ffffb601`cadff350 ffffb601`cadfee50 00000000`0000003c : nt!KdTrap+0x2d
ffffb601`cadfee20 fffff802`3d212eec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x177
ffffb601`cadff4e0 fffff802`3d20af19 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c
ffffb601`cadff6c0 fffff804`db90f6b9 : 00000000`00004dac 00000000`00000000 00000000`00000000 ffffce08`215f8d60 : nt!KiDivideErrorFault+0x319
ffffb601`cadff850 00000000`00004dac : 00000000`00000000 00000000`00000000 ffffce08`215f8d60 00000000`00000000 : EasyAntiCheat_EOS+0x9bf6b9
ffffb601`cadff858 00000000`00000000 : 00000000`00000000 ffffce08`215f8d60 00000000`00000000 00000000`00000000 : 0x4dac


SYMBOL_NAME: EasyAntiCheat_EOS+9bf6b9

MODULE_NAME: EasyAntiCheat_EOS

IMAGE_NAME: EasyAntiCheat_EOS.sys

STACK_COMMAND: .process /r /p 0xffffce081f38b080; .thread 0xffffce0829ea0080 ; kb

BUCKET_ID_FUNC_OFFSET: 9bf6b9

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_EasyAntiCheat_EOS!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {66663eff-c7cb-3b29-1135-c652fb10a94b}

Followup: MachineOwner
---------

[MonkehMaster]

eac had a problem with discord?

[DeineBadewanne]

MonkehMaster původně napsal:

eac had a problem with discord?

Even if closed, the bsod still occures

[Midnight Aurais]

it could possibly be that your discord is compromised why would the anticheat complain about it though

remove fortnite and use like revo unistaller free and unistall discord through it and let it check for remaining files use some common sense if there are system files do not include but if they are only about discord remove

https://www.revouninstaller.com/revo-uninstaller-free-download/

open file explorer and change the address to %temp% and enter delete everything that is in that temp folder do not worry temp is as the name implies temporary this folder exists so programs have a place to throw their trash in

if it gives error that a file is in use then ignore the remaining files it cannot delete it

once that is done download and install fortnite and launch the game if bsod is gone great if not then the error in windbg might now describe a different program as a culprit so analyze it again

if there is no bsod redownload discord from https://discord.com/ don't use the one you might have downloaded already better safe then sorry

also you seem to not be the only one having this issue it been going around near end of 2024 all of them have the same process discord in common you may need to use the browser version instead if this keeps happening it may be just a thing discord or easyanticheat has to fix

[DeineBadewanne]

Midnight Aurais původně napsal:

it could possibly be that your discord is compromised why would the anticheat complain about it though

remove fortnite and use like revo unistaller free and unistall discord through it and let it check for remaining files use some common sense if there are system files do not include but if they are only about discord remove

https://www.revouninstaller.com/revo-uninstaller-free-download/

open file explorer and change the address to %temp% and enter delete everything that is in that temp folder do not worry temp is as the name implies temporary this folder exists so programs have a place to throw their trash in

if it gives error that a file is in use then ignore the remaining files it cannot delete it

once that is done download and install fortnite and launch the game if bsod is gone great if not then the error in windbg might now describe a different program as a culprit so analyze it again

if there is no bsod redownload discord from https://discord.com/ don't use the one you might have downloaded already better safe then sorry

also you seem to not be the only one having this issue it been going around near end of 2024 all of them have the same process discord in common you may need to use the browser version instead if this keeps happening it may be just a thing discord or easyanticheat has to fix

I've tested, it didnt work, uninstalled discord with revo, deleted temp files, first it came up with eac is not installed fixed that and then it crashed again in a Watchdog bsod, i've let that load for about half an hour and it was still on 0%, don't even have a minidump to further look into it because of that

[ˢᵈˣ FatCat]

just install your fortnite on different drive, not the system