Behçet Cantürk
Kilopat
Daha fazla
- Cinsiyet
- Erkek
- Meslek
- E-Ticaret Uzmanı
- Ekran kartı
- Palit 3
- Anakart
- AMD Ryzen 5 5600
Merhaba, PC yi Game Garajdan hazır sistem olarak almıştım. 6. ayına kadar sorun yoktu fakat yaz aylar geldiğinden beri ara sıra oyun sırasında mavi ekran alıyorum.
Bazen veriyor bazen vermiyor, ama dikkat ettiğimde mavi ekran sırasında PC'nin çok ısınmış olmasıydı.
drive.google.com
******************************************************************************
* *
* 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: ffffb403d6543028, 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: 2296
Key : Analysis.Elapsed.mSec
Value: 5114
Key : Analysis.IO.Other.Mb
Value: 21
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 24
Key : Analysis.Init.CPU.mSec
Value: 155
Key : Analysis.Init.Elapsed.mSec
Value: 65859
Key : Analysis.Memory.CommitPeak.Mb
Value: 93
Key : Bugcheck.Code.LegacyAPI
Value: 0x124
Key : Failure.Bucket
Value: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys
Key : Failure.Hash
Value: {b0905187-9dbc-d607-4dc5-8630b9eddb7f}
Key : WER.OS.Branch
Value: ni_release
Key : WER.OS.Version
Value: 10.0.22621.1
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffb403d6543028
BUGCHECK_P3: bc000800
BUGCHECK_P4: 1010135
FILE_IN_CAB: 112623-5218-01.dmp
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: GH.exe
STACK_TEXT:
ffffe000`22fe6938 fffff803`0c0feccb : 00000000`00000124 00000000`00000000 ffffb403`d6543028 00000000`bc000800 : nt!KeBugCheckEx
ffffe000`22fe6940 fffff803`081810c0 : 00000000`00000000 ffffe000`22fe6a19 ffffb403`d6543028 ffffb403`d174f420 : nt!HalBugCheckSystem+0xeb
ffffe000`22fe6980 fffff803`0c20e7ff : 00000000`00000000 ffffe000`22fe6a19 ffffb403`d6543028 000010c8`85880000 : PSHED!PshedBugCheckSystem+0x10
ffffe000`22fe69b0 fffff803`0c1006fa : ffffb403`d6f03980 ffffb403`d6f03980 ffffb403`d174f470 fffff803`0bf805de : nt!WheaReportHwError+0x38f
ffffe000`22fe6a80 fffff803`0c100b50 : 00000000`0000000a ffffb403`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
ffffe000`22fe6bf0 fffff803`0c1009e4 : ffffb403`d1750780 d78bc38b`00000000 ffffe000`22fe6e00 8d8d4890`00000000 : nt!HalpMceHandlerCore+0x138
ffffe000`22fe6c50 fffff803`0c0ffe77 : ffffb403`d1750780 ffffe000`22fe6ef0 00000000`00000000 8d489000`00998be8 : nt!HalpMceHandler+0xe0
ffffe000`22fe6c90 fffff803`0c10260b : ffffb403`d1750780 e8000004`d88d8d48 8d8d4890`00009964 009957e8`00000500 : nt!HalpHandleMachineCheck+0x97
ffffe000`22fe6cc0 fffff803`0c169109 : 3de80000`05508d8d 788d8d48`90000099 00009930`e8000005 000005a0`8d8d4890 : nt!HalHandleMcheck+0x3b
ffffe000`22fe6cf0 fffff803`0c02873e : 05f08d8d`48900000 90000099`09e80000 e8000006`188d8d48 8d8d4890`000098fc : nt!KiHandleMcheck+0x9
ffffe000`22fe6d20 fffff803`0c028353 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe000`22fe6ef0 : nt!KxMcheckAbort+0x7e
ffffe000`22fe6e60 00007ffd`1b347873 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
000000db`582ffc70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`1b347873
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys
OS_VERSION: 10.0.22621.1
BUILDLAB_STR: ni_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {b0905187-9dbc-d607-4dc5-8630b9eddb7f}
Followup: MachineOwner
---------
Bazen veriyor bazen vermiyor, ama dikkat ettiğimde mavi ekran sırasında PC'nin çok ısınmış olmasıydı.
112623-5218-01.dmp
![drive.google.com](https://ssl.gstatic.com/images/branding/product/1x/drive_2020q4_32dp.png)
******************************************************************************
* *
* 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: ffffb403d6543028, 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: 2296
Key : Analysis.Elapsed.mSec
Value: 5114
Key : Analysis.IO.Other.Mb
Value: 21
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 24
Key : Analysis.Init.CPU.mSec
Value: 155
Key : Analysis.Init.Elapsed.mSec
Value: 65859
Key : Analysis.Memory.CommitPeak.Mb
Value: 93
Key : Bugcheck.Code.LegacyAPI
Value: 0x124
Key : Failure.Bucket
Value: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys
Key : Failure.Hash
Value: {b0905187-9dbc-d607-4dc5-8630b9eddb7f}
Key : WER.OS.Branch
Value: ni_release
Key : WER.OS.Version
Value: 10.0.22621.1
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffb403d6543028
BUGCHECK_P3: bc000800
BUGCHECK_P4: 1010135
FILE_IN_CAB: 112623-5218-01.dmp
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: GH.exe
STACK_TEXT:
ffffe000`22fe6938 fffff803`0c0feccb : 00000000`00000124 00000000`00000000 ffffb403`d6543028 00000000`bc000800 : nt!KeBugCheckEx
ffffe000`22fe6940 fffff803`081810c0 : 00000000`00000000 ffffe000`22fe6a19 ffffb403`d6543028 ffffb403`d174f420 : nt!HalBugCheckSystem+0xeb
ffffe000`22fe6980 fffff803`0c20e7ff : 00000000`00000000 ffffe000`22fe6a19 ffffb403`d6543028 000010c8`85880000 : PSHED!PshedBugCheckSystem+0x10
ffffe000`22fe69b0 fffff803`0c1006fa : ffffb403`d6f03980 ffffb403`d6f03980 ffffb403`d174f470 fffff803`0bf805de : nt!WheaReportHwError+0x38f
ffffe000`22fe6a80 fffff803`0c100b50 : 00000000`0000000a ffffb403`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
ffffe000`22fe6bf0 fffff803`0c1009e4 : ffffb403`d1750780 d78bc38b`00000000 ffffe000`22fe6e00 8d8d4890`00000000 : nt!HalpMceHandlerCore+0x138
ffffe000`22fe6c50 fffff803`0c0ffe77 : ffffb403`d1750780 ffffe000`22fe6ef0 00000000`00000000 8d489000`00998be8 : nt!HalpMceHandler+0xe0
ffffe000`22fe6c90 fffff803`0c10260b : ffffb403`d1750780 e8000004`d88d8d48 8d8d4890`00009964 009957e8`00000500 : nt!HalpHandleMachineCheck+0x97
ffffe000`22fe6cc0 fffff803`0c169109 : 3de80000`05508d8d 788d8d48`90000099 00009930`e8000005 000005a0`8d8d4890 : nt!HalHandleMcheck+0x3b
ffffe000`22fe6cf0 fffff803`0c02873e : 05f08d8d`48900000 90000099`09e80000 e8000006`188d8d48 8d8d4890`000098fc : nt!KiHandleMcheck+0x9
ffffe000`22fe6d20 fffff803`0c028353 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe000`22fe6ef0 : nt!KxMcheckAbort+0x7e
ffffe000`22fe6e60 00007ffd`1b347873 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
000000db`582ffc70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`1b347873
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys
OS_VERSION: 10.0.22621.1
BUILDLAB_STR: ni_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {b0905187-9dbc-d607-4dc5-8630b9eddb7f}
Followup: MachineOwner
---------
Son düzenleyen: Moderatör: