Need help with crashes, processor isssue?

YuckyMcNasty · ‎01-04-2026

I have an 14900KS that im getting hard crashes (no BSOD, straight to reboot) after about 1.5Hrs in CoD. I am getting a minidump and have attached a few, they usually say something to the effect of DOUBLE_FAULT. I have tried default settings, and manually applying intels reccomended settings with no diffrence. I have even tried limiting icc_max to 200A and no change.

YuckyMcNasty · ‎01-04-2026

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffff80808af6de70
Arg3: fffffd87e3764bf0
Arg4: fffff8059933e361

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1125

    Key  : Analysis.Elapsed.mSec
    Value: 1972

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29482.1003

    Key  : Analysis.Version.Description
    Value: 10.2509.29.03 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2509.29.3

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007f

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1000007f

    Key  : Dump.Attributes.AsUlong
    Value: 0x1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

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

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x7f_8_wtd!unknown_function

    Key  : Failure.Hash
    Value: {8fba2b0e-edf5-f7c6-5b48-cd11ea0af79a}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7

    Key  : Stack.Pointer
    Value: NMI

    Key  : WER.System.BIOSRevision
    Value: 5.27.0.0


BUGCHECK_CODE:  7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffff80808af6de70

BUGCHECK_P3: fffffd87e3764bf0

BUGCHECK_P4: fffff8059933e361

FILE_IN_CAB:  010426-16406-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffd20203a1d040

DPC_STACK_BASE:  FFFFFD87E3767FB0

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffffd87`e3764bf0 fffff805`994eb036     : ffffd201`0000002f fffff805`99fc7c40 fffffd87`e3764e88 ffff8080`8b1d1180 : nt!KiHeteroIdleSetReduction+0x151
fffffd87`e3764c80 fffff805`992bbc06     : fffffd87`e3764da1 fffffd87`e3764da1 fffff805`99e15840 fffff805`99e15840 : nt!KiHeteroSelectIdleProcessorFromSubNode+0x116
fffffd87`e3764cf0 fffff805`9932face     : 00000000`00022045 00000000`00000000 fffffd87`e3764f78 ffffd201`b3100000 : nt!KiHeteroSelectIdleProcessorFromNode+0x1c6
fffffd87`e3764e00 fffff805`9932f0f6     : ffffd201`c98e3040 fffff805`99275dcc 00000000`0000ff00 ffff8080`8af51180 : nt!KiDeferredReadySingleThread+0x7be
fffffd87`e3764f50 fffff805`9932edb6     : 00000000`00000000 fffff805`00000001 00000000`00000000 00000000`00000000 : nt!KiProcessThreadWaitList+0x106
fffffd87`e3764ff0 fffff805`993343f8     : ffff8080`8af51180 ffffd201`b3623ae8 00000000`00000000 00000000`00000001 : nt!KiExitDispatcher+0x46
fffffd87`e3765050 fffff805`99252f4f     : ffffd201`f19fbe01 00000000`00000001 ffffd201`0000000c ffffd201`b34cb640 : nt!ExQueueWorkItemFromIo+0x318
fffffd87`e37650d0 fffff805`2b4dbb65     : ffffd201`f19fbde0 ffffd201`f19fbde0 ffffd201`ef491b80 fffffd87`e3765249 : nt!IoQueueWorkItem+0x1f
(Inline Function) --------`--------     : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!MxWorkItem::Enqueue+0x20 [minkernel\wdf\framework\shared\inc\primitives\km\MxWorkItemKm.h @ 63] 
fffffd87`e3765100 fffff805`2b4db9d3     : 00000000`00000002 ffffd201`f19fbde0 00000000`00000000 00000000`0000a910 : Wdf01000!FxWorkItem::Enqueue+0xe9 [minkernel\wdf\framework\shared\core\fxworkitem.cpp @ 335] 
fffffd87`e3765150 fffff805`4e3148cf     : ffffd201`f00cb6e0 ffffd201`f19fbde0 fffffd87`e3765249 ffffd201`b44da000 : Wdf01000!imp_WdfWorkItemEnqueue+0x53 [minkernel\wdf\framework\shared\core\fxworkitemapi.cpp @ 179] 
fffffd87`e37651c0 ffffd201`f00cb6e0     : ffffd201`f19fbde0 fffffd87`e3765249 ffffd201`b44da000 00000000`00000000 : wtd+0x48cf
fffffd87`e37651c8 ffffd201`f19fbde0     : fffffd87`e3765249 ffffd201`b44da000 00000000`00000000 00000000`00000000 : 0xffffd201`f00cb6e0
fffffd87`e37651d0 fffffd87`e3765249     : ffffd201`b44da000 00000000`00000000 00000000`00000000 00000000`00000040 : 0xffffd201`f19fbde0
fffffd87`e37651d8 ffffd201`b44da000     : 00000000`00000000 00000000`00000000 00000000`00000040 00000000`00000001 : 0xfffffd87`e3765249
fffffd87`e37651e0 00000000`00000000     : 00000000`00000000 00000000`00000040 00000000`00000001 00000000`00001001 : 0xffffd201`b44da000


SYMBOL_NAME:  wtd+48cf

MODULE_NAME: wtd

IMAGE_NAME:  wtd.sys

STACK_COMMAND: .process /r /p 0xffffd201b34d1040; .thread 0xffffd20203a1d040 ; kb

BUCKET_ID_FUNC_OFFSET:  48cf

FAILURE_BUCKET_ID:  0x7f_8_wtd!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8fba2b0e-edf5-f7c6-5b48-cd11ea0af79a}

YuckyMcNasty · ‎01-04-2026

Ok, for anyone else struggling with this, I have been given the runaround by Gigabyte trying to find out where intels reccomended settings values are located in the BIOS. So Far I have been able to manually track them down to the following, with the Gigabyte BIOS name followed by Intels setting name in [...] and then - with Intels reccomended value.

Intel Default Settings [ " ] - Enabled
IA CEP (Current Excursion Protection) [IA current extrusion protection] - Enabled
??? [SA current extrusion protection] - Enabled
Frequency TVB > Frequency Clipping TVB [Intel Thermal Velocity boost] - Enabled
Enhanced TVB [Intel eTVB (Enhanced Thermal Velocity Boost)] - Enabled
Voltage Reduction Initiated TVB [Thermal Velocity Boost Voltage Optimizations] - Enabled
??? [ICCMAX Unlimited] - Disable
??? [TjMAX Offset] - "0"

IA VR voltage limit [VIDMax] - 1.52V
??? [ICCMax_App] - 320A
Package Power Limit1 - TDP (Watts) [Power Limit 1] [Long] - 253W
Package Power Limit1 Time - 56ms
Package Power Limit2 - TDP (Watts) [Power Limit 2] [Short] - 253W
Package Power Limit2 Time - 2.44ms
Core Current Limit(Amps) [ICCMax] - 400A
VCCSA [System Agent Voltage] {< 1.35V} - Auto
Memory Controller (VDD2/IMC) {< 1.35V} - Auto
Load Line Calibration - Min 0 - Max 1.1 mO
AC and DC LL 0.55 mOhm (55 Gigabyte value); both values must be the same per Intel.

Mike_Intel · ‎01-04-2026

Hello YuckyMcNasty,

Thank you for posting in Intel community Forum.

Before anything else, let me share this link about the issue that you encountered. Intel is aware of this and kindly check the link for the fixes:

Intel® Core™ 13th and 14th Gen Desktop Processor Vmin Shift...

Based on your last post, you provided some settings. How is your system after applying these settings?

If you have questions, please let us know. Thank you.

Best regards,

Michael L.

Intel Customer Support Technician

YuckyMcNasty · ‎01-05-2026

Im aware of the CPU degradation issue, im on my fourth or fifth one at this point. Im still getting crashes even after manually setting the intel recommended settings. its usually a quick crash to reboot, no BSOD displayed but it does write a minidump. I would like to find out where the SA Current excursion and ICCMax_APP setting is in my BIOS to make sure its being enforced but cant find it.

Mike_Intel · ‎01-06-2026

Hello YuckyMcNasty,

Thank you for the clarification.

If your question is about BIOS, you may also try to check or contact the manufacturer of the board.

Once verified and your processor is already having instability issue, you may contact your local Warranty to replace the processor.

If you have questions, please let us know. Thank you.

Best regards,

Michael L.

Intel Customer Support Technician