Çözüldü WHEA_UNCORRECTABLE_ERROR mavi ekran hatası

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

Falconer

Femtopat
Katılım
24 Ağustos 2022
Mesajlar
48
Daha fazla  
Cinsiyet
Erkek
Merhaba, durmadan bu hata koduyla mavi ekran alıyorum. Aşağıya minidump dosyamı bırakıyorum şimdiden teşekkür ederim.
 
Son düzenleyen: Moderatör:
Çözüm
Overclock yaptınız 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: ffffb987823d1028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, 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_PROCESSOR_GENERIC_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_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x18561b, File: 0x185787 - C:\ProgramData\Dbg\sym\BTHport.sys\70388B82185000\BTHport.sys

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 19140

 Key : Analysis.Elapsed.mSec
 Value: 48777

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

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

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

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

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x124

 Key : Failure.Bucket
 Value: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

 Key : Failure.Hash
 Value: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

 Key : WER.OS.Branch
 Value: vb_release

 Key : WER.OS.Version
 Value: 10.0.19041.1

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffb987823d1028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

FILE_IN_CAB: 062923-9421-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa801`9f73f908 fffff803`23cb77ba : 00000000`00000124 00000000`00000000 ffffb987`823d1028 00000000`be000000 : nt!KeBugCheckEx
ffffa801`9f73f910 fffff803`226a15b0 : 00000000`00000000 ffffb987`823d1028 ffffb987`7deb0b30 ffffb987`823d1028 : nt!HalBugCheckSystem+0xca
ffffa801`9f73f950 fffff803`23db9a9e : 00000000`00000000 ffffa801`9f73f9f9 ffffb987`823d1028 ffffb987`7deb0b30 : PSHED!PshedBugCheckSystem+0x10
ffffa801`9f73f980 fffff803`23cb90e1 : ffffb987`7dbe3070 ffffb987`7dbe3070 ffffb987`7deb0b80 ffffb987`7deb0b30 : nt!WheaReportHwError+0x46e
ffffa801`9f73fa60 fffff803`23cb9453 : 00000000`00000001 ffffb987`7deb0b80 ffffb987`7deb0b30 00000000`00000001 : nt!HalpMcaReportError+0xb1
ffffa801`9f73fbd0 fffff803`23cb9330 : ffffb987`7daf4a38 e8004024`00000001 00000000`00000000 48482454`8b483c78 : nt!HalpMceHandlerCore+0xef
ffffa801`9f73fc20 fffff803`23cb9581 : 00000000`00000008 00000000`00000001 00000000`00000000 0975d285`48402454 : nt!HalpMceHandler+0xe0
ffffa801`9f73fc60 fffff803`23cb87eb : 00000000`00000000 00000000`00000000 ffffa801`9f73fef0 8d4c0020`24648348 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffa801`9f73fc90 fffff803`23cbb035 : ffffb987`7daf4a38 8d4c0020`24648348 058d4cff`cdf0bb0d 2d158d48`ffd1e1a4 : nt!HalpHandleMachineCheck+0x5f
ffffa801`9f73fcc0 fffff803`23d10b59 : 8d48001f`12da058d 05894800`1f12630d c5058948`001f12d4 ff82d2f0`e8001f12 : nt!HalHandleMcheck+0x35
ffffa801`9f73fcf0 fffff803`23c0cbba : a286158d`48002e00 48382444`8948fffe d48fa7e8`30244c8d ccccc348`c48348ff : nt!KiHandleMcheck+0x9
ffffa801`9f73fd20 fffff803`23c0c877 : 00000000`00000000 fffff803`23c0c7ac 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffa801`9f73fe60 fffff803`5482138f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
fffff309`5042f5b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Followup: MachineOwner
---------
Overclock yaptınız 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: ffffb987823d1028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, 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_PROCESSOR_GENERIC_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_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x18561b, File: 0x185787 - C:\ProgramData\Dbg\sym\BTHport.sys\70388B82185000\BTHport.sys

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 19140

 Key : Analysis.Elapsed.mSec
 Value: 48777

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

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

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

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

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x124

 Key : Failure.Bucket
 Value: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

 Key : Failure.Hash
 Value: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

 Key : WER.OS.Branch
 Value: vb_release

 Key : WER.OS.Version
 Value: 10.0.19041.1

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffb987823d1028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

FILE_IN_CAB: 062923-9421-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa801`9f73f908 fffff803`23cb77ba : 00000000`00000124 00000000`00000000 ffffb987`823d1028 00000000`be000000 : nt!KeBugCheckEx
ffffa801`9f73f910 fffff803`226a15b0 : 00000000`00000000 ffffb987`823d1028 ffffb987`7deb0b30 ffffb987`823d1028 : nt!HalBugCheckSystem+0xca
ffffa801`9f73f950 fffff803`23db9a9e : 00000000`00000000 ffffa801`9f73f9f9 ffffb987`823d1028 ffffb987`7deb0b30 : PSHED!PshedBugCheckSystem+0x10
ffffa801`9f73f980 fffff803`23cb90e1 : ffffb987`7dbe3070 ffffb987`7dbe3070 ffffb987`7deb0b80 ffffb987`7deb0b30 : nt!WheaReportHwError+0x46e
ffffa801`9f73fa60 fffff803`23cb9453 : 00000000`00000001 ffffb987`7deb0b80 ffffb987`7deb0b30 00000000`00000001 : nt!HalpMcaReportError+0xb1
ffffa801`9f73fbd0 fffff803`23cb9330 : ffffb987`7daf4a38 e8004024`00000001 00000000`00000000 48482454`8b483c78 : nt!HalpMceHandlerCore+0xef
ffffa801`9f73fc20 fffff803`23cb9581 : 00000000`00000008 00000000`00000001 00000000`00000000 0975d285`48402454 : nt!HalpMceHandler+0xe0
ffffa801`9f73fc60 fffff803`23cb87eb : 00000000`00000000 00000000`00000000 ffffa801`9f73fef0 8d4c0020`24648348 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffa801`9f73fc90 fffff803`23cbb035 : ffffb987`7daf4a38 8d4c0020`24648348 058d4cff`cdf0bb0d 2d158d48`ffd1e1a4 : nt!HalpHandleMachineCheck+0x5f
ffffa801`9f73fcc0 fffff803`23d10b59 : 8d48001f`12da058d 05894800`1f12630d c5058948`001f12d4 ff82d2f0`e8001f12 : nt!HalHandleMcheck+0x35
ffffa801`9f73fcf0 fffff803`23c0cbba : a286158d`48002e00 48382444`8948fffe d48fa7e8`30244c8d ccccc348`c48348ff : nt!KiHandleMcheck+0x9
ffffa801`9f73fd20 fffff803`23c0c877 : 00000000`00000000 fffff803`23c0c7ac 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffa801`9f73fe60 fffff803`5482138f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
fffff309`5042f5b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Followup: MachineOwner
---------
 
Çözüm
Overclock yaptınız 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: ffffb987823d1028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, 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_PROCESSOR_GENERIC_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_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x18561b, File: 0x185787 - C:\ProgramData\Dbg\sym\BTHport.sys\70388B82185000\BTHport.sys

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 19140

 Key : Analysis.Elapsed.mSec
 Value: 48777

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

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

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

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

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x124

 Key : Failure.Bucket
 Value: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

 Key : Failure.Hash
 Value: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

 Key : WER.OS.Branch
 Value: vb_release

 Key : WER.OS.Version
 Value: 10.0.19041.1

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffb987823d1028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

FILE_IN_CAB: 062923-9421-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa801`9f73f908 fffff803`23cb77ba : 00000000`00000124 00000000`00000000 ffffb987`823d1028 00000000`be000000 : nt!KeBugCheckEx
ffffa801`9f73f910 fffff803`226a15b0 : 00000000`00000000 ffffb987`823d1028 ffffb987`7deb0b30 ffffb987`823d1028 : nt!HalBugCheckSystem+0xca
ffffa801`9f73f950 fffff803`23db9a9e : 00000000`00000000 ffffa801`9f73f9f9 ffffb987`823d1028 ffffb987`7deb0b30 : PSHED!PshedBugCheckSystem+0x10
ffffa801`9f73f980 fffff803`23cb90e1 : ffffb987`7dbe3070 ffffb987`7dbe3070 ffffb987`7deb0b80 ffffb987`7deb0b30 : nt!WheaReportHwError+0x46e
ffffa801`9f73fa60 fffff803`23cb9453 : 00000000`00000001 ffffb987`7deb0b80 ffffb987`7deb0b30 00000000`00000001 : nt!HalpMcaReportError+0xb1
ffffa801`9f73fbd0 fffff803`23cb9330 : ffffb987`7daf4a38 e8004024`00000001 00000000`00000000 48482454`8b483c78 : nt!HalpMceHandlerCore+0xef
ffffa801`9f73fc20 fffff803`23cb9581 : 00000000`00000008 00000000`00000001 00000000`00000000 0975d285`48402454 : nt!HalpMceHandler+0xe0
ffffa801`9f73fc60 fffff803`23cb87eb : 00000000`00000000 00000000`00000000 ffffa801`9f73fef0 8d4c0020`24648348 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffa801`9f73fc90 fffff803`23cbb035 : ffffb987`7daf4a38 8d4c0020`24648348 058d4cff`cdf0bb0d 2d158d48`ffd1e1a4 : nt!HalpHandleMachineCheck+0x5f
ffffa801`9f73fcc0 fffff803`23d10b59 : 8d48001f`12da058d 05894800`1f12630d c5058948`001f12d4 ff82d2f0`e8001f12 : nt!HalHandleMcheck+0x35
ffffa801`9f73fcf0 fffff803`23c0cbba : a286158d`48002e00 48382444`8948fffe d48fa7e8`30244c8d ccccc348`c48348ff : nt!KiHandleMcheck+0x9
ffffa801`9f73fd20 fffff803`23c0c877 : 00000000`00000000 fffff803`23c0c7ac 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffa801`9f73fe60 fffff803`5482138f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
fffff309`5042f5b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Followup: MachineOwner
---------
İşlemcide undervolt var bir de RAM'lerde X.M.P açık fakat RAM'lerim 3200 MHz overlock ile 2666 MHz'de çalışıyor.
 

Yeni konular

Geri
Yukarı