Çözüldü 5950X ve RTX 4080 sistem video izlerken mavi ekran veriyor

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
Çözüm
Hata hala aynı.

Sadece sıkıntılı olabilecek sürücüler arasında şunlar var:
  • eelam.sys = ESET
  • vgk.sys = Riot Vanguard
  • NTIOLib_X64 = MSI araçlarından biri
En azından probleminiz çözülene kadar kaldırabilirsiniz bu yazılımları.

Vanguard kaldırma/tekrar yükleme işlemi için aşağıdaki konuda sadece Vanguard ile alakalı paylaştığım kısma bir bakın.



Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe206b1c02028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000fc800800, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000060c0859, Low order 32-bits of the MCi_STATUS value.

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2405

    Key  : Analysis.Elapsed.mSec
    Value: 4656

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    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: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

    Key  : Failure.Hash
    Value: {b0905187-9dbc-d607-4dc5-8630b9eddb7f}


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe206b1c02028

BUGCHECK_P3: fc800800

BUGCHECK_P4: 60c0859

FILE_IN_CAB:  061123-15437-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:  msedge.exe

STACK_TEXT:
ffff8200`c1e3e938 fffff801`4bf222bb     : 00000000`00000124 00000000`00000000 ffffe206`b1c02028 00000000`fc800800 : nt!KeBugCheckEx
ffff8200`c1e3e940 fffff801`498e10c0     : 00000000`00000000 ffff8200`c1e3ea19 ffffe206`b1c02028 ffffe206`a4aff9d0 : nt!HalBugCheckSystem+0xeb
ffff8200`c1e3e980 fffff801`4c01681f     : 00000000`00000000 ffff8200`c1e3ea19 ffffe206`b1c02028 00000000`00000000 : PSHED!PshedBugCheckSystem+0x10
ffff8200`c1e3e9b0 fffff801`4bf23cea     : ffffe206`a93a6b10 ffffe206`a93a6b10 ffffe206`a4affa20 fffff801`4bd96dba : nt!WheaReportHwError+0x38f
ffff8200`c1e3ea80 fffff801`4bf24140     : 00000000`0000000f ffffe206`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
ffff8200`c1e3ebf0 fffff801`4bf23fd4     : ffffe206`a48f8b40 00000000`00000000 ffff8200`c1e3ee00 00000000`00000000 : nt!HalpMceHandlerCore+0x138
ffff8200`c1e3ec50 fffff801`4bf23467     : ffffe206`a48f8b40 ffff8200`c1e3eef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffff8200`c1e3ec90 fffff801`4bf25a8b     : ffffe206`a48f8b40 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x97
ffff8200`c1e3ecc0 fffff801`4bf85739     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffff8200`c1e3ecf0 fffff801`4be3df3e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffff8200`c1e3ed20 fffff801`4be3db53     : 00000000`00000000 00000000`00000000 00007934`00b47f70 ffff8200`c1e3eef0 : nt!KxMcheckAbort+0x7e
ffff8200`c1e3ee60 00007fff`5e75f829     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
00000083`e322ee10 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`5e75f829


MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

Followup:     MachineOwner
---------
* NVIDIA ekran kartı sürücünüzü güncelleyin.

* Chipset sürücülerini AMD sitesinden indirip güncelleyin, eskilerini silin.

* Sistemde Windows'un Hyper-V (sanallaştırma sistemi) açık. Sanal makine, sanal makine yazılımı, emülatör (BlueStacks vs.) kullanmıyorsanız Hyper-V'yi kapatabilirsiniz. Problem yaratabiliyor bazı sistemlerde.

* Sanallaştırmayla işiniz yoksa BIOS'tan da SVM (sanallaştırma) modunu kapatabilirsiniz (açıksa).


Bu konuyla alakalı bazı sorularım olacak.

* Ne zaman başladı bu mavi ekranlar?
* Herhangi bir değişiklik yapmış mıydınız donanımda?
* Çünkü bu hata genelde donanımsal oluyor.

* İşlemciniz ısınıyor mu?
* Mesela BIOS ekranında, Windows'ta boşta ve oyunlarda kaç derece?

* İşlemcinin soğutucusu ile alakalı işlemler yaptınız mı yakın zamanda?
* Yaptıysanız, çok sıkmış olabilir misiniz?
* İşlemciye baskı sebebiyle pinlerde bir yamulma olmuş olabilir.

* İşlemcinin güç beslemesiyle alakalı bir problem olabilir, yetersiz olabilir.
* Bu da PSU'da bir arızaya işaret eder genelde.

* İşlemcide herhangi bir overclock var mı?
* SSD'nizin sağlığı nasıl?
* Herhangi bir firmware güncellemesi var mı?


* RAM'den kaynaklanması düşük bir ihtimal ancak boş bir zamanınızda RAM testi yapın.

* Memtest güncel sürüm:
https://www.memtest86.com/downloads/memtest86-usb.zip


Dökümler:
Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff800d2e113028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000fc800800, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000060c0859, Low order 32-bits of the MCi_STATUS value.

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2046

    Key  : Analysis.Elapsed.mSec
    Value: 4536

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    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: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

    Key  : Failure.Hash
    Value: {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    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: 3f7


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff800d2e113028

BUGCHECK_P3: fc800800

BUGCHECK_P4: 60c0859

FILE_IN_CAB:  061023-15984-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  lghub_agent.ex

STACK_TEXT:
ffffe380`77257938 fffff800`36af603b     : 00000000`00000124 00000000`00000000 ffff800d`2e113028 00000000`fc800800 : nt!KeBugCheckEx
ffffe380`77257940 fffff800`320910c0     : 00000000`00000000 ffffe380`77257a19 ffff800d`2e113028 ffff800d`238f2d10 : nt!HalBugCheckSystem+0xeb
ffffe380`77257980 fffff800`36bff8ff     : 00000000`00000000 ffffe380`77257a19 ffff800d`2e113028 00000000`031e0000 : PSHED!PshedBugCheckSystem+0x10
ffffe380`772579b0 fffff800`36af7a6a     : ffff800d`26a96b10 ffff800d`26a96b10 ffff800d`238f2d60 fffff800`369c043a : nt!WheaReportHwError+0x38f
ffffe380`77257a80 fffff800`36af7eb5     : 00000000`0000000d ffff800d`00000005 ffff8000`00000000 ffffffff`ffffffff : nt!HalpMcaReportError+0xb2
ffffe380`77257bf0 fffff800`36af7cda     : 00000000`0000000d 00000000`00000000 ffffe380`77257e00 00000000`0000000c : nt!HalpMceHandlerCore+0x12d
ffffe380`77257c50 fffff800`36af71e6     : ffff800d`21cf69c0 ffffe380`77257ef0 00000000`0000000d 00000000`00000000 : nt!HalpMceHandler+0x66
ffffe380`77257c90 fffff800`36af997b     : ffff800d`21cf69c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x96
ffffe380`77257cc0 fffff800`36b5bf09     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffffe380`77257cf0 fffff800`36a3d73e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffe380`77257d20 fffff800`36a3d353     : 00000000`00000010 00000000`00000000 ffff800d`40f760c0 ffffe380`77257ef0 : nt!KxMcheckAbort+0x7e
ffffe380`77257e60 fffff800`3681ece0     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
fffffa8e`fbb67b90 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBeginThreadAccountingPeriod+0x50


MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

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


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

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffff8405505b9140, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: ffff8405505b9140, The process object that initiated the termination.
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2296

    Key  : Analysis.Elapsed.mSec
    Value: 2736

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xef

    Key  : CriticalProcessDied.ExceptionCode
    Value: 505af140

    Key  : CriticalProcessDied.Process
    Value: LsaIso.exe

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    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: 0xEF_LsaIso.exe_BUGCHECK_CRITICAL_PROCESS_505af140_nt!PspCatchCriticalBreak

    Key  : Failure.Hash
    Value: {cc608552-f6ec-b153-1aaa-5c337c6df97d}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    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: 3f7


BUGCHECK_CODE:  ef

BUGCHECK_P1: ffff8405505b9140

BUGCHECK_P2: 0

BUGCHECK_P3: ffff8405505b9140

BUGCHECK_P4: 0

FILE_IN_CAB:  060623-13859-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

PROCESS_NAME:  LsaIso.exe

CRITICAL_PROCESS:  LsaIso.exe

ERROR_CODE: (NTSTATUS) 0x505af140 - <Unable to get error code text>

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

STACK_TEXT:
ffff810e`3171a4a8 fffff807`159abd0b     : 00000000`000000ef ffff8405`505b9140 00000000`00000000 ffff8405`505b9140 : nt!KeBugCheckEx
ffff810e`3171a4b0 fffff807`158fba75     : ffff8405`505b9140 fffff807`15346035 00000000`00000002 fffff807`153462ff : nt!PspCatchCriticalBreak+0x11b
ffff810e`3171a540 fffff807`157ad47f     : ffff8405`505b9140 00000000`c0000022 ffff8405`505b9140 ffff8405`505b9140 : nt!PspTerminateAllThreads+0x14b6fd
ffff810e`3171a5b0 fffff807`157ad271     : ffffffff`ffffffff ffff8405`505b9140 ffff8405`505af140 ffff8405`505b9140 : nt!PspTerminateProcess+0xe3
ffff810e`3171a5f0 fffff807`154406e8     : 00000000`00000420 ffff8405`505af140 ffff8405`505b9140 00000000`00000000 : nt!NtTerminateProcess+0xb1
ffff810e`3171a670 fffff807`15431180     : fffff807`15593d13 ffff8405`505d12f0 00000000`00000001 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
ffff810e`3171a808 fffff807`15593d13     : ffff8405`505d12f0 00000000`00000001 00000000`00000000 ffff810e`3171ab70 : nt!KiServiceLinkage
ffff810e`3171a810 fffff807`15213323     : 00000000`00000000 00000000`00000001 ffff8405`505af140 00000000`00000000 : nt!PsDispatchIumService+0x9f
ffff810e`3171aa80 fffff807`159a9e55     : ffff8405`505af140 ffff8405`505af140 ffff8405`3c923080 fffff807`15226950 : nt!VslpEnterIumSecureMode+0x287
ffff810e`3171ab50 fffff807`15430854     : 00000000`00000000 00000000`00000000 fffff807`159a9d90 00000000`00000000 : nt!PspSecureThreadStartup+0xc5
ffff810e`3171ac00 00000000`00000000     : ffff810e`3171b000 ffff810e`31714000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!PspCatchCriticalBreak+11b

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1702

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  11b

FAILURE_BUCKET_ID:  0xEF_LsaIso.exe_BUGCHECK_CRITICAL_PROCESS_505af140_nt!PspCatchCriticalBreak

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {cc608552-f6ec-b153-1aaa-5c337c6df97d}

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


*******************************************************************************
*                                                                             *
*                        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: ffff9005e3bd88e0
Arg4: ffffe586eec19b00

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1921

    Key  : Analysis.Elapsed.mSec
    Value: 5871

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x119

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    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: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

    Key  : Failure.Hash
    Value: {9a11bf9c-270e-962e-7a82-3efdab93c10e}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    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: 3f7


BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffff9005e3bd88e0

BUGCHECK_P4: ffffe586eec19b00

FILE_IN_CAB:  061023-14343-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff9005`e3bd8778 fffff807`9e505685     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9005`e3bd88e0 : nt!KeBugCheckEx
ffff9005`e3bd8780 fffff807`bbee7208     : 00000000`00000000 ffffe586`e35f2ad0 ffffe586`e35f2ad8 ffffe586`e35f2ae0 : watchdog!WdLogSingleEntry5+0x3b45
ffff9005`e3bd8830 fffff807`bbf461fa     : ffffe586`00000000 ffffe586`eec19b00 ffffe586`ffc3a000 ffffe586`eec19b00 : dxgmms2!VidSchiSendToExecutionQueue+0x1a358
ffff9005`e3bd8a00 fffff807`bbfc6c1c     : ffffe586`eec19b00 ffff9005`e3bd8ab9 ffffe586`ffc3a000 fffff807`bbecb5fc : dxgmms2!VidSchiSendToExecutionQueueWithWait+0x5a
ffff9005`e3bd8a30 fffff807`bbf9dc4c     : fffff807`eed50000 ffffe586`f5969820 ffffe586`e1986010 fffff807`bbf74920 : dxgmms2!VidSchiSubmitPagingCommand+0x358
ffff9005`e3bd8b20 fffff807`bbf749ea     : 00000000`00000000 fffff807`bbf74920 ffffe586`ffc3a000 00000000`00000080 : dxgmms2!VidSchiRun_PriorityTable+0x2920c
ffff9005`e3bd8b70 fffff807`8440dc67     : ffffe586`fd675040 fffff807`00000001 ffffe586`ffc3a000 00000000`00000000 : dxgmms2!VidSchiWorkerThread+0xca
ffff9005`e3bd8bb0 fffff807`84630854     : ffffbc81`43d56180 ffffe586`fd675040 fffff807`8440dc10 00000000`00000246 : nt!PspSystemThreadStartup+0x57
ffff9005`e3bd8c00 00000000`00000000     : ffff9005`e3bd9000 ffff9005`e3bd2000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+1a358

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.22621.1702

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1a358

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9a11bf9c-270e-962e-7a82-3efdab93c10e}

Followup:     MachineOwner
---------
 
* NVIDIA ekran kartı sürücünüzü güncelleyin.

* Chipset sürücülerini AMD sitesinden indirip güncelleyin, eskilerini silin.

* Sistemde Windows'un Hyper-V (sanallaştırma sistemi) açık. Sanal makine, sanal makine yazılımı, emülatör (BlueStacks vs.) kullanmıyorsanız Hyper-V'yi kapatabilirsiniz. Problem yaratabiliyor bazı sistemlerde.

* Sanallaştırmayla işiniz yoksa BIOS'tan da SVM (sanallaştırma) modunu kapatabilirsiniz (açıksa).


Bu konuyla alakalı bazı sorularım olacak.

* Ne zaman başladı bu mavi ekranlar?
Bu gün sabah youtube dan tam ekran Diablo 4 Cinematic lerini izlerken
* Herhangi bir değişiklik yapmış mıydınız donanımda?
Hayır.
* Çünkü bu hata genelde donanımsal oluyor.

* İşlemciniz ısınıyor mu?
hayır boşta 45derecelerde geziyor yük altında da kapanmıyor 85 derecelrde 91 vuruyor max ama kapanmıyor
* Mesela BIOS ekranında, Windows'ta boşta ve oyunlarda kaç derece?
45 55 dolayları
* İşlemcinin soğutucusu ile alakalı işlemler yaptınız mı yakın zamanda?
Bios dan fan ayarları ile oynamıştım hepsini full speed e çekip öyle bırakmışım sanırım
sorun da bu idi sanırım çünkü onu düzelltikten sonra hata tekrarlamadı
* Yaptıysanız, çok sıkmış olabilir misiniz?
olumsuz
* İşlemciye baskı sebebiyle pinlerde bir yamulma olmuş olabilir.
olumsuz
* İşlemcinin güç beslemesiyle alakalı bir problem olabilir, yetersiz olabilir.
1000w asus gold sertifikalı psu var kablolar da da bi sıkıntı yok
* Bu da PSU'da bir arızaya işaret eder genelde.

* İşlemcide herhangi bir overclock var mı?
eco mod da kullanıyorum uzun zamandır bi sorun yok
* SSD'nizin sağlığı nasıl?
bu modeli sağlığı 90
* Herhangi bir firmware güncellemesi var mı?
olumsuz
 
Hyper-V hâlâ açık.

Ayrıca CSM açıksa kapatmak için: how to enable virtualization on a MSI X570 motherboard (burada açmayı gösteriyor, siz kapatırsınız).

Yine WHEA_UNCORRECTABLE_ERROR (124).

* İşlemcide veya anakartta da bir problem olabilir.
Rich (BB code):
12: kd> !errrec ffff8482d6744028
===============================================================================
Common Platform Error Record @ ffff8482d6744028
-------------------------------------------------------------------------------
Record Id     : 01d99b98d2d3c23c
Severity      : Fatal (1)
Length        : 1019
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/10/2023 16:05:57 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Memory
-------------------------------------------------------------------------------
Descriptor    @ ffff8482d67440a8
Section       @ ffff8482d67441c8
Offset        : 416
Length        : 80
Flags         : 0x00000001 Primary
Severity      : Fatal

Physical Addr.: 0x00000001356a1040

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffff8482d6744138
Section       @ ffff8482d67442d8
Offset        : 688
Length        : 292
Flags         : 0x00000000
Severity      : Fatal


Error         : Unknown (Proc 0 Bank 0)
  Status      : 0x0000000000000000

===============================================================================
Section 3     : {c34832a1-02c3-4c52-a9f1-9f1d5d7723fc}
-------------------------------------------------------------------------------
Descriptor    @ ffff8482d6744180
Section       @ ffff8482d67443fc
Offset        : 980
Length        : 39
Flags         : 0x00000000
Severity      : Informational

*** Unknown section format ***


* Kaç adet RAM kullanıyorsunuz? 2 taneyse RAM'lerden birini sökün, mavi ekran aldığınız senaryoyu canlandırın. Mavi ekran alırsanız sökün, diğerini takın ve yine deneyin.


* İki türlü de mavi ekran alırsanız RAM testi yapın.


* Memtest güncel sürüm:

https://www.memtest86.com/downloads/memtest86-usb.zip



Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff8482d6744028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000fc800800, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000060c0859, Low order 32-bits of the MCi_STATUS value.

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2421

    Key  : Analysis.Elapsed.mSec
    Value: 4633

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Dump.Attributes.AsUlong
    Value: 808

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

    Key  : Failure.Hash
    Value: {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    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: 3f7


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff8482d6744028

BUGCHECK_P3: fc800800

BUGCHECK_P4: 60c0859

FILE_IN_CAB:  061023-14062-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x808
  Kernel Generated Triage Dump

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  msedge.exe

STACK_TEXT:
ffffc480`05986938 fffff803`7d6f603b     : 00000000`00000124 00000000`00000000 ffff8482`d6744028 00000000`fc800800 : nt!KeBugCheckEx
ffffc480`05986940 fffff803`7c5010c0     : 00000000`00000000 ffffc480`05986a19 ffff8482`d6744028 ffff8482`caef39f0 : nt!HalBugCheckSystem+0xeb
ffffc480`05986980 fffff803`7d7ff8ff     : 00000000`00000000 ffffc480`05986a19 ffff8482`d6744028 00000000`0303a000 : PSHED!PshedBugCheckSystem+0x10
ffffc480`059869b0 fffff803`7d6f7a6a     : ffff8482`cdfbeb10 ffff8482`cdfbeb10 ffff8482`caef3a40 fffff803`7d5c043a : nt!WheaReportHwError+0x38f
ffffc480`05986a80 fffff803`7d6f7eb5     : 00000000`0000000c ffff8482`00000003 fffffb0b`8d919000 fffffb0b`8d920000 : nt!HalpMcaReportError+0xb2
ffffc480`05986bf0 fffff803`7d6f7cda     : 00000000`0000000c 00000000`00000000 ffffc480`05986e00 00000000`00000000 : nt!HalpMceHandlerCore+0x12d
ffffc480`05986c50 fffff803`7d6f71e6     : ffff8482`ca2f8900 ffffc480`05986ef0 00000000`0000000c 00000000`00000000 : nt!HalpMceHandler+0x66
ffffc480`05986c90 fffff803`7d6f997b     : ffff8482`ca2f8900 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x96
ffffc480`05986cc0 fffff803`7d75bf09     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffffc480`05986cf0 fffff803`7d63d73e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffc480`05986d20 fffff803`7d63d353     : 00000000`00000010 00000000`00000000 ffff8482`e9ec6380 ffffc480`05986ef0 : nt!KxMcheckAbort+0x7e
ffffc480`05986e60 fffff803`7d8a0f99     : fffffb0b`8d91ee60 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KiMcheckAbort+0x2d3
fffffb0b`8d91eaf0 ffffaf04`00ea259c     : 00000000`00000000 00000000`00000006 ffffe583`b5383250 fffff803`91e91269 : nt!ObWaitForMultipleObjects+0x2e9
fffffb0b`8d91eff0 ffffaf04`00e51447     : 00000000`00000000 ffffe583`c2239a30 00000000`ffffffff 00000000`00001cff : win32kfull!xxxMsgWaitForMultipleObjectsEx+0xd8
fffffb0b`8d91f0a0 ffffaf03`ffe47513     : ffff8482`e64d3080 00000033`dd7ff2a8 00000000`ffffffff fffff803`00001cff : win32kfull!NtUserMsgWaitForMultipleObjectsEx+0x3d7
fffffb0b`8d91f9f0 fffff803`7d6406e8     : 00000000`00000000 ffff8482`e9da3080 fffffb0b`8d91fb20 000079a4`004caed0 : win32k!NtUserMsgWaitForMultipleObjectsEx+0x1f
fffffb0b`8d91fa30 00007ffe`9ef9acf4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000033`dd7ff288 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`9ef9acf4


MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

Followup:     MachineOwner
---------
 
Hyper-V hâlâ açık.
CSM açıksa kapatmak için: how to enable virtualization on a MSI X570 motherboard (burada açmayı gösteriyor, siz kapatırsınız).

Yine WHEA_UNCORRECTABLE_ERROR (124).

* BIOS güncel mi? Çünkü dökümden bakmama izin vermiyor. Bu hata BIOS ile alakalı olabilir, stabilite/performans/uyumluluk güncellemeleri geldiyse ve BIOS güncellenmediyse bu hata oluyor olabilir.

* İşlemcide veya anakartta da bir problem olabilir.
Rich (BB code):
12: kd> !errrec ffff8482d6744028
===============================================================================
Common Platform Error Record @ ffff8482d6744028
-------------------------------------------------------------------------------
Record Id     : 01d99b98d2d3c23c
Severity      : Fatal (1)
Length        : 1019
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/10/2023 16:05:57 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Memory
-------------------------------------------------------------------------------
Descriptor    @ ffff8482d67440a8
Section       @ ffff8482d67441c8
Offset        : 416
Length        : 80
Flags         : 0x00000001 Primary
Severity      : Fatal

Physical Addr.: 0x00000001356a1040

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffff8482d6744138
Section       @ ffff8482d67442d8
Offset        : 688
Length        : 292
Flags         : 0x00000000
Severity      : Fatal


Error         : Unknown (Proc 0 Bank 0)
  Status      : 0x0000000000000000

===============================================================================
Section 3     : {c34832a1-02c3-4c52-a9f1-9f1d5d7723fc}
-------------------------------------------------------------------------------
Descriptor    @ ffff8482d6744180
Section       @ ffff8482d67443fc
Offset        : 980
Length        : 39
Flags         : 0x00000000
Severity      : Informational

*** Unknown section format ***


* Kaç adet RAM kullanıyorsunuz? 2 taneyse RAM'lerden birini sökün, mavi ekran aldığınız senaryoyu canlandırın. Mavi ekran alırsanız sökün, diğerini takın ve yine deneyin.


* İki türlü de mavi ekran alırsanız RAM testi yapın.


* Memtest güncel sürüm:

https://www.memtest86.com/downloads/memtest86-usb.zip



Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff8482d6744028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000fc800800, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000060c0859, Low order 32-bits of the MCi_STATUS value.

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2421

    Key  : Analysis.Elapsed.mSec
    Value: 4633

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Dump.Attributes.AsUlong
    Value: 808

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

    Key  : Failure.Hash
    Value: {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    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: 3f7


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff8482d6744028

BUGCHECK_P3: fc800800

BUGCHECK_P4: 60c0859

FILE_IN_CAB:  061023-14062-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x808
  Kernel Generated Triage Dump

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  msedge.exe

STACK_TEXT:
ffffc480`05986938 fffff803`7d6f603b     : 00000000`00000124 00000000`00000000 ffff8482`d6744028 00000000`fc800800 : nt!KeBugCheckEx
ffffc480`05986940 fffff803`7c5010c0     : 00000000`00000000 ffffc480`05986a19 ffff8482`d6744028 ffff8482`caef39f0 : nt!HalBugCheckSystem+0xeb
ffffc480`05986980 fffff803`7d7ff8ff     : 00000000`00000000 ffffc480`05986a19 ffff8482`d6744028 00000000`0303a000 : PSHED!PshedBugCheckSystem+0x10
ffffc480`059869b0 fffff803`7d6f7a6a     : ffff8482`cdfbeb10 ffff8482`cdfbeb10 ffff8482`caef3a40 fffff803`7d5c043a : nt!WheaReportHwError+0x38f
ffffc480`05986a80 fffff803`7d6f7eb5     : 00000000`0000000c ffff8482`00000003 fffffb0b`8d919000 fffffb0b`8d920000 : nt!HalpMcaReportError+0xb2
ffffc480`05986bf0 fffff803`7d6f7cda     : 00000000`0000000c 00000000`00000000 ffffc480`05986e00 00000000`00000000 : nt!HalpMceHandlerCore+0x12d
ffffc480`05986c50 fffff803`7d6f71e6     : ffff8482`ca2f8900 ffffc480`05986ef0 00000000`0000000c 00000000`00000000 : nt!HalpMceHandler+0x66
ffffc480`05986c90 fffff803`7d6f997b     : ffff8482`ca2f8900 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x96
ffffc480`05986cc0 fffff803`7d75bf09     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffffc480`05986cf0 fffff803`7d63d73e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffc480`05986d20 fffff803`7d63d353     : 00000000`00000010 00000000`00000000 ffff8482`e9ec6380 ffffc480`05986ef0 : nt!KxMcheckAbort+0x7e
ffffc480`05986e60 fffff803`7d8a0f99     : fffffb0b`8d91ee60 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KiMcheckAbort+0x2d3
fffffb0b`8d91eaf0 ffffaf04`00ea259c     : 00000000`00000000 00000000`00000006 ffffe583`b5383250 fffff803`91e91269 : nt!ObWaitForMultipleObjects+0x2e9
fffffb0b`8d91eff0 ffffaf04`00e51447     : 00000000`00000000 ffffe583`c2239a30 00000000`ffffffff 00000000`00001cff : win32kfull!xxxMsgWaitForMultipleObjectsEx+0xd8
fffffb0b`8d91f0a0 ffffaf03`ffe47513     : ffff8482`e64d3080 00000033`dd7ff2a8 00000000`ffffffff fffff803`00001cff : win32kfull!NtUserMsgWaitForMultipleObjectsEx+0x3d7
fffffb0b`8d91f9f0 fffff803`7d6406e8     : 00000000`00000000 ffff8482`e9da3080 fffffb0b`8d91fb20 000079a4`004caed0 : win32k!NtUserMsgWaitForMultipleObjectsEx+0x1f
fffffb0b`8d91fa30 00007ffe`9ef9acf4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000033`dd7ff288 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`9ef9acf4


MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

Followup:     MachineOwner
---------
Tamamdır SVM yi kapattım
2 stick ram var
Bios u 2 3 gün önce güncelledim
dün ekran kartını güncellemiştim akşam yatmadan
sanırım beta bi sürücü kurmuşum onu da normal son çıkan sürücüye güncelledim şimdi

bi kere de hypervisor error u verdi mavi ekran da onun dump ı yok

hata almaya devam edersem memtest yapacağım
 
O zaman dediğim gibi Hyper-V'ye ihtiyacınız yoksa kapatın. Kapatmanın birkaç farklı yöntemi var, bazen kapalı sanıyorsunuz yine açık kalıyor vs.. Kapalı olduğundan emin olun yani.

İlk etapta yine dediğim gibi tek RAM ile deneyin. Hata alırsanız RAM'leri değişin yine tek RAM ile deneyin. Devam ederse iki RAM'i de takın. Memtest86 durağından başlayarak 3-4 saatlik bir yolculuk olacak. :)

SSD sağlığı %90 demiştiniz. Sadece SSD var değil mi sistemde?

HDD Sentinel, CrystalDiskInfo gibi programlarla SMART verilerini paylaşır mısınız?

Hatta SSD'nin kendi yazılımı (PNY SSD Toolbox) üzerinden paylaşmanız daha iyi olur bu verileri.
 
Son düzenleme:
O zaman dediğim gibi Hyper-V'ye ihtiyacınız yoksa kapatın. Kapatmanın birkaç farklı yöntemi var, bazen kapalı sanıyorsunuz yine açık kalıyor vs.. Kapalı olduğundan emin olun yani.

İlk etapta yine dediğim gibi tek RAM ile deneyin. Hata alırsanız RAM'leri değişin yine tek RAM ile deneyin. Devam ederse iki RAM'i de takın. Memtest86 durağından başlayarak 3-4 saatlik bir yolculuk olacak. :)

SSD sağlığı %90 demiştiniz. Sadece SSD var değil mi sistemde?

HDD3 Sentinel, CrystalDiskInfo gibi programlarla SMART verilerini paylaşır mısınız?
1 tane 2 tb m2 var sistem ona kurulu
2 tane 1 tb m2 var onlar raid 0
2 tane de 480 lik normal ssd var onlar da raid 0
Screenshot_1.png


Hyper V kapandı eminim hem bios dan hem windos dan kontrol ettim

O zaman dediğim gibi Hyper-V'ye ihtiyacınız yoksa kapatın. Kapatmanın birkaç farklı yöntemi var, bazen kapalı sanıyorsunuz yine açık kalıyor vs.. Kapalı olduğundan emin olun yani.

İlk etapta yine dediğim gibi tek RAM ile deneyin. Hata alırsanız RAM'leri değişin yine tek RAM ile deneyin. Devam ederse iki RAM'i de takın. Memtest86 durağından başlayarak 3-4 saatlik bir yolculuk olacak. :)

SSD sağlığı %90 demiştiniz. Sadece SSD var değil mi sistemde?

HDD Sentinel, CrystalDiskInfo gibi programlarla SMART verilerini paylaşır mısınız?

Hatta SSD'nin kendi yazılımı (PNY SSD Toolbox) üzerinden paylaşmanız daha iyi olur bu verileri.
PNY SSD Toolbox GÖRMÜYOR

1686472829612.png


SSD NİN LİNKİ

Bu gün yine verdi
Hata verdiğinde hep microsoft edge de oluyorum tarayıcı olarak onu kullanıyorum

DUMP

Sanırım mem test yapmam gerekecek
 
Son düzenleme:
HYPERVISOR_ERROR (20001)

Hyper-V hala açık. Ama bu mavi ekranın tarihi 10 Haziran. Belki kapatmadan önce almıştınız bilmiyorum. Hyper-V ile alakalı gibi görünüyor kapatmaya çalışın.

* Son olarak, X570 chipset sürücülerini AMD sitesinden indirip güncellediniz değil mi?


Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000026
Arg2: 0000000000000000
Arg3: fffff806706353de
Arg4: ffff920d372cf2e0

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2375

    Key  : Analysis.Elapsed.mSec
    Value: 7018

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x20001

    Key  : Dump.Attributes.AsUlong
    Value: 808

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x20001_26_0_amdppm!HvRequestIdle

    Key  : Failure.Hash
    Value: {4defc9e5-392b-116d-2fc4-4d3a2bb055be}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    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: 3f7


BUGCHECK_CODE:  20001

BUGCHECK_P1: 26

BUGCHECK_P2: 0

BUGCHECK_P3: fffff806706353de

BUGCHECK_P4: ffff920d372cf2e0

FILE_IN_CAB:  061023-15140-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x808
  Kernel Generated Triage Dump

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffaa01`28acdca8 fffff806`70738ad1     : 00000000`00020001 00000000`00000026 00000000`00000000 fffff806`706353de : nt!KeBugCheckEx
ffffaa01`28acdcb0 fffff806`70676a76     : 00000000`00000100 fffff806`7040770c ffffaa01`28ad6350 ffffaa01`28acdd30 : nt!HvlSkCrashdumpCallbackRoutine+0x81
ffffaa01`28acdcf0 fffff806`70639542     : 00000000`00000100 ffffaa01`28acdef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x26fa96
ffffaa01`28acdd30 fffff806`706392ae     : 00000000`00000100 ffffaa01`28acdef0 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffffaa01`28acde70 fffff806`6d440003     : fffff806`705971ed 00000000`00000000 00000000`00400a02 ffff920d`2cd17a70 : nt!KiNmiInterrupt+0x26e
ffff920d`2cd173f8 fffff806`705971ed     : 00000000`00000000 00000000`00400a02 ffff920d`2cd17a70 fffff806`7042b2e7 : 0xfffff806`6d440003
ffff920d`2cd17400 fffff806`70737d25     : 00000000`00000000 fffff806`7059301b 0000000f`e3b3cd0c 00000000`00989680 : nt!HvcallInitiateHypercall+0x6d
ffff920d`2cd174a0 fffff806`9eba9d2d     : 00000000`000100de fffff806`704b7d58 00000000`00000000 00000000`00000000 : nt!HvlRequestProcessorHalt+0x35
ffff920d`2cd174d0 fffff806`9eba18d3     : 00000000`00000000 00000000`00000000 ffffaa01`28a99510 00000000`0000008b : amdppm!HvRequestIdle+0x2d
ffff920d`2cd17520 fffff806`704bebb7     : 00000000`0000008b ffffaa01`28a91180 00000000`00000000 ffffaa01`28a91180 : amdppm!AcpiCStateIdleExecute+0x23
ffff920d`2cd17550 fffff806`704bda1b     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`70627a10 : nt!PpmIdleExecuteTransition+0x1137
ffff920d`2cd17a10 fffff806`706306a4     : 00000000`00000000 ffffbd0e`5ae11040 ffffbd0e`76ab0080 ffffbd0e`79b1c080 : nt!PoIdle+0x67b
ffff920d`2cd17c00 00000000`00000000     : ffff920d`2cd18000 ffff920d`2cd11000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME:  amdppm!HvRequestIdle+2d

MODULE_NAME: amdppm

IMAGE_NAME:  amdppm.sys

IMAGE_VERSION:  10.0.22621.1774

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  2d

FAILURE_BUCKET_ID:  0x20001_26_0_amdppm!HvRequestIdle

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4defc9e5-392b-116d-2fc4-4d3a2bb055be}

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


Olabilir Memtest86 da yapabilirsiniz, ihtimalleri elemiş oluruz en azından.
 

Geri
Yukarı