i7 6700K sistemde mavi ekran hatası

Kayagrey · 15 Mayıs 2021

Bilgisayarım bazı oyunları oynarken mavi ekran veriyor sebebini anlamadığım şekilde.

Minidump dosyalarım: Yeni klasör (4).rar

Sistem özelliklerim:

PanzerTR · 15 Mayıs 2021

İşlemciniz yüksek sıcaklıklara çıkıyor mu? Güç beslemesi yeterli mi?

İşlemcinizde bir OC işlemi varsa kaldırın.

Sorunun kaynağı işlemci gibi gözüküyor.

Kod:

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff940021040180, The PRCB address of the hung processor.
Arg4: 0000000000000006, The index of the hung processor.

Debugging Details:
------------------

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 15

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 22

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

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

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

    Key  : WER.CorruptModuleList
    Value: 1


BUGCHECK_CODE:  101

BUGCHECK_P1: 18

BUGCHECK_P2: 0

BUGCHECK_P3: ffff940021040180

BUGCHECK_P4: 6

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT:
fffff807`4347dc88 fffff807`40c3ad32     : 00000000`00000101 00000000`00000018 00000000`00000000 ffff9400`21040180 : 0xfffff807`40bf5e40
fffff807`4347dc90 00000000`00000101     : 00000000`00000018 00000000`00000000 ffff9400`21040180 00000000`00000006 : 0xfffff807`40c3ad32
fffff807`4347dc98 00000000`00000018     : 00000000`00000000 ffff9400`21040180 00000000`00000006 00000000`00000000 : 0x101
fffff807`4347dca0 00000000`00000000     : ffff9400`21040180 00000000`00000006 00000000`00000000 ffffffff`ffffff00 : 0x18


SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  CORRUPT_MODULELIST_CLOCK_WATCHDOG_TIMEOUT

OSPLATFORM_TYPE:  x64


Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Semih\AppData\Local\Temp\7zO0517D315\051521-10671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`3ae00000 PsLoadedModuleList = 0xfffff806`3ba2a1b0
Debug session time: Sat May 15 19:08:49.692 2021 (UTC + 3:00)
System Uptime: 0 days 2:55:24.347
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`3b1f6cf0 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffda01`f529b8f0=0000000000000124
6: 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
WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffc9821523b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000030005, 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                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3296

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3337

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

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

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

    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


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc9821523b028

BUGCHECK_P3: f2000000

BUGCHECK_P4: 30005

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  r5apex.exe

STACK_TEXT: 
ffffda01`f529b8e8 fffff806`3b2b450a     : 00000000`00000124 00000000`00000000 ffffc982`1523b028 00000000`f2000000 : nt!KeBugCheckEx
ffffda01`f529b8f0 fffff806`398215b0     : 00000000`00000000 ffffc982`1523b028 ffffc982`111efcf0 ffffc982`1523b028 : nt!HalBugCheckSystem+0xca
ffffda01`f529b930 fffff806`3b3b62fe     : 00000000`00000000 ffffda01`f529b9d9 ffffc982`1523b028 ffffc982`111efcf0 : PSHED!PshedBugCheckSystem+0x10
ffffda01`f529b960 fffff806`3b2b5e31     : ffffc982`15226880 ffffc982`15226880 ffffc982`111efd40 ffffc982`111efcf0 : nt!WheaReportHwError+0x46e
ffffda01`f529ba40 fffff806`3b2b61a3     : 00000000`00000006 ffffc982`111efd40 ffffc982`111efcf0 00000000`00000006 : nt!HalpMcaReportError+0xb1
ffffda01`f529bbb0 fffff806`3b2b6080     : ffffc982`10edefa0 8b484370`00000001 00000000`00000000 90ffa004`51e8204e : nt!HalpMceHandlerCore+0xef
ffffda01`f529bc00 fffff806`3b2b62d1     : 00000000`00000008 00000000`00000001 00000000`00000000 4d89ffe6`890de9c0 : nt!HalpMceHandler+0xe0
ffffda01`f529bc40 fffff806`3b2b553b     : 00000000`00000000 00000000`00000000 ffffda01`f529bed0 46e990ff`beb533e8 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffda01`f529bc70 fffff806`3b2b7d85     : ffffc982`10edefa0 e9168966`d52b4166 00009abb`fff2b901 8b44fff2`ba17e9c0 : nt!HalpHandleMachineCheck+0x5f
ffffda01`f529bca0 fffff806`3b30d619     : 24448948`004ec2e4 7c89488f`458d4830 e8202444`89482824 bbd8e990`fff43cac : nt!HalHandleMcheck+0x35
ffffda01`f529bcd0 fffff806`3b205dfa     : 4589d08b`00000001 8b202070`50b8418b 8b48001a`b24ae8cb 00c1840f`c08548f8 : nt!KiHandleMcheck+0x9
ffffda01`f529bd00 fffff806`3b205ab7     : 00000000`00000000 00000000`00000000 00000280`28381f70 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffda01`f529be40 00007ff8`80bffc7d     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
000000fa`ea95f090 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`80bffc7d


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; 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
---------

Kayagrey · 15 Mayıs 2021

PanzerTR dedi:

İşlemciniz yüksek sıcaklıklara çıkıyor mu? Güç beslemesi yeterli mi?

İşlemcinizde bir OC işlemi varsa kaldırın.

Sorunun kaynağı işlemci gibi gözüküyor.

Kod:

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an.
MP system within the allocated interval. This indicates that the specified.
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff940021040180, The PRCB address of the hung processor.
Arg4: 0000000000000006, The index of the hung processor.

Debugging Details:
------------------

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 15.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 22.

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

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

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

 Key : WER.CorruptModuleList
 Value: 1

BUGCHECK_CODE: 101.

BUGCHECK_P1: 18.

BUGCHECK_P2: 0

BUGCHECK_P3: ffff940021040180.

BUGCHECK_P4: 6

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
fffff807`4347dc88 fffff807`40c3ad32 : 00000000`00000101 00000000`00000018 00000000`00000000 ffff9400`21040180 : 0xfffff807`40bf5e40
fffff807`4347dc90 00000000`00000101 : 00000000`00000018 00000000`00000000 ffff9400`21040180 00000000`00000006 : 0xfffff807`40c3ad32
fffff807`4347dc98 00000000`00000018 : 00000000`00000000 ffff9400`21040180 00000000`00000006 00000000`00000000 : 0x101.
fffff807`4347dca0 00000000`00000000 : ffff9400`21040180 00000000`00000006 00000000`00000000 ffffffff`ffffff00 : 0x18.

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module.

IMAGE_NAME: Unknown_Image.

STACK_COMMAND: .thread ; .cxr ; kb.

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_CLOCK_WATCHDOG_TIMEOUT

OSPLATFORM_TYPE: x64.

Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64.
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Semih\AppData\Local\Temp\7zO0517D315\051521-10671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available.

************* Path validation summary **************
Response Time (ms) Location.
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64.
Product: WinNt, suite: TerminalServer SingleUserTS.
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`3ae00000 PsLoadedModuleList = 0xfffff806`3ba2a1b0
Debug session time: Sat May 15 19:08:49.692 2021 (UTC + 3:00)
System Uptime: 0 days 2:55:24.347
Loading Kernel Symbols.
...............................................................
................................................................
................................................................
........................................
Loading User Symbols.
Loading unloaded module list.
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`3b1f6cf0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffda01`f529b8f0=0000000000000124
6: 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.
WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception.
Arg2: ffffc9821523b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000030005, 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 ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 3296.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 3337.

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

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

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

 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

BUGCHECK_CODE: 124.

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc9821523b028.

BUGCHECK_P3: f2000000.

BUGCHECK_P4: 30005.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: r5apex.exe

STACK_TEXT:
ffffda01`f529b8e8 fffff806`3b2b450a : 00000000`00000124 00000000`00000000 ffffc982`1523b028 00000000`f2000000 : nt!KeBugCheckEx
ffffda01`f529b8f0 fffff806`398215b0 : 00000000`00000000 ffffc982`1523b028 ffffc982`111efcf0 ffffc982`1523b028 : nt!HalBugCheckSystem+0xca
ffffda01`f529b930 fffff806`3b3b62fe : 00000000`00000000 ffffda01`f529b9d9 ffffc982`1523b028 ffffc982`111efcf0 : PSHED!PshedBugCheckSystem+0x10
ffffda01`f529b960 fffff806`3b2b5e31 : ffffc982`15226880 ffffc982`15226880 ffffc982`111efd40 ffffc982`111efcf0 : nt!WheaReportHwError+0x46e
ffffda01`f529ba40 fffff806`3b2b61a3 : 00000000`00000006 ffffc982`111efd40 ffffc982`111efcf0 00000000`00000006 : nt!HalpMcaReportError+0xb1
ffffda01`f529bbb0 fffff806`3b2b6080 : ffffc982`10edefa0 8b484370`00000001 00000000`00000000 90ffa004`51e8204e : nt!HalpMceHandlerCore+0xef
ffffda01`f529bc00 fffff806`3b2b62d1 : 00000000`00000008 00000000`00000001 00000000`00000000 4d89ffe6`890de9c0 : nt!HalpMceHandler+0xe0
ffffda01`f529bc40 fffff806`3b2b553b : 00000000`00000000 00000000`00000000 ffffda01`f529bed0 46e990ff`beb533e8 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffda01`f529bc70 fffff806`3b2b7d85 : ffffc982`10edefa0 e9168966`d52b4166 00009abb`fff2b901 8b44fff2`ba17e9c0 : nt!HalpHandleMachineCheck+0x5f
ffffda01`f529bca0 fffff806`3b30d619 : 24448948`004ec2e4 7c89488f`458d4830 e8202444`89482824 bbd8e990`fff43cac : nt!HalHandleMcheck+0x35
ffffda01`f529bcd0 fffff806`3b205dfa : 4589d08b`00000001 8b202070`50b8418b 8b48001a`b24ae8cb 00c1840f`c08548f8 : nt!KiHandleMcheck+0x9
ffffda01`f529bd00 fffff806`3b205ab7 : 00000000`00000000 00000000`00000000 00000280`28381f70 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffda01`f529be40 00007ff8`80bffc7d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
000000fa`ea95f090 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`80bffc7d

MODULE_NAME: GenuineIntel.

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; 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.
---------

Oyun oynarken Max 75 derece gördüm. OC işlemi olup olmadığını nasıl anlayabilirim? Sadece tek oyunda mavi ekran alıyorum bu arada.

PanzerTR · 15 Mayıs 2021

Kayagrey dedi:
OC işlemi olup olmadığını nasıl anlayabilirim?

Kendinize ya da sisteme ulaşımı olan birisine sorun.

Sıcaklık ve kullanım değerlerini takip edin. Eğer yüksek sıcaklık veya değerde mavi ekran alıyorsanız sorunun kaynağı işlemcidir.

Kayagrey dedi:
Sadece tek oyunda mavi ekran alıyorum bu arada.

Hangi oyun?

Kayagrey dedi:
Oyun oynarken Max 75 derece gördüm.

Yüksek bir değer fakat aşırı yüksek sayılmaz. Sadece bu sıcaklık değerlerinde mi mavi ekran alıyorsunuz?

Kayagrey · 15 Mayıs 2021

PanzerTR dedi:
Kendinize ya da sisteme ulaşımı olan birisine sorun.

Sıcaklık ve kullanım değerlerini takip edin. Eğer yüksek sıcaklık veya değerde mavi ekran alıyorsanız sorunun kaynağı işlemcidir.

Hangi oyun?

Yüksek bir değer fakat aşırı yüksek sayılmaz. Sadece bu sıcaklık değerlerinde mi mavi ekran alıyorsunuz?

Apex Legends. Hocam bilgisayarım çok zor ısınıyor ve aniden mavi ekran alıyorum. Şimdiye kadar 3 kere aldım. Sıcaklıktan olduğunu düşünmüyorum mesela menüden menüye geçişte alıyorum oyun içinde.

PanzerTR · 15 Mayıs 2021

Kayagrey dedi:
OC işlemi olup olmadığını nasıl anlayabilirim?

Eğer önemli bir ayarınız yoksa BIOS ayarlarını sıfırlayın.

Anakart üzerindeki tüm CPU güç giriş pinleri dolu mu? Yani CPU güç beslemesi yeterli mi?

Windows arama > Güç ve uyku ayarları > Ek güç ayarları > (Sol menüden) Güç düğmelerinin yapacaklarını seçin > Şu anda kullanılamayan ayarları değiştir >Hızlı başlatma

kapatın.

Olay görüntüleyicisi raporu paylaşın.

Rehber: Olay Görüntüleyicisi Raporu Almak

Windows + R tıklayıp boşluğa eventvwr yazıp enter'a basın. Sizden istenilen*** hangi bölüm ise 1 yazılı yerden oraya sağ tıklayın. Eğer Yönetim olaylarından alacaksanız ona sağ tıklayıp resimdeki 2 olarak işaretlenmişi seçin. **İstenilen: Uygulama, Kur ve Sistem çıktılarını paylaşın. Eğer...

www.technopat.net

Kayagrey · 15 Mayıs 2021

PanzerTR dedi:
Eğer önemli bir ayarınız yoksa BIOS ayarlarını sıfırlayın.

Anakart üzerindeki tüm CPU güç giriş pinleri dolu mu? Yani CPU güç beslemesi yeterli mi?

Windows arama > Güç ve uyku ayarları > Ek güç ayarları > (Sol menüden) Güç düğmelerinin yapacaklarını seçin > Şu anda kullanılamayan ayarları değiştir >Hızlı başlatma kapatın.

Olay görüntüleyicisi raporu paylaşın.

Rehber: Olay Görüntüleyicisi Raporu Almak

Windows + R tıklayıp boşluğa eventvwr yazıp enter'a basın. Sizden istenilen*** hangi bölüm ise 1 yazılı yerden oraya sağ tıklayın. Eğer Yönetim olaylarından alacaksanız ona sağ tıklayıp resimdeki 2 olarak işaretlenmişi seçin. **İstenilen: Uygulama, Kur ve Sistem çıktılarını paylaşın. Eğer...

www.technopat.net

Hangi olayları paylaşmamı istiyorsunuz? Ve BIOS ayarlarını en son sıfırlamayı düşünüyorum.

PanzerTR · 15 Mayıs 2021

Kayagrey dedi:
Hangi olayları paylaşmamı istiyorsunuz?

Windows günlükleri kısımı altındaki raporları paylaşın.

Kayagrey dedi:
Ve BIOS ayarlarını en son sıfırlamayı düşünüyorum.

BIOS ayarlarını en son çare sıfırlarsınız o halde.

Kayagrey · 15 Mayıs 2021

Günlükler: Documents.rar
Kasanın pek içini dışını bilmediğim için size pek yardımcı olamıyorum ama uğraştığınız için teşekkür ederim.

PanzerTR · 15 Mayıs 2021

@Kayagrey

Dediğim diğer adımları uygulamayı deneyin.

Ek olarak C:\WINDOWS\MEMORY.DMP yolunu izleyin ve oradaki dosyayı sıkıştırarak atın.

Kayagrey dedi:
Kasanın pek içini dışını bilmediğim için size pek yardımcı olamıyorum.

Dosyalardan "STRIX Z270E GAMING" anakarta sahip olduğunu görüyorum.

Şu sol üstteki giriş tamamen dolu mu? Güç beslemesi için soruyorum.

i7 6700K sistemde mavi ekran hatası

Ayrıntılı düzenleme

Kayagrey

Hectopat

PanzerTR

Gigapat

Kayagrey

Hectopat

PanzerTR

Gigapat

Kayagrey

Hectopat

PanzerTR

Gigapat

Rehber: Olay Görüntüleyicisi Raporu Almak

Kayagrey

Hectopat

Rehber: Olay Görüntüleyicisi Raporu Almak

PanzerTR

Gigapat

Kayagrey

Hectopat

PanzerTR

Gigapat

Benzer konular

Technopat Haberler

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz