5900X CLOCK_WATCHDOG_TIMEOUT (101) hatası

Recep Baltaş · 16 Kasım 2021

Sorunun işlemci kaynaklı olduğunu düşünüyorum. Göz atmak isteyenler için dökümler: Minidump

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: 0000000000000008, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd781be1ce180, The PRCB address of the hung processor.
Arg4: 0000000000000008, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3265

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 26218

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

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

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

    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:  111321-10796-01.dmp

BUGCHECK_CODE:  101

BUGCHECK_P1: 8

BUGCHECK_P2: 0

BUGCHECK_P3: ffffd781be1ce180

BUGCHECK_P4: 8

FAULTING_PROCESSOR: 8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  hamachi-2-ui.exe

STACK_TEXT: 
ffffd781`be9f1c88 fffff801`32a1f56e     : 00000000`00000101 00000000`00000008 00000000`00000000 ffffd781`be1ce180 : nt!KeBugCheckEx
ffffd781`be9f1c90 fffff801`3281c3cd     : 00000000`00000000 ffffd781`be9d7180 00000000`00200246 00000000`0032851e : nt!KeAccumulateTicks+0x2063be
ffffd781`be9f1cf0 fffff801`3281c971     : 00000000`00000000 00000000`001e1cbd ffffd781`be9d7180 00000000`00001001 : nt!KiUpdateRunTime+0x5d
ffffd781`be9f1d40 fffff801`328167e3     : ffffd781`be9d7180 00000000`00000000 fffff801`33231588 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffd781`be9f1e80 fffff801`3281f1a2     : ffffae81`423f2030 ffffae81`423f20b0 ffffae81`423f2000 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffffd781`be9f1f30 fffff801`328de055     : 00000078`73727eea ffff840c`d1ae1460 ffff840c`d1ae1510 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffd781`be9f1f60 fffff801`329f8d4a     : ffffae81`423f20b0 ffff840c`d1ae1460 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffd781`be9f1fb0 fffff801`329f92b7     : ffffae81`423f2200 fffff801`329f9344 00000000`00000001 ffffae81`423f2200 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffae81`423f2030 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


SYMBOL_NAME:  nt!KeAccumulateTicks+2063be

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1348

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  2063be

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffffffffffc08, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8004416ad39, address which referenced memory

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3390

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 29121

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

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

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

    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:  111321-8015-01.dmp

BUGCHECK_CODE:  d1

BUGCHECK_P1: fffffffffffffc08

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8004416ad39

READ_ADDRESS: fffff800310fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 fffffffffffffc08

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  java-r

DPC_STACK_BASE:  FFFFEF0646A67FB0

TRAP_FRAME:  ffffef0646a67640 -- (.trap 0xffffef0646a67640)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffcc0ef0902000 rbx=0000000000000000 rcx=ffffcc0ef0902000
rdx=ffffa300a08a7180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8004416ad39 rsp=ffffef0646a677d0 rbp=ffffcc0ef0902000
 r8=000000000000082f  r9=000000000000002f r10=0000fffff8003072
r11=ffff92fe11400000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nvlddmkm+0x80ad39:
fffff800`4416ad39 833b00          cmp     dword ptr [rbx],0 ds:00000000`00000000=????????
Resetting default scope

STACK_TEXT: 
ffffef06`46a674f8 fffff800`30809269     : 00000000`0000000a ffffffff`fffffc08 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffef06`46a67500 fffff800`30805569     : 00000000`00000000 ffffa300`a08a7180 ffffcc0e`f5de3080 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffef06`46a67640 fffff800`4416ad39     : ffffcc0e`f0903fb8 ffffcc0f`0045e260 ffffa300`a08a7180 00000000`00000000 : nt!KiPageFault+0x469
ffffef06`46a677d0 ffffcc0e`f0903fb8     : ffffcc0f`0045e260 ffffa300`a08a7180 00000000`00000000 00000000`00000000 : nvlddmkm+0x80ad39
ffffef06`46a677d8 ffffcc0f`0045e260     : ffffa300`a08a7180 00000000`00000000 00000000`00000000 00000000`00000001 : 0xffffcc0e`f0903fb8
ffffef06`46a677e0 ffffa300`a08a7180     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : 0xffffcc0f`0045e260
ffffef06`46a677e8 00000000`00000000     : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : 0xffffa300`a08a7180


SYMBOL_NAME:  nvlddmkm+80ad39

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  80ad39

FAILURE_BUCKET_ID:  AV_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup:     MachineOwner
---------

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: 0000000000000008, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffc400dcd69180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5171

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 30150

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

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

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

    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:  111221-9328-01.dmp

BUGCHECK_CODE:  101

BUGCHECK_P1: 8

BUGCHECK_P2: 0

BUGCHECK_P3: ffffc400dcd69180

BUGCHECK_P4: 2

FAULTING_PROCESSOR: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

STACK_TEXT: 
ffffc400`dd9f1c88 fffff806`2e01f56e     : 00000000`00000101 00000000`00000008 00000000`00000000 ffffc400`dcd69180 : nt!KeBugCheckEx
ffffc400`dd9f1c90 fffff806`2de1c3cd     : 00000000`00000000 ffffc400`dd9d7180 00000000`00000246 00000000`0004a9b0 : nt!KeAccumulateTicks+0x2063be
ffffc400`dd9f1cf0 fffff806`2de1c971     : 00000000`00000000 00000000`0002c77e ffffc400`dd9d7180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffc400`dd9f1d40 fffff806`2de167e3     : ffffc400`dd9d7180 00000000`00000000 fffff806`2e831558 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffc400`dd9f1e80 fffff806`2de1f1a2     : fffff887`2c2f7020 fffff887`2c2f70a0 fffff887`2c2f7000 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffffc400`dd9f1f30 fffff806`2dede055     : 0000000b`1e1afba8 ffff8004`602e3460 ffff8004`602e3510 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffc400`dd9f1f60 fffff806`2dff8d4a     : fffff887`2c2f70a0 ffff8004`602e3460 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffc400`dd9f1fb0 fffff806`2dff92b7     : fffff887`2c2f71f0 00001f80`00ff0244 00000000`134d9c69 fffff887`2c2f71f0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff887`2c2f7020 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


SYMBOL_NAME:  nt!KeAccumulateTicks+2063be

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1348

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  2063be

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------

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: 0000000000000008, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffc301ab7c0180, The PRCB address of the hung processor.
Arg4: 0000000000000008, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4186

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 42096

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

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

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

    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:  111321-10890-02.dmp

BUGCHECK_CODE:  101

BUGCHECK_P1: 8

BUGCHECK_P2: 0

BUGCHECK_P3: ffffc301ab7c0180

BUGCHECK_P4: 8

FAULTING_PROCESSOR: 8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  2

PROCESS_NAME:  node.exe

TRAP_FRAME:  ffff950d871e3468 -- (.trap 0xffff950d871e3468)
Unable to read trap frame at ffff950d`871e3468

STACK_TEXT: 
ffffc301`abfe4c88 fffff806`1e41f56e     : 00000000`00000101 00000000`00000008 00000000`00000000 ffffc301`ab7c0180 : nt!KeBugCheckEx
ffffc301`abfe4c90 fffff806`1e21c3cd     : 00000000`00000000 ffffc301`abfca180 00000000`00000246 00000000`0004ed3e : nt!KeAccumulateTicks+0x2063be
ffffc301`abfe4cf0 fffff806`1e21c971     : 00000000`00000000 00000000`0002efc2 ffffc301`abfca180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffc301`abfe4d40 fffff806`1e2167e3     : ffffc301`abfca180 00000000`00000000 fffff806`1ec31678 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffc301`abfe4e80 fffff806`1e21f1a2     : fffffa0a`c17ce530 fffffa0a`c17ce5b0 fffffa0a`c17ce500 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffffc301`abfe4f30 fffff806`1e2de055     : 0000000b`bf2b2aad ffff800b`030e3460 ffff800b`030e3510 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffc301`abfe4f60 fffff806`1e3f8d4a     : fffffa0a`c17ce5b0 ffff800b`030e3460 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffc301`abfe4fb0 fffff806`1e3f92b7     : fffffa0a`c17ce700 00001f80`003f0244 00000000`221ba31f fffffa0a`c17ce700 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffa0a`c17ce530 fffff806`1e280c6b     : 00000000`00000000 fffff806`1e33cb40 ffff950d`871e3468 ffff950d`871e3010 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffa0a`c17ce6c0 fffff806`1e33cb40     : ffff950d`871e3468 ffff950d`871e3010 ffff800b`1f68dcc8 00000000`00120089 : nt!KeYieldProcessorEx+0x1b
fffffa0a`c17ce6d0 fffff806`1e2b2dc4     : ffff800b`2224f334 00000000`000ac750 ffffb5ca`86c6ffd8 fffffa0a`c17cf1b8 : nt!MiCompareTbFlushTimeStamp+0x6c
fffffa0a`c17ce700 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFlushTbAsNeeded+0x1a4


SYMBOL_NAME:  nt!KeAccumulateTicks+2063be

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1348

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  2063be

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------

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: 0000000000000008, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffe300457d5180, The PRCB address of the hung processor.
Arg4: 0000000000000008, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4281

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 17553

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

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

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

    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:  111321-9484-01.dmp

BUGCHECK_CODE:  101

BUGCHECK_P1: 8

BUGCHECK_P2: 0

BUGCHECK_P3: ffffe300457d5180

BUGCHECK_P4: 8

FAULTING_PROCESSOR: 8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

STACK_TEXT: 
ffffe300`45679c88 fffff804`05e1f56e     : 00000000`00000101 00000000`00000008 00000000`00000000 ffffe300`457d5180 : nt!KeBugCheckEx
ffffe300`45679c90 fffff804`05c1c3cd     : 00000000`00000000 ffffe300`4565f180 00000000`00000246 00000000`00001034 : nt!KeAccumulateTicks+0x2063be
ffffe300`45679cf0 fffff804`05c1c971     : 00000000`00000e00 00000000`000009a8 ffffe300`4565f180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffe300`45679d40 fffff804`05c167e3     : ffffe300`4565f180 00000000`00000000 fffff804`06631678 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffe300`45679e80 fffff804`05c1f1a2     : ffffdd08`c199e160 ffffdd08`c199e1e0 ffffdd08`c199e100 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
ffffe300`45679f30 fffff804`05cde055     : 00000000`26c38043 ffff9284`322d9380 ffff9284`322d9430 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffe300`45679f60 fffff804`05df8d4a     : ffffdd08`c199e1e0 ffff9284`322d9380 80000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffe300`45679fb0 fffff804`05df92b7     : 00000000`24b2e0d3 ffffe300`45662088 ffffdd08`c199e291 00000000`00000003 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffdd08`c199e160 fffff804`05c3a300     : ffffa402`3cc568a8 ffffdd08`c199e4c8 00000000`00000001 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffdd08`c199e2f0 fffff804`05c1e88c     : 00000000`00000000 00000000`00000002 ffffe300`45380180 fffff804`05c86ada : nt!KiIpiSendRequestEx+0xb0
ffffdd08`c199e330 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x1bc


SYMBOL_NAME:  nt!KeAccumulateTicks+2063be

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1348

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  2063be

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------

Xantern · 16 Kasım 2021

Bence de işlemci kaynaklı.

KojiroHyuga04 · 16 Kasım 2021

OC işlemi var sanırım, işlemi geri çekin.
Bluestacks kaldırın.
Wi-Fi sürücünüzü güncelleyin.

Hamachi kaldırın.
Intel Bluetooth sürücüsünü güncelleyin.

Ayrıca NVIDIA ekran kartı sürücüsünü DDU ile kaldırıp en güncelini kurun.

Kolay gelsin hocam.

Hocam benim bir telefon sorunum var. Açtığım bir sürü konu var, yardımcı olur musunuz?

Tamino · 16 Kasım 2021

İlk öncelikle BIOS güncellemesi yapılması gerekiyor. 7C90v17 sürümüne güncellemeliyiz.

MSI MPG B550 GAMING CARBON WIFI AMD AM4 DDR4 CF M.2 USB 3.2 Gen 2 Wi-Fi 6 HDMI ATX Gaming Motherboard

Ek olarak BIOS ayarlarını default yapmalıyız. Eğer bu dediklerim işe yaramazsa CPB'yi kapatmayı denemeliyiz.

Daha sonra ekran kartı sürücüsünü ve ağ sürücüsünü güncellemeliyiz.

Olay Görüntüleyicisini de kontrol etmekte fayda var...

Recep Baltaş · 16 Kasım 2021

BIOS güncellemesini bugün yaptı. OC olduğunu sanmıyorum ama sorarım yine de.

Tamino · 18 Kasım 2021

Mavi ekranı alan arkadaş tekrar mavi ekran aldı mı acaba? Merak ettim açıkçası.

5900X CLOCK_WATCHDOG_TIMEOUT (101) hatası

Ayrıntılı düzenleme

Recep Baltaş

Technopat

Xantern

Terapat

KojiroHyuga04

Petapat

Tamino

Attopat

Recep Baltaş

Technopat

Tamino

Attopat

Benzer konular

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz