Son kullanma tarihi geçmiş, bayatlamış bir tarayıcı kullanıyorsanız, Mercedes kullanmak yerine tosbağaya binmek gibi... Web sitelerini düzgün görüntüleyemiyorsanız eh, bi' zahmet tarayıcınızı güncelleyiniz. Modern Web standartlarını karşılayan bir tarayıcı alternatifine göz atın.
Çözüldü5950X ve RTX 4080 sistem video izlerken mavi ekran veriyor
Bir arkadaşım sürekli mavi ekran hatası ile karşılaşıyor. Minidump dosyasını paylaşıyorum. Yorumlarınızı bekliyorum. https://drive.google.com/file/d/1k9Xt4NDN5lUJni3jen0Z8dv2ipLFhIka/view?usp=sharing
www.technopat.net
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
---------
* 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.
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ı
* 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.
*******************************************************************************
* *
* 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
---------
* 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.
* 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.
*******************************************************************************
* *
* 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
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?
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?
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?
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?