S.M.A.R.T Status bad. Backup and Replace Hatası

Hasan güran

Hectopat
Katılım
19 Temmuz 2017
Mesajlar
14
Yer
Ankara
Daha fazla  
Cinsiyet
Erkek
Meslek
Diş teknikeri
Arkadaşlar bilgisayarım başlarken bazen S. M. A. R. T. Status bad. Backup and replace hatası veriyor ama bazen ve kasanın üstündeki kırmızı ışık sürekli yanıyor, bazen yanıp sönüyor mavi ekran hatası da veriyor bazen özellikle oyun oynarken.
Not: Crystaldiskinfo sonucu resimdeki gibi ve ekran kartı sıcaklığım da 60 derecenin üstüne çıktıgını görmedim.

EFB64EE8-08BD-45F7-BEBD-487EBADECF4C.jpeg
image.jpg
 
Son düzenleyen: Moderatör:
IObit araçlarını kullandığın için ilk olarak temiz kurulum yap. (Format)

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

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  2011

BIOS_DATE:  10/17/2018

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  A68HM-K

BASEBOARD_VERSION:  Rev X.0x

DUMP_TYPE:  2

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80463700180

BUGCHECK_P4: 0

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT

FAULTING_PROCESSOR: 0

CPU_COUNT: 4

CPU_MHZ: c1c

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 30

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  Monitor.exe

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-ME9UFOB

ANALYSIS_SESSION_TIME:  04-17-2020 18:48:20.0458

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80467a3d7a0 to fffff804679c2360

STACK_TEXT: 
ffffc501`b8fd2b08 fffff804`67a3d7a0 : 00000000`00000101 00000000`00000030 00000000`00000000 fffff804`63700180 : nt!KeBugCheckEx
ffffc501`b8fd2b10 fffff804`678b8e2c : fffff780`00000320 ffffc501`b9420180 00000000`000118e6 00000000`000118e6 : nt!KeAccumulateTicks+0x181530
ffffc501`b8fd2b70 fffff804`6775d562 : 00000000`00000000 ffff9b01`7f9f9fb0 ffff9b01`7f9fa030 00000000`0000000c : nt!KeClockInterruptNotify+0x98c
ffffc501`b8fd2f30 fffff804`6782cc75 : 00000002`9dceab11 ffffe683`acaa4500 ffffe683`acaa45b0 ffffc49c`6c57b613 : hal!HalpTimerClockInterrupt+0xf2
ffffc501`b8fd2f60 fffff804`679c3dea : ffff9b01`7f9fa030 ffffe683`acaa4500 00000000`00000050 ffffe683`acaa4500 : nt!KiCallInterruptServiceRoutine+0xa5
ffffc501`b8fd2fb0 fffff804`679c4357 : 00000000`00000000 ffff9b01`7f9fa030 ffffe683`acaa4500 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff9b01`7f9f9fb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


THREAD_SHA1_HASH_MOD_FUNC:  5e958d63ed6cce864bfe4c595207e0e484aa7e7c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  580a054f4e3454fd73d05fa0ebc9e8902fda11a3

THREAD_SHA1_HASH_MOD:  e2266a530ca7fbace00cfa9add8dc0ac4504d759

FOLLOWUP_IP:
nt!KeAccumulateTicks+181530
fffff804`67a3d7a0 cc              int     3

FAULT_INSTR_CODE:  cb8b48cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeAccumulateTicks+181530

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.752

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  181530

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

PRIMARY_PROBLEM_CLASS:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

TARGET_TIME:  2020-04-16T13:19:36.000Z

OSBUILD:  18362

OSSERVICEPACK:  752

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  5aa

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_invalid_context_nt!keaccumulateticks

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

Followup:     MachineOwner
---------
 
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Geri
Yukarı