3060 Ti sistem mavi ekran hatası

Hüseyin20c · 14 Temmuz 2023

minidump.rar
Merhaba sistemim yeni topladım fakat mavi ekran hatası alıyorum yardımcı olursanız sevinirim.

EgeN7 · 14 Temmuz 2023

Olasılıklar çok.
Ancak genellikle donanımsal olur.
Ne sıklıkla oluyor bu hata?
Ne yaparken oluyor?
Ben ihtimalleri sıralayayım. Mutlaka hepsini dikkatlice kontrol edin.

- İşlemci soğutucu montajında fiziksel bir problem.
- Soğutucu bloğun hizasının düz olduğundan emin olun.
- Soğutucu vidalarını çok sıkı veya çok gevşek yapmayın.
- İşlemciye baskı uyguluyor olabilir.

- İşlemcide ve RAM'lerde stabil olmayan bir overclock / undervolt olma ihtimali.
- BIOS ayarlarında bir oynama varsa BIOS'u sıfırlayın, load optimized defaults yapabilirsiniz.

- Güncel olmayan chipset sürücüleri.
- Buradan güncelleyin: https://www.amd.com/en/support/chipsets/amd-socket-am4/b550

- İşlemcinin aşırı ısınma ihtimali.
- İşlemcinin sıcaklığını kontrol edin.
- Hangi senaryoda mavi ekran alıyorsanız mutlaka işlemci sıcaklığının kaç olduğuna bir bakın.

- BIOS güncel olmaması.
- Sürümü dökümden göremedim.
- Güncel değilse mutlaka güncelleyin.

ROG STRIX B550-F GAMING | ROG Strix | Gaming motherboards｜ROG - Republic of Gamers｜ROG Türkiye

PCIe® 4.0, eşli güç aşamaları, Intel® 2.5Gb Ethernet, Soğutma bloklu Çift M.2, SATA 6 Gbps, USB 3.2 Gen 2 ve Aura Sync RGB Aydınlatma özelliklerine sahip AMD B550 Ryzen AM4 Gaming ATX anakart

rog.asus.com

- Son olarak güç kaynağındaki bir arıza. Dolayısıyla işlemciye stabil güç gitmemesi.
- Ama önce diğer ihtimalleri göz önünde bulundurun.

Döküm:

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: ffff9903539dc028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000bc000800, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000001010135, 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: 2140

    Key  : Analysis.Elapsed.mSec
    Value: 2347

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

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

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

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

BUGCHECK_P3: bc000800

BUGCHECK_P4: 1010135

FILE_IN_CAB:  071423-6312-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:  chrome.exe

STACK_TEXT:
ffffc181`48406938 fffff801`687223fb     : 00000000`00000124 00000000`00000000 ffff9903`539dc028 00000000`bc000800 : nt!KeBugCheckEx
ffffc181`48406940 fffff801`643310c0     : 00000000`00000000 ffffc181`48406a19 ffff9903`539dc028 ffff9903`4d4fc610 : nt!HalBugCheckSystem+0xeb
ffffc181`48406980 fffff801`6881695f     : 00000000`00000000 ffffc181`48406a19 ffff9903`539dc028 ffffc181`48417000 : PSHED!PshedBugCheckSystem+0x10
ffffc181`484069b0 fffff801`68723e2a     : ffff9903`4d3b8b00 ffff9903`4d3b8b00 ffff9903`4d4fc660 fffff801`685971aa : nt!WheaReportHwError+0x38f
ffffc181`48406a80 fffff801`68724280     : 00000000`0000000c ffff9903`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
ffffc181`48406bf0 fffff801`6872409a     : 00000000`0000000c 00000000`00000000 ffffc181`48406e00 00000000`00000000 : nt!HalpMceHandlerCore+0x138
ffffc181`48406c50 fffff801`687235a7     : ffff9903`4d34d900 ffffc181`48406ef0 00000000`0000000c 00000000`00000000 : nt!HalpMceHandler+0x66
ffffc181`48406c90 fffff801`68725bcb     : ffff9903`4d34d900 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x97
ffffc181`48406cc0 fffff801`68785879     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffffc181`48406cf0 fffff801`6863e03e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffc181`48406d20 fffff801`6863dc53     : 00000000`00000000 00000000`00000000 7fffffff`ffffffff ffffc181`48406ef0 : nt!KxMcheckAbort+0x7e
ffffc181`48406e60 00007ffa`e67efa6f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
0000002c`afdff080 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`e67efa6f


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

Hüseyin20c · 14 Temmuz 2023

Mavi ekran gelmesı belli olmuyor boşta dururken de gelıyor oyun oynarken gelıyor sıcaklıkları izliyorum yuk altında hersey stabil gözukuyor 850 watt thermaltake butun parcalarım sıfır güc kaynagını da bu yuzden almıstım mavi ekran gelıyor dıye sonra ramları garantıye yolladım hıcbırsey cıkmadı arza yok

EgeN7 dedi:

Olasılıklar çok.
Ancak genellikle donanımsal olur.
Ne sıklıkla oluyor bu hata?
Ne yaparken oluyor?
Ben ihtimalleri sıralayayım. Mutlaka hepsini dikkatlice kontrol edin.

- İşlemci soğutucu montajında fiziksel bir problem.
- Soğutucu bloğun hizasının düz olduğundan emin olun.
- Soğutucu vidalarını çok sıkı veya çok gevşek yapmayın.
- İşlemciye baskı uyguluyor olabilir.

- İşlemcide ve RAM'lerde stabil olmayan bir overclock / undervolt olma ihtimali.
- BIOS ayarlarında bir oynama varsa BIOS'u sıfırlayın, load optimized defaults yapabilirsiniz.

- Güncel olmayan chipset sürücüleri.
- Buradan güncelleyin: https://www.amd.com/en/support/chipsets/amd-socket-am4/b550

- İşlemcinin aşırı ısınma ihtimali.
- İşlemcinin sıcaklığını kontrol edin.
- Hangi senaryoda mavi ekran alıyorsanız mutlaka işlemci sıcaklığının kaç olduğuna bir bakın.

- BIOS güncel olmaması.
- Sürümü dökümden göremedim.
- Güncel değilse mutlaka güncelleyin.

ROG STRIX B550-F GAMING | ROG Strix | Gaming motherboards｜ROG - Republic of Gamers｜ROG Türkiye

PCIe® 4.0, eşli güç aşamaları, Intel® 2.5Gb Ethernet, Soğutma bloklu Çift M.2, SATA 6 Gbps, USB 3.2 Gen 2 ve Aura Sync RGB Aydınlatma özelliklerine sahip AMD B550 Ryzen AM4 Gaming ATX anakart

rog.asus.com

- Son olarak güç kaynağındaki bir arıza. Dolayısıyla işlemciye stabil güç gitmemesi.
- Ama önce diğer ihtimalleri göz önünde bulundurun.

Döküm:

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: ffff9903539dc028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000bc000800, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000001010135, 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: 2140

    Key  : Analysis.Elapsed.mSec
    Value: 2347

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

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

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

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

BUGCHECK_P3: bc000800

BUGCHECK_P4: 1010135

FILE_IN_CAB:  071423-6312-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:  chrome.exe

STACK_TEXT:
ffffc181`48406938 fffff801`687223fb     : 00000000`00000124 00000000`00000000 ffff9903`539dc028 00000000`bc000800 : nt!KeBugCheckEx
ffffc181`48406940 fffff801`643310c0     : 00000000`00000000 ffffc181`48406a19 ffff9903`539dc028 ffff9903`4d4fc610 : nt!HalBugCheckSystem+0xeb
ffffc181`48406980 fffff801`6881695f     : 00000000`00000000 ffffc181`48406a19 ffff9903`539dc028 ffffc181`48417000 : PSHED!PshedBugCheckSystem+0x10
ffffc181`484069b0 fffff801`68723e2a     : ffff9903`4d3b8b00 ffff9903`4d3b8b00 ffff9903`4d4fc660 fffff801`685971aa : nt!WheaReportHwError+0x38f
ffffc181`48406a80 fffff801`68724280     : 00000000`0000000c ffff9903`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
ffffc181`48406bf0 fffff801`6872409a     : 00000000`0000000c 00000000`00000000 ffffc181`48406e00 00000000`00000000 : nt!HalpMceHandlerCore+0x138
ffffc181`48406c50 fffff801`687235a7     : ffff9903`4d34d900 ffffc181`48406ef0 00000000`0000000c 00000000`00000000 : nt!HalpMceHandler+0x66
ffffc181`48406c90 fffff801`68725bcb     : ffff9903`4d34d900 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x97
ffffc181`48406cc0 fffff801`68785879     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffffc181`48406cf0 fffff801`6863e03e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffc181`48406d20 fffff801`6863dc53     : 00000000`00000000 00000000`00000000 7fffffff`ffffffff ffffc181`48406ef0 : nt!KxMcheckAbort+0x7e
ffffc181`48406e60 00007ffa`e67efa6f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
0000002c`afdff080 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`e67efa6f


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

Mavi ekran gelmesı belli olmuyor boşta dururken de gelıyor oyun oynarken gelıyor sıcaklıkları izliyorum yuk altında hersey stabil gözukuyor 850 watt thermaltake butun parcalarım sıfır güc kaynagını da bu yuzden almıstım mavi ekran gelıyor dıye sonra ramları garantıye yolladım hıcbırsey cıkmadı arza yok

3060 Ti sistem mavi ekran hatası

Ayrıntılı düzenleme

Hüseyin20c

Zeptopat

EgeN7

Gigapat

ROG STRIX B550-F GAMING | ROG Strix | Gaming motherboards｜ROG - Republic of Gamers｜ROG Türkiye

Hüseyin20c

Zeptopat

ROG STRIX B550-F GAMING | ROG Strix | Gaming motherboards｜ROG - Republic of Gamers｜ROG Türkiye

Benzer konular

Technopat Haberler

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz