Kendi kendine günde 10-15 kez mavi ekran hatası almak

Minidump paylaş.

Sebebi amdfendr.sys yani AMD crash Defender.

Başlat > arama yerine > MSConfig yazın > hizmetler sekmesine girin.

AMD crash Defender service.

AMD external events Utility.

Bu üstteki ikilinin tiklerini kaldırın, uygula ve tamam deyin, PC'yi yeniden başlatın.

Bakalım aynı senaryoda mavi ekran alacak mısınız tekrar?

Aşağıdaki resimde de ekstra olarak "AMD log Utility" var, sizde de varsa onu şimdilik devre dışı bırakmasanız da olur. Yine aynı senaryoda mavi ekran alırsanız onu da devre dışı bırakırsınız.

Jellyel7 dedi:

Minidump paylaş.

Sebebi amdfendr.sys yani AMD crash Defender.

Başlat > arama yerine > MSConfig yazın > hizmetler sekmesine girin.

AMD crash Defender service.

AMD external events Utility.

Bu üstteki ikilinin tiklerini kaldırın, uygula ve tamam deyin, PC'yi yeniden başlatın.

Bakalım aynı senaryoda mavi ekran alacak mısınız tekrar?

Aşağıdaki resimde de ekstra olarak "AMD log Utility" var, sizde de varsa onu şimdilik devre dışı bırakmasanız da olur. Yine aynı senaryoda mavi ekran alırsanız onu da devre dışı bırakırsınız.

Eki Görüntüle 2301937

Rich (BB code):Panoya kopyala

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80224df5625, The address that the exception occurred at
Arg3: fffff80214d27a00, Parameter 0 of the exception
Arg4: ffffac816bf70840, Parameter 1 of the exception

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

*** WARNING: Unable to verify timestamp for amdfendr.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1874

    Key  : Analysis.Elapsed.mSec
    Value: 10961

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1e

    Key  : Failure.Bucket
    Value: 0x1E_C000001D_BAD_IP_amdfendr!unknown_function

    Key  : Failure.Hash
    Value: {20fb5e88-e85f-ce1d-4007-c4c106144646}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff80224df5625

BUGCHECK_P3: fffff80214d27a00

BUGCHECK_P4: ffffac816bf70840

FILE_IN_CAB:  083024-6609-01.dmp

FAULTING_THREAD:  fffff80214d27a00

EXCEPTION_PARAMETER1:  fffff80214d27a00

EXCEPTION_PARAMETER2:  ffffac816bf70840

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

FAILED_INSTRUCTION_ADDRESS:
amdfendr+15625
fffff802`24df5625 c3              ret

STACK_TEXT:
fffff802`19881b78 fffff802`1446e7d5     : 00000000`0000001e ffffffff`c000001d fffff802`24df5625 fffff802`14d27a00 : nt!KeBugCheckEx
fffff802`19881b80 fffff802`14412bec     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x164d05
fffff802`19882240 fffff802`1440c678     : fffff802`19882571 fffff802`3d1ae811 ffffac81`6ddab000 00000000`00000002 : nt!KiExceptionDispatch+0x12c
fffff802`19882420 fffff802`24df5625     : fffff802`24df651f ffffac81`6bf70840 fffff802`198826e0 fffff802`19882760 : nt!KiInvalidOpcodeFault+0x338
fffff802`198825b8 fffff802`24df651f     : ffffac81`6bf70840 fffff802`198826e0 fffff802`19882760 00000000`000124f8 : amdfendr+0x15625
fffff802`198825c0 ffffac81`6bf70840     : fffff802`198826e0 fffff802`19882760 00000000`000124f8 00000000`00000000 : amdfendr+0x1651f
fffff802`198825c8 fffff802`198826e0     : fffff802`19882760 00000000`000124f8 00000000`00000000 fffff802`198826c8 : 0xffffac81`6bf70840
fffff802`198825d0 fffff802`19882760     : 00000000`000124f8 00000000`00000000 fffff802`198826c8 fffff802`19882634 : 0xfffff802`198826e0
fffff802`198825d8 00000000`000124f8     : 00000000`00000000 fffff802`198826c8 fffff802`19882634 fffff802`19882640 : 0xfffff802`19882760
fffff802`198825e0 00000000`00000000     : fffff802`198826c8 fffff802`19882634 fffff802`19882640 fffff802`00019fa0 : 0x124f8


SYMBOL_NAME:  amdfendr+15625

MODULE_NAME: amdfendr

IMAGE_NAME:  amdfendr.sys

STACK_COMMAND:  .process /r /p 0xfffff80214d24a00; .thread 0xfffff80214d27a00 ; kb

BUCKET_ID_FUNC_OFFSET:  15625

FAILURE_BUCKET_ID:  0x1E_C000001D_BAD_IP_amdfendr!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {20fb5e88-e85f-ce1d-4007-c4c106144646}

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

Unloaded modules:
fffff802`1a1b0000 fffff802`1a1c0000   dump_storpor
fffff802`19c00000 fffff802`19c33000   dump_storahc
fffff802`19c60000 fffff802`19c7e000   dump_dumpfve
fffff802`24d30000 fffff802`24d4c000   dam.sys
fffff802`18610000 fffff802`1861c000   WdBoot.sys
fffff802`196d0000 fffff802`196e1000   hwpolicy.sys
0: kd> lmvm amdkmdag
Browse full module list
start             end                 module name
fffff802`3d6d0000 fffff802`436a8000   amdkmdag   (deferred)            
    Image path: \SystemRoot\System32\DriverStore\FileRepository\u0403196.inf_amd64_d0c41aa30f8bcfb2\B402774\amdkmdag.sys
    Image name: amdkmdag.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Wed May  8 10:41:54 2024 (663B2CC2)
    CheckSum:         05F86140
    ImageSize:        05FD8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Kod:Panoya kopyala

Genişletmek için tıkla...

düzelmedi ve ardından birkaç tane daha mavi ekran aldım

Servise gönderimini sağlayın ekran kartını.

Jellyel7 dedi:

Servise gönderimini sağlayın ekran kartını.

Genişletmek için tıkla...

Ekran kartını sokuncede mavi ekran alıyorum