Bluescreen, code 11d

Question

Hello, i have recived bluescreens lately and i find it very hard to trobleshoot to find whats the error is.

I have some information when it happends and some logs.

When i play Satisfactory and Fortnite Lego, so i think it has something about temperature. Hope you guys can help
I tried to format the computer, but the Bluescreen are still there.

https://1drv.ms/f/s!AoJtxshAobP2s0RSbTWG8MLgSVuD?e=t88PTp

Problemsignatur

Problemhendelsesnavn: BlueScreen

Kode: 11d

Parameter 1: 7

Parameter 2: ffffb08fb15d0000

Parameter 3: 1000

Parameter 4: 10fd

OS-versjon: 10_0_22621

Service Pack: 0_0

Produkt: 768_1

OS-versjon: 10.0.22621.2.0.0.768.101

ID for nasjonal innstilling: 1044

Beskrivelse

Computer restarted after a errorcontroll. Feilkontrollen var: 0x0000011d (0x0000000000000007, 0xffffb08fb15d0000, 0x0000000000001000, 0x00000000000010fd). Dump ble lagret i: C:\WINDOWS\Minidump\121723-5984-01.dmp. Rapport-ID: ac65a330-8119-4a51-84a7-148f536781de.

******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

EVENT_TRACING_FATAL_ERROR (11d) Event Tracing subsystem has encountered an unexpected fatal error. First parameter indicates the type of failure. Arguments: Arg1: 0000000000000007, Trace buffer corruption. Arg2: ffffb08fb15d0000 Arg3: 0000000000001000 Arg4: 00000000000010fd

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 78

Key  : Analysis.Elapsed.mSec
Value: 8654

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x11d

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  : Failure.Bucket
Value: 0x11D\_nt!EtwpEnqueueAvailableBuffer

Key  : Failure.Hash
Value: {9082fc0e-b919-27ea-ba62-61b267b092b3}

BUGCHECK_CODE: 11d

BUGCHECK_P1: 7

BUGCHECK_P2: ffffb08fb15d0000

BUGCHECK_P3: 1000

BUGCHECK_P4: 10fd

FILE_IN_CAB: 121723-5984-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008 Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: FortniteClient

DPC_STACK_BASE: FFFF860AC0F17FB0

STACK_TEXT:
ffff860ac0f17578 fffff8051d06bed4 : 000000000000011d 0000000000000007 ffffb08fb15d0000 0000000000001000 : nt!KeBugCheckEx ffff860ac0f17580 fffff8051ce0bc7b : ffffc0805c6ed100 ffffb08fb13fb5c0 ffffb08fb15d0000 ffffb08fbfe5f080 : nt!EtwpEnqueueAvailableBuffer+0x25fe64 ffff860ac0f175c0 fffff8051ce0bd50 : ffffb08fb15d000e 0000000000000000 000000000000000a 0000000000000000 : nt!EtwpPrepareDirtyBuffer+0x2b ffff860ac0f17600 fffff8051ce7b379 : 0000000000000020 ffff860ac0f17768 ffffb08fb15d0000 0000000000000000 : nt!EtwpSwitchBuffer+0xb0 ffff860ac0f17650 fffff8051ce7b848 : ffff860ac0f17e00 0000000000000000 0000000000000000 ffff860ac0f17748 : nt!EtwpReserveTraceBuffer+0x309 ffff860ac0f17710 fffff8051ce717a3 : 0000000000000000 ffffb08fb12e3000 ffffc0805ce3b6f0 ffff860a00000002 : nt!EtwpLogKernelEvent+0x3c8 ffff860ac0f177c0 fffff8051ce72741 : 0000000000000000 ffff860ac0f17e00 ffffb08fc27c1990 000000000005ac0e : nt!KiExecuteAllDpcs+0x743 ffff860ac0f17d00 fffff8051d020135 : 0000000000000000 0000000000000000 ffffc0805c531180 0000000000000000 : nt!KiRetireDpcList+0x1b1 ffff860ac0f17fb0 fffff8051d0200df : ffff860ac64bd6e9 fffff8051ce609d5 0000000000000006 ffffb08fdadc1b60 : nt!KxSwapStacksAndRetireDpcList+0x5 ffff860ac64bd650 fffff8051ce609d5 : 0000000000000006 ffffb08fdadc1b60 0000000000000001 0000000000000000 : nt!KiPlatformSwapStacksAndCallReturn ffff860ac64bd660 fffff8051d01f520 : 0000000000000000 0000000000000000 ffffb08fc27c1080 ffffb08fc27c1990 : nt!KiDispatchInterrupt+0xd5 ffff860ac64bd750 fffff8051ce69961 : ffffc0805c531180 0000000000000000 0000000000000000 0000000000000000 : nt!KiDpcInterrupt+0x350 ffff860ac64bd8e8 fffff8051ce691fb : ffffb08fd9e42660 ffffb08f00000000 0000000000000000 0000000000000000 : nt!KiExitDispatcher+0xc1 ffff860ac64bd920 fffff8051d3a93b9 : 0000000000000000 ffff860ac64bdaa0 0000000000000000 ffffb08fc28741c0 : nt!KeSetEvent+0xeb ffff860ac64bd9b0 fffff8051d02bbe5 : ffffb08fc27c1080 ffffb08fdadc1b60 ffff860a00000000 ffffb08f00000000 : nt!NtSetEvent+0xb9 ffff860ac64bda20 00007ffb70d2f534 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25 000000866c53f3e8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb`70d2f534

SYMBOL_NAME: nt!EtwpEnqueueAvailableBuffer+25fe64

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.2861

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 25fe64

FAILURE_BUCKET_ID: 0x11D_nt!EtwpEnqueueAvailableBuffer

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9082fc0e-b919-27ea-ba62-61b267b092b3}

Followup: MachineOwner

Answer 1

I did 5 loops and no errors.

Answer 2

Sorry, I was offline.

To test your RAM, the best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

Answer 3

Hello Dave,

Sorry, i dont have any more Minidump files to send you.

Is it possible to take a RAM-test to make sure that the RAM is defect?

CPU idles as 40 degrees and the watercoolingsystem is Corsair iCUE H150i Elite LCD
Intel Core i7-12700K Alder Lake

ZOTAC GeForce RTX3080Ti AMP HOLO

G.Skill Trident Z Neo DDR4 3600Mhz 32GB

ASRock Z690 Steel Legend MB

Corsair AX 860, 860W PSU

Answer 4

Hi, I am Dave, I will help you with this.

Your one minidump file just indicates memory (RAM) corruption no specific cause is listed

Do you have any more minidump files you can upload for analysis?