R5 2600 ve RX 580'li sistemde 1 saat aralıklarla mavi ekran alıyorum

onlyahmett · 26 Mayıs 2023

Merhaba. Her 1 saatte 1 mavi ekran hatası yiyorum DMP dosyası;

052623-6390-01.dmp

drive.google.com

EgeN7 · 26 Mayıs 2023

Sadece bir tane mi dosya oluşmuş?

Bu arada anakartınız nedense Intel görünüyor. Yanlış BIOS mu yüklediniz acaba? Yanlış yükleseniz bile açabiliyor olmanız mucize olurdu açıkçası.

İşlemci Ryzen 5 2600, anakart ise Intel platformu gösteriyor. İlginç.

Kod:

BiosVendor = VMware, Inc.
BiosVersion = VMW201.00V.20904234.B64.2212051119
BiosReleaseDate = 12/05/2022
SystemManufacturer = VMware, Inc.
SystemProductName = VMware20,1
SystemVersion = None
BaseBoardManufacturer = Intel Corporation
BaseBoardProduct = 440BX Desktop Reference Platform
BaseBoardVersion = None
1: kd> !sysinfo cpuspeed
CPUID:           "AMD Ryzen 5 2600 Six-Core Processor            "
Rated Speed:     Not detected!
Measured Speed:  3400

Aşağıdaki linkten CPU-Z'yi indirip "Mainboard" sekmesinin ekran görüntüsünü atar mısınız?

CPU-Z

Sisteminizin işlemcisi, anakartı ve RAM'i gibi temel bileşenlerinin detaylarını öğrenebileceğiniz faydalı bir araçtır. İşlemcinizi test edip, diğer işlemcilerle karşılaştırma yapma olanağı sağlar.

www.technopat.net

Döküm:

Kod:

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This BugCheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a39fefe48359e7b2, Reserved
Arg2: b3b6fc6ad5dda843, Reserved
Arg3: ffffb08bf606b0c0, Failure type dependent information
Arg4: 000000000000001a, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    2a  : Type 4 pool corruption
    2b  : Modification of a function or .pdata
    2c  : Image integrity corruption
    2d  : Processor misconfiguration
    2e  : Type 5 process list corruption
    2f  : Process shadow corruption
    30  : Retpoline code page corruption
    101 : General pool corruption
    102 : Modification of win32k.sys

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2375

    Key  : Analysis.Elapsed.mSec
    Value: 5038

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x109

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

    Key  : Failure.Hash
    Value: {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}

    Key  : Hypervisor.Enlightenments.Value
    Value: 12576

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 3120

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 0

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 0

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 1

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 0

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 83038

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 0

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 0

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 0

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.Value
    Value: 0

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0


BUGCHECK_CODE:  109

BUGCHECK_P1: a39fefe48359e7b2

BUGCHECK_P2: b3b6fc6ad5dda843

BUGCHECK_P3: ffffb08bf606b0c0

BUGCHECK_P4: 1a

FILE_IN_CAB:  052623-6390-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:  System

STACK_TEXT:
fffffe01`fe09de28 00000000`00000000     : 00000000`00000109 a39fefe4`8359e7b2 b3b6fc6a`d5dda843 ffffb08b`f606b0c0 : nt!KeBugCheckEx


SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  BAD_STACK_0x109

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}

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

onlyahmett · 26 Mayıs 2023

EgeN7 dedi:

Sadece bir tane mi dosya oluşmuş?

Bu arada anakartınız nedense Intel görünüyor. Yanlış BIOS mu yüklediniz acaba? Yanlış yükleseniz bile açabiliyor olmanız mucize olurdu açıkçası.

İşlemci Ryzen 5 2600, anakart ise Intel platformu gösteriyor. İlginç.

Kod:

BiosVendor = VMware, Inc.
BiosVersion = VMW201.00V.20904234.B64.2212051119
BiosReleaseDate = 12/05/2022
SystemManufacturer = VMware, Inc.
SystemProductName = VMware20,1
SystemVersion = None
BaseBoardManufacturer = Intel Corporation
BaseBoardProduct = 440BX Desktop Reference Platform
BaseBoardVersion = None
1: kd> !sysinfo cpuspeed
CPUID: "AMD Ryzen 5 2600 Six-Core Processor "
Rated Speed: Not detected!
Measured Speed: 3400

Aşağıdaki linkten CPU-Z'yi indirip "Mainboard" sekmesinin ekran görüntüsünü atar mısınız?

CPU-Z

Sisteminizin işlemcisi, anakartı ve RAM'i gibi temel bileşenlerinin detaylarını öğrenebileceğiniz faydalı bir araçtır. İşlemcinizi test edip, diğer işlemcilerle karşılaştırma yapma olanağı sağlar.

www.technopat.net

Döküm:

Kod:

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This BugCheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a39fefe48359e7b2, Reserved
Arg2: b3b6fc6ad5dda843, Reserved
Arg3: ffffb08bf606b0c0, Failure type dependent information
Arg4: 000000000000001a, Type of corrupted region, can be
 0 : A generic data region
 1 : Modification of a function or .pdata
 2 : A processor IDT
 3 : A processor GDT
 4 : Type 1 process list corruption
 5 : Type 2 process list corruption
 6 : Debug routine modification
 7 : Critical MSR modification
 8 : Object type
 9 : A processor IVT
 a : Modification of a system service function
 b : A generic session data region
 c : Modification of a session function or .pdata
 d : Modification of an import table
 e : Modification of a session import table
 f : Ps Win32 callout modification
 10 : Debug switch routine modification
 11 : IRP allocator modification
 12 : Driver call dispatcher modification
 13 : IRP completion dispatcher modification
 14 : IRP deallocator modification
 15 : A processor control register
 16 : Critical floating point control register modification
 17 : Local APIC modification
 18 : Kernel notification callout modification
 19 : Loaded module list modification
 1a : Type 3 process list corruption
 1b : Type 4 process list corruption
 1c : Driver object corruption
 1d : Executive callback object modification
 1e : Modification of module padding
 1f : Modification of a protected process
 20 : A generic data region
 21 : A page hash mismatch
 22 : A session page hash mismatch
 23 : Load config directory modification
 24 : Inverted function table modification
 25 : Session configuration modification
 26 : An extended processor control register
 27 : Type 1 pool corruption
 28 : Type 2 pool corruption
 29 : Type 3 pool corruption
 2a : Type 4 pool corruption
 2b : Modification of a function or .pdata
 2c : Image integrity corruption
 2d : Processor misconfiguration
 2e : Type 5 process list corruption
 2f : Process shadow corruption
 30 : Retpoline code page corruption
 101 : General pool corruption
 102 : Modification of win32k.sys

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 2375

 Key : Analysis.Elapsed.mSec
 Value: 5038

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x109

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

 Key : Failure.Hash
 Value: {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}

 Key : Hypervisor.Enlightenments.Value
 Value: 12576

 Key : Hypervisor.Enlightenments.ValueHex
 Value: 3120

 Key : Hypervisor.Flags.AnyHypervisorPresent
 Value: 1

 Key : Hypervisor.Flags.ApicEnlightened
 Value: 0

 Key : Hypervisor.Flags.ApicVirtualizationAvailable
 Value: 0

 Key : Hypervisor.Flags.AsyncMemoryHint
 Value: 0

 Key : Hypervisor.Flags.CoreSchedulerRequested
 Value: 0

 Key : Hypervisor.Flags.CpuManager
 Value: 0

 Key : Hypervisor.Flags.DeprecateAutoEoi
 Value: 1

 Key : Hypervisor.Flags.DynamicCpuDisabled
 Value: 0

 Key : Hypervisor.Flags.Epf
 Value: 0

 Key : Hypervisor.Flags.ExtendedProcessorMasks
 Value: 0

 Key : Hypervisor.Flags.HardwareMbecAvailable
 Value: 0

 Key : Hypervisor.Flags.MaxBankNumber
 Value: 0

 Key : Hypervisor.Flags.MemoryZeroingControl
 Value: 0

 Key : Hypervisor.Flags.NoExtendedRangeFlush
 Value: 1

 Key : Hypervisor.Flags.NoNonArchCoreSharing
 Value: 0

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

 Key : Hypervisor.Flags.ValueHex
 Value: 83038

 Key : Hypervisor.Flags.VpAssistPage
 Value: 1

 Key : Hypervisor.Flags.VsmAvailable
 Value: 0

 Key : Hypervisor.RootFlags.AccessStats
 Value: 0

 Key : Hypervisor.RootFlags.CrashdumpEnlightened
 Value: 0

 Key : Hypervisor.RootFlags.CreateVirtualProcessor
 Value: 0

 Key : Hypervisor.RootFlags.DisableHyperthreading
 Value: 0

 Key : Hypervisor.RootFlags.HostTimelineSync
 Value: 0

 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
 Value: 0

 Key : Hypervisor.RootFlags.IsHyperV
 Value: 0

 Key : Hypervisor.RootFlags.LivedumpEnlightened
 Value: 0

 Key : Hypervisor.RootFlags.MapDeviceInterrupt
 Value: 0

 Key : Hypervisor.RootFlags.MceEnlightened
 Value: 0

 Key : Hypervisor.RootFlags.Nested
 Value: 0

 Key : Hypervisor.RootFlags.StartLogicalProcessor
 Value: 0

 Key : Hypervisor.RootFlags.Value
 Value: 0

 Key : Hypervisor.RootFlags.ValueHex
 Value: 0

BUGCHECK_CODE: 109

BUGCHECK_P1: a39fefe48359e7b2

BUGCHECK_P2: b3b6fc6ad5dda843

BUGCHECK_P3: ffffb08bf606b0c0

BUGCHECK_P4: 1a

FILE_IN_CAB: 052623-6390-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: System

STACK_TEXT:
fffffe01`fe09de28 00000000`00000000 : 00000000`00000109 a39fefe4`8359e7b2 b3b6fc6a`d5dda843 ffffb08b`f606b0c0 : nt!KeBugCheckEx

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: BAD_STACK_0x109

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}

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

Sanal makine olduğundan dolayı öyle gözüküyordur

EgeN7 · 26 Mayıs 2023

Şimdi taşlar yerine oturdu gibi.
Tam da yaşadığınız CRITICAL_STRUCTURE_CORRUPTION (109) hatasının Hyper-V ve sanal makine ile bağı varmış zaten. Açıkçası ben de araştırınca gördüm. Sanal makine vb. işlerle pek uğraşmadım daha önce. Ama daha önce yazılan çözümleri göstereyim en azından.

Tüm sanal makinelerdeki UEFI firmware ayarları aynı şekilde yapılmalıymış.

Üstteki pek bir şey ifade etmeyebilir. Asıl olay burada başlıyor.

Aşağıdaki arkadaş BIOS'ta System Profile Settings kısmının altındaki Monitor/Mwait ayarından bahsetmiş. Bazı makinelerinde bu ayar enabled'mış, bazılarında disabled'mış. Bu yüzden sorun yaşamış.

Bu MONITOR/MWAIT ile alakalı konuyu Nutanix de açıklamış aynı şekilde.

Hyper-V'deki tüm hostların aynı konfigürasyonu kullandığından emin olun demiş. Bazı durumlarda meşhur MONITOR/MWAIT ayarımız bazı makinelerde kafasına göre enabled veya disabled olabileceğinden dolayı bu hata olabilir denmiş.

Sizin durumunuzda kaç sanal makine vs. var bilmiyorum ama nihai çözüm sanal makinelerin hepsinin BIOS'taki bu ayarlarının birbiriyle aynı olması gerektiği yönünde. MONITOR/MWAIT olandan bahsediyorum.

Kaynaklar:

Nutanix Support & Insights

portal.nutanix.com

Virtual machines crashing with Bugcheck CRITICAL_STRUCTURE_CORRUPTION (109)

social.technet.microsoft.com

Microsoft Hyper-V: UEFI ayarları sunucu gönderme ve alma konusunda farklı olduğunda BSOD sanal makine geçişi - Lenovo Sunucusu - Lenovo Support NI

support.lenovo.com

R5 2600 ve RX 580'li sistemde 1 saat aralıklarla mavi ekran alıyorum

Ayrıntılı düzenleme

onlyahmett

Hectopat

052623-6390-01.dmp

EgeN7

Gigapat

CPU-Z

onlyahmett

Hectopat

CPU-Z

EgeN7

Gigapat

Nutanix Support & Insights

Virtual machines crashing with Bugcheck CRITICAL_STRUCTURE_CORRUPTION (109)

Microsoft Hyper-V: UEFI ayarları sunucu gönderme ve alma konusunda farklı olduğunda BSOD sanal makine geçişi - Lenovo Sunucusu - Lenovo Support NI

Benzer konular

Technopat Haberler

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz