Pc crashing on AMD cpu and NVIDIA gpu

M

MicrosoftDotCom

New member
Hello everyone!

I recently build a pc (2 days ago) and once a day it crashes (sudden restart or bluescreen).
It crashed once while playing fortnite and once while opening the NVIDIA Geforce Experience app.

When I check the dump file in windows 11 with WinDbg, it shows a relation to the amdfendr.sys module (from the AMD Crash Defender System).
This is what I don't understand about it, assuming the AMD Crash Defender System is a gpu component of AMD, why does my pc have it on a NVIDIA gpu?
Did it come with the chipset driver installation for my AMD motherboard? The integrated graphics card on the motherboard is from AMD.

A similar issue was posted by someone else on this forum, see click link
And to test if the crashes persisted I disabled the AMD Crash Defender System following these steps:

computer management > services and applications > services > amd crash defender service (doubleclick) > general tab > startup type > disabled

I double checked in the task manager that the relevant service (AMD Crash Defender System service) is indeed not active and it shows status 'stopped'.

My question is the following, what can I do to fix the crashes and why are the dump files reporting this specific module when it's disabled?
Full specs are listed below, also two dump files are attached.


Computer Specs:

CPU: AMD Ryzen 7 7800X3D
MOBO: MSI MAG B650 TOMAHAWK WIFI (MS-7D75)
MEMORY: G.Skill F5-6000J3038F16G (16GB x 2 @ 6000mhz with EXPO)
GPU: MSI RTX 2080 Super Gaming X Trio
OS: Windows 11 Education 24H2


Last dump analysis

Code: 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffffbd8367ed72b0
Arg4: ffffbe83cbc2be70

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 968

    Key  : Analysis.Elapsed.mSec
    Value: 10892

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

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

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

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

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

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

    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: 0x119

    Key  : Bugcheck.Code.TargetModel
    Value: 0x119

    Key  : Dump.Attributes.AsUlong
    Value: 0x31808

    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: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_amdfendr!unknown_function

    Key  : Failure.Hash
    Value: {f832bfef-8bf1-28a9-1049-a27f576d3329}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24a10ef

    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


BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffffbd8367ed72b0

BUGCHECK_P4: ffffbe83cbc2be70

FILE_IN_CAB:  041025-13640-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x31808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffbe83cbbcb480

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffffbd8367ed4b50 -- (.trap 0xffffbd8367ed4b50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=000000000004002f rsi=0000000000000000 rdi=0000000000000000
rip=fffff800e4df29a9 rsp=ffffbd8367ed4ce8 rbp=0000000000000001
 r8=ffffbd8367ed4df0  r9=000000000000002f r10=0000fffff800e4df
r11=ffffd5f85e200000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz ac pe cy
nt!HalpApic1WriteIcr+0x9:
fffff800`e4df29a9 448b8000030000  mov     r8d,dword ptr [rax+300h] ds:00000000`00000300=????????
Resetting default scope

STACK_TEXT:
ffffbd83`67ed4a08 fffff800`e508f8e9     : 00000000`0000000a 00000000`00000300 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffbd83`67ed4a10 fffff800`e508aba8     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffbd83`67ed4b50 fffff800`e4df29a9     : fffff800`e4db8906 ffffbd83`67ed4d18 00000000`00001030 ffffbe83`bf291ba0 : nt!KiPageFault+0x468
ffffbd83`67ed4ce8 fffff800`e4db8906     : ffffbd83`67ed4d18 00000000`00001030 ffffbe83`bf291ba0 ffffbe83`d5aae540 : nt!HalpApic1WriteIcr+0x9
ffffbd83`67ed4cf0 fffff800`e4c2779b     : ffffbe83`00000000 00000000`00000200 ffffbd83`67ed4e10 ffffbe83`bf291ba0 : nt!HalpApicRequestInterrupt+0x96
ffffbd83`67ed4d60 fffff800`e4c09910     : ffffbd83`67ed51f0 00000000`00000000 00000000`00000000 fffff800`ca971bc7 : nt!HalpInterruptSendIpi+0x13b
ffffbd83`67ed5080 fffff800`e4c09371     : 0000ffff`f800ca97 ffffbe83`c16fd880 00000000`00000000 00000000`00000008 : nt!KiInsertQueueDpc+0x590
ffffbd83`67ed5180 fffff800`ca970e0b     : ffffbe83`c16fd001 ffffbd83`67ed5200 ffffbe83`c16fd880 00000000`00029dd3 : nt!KeInsertQueueDpc+0x11
ffffbd83`67ed51c0 ffffbe83`c16fd001     : ffffbd83`67ed5200 ffffbe83`c16fd880 00000000`00029dd3 00000000`00000000 : amdfendr+0x10e0b
ffffbd83`67ed51c8 ffffbd83`67ed5200     : ffffbe83`c16fd880 00000000`00029dd3 00000000`00000000 00000000`00000002 : 0xffffbe83`c16fd001
ffffbd83`67ed51d0 ffffbe83`c16fd880     : 00000000`00029dd3 00000000`00000000 00000000`00000002 00000000`00000000 : 0xffffbd83`67ed5200
ffffbd83`67ed51d8 00000000`00029dd3     : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xffffbe83`c16fd880
ffffbd83`67ed51e0 00000000`00000000     : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : 0x29dd3


SYMBOL_NAME:  amdfendr+10e0b

MODULE_NAME: amdfendr

IMAGE_NAME:  amdfendr.sys

STACK_COMMAND:  .process /r /p 0xffffbe83b8593040; .thread 0xffffbe83cbbcb480 ; kb

BUCKET_ID_FUNC_OFFSET:  10e0b

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_amdfendr!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f832bfef-8bf1-28a9-1049-a27f576d3329}

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

SpyderTracks

We love you Ukraine
These forums are for support on PCSpecialist systems only I'm afraid, as it's a self build you'd need an open forum like Toms Hardware
 
You must log in or register to reply here.
Top