Berke Eren
80+
- Katılım
- 10 Kasım 2021
- Mesajlar
- 299
Dahası
- Reaksiyon skoru
- 149
- İsim
- Berke
Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\berke\Desktop\Yeni klasör\012222-13906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`0d200000 PsLoadedModuleList = 0xfffff806`0de2a2b0
Debug session time: Sat Jan 22 20:03:25.179 2022 (UTC + 3:00)
System Uptime: 0 days 0:10:03.894
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
...
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`0d5f72e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff806`1227ecd0=0000000000000124
0: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000000004, PCI Express Error
Arg2: ffffa00601e14028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for pci.sys
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2124
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 28792
Key : Analysis.Init.CPU.mSec
Value: 311
Key : Analysis.Init.Elapsed.mSec
Value: 32868
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 012222-13906-01.dmp
BUGCHECK_CODE: 124
BUGCHECK_P1: 4
BUGCHECK_P2: ffffa00601e14028
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff806`1227ecc8 fffff806`0d6b44ba : 00000000`00000124 00000000`00000004 ffffa006`01e14028 00000000`00000000 : nt!KeBugCheckEx
fffff806`1227ecd0 fffff806`0ae915b0 : 00000000`00000000 ffffa006`01e14028 ffffa006`01e314b0 ffffa006`01e14028 : nt!HalBugCheckSystem+0xca
fffff806`1227ed10 fffff806`0d7b615e : 00000000`00000000 fffff806`1227edb9 ffffa006`01e14028 ffffa006`01e314b0 : PSHED!PshedBugCheckSystem+0x10
fffff806`1227ed40 fffff806`10a936b3 : 00000000`00000001 00000000`00000001 ffffa006`01e2f4b0 ffffa006`01cb3010 : nt!WheaReportHwError+0x46e
fffff806`1227ee20 00000000`00000001 : 00000000`00000001 ffffa006`01e2f4b0 ffffa006`01cb3010 ffff886f`00000004 : pci+0x236b3
fffff806`1227ee28 00000000`00000001 : ffffa006`01e2f4b0 ffffa006`01cb3010 ffff886f`00000004 00000000`00000001 : 0x1
fffff806`1227ee30 ffffa006`01e2f4b0 : ffffa006`01cb3010 ffff886f`00000004 00000000`00000001 00000000`00000001 : 0x1
fffff806`1227ee38 ffffa006`01cb3010 : ffff886f`00000004 00000000`00000001 00000000`00000001 00000000`00000001 : 0xffffa006`01e2f4b0
fffff806`1227ee40 ffff886f`00000004 : 00000000`00000001 00000000`00000001 00000000`00000001 00000000`00001000 : 0xffffa006`01cb3010
fffff806`1227ee48 00000000`00000001 : 00000000`00000001 00000000`00000001 00000000`00001000 00000182`a6a0fee3 : 0xffff886f`00000004
fffff806`1227ee50 00000000`00000001 : 00000000`00000001 00000000`00001000 00000182`a6a0fee3 ffffa006`01cb3010 : 0x1
fffff806`1227ee58 00000000`00000001 : 00000000`00001000 00000182`a6a0fee3 ffffa006`01cb3010 fffff806`10a93ea6 : 0x1
fffff806`1227ee60 00000000`00001000 : 00000182`a6a0fee3 ffffa006`01cb3010 fffff806`10a93ea6 ffffd800`4dfe9a00 : 0x1
fffff806`1227ee68 00000182`a6a0fee3 : ffffa006`01cb3010 fffff806`10a93ea6 ffffd800`4dfe9a00 fffff806`1227eec0 : 0x1000
fffff806`1227ee70 ffffa006`01cb3010 : fffff806`10a93ea6 ffffd800`4dfe9a00 fffff806`1227eec0 ffffd800`4dfe9ab0 : 0x00000182`a6a0fee3
fffff806`1227ee78 fffff806`10a93ea6 : ffffd800`4dfe9a00 fffff806`1227eec0 ffffd800`4dfe9ab0 00000000`00000000 : 0xffffa006`01cb3010
fffff806`1227ee80 ffffd800`4dfe9a00 : fffff806`1227eec0 ffffd800`4dfe9ab0 00000000`00000000 ffffa006`009f97b8 : pci+0x23ea6
fffff806`1227ee88 fffff806`1227eec0 : ffffd800`4dfe9ab0 00000000`00000000 ffffa006`009f97b8 fffff806`0d4f405f : 0xffffd800`4dfe9a00
fffff806`1227ee90 ffffd800`4dfe9ab0 : 00000000`00000000 ffffa006`009f97b8 fffff806`0d4f405f 00000000`01000000 : 0xfffff806`1227eec0
fffff806`1227ee98 00000000`00000000 : ffffa006`009f97b8 fffff806`0d4f405f 00000000`01000000 ffffa006`009f9000 : 0xffffd800`4dfe9ab0
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_4_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {3ac2a448-0f1c-be1d-61a6-2c69263f9152}
Followup: MachineOwner
---------
Minidump dosyasında bu şekilde bi hata kodu var. Sanırım işlemciyle alakalı bi sorun ama emin olmak için buraya da sormak istedim bilgisi olan bilgilendirebilir mi?
sistem bilgisi:
3050 Tİ ekran kartı- i5 11400h işlemci
Ram testi , ssd testi yaptım onlarda bi sıkıntı yok.
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\berke\Desktop\Yeni klasör\012222-13906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`0d200000 PsLoadedModuleList = 0xfffff806`0de2a2b0
Debug session time: Sat Jan 22 20:03:25.179 2022 (UTC + 3:00)
System Uptime: 0 days 0:10:03.894
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
...
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`0d5f72e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff806`1227ecd0=0000000000000124
0: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000000004, PCI Express Error
Arg2: ffffa00601e14028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for pci.sys
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2124
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 28792
Key : Analysis.Init.CPU.mSec
Value: 311
Key : Analysis.Init.Elapsed.mSec
Value: 32868
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 012222-13906-01.dmp
BUGCHECK_CODE: 124
BUGCHECK_P1: 4
BUGCHECK_P2: ffffa00601e14028
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff806`1227ecc8 fffff806`0d6b44ba : 00000000`00000124 00000000`00000004 ffffa006`01e14028 00000000`00000000 : nt!KeBugCheckEx
fffff806`1227ecd0 fffff806`0ae915b0 : 00000000`00000000 ffffa006`01e14028 ffffa006`01e314b0 ffffa006`01e14028 : nt!HalBugCheckSystem+0xca
fffff806`1227ed10 fffff806`0d7b615e : 00000000`00000000 fffff806`1227edb9 ffffa006`01e14028 ffffa006`01e314b0 : PSHED!PshedBugCheckSystem+0x10
fffff806`1227ed40 fffff806`10a936b3 : 00000000`00000001 00000000`00000001 ffffa006`01e2f4b0 ffffa006`01cb3010 : nt!WheaReportHwError+0x46e
fffff806`1227ee20 00000000`00000001 : 00000000`00000001 ffffa006`01e2f4b0 ffffa006`01cb3010 ffff886f`00000004 : pci+0x236b3
fffff806`1227ee28 00000000`00000001 : ffffa006`01e2f4b0 ffffa006`01cb3010 ffff886f`00000004 00000000`00000001 : 0x1
fffff806`1227ee30 ffffa006`01e2f4b0 : ffffa006`01cb3010 ffff886f`00000004 00000000`00000001 00000000`00000001 : 0x1
fffff806`1227ee38 ffffa006`01cb3010 : ffff886f`00000004 00000000`00000001 00000000`00000001 00000000`00000001 : 0xffffa006`01e2f4b0
fffff806`1227ee40 ffff886f`00000004 : 00000000`00000001 00000000`00000001 00000000`00000001 00000000`00001000 : 0xffffa006`01cb3010
fffff806`1227ee48 00000000`00000001 : 00000000`00000001 00000000`00000001 00000000`00001000 00000182`a6a0fee3 : 0xffff886f`00000004
fffff806`1227ee50 00000000`00000001 : 00000000`00000001 00000000`00001000 00000182`a6a0fee3 ffffa006`01cb3010 : 0x1
fffff806`1227ee58 00000000`00000001 : 00000000`00001000 00000182`a6a0fee3 ffffa006`01cb3010 fffff806`10a93ea6 : 0x1
fffff806`1227ee60 00000000`00001000 : 00000182`a6a0fee3 ffffa006`01cb3010 fffff806`10a93ea6 ffffd800`4dfe9a00 : 0x1
fffff806`1227ee68 00000182`a6a0fee3 : ffffa006`01cb3010 fffff806`10a93ea6 ffffd800`4dfe9a00 fffff806`1227eec0 : 0x1000
fffff806`1227ee70 ffffa006`01cb3010 : fffff806`10a93ea6 ffffd800`4dfe9a00 fffff806`1227eec0 ffffd800`4dfe9ab0 : 0x00000182`a6a0fee3
fffff806`1227ee78 fffff806`10a93ea6 : ffffd800`4dfe9a00 fffff806`1227eec0 ffffd800`4dfe9ab0 00000000`00000000 : 0xffffa006`01cb3010
fffff806`1227ee80 ffffd800`4dfe9a00 : fffff806`1227eec0 ffffd800`4dfe9ab0 00000000`00000000 ffffa006`009f97b8 : pci+0x23ea6
fffff806`1227ee88 fffff806`1227eec0 : ffffd800`4dfe9ab0 00000000`00000000 ffffa006`009f97b8 fffff806`0d4f405f : 0xffffd800`4dfe9a00
fffff806`1227ee90 ffffd800`4dfe9ab0 : 00000000`00000000 ffffa006`009f97b8 fffff806`0d4f405f 00000000`01000000 : 0xfffff806`1227eec0
fffff806`1227ee98 00000000`00000000 : ffffa006`009f97b8 fffff806`0d4f405f 00000000`01000000 ffffa006`009f9000 : 0xffffd800`4dfe9ab0
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_4_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {3ac2a448-0f1c-be1d-61a6-2c69263f9152}
Followup: MachineOwner
---------
Minidump dosyasında bu şekilde bi hata kodu var. Sanırım işlemciyle alakalı bi sorun ama emin olmak için buraya da sormak istedim bilgisi olan bilgilendirebilir mi?
sistem bilgisi:
3050 Tİ ekran kartı- i5 11400h işlemci
Ram testi , ssd testi yaptım onlarda bi sıkıntı yok.
