Çözüldü KERNEL_DATA_INPAGE_ERROR mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
Katılım
21 Temmuz 2017
Mesajlar
1.826
Çözümler
14
Yer
Gensokyo
Daha fazla  
Cinsiyet
Erkek
Bilgisayarım her türlü yükte mavi ekran veriyor. Verdiği hata her zaman değişiyor.
Aldıklarımdan bazıları;
  • KERNEL_SECURITY_CHECK_FAILURE
  • IRQL_NOT_LESS_OR_EQUAL
  • SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Acaba yardım edebilir misiniz?

Minidump:

Memtest86 raporu:

Sistem özellikleri:
  • Asrock A320M HDV R4.0
  • Ryzen 3 2200G
  • Corsair Vengeance LPX 1X8GB
  • FSP Hyper K 500W
 
Depolama birimi hataları.

Sisteme takılı tüm depolama birimlerinin Error Scan ve Health sonuçlarını paylaş, ayrıca takılı kabloları kontrol et yedek varsa değiştir.
Kod:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000006, Exception code that caused the bugcheck
Arg2: fffff8077fa8e922, Address of the instruction which caused the bugcheck
Arg3: fffffe8ea1394cc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

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

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_PRODUCT_NAME:  To Be Filled By O.E.M.

SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  To Be Filled By O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  P2.30

BIOS_DATE:  06/26/2019

BASEBOARD_MANUFACTURER:  ASRock

BASEBOARD_PRODUCT:  A320M-HDV R4.0

BASEBOARD_VERSION:                    

DUMP_TYPE:  2

BUGCHECK_P1: c0000006

BUGCHECK_P2: fffff8077fa8e922

BUGCHECK_P3: fffffe8ea1394cc0

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - <Unable to get error code text>

FAULTING_IP:
nt!HvpGetCellPaged+a2
fffff807`7fa8e922 418b02          mov     eax,dword ptr [r10]

CONTEXT:  fffffe8ea1394cc0 -- (.cxr 0xfffffe8ea1394cc0)
rax=0000000000000000 rbx=fffffe8ea13956f0 rcx=0000000000000007
rdx=00000000001cbde0 rsi=0000000000000043 rdi=ffff800aab4c7000
rip=fffff8077fa8e922 rsp=fffffe8ea13956b8 rbp=0000000000000193
r8=000000000000001c  r9=ffffc582faf17080 r10=000001cb3d10cde0
r11=0000000000000de0 r12=fffffe8ea1395920 r13=00000000000001cd
r14=000001cb3d4f17b8 r15=ffff800aab4c7000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
nt!HvpGetCellPaged+0xa2:
fffff807`7fa8e922 418b02          mov     eax,dword ptr [r10] ds:002b:000001cb`3d10cde0=????????
Resetting default scope

BUGCHECK_STR:  0x3B_c0000006

CPU_COUNT: 4

CPU_MHZ: dac

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 11

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  Registry

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-03-2020 20:43:54.0957

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff8077f9f5624 to fffff8077fa8e922

STACK_TEXT:
fffffe8e`a13956b8 fffff807`7f9f5624 : 000001cb`3cfd5ce9 00000000`00000000 ffffc582`faf173a0 fffff807`7f439ddd : nt!HvpGetCellPaged+0xa2
fffffe8e`a13956c0 fffff807`7f9f3e24 : fffffe8e`a13957f9 000001cb`3d4f116c ffff800a`c7931ec0 ffff800a`00000000 : nt!CmpFindNameInListWithStatus+0xd4
fffffe8e`a1395750 fffff807`7f9f45de : 00000000`00000022 00000000`00000000 00000000`00000000 00007fff`957b0760 : nt!CmQueryValueKey+0x144
fffffe8e`a1395850 fffff807`7f5d2d18 : 00000000`081ce298 00000000`00000003 00000000`00000000 00000000`00000001 : nt!NtQueryValueKey+0x4ee
fffffe8e`a1395a90 00007fff`982dc3a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`081cec88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`982dc3a4


THREAD_SHA1_HASH_MOD_FUNC:  3bb86d2080561fd5244ef534d6e04cb007d61f41

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  b2a0d06ac2fffbb17fd236440aca3152d29598c4

THREAD_SHA1_HASH_MOD:  f08ac56120cad14894587db086f77ce277bfae84

FOLLOWUP_IP:
nt!HvpGetCellPaged+a2
fffff807`7fa8e922 418b02          mov     eax,dword ptr [r10]

FAULT_INSTR_CODE:  41028b41

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!HvpGetCellPaged+a2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f6eba0

IMAGE_VERSION:  10.0.18362.592

STACK_COMMAND:  .cxr 0xfffffe8ea1394cc0 ; kb

BUCKET_ID_FUNC_OFFSET:  a2

FAILURE_BUCKET_ID:  0x3B_c0000006_nt!HvpGetCellPaged

BUCKET_ID:  0x3B_c0000006_nt!HvpGetCellPaged

PRIMARY_PROBLEM_CLASS:  0x3B_c0000006_nt!HvpGetCellPaged

TARGET_TIME:  2020-01-24T08:42:14.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-08-22 03:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME:  3860

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_c0000006_nt!hvpgetcellpaged

FAILURE_ID_HASH:  {68f3db38-ae8e-4bae-c37a-85819946495f}

Followup:     MachineOwner
---------
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: ffff968432aa66c0, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

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

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_PRODUCT_NAME:  To Be Filled By O.E.M.

SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  To Be Filled By O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  P2.30

BIOS_DATE:  06/26/2019

BASEBOARD_MANUFACTURER:  ASRock

BASEBOARD_PRODUCT:  A320M-HDV R4.0

BASEBOARD_VERSION:                    

DUMP_TYPE:  2

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffff968432aa66c0

BUGCHECK_P4: 0

ERROR_CODE: (NTSTATUS) 0xc000000e - <Unable to get error code text>

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

CPU_COUNT: 4

CPU_MHZ: dac

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 11

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-03-2020 20:43:57.0222

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff8054a215485 to fffff8054a1c14e0

STACK_TEXT:
ffffd38a`e61e7408 fffff805`4a215485 : 00000000`0000007a 00000000`00000020 ffffffff`c000000e ffff9684`32aa66c0 : nt!KeBugCheckEx
ffffd38a`e61e7410 fffff805`4a1323fb : 00000000`00000000 ffffd38a`c000000e fffff805`00000000 00000000`00100000 : nt!MiWriteComplete+0x18ffb5
ffffd38a`e61e74c0 fffff805`4a03e26d : ffff9684`32aa7080 ffff9684`32853918 00010000`00000000 00000002`4a468940 : nt!IopCompletePageWrite+0x4b
ffffd38a`e61e74f0 fffff805`4a1c5822 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000002 : nt!KiDeliverApc+0x19d
ffffd38a`e61e75b0 fffff805`4a064855 : 00000000`000b24a7 00000000`000b24a7 00000000`0014d624 ffff9684`32a4fa90 : nt!KiApcInterrupt+0x2f2
ffffd38a`e61e7740 fffff805`4a1492fa : 000b24a7`00000084 ffffd38a`e61e7889 00000000`00000000 00000000`0014d624 : nt!MiReleasePageFileInfo+0x135
ffffd38a`e61e77b0 fffff805`4a149cf8 : ffff9684`32aad010 ffffd38a`00000001 00000000`0014d625 fffff805`00000000 : nt!MiStoreWriteModifiedPages+0x432
ffffd38a`e61e78f0 fffff805`4a19085a : ffff9684`32aad010 00000000`00000100 fffff805`000b250f 00000000`00000100 : nt!MiGatherPagefilePages+0x44c
ffffd38a`e61e79f0 fffff805`4a12a7a5 : ffff9684`32aa7080 ffff9684`32aa7080 00000000`00000080 fffff805`4a190600 : nt!MiModifiedPageWriter+0x25a
ffffd38a`e61e7c10 fffff805`4a1c8b2a : fffff805`45fda180 ffff9684`32aa7080 fffff805`4a12a750 dadc66fd`8c7b3827 : nt!PspSystemThreadStartup+0x55
ffffd38a`e61e7c60 00000000`00000000 : ffffd38a`e61e8000 ffffd38a`e61e2000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC:  40e67fa8bc05641f7eef2a732e4b6dcf3ef3544b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  f9ec3d997861dc57956688758b29700943ab5179

THREAD_SHA1_HASH_MOD:  b28610981796779b4ac02f58898fde25728a775c

FOLLOWUP_IP:
nt!MiWriteComplete+18ffb5
fffff805`4a215485 cc              int     3

FAULT_INSTR_CODE:  458b41cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiWriteComplete+18ffb5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4f6eba0

IMAGE_VERSION:  10.0.18362.592

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  18ffb5

FAILURE_BUCKET_ID:  0x7a_c000000e_nt!MiWriteComplete

BUCKET_ID:  0x7a_c000000e_nt!MiWriteComplete

PRIMARY_PROBLEM_CLASS:  0x7a_c000000e_nt!MiWriteComplete

TARGET_TIME:  2020-02-01T20:13:01.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-08-22 03:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME:  1d7f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7a_c000000e_nt!miwritecomplete

FAILURE_ID_HASH:  {fcc12098-ee04-35bd-5cea-593a2c6ec31d}

Followup:     MachineOwner
---------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000006, Exception code that caused the bugcheck
Arg2: fffff8066f08e922, Address of the instruction which caused the bugcheck
Arg3: ffffb488b51a24f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

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

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_PRODUCT_NAME:  To Be Filled By O.E.M.

SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  To Be Filled By O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  P2.30

BIOS_DATE:  06/26/2019

BASEBOARD_MANUFACTURER:  ASRock

BASEBOARD_PRODUCT:  A320M-HDV R4.0

BASEBOARD_VERSION:                    

DUMP_TYPE:  2

BUGCHECK_P1: c0000006

BUGCHECK_P2: fffff8066f08e922

BUGCHECK_P3: ffffb488b51a24f0

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - <Unable to get error code text>

FAULTING_IP:
nt!HvpGetCellPaged+a2
fffff806`6f08e922 418b02          mov     eax,dword ptr [r10]

CONTEXT:  ffffb488b51a24f0 -- (.cxr 0xffffb488b51a24f0)
rax=0000000000000000 rbx=ffffb488b51a2f40 rcx=0000000000000007
rdx=00000000016f7f68 rsi=0000000000000341 rdi=ffffb78513571000
rip=fffff8066f08e922 rsp=ffffb488b51a2ee8 rbp=ffffb78513571000
r8=000000000000001c  r9=ffff9183135ea0c0 r10=0000027409a98f68
r11=0000000000000f68 r12=00000000ce4cf905 r13=ffffb488b51a31a0
r14=0000000000000341 r15=00000274099bd024
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
nt!HvpGetCellPaged+0xa2:
fffff806`6f08e922 418b02          mov     eax,dword ptr [r10] ds:002b:00000274`09a98f68=????????
Resetting default scope

BUGCHECK_STR:  0x3B_c0000006

CPU_COUNT: 4

CPU_MHZ: dac

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 11

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  Registry

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-03-2020 20:44:01.0596

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff8066f02979f to fffff8066f08e922

STACK_TEXT:
ffffb488`b51a2ee8 fffff806`6f02979f : 00000000`7f147a21 ffffb488`b51a3270 ffff9183`135ea0c0 ffffb785`1d343c10 : nt!HvpGetCellPaged+0xa2
ffffb488`b51a2ef0 fffff806`6f028099 : 00000001`ffffffff 00000000`ce4cf905 ffffb785`00000001 ffffb785`1d343be0 : nt!CmpDoCompareKeyName+0x2f
ffffb488`b51a2f40 fffff806`6eff226a : ffffb785`1d343be0 00000000`00000006 ffffb488`b51a3138 ffffb488`b51a31c0 : nt!CmpWalkOneLevel+0x709
ffffb488`b51a3050 fffff806`6efef2d4 : ffffb488`0000001c ffffb488`b51a33a0 ffffb488`b51a3368 00000000`00000000 : nt!CmpDoParseKey+0x9fa
ffffb488`b51a32f0 fffff806`6efed1bf : ffff9183`189c29a0 ffffb785`2631a701 00000000`00000000 00000000`00000001 : nt!CmpParseKey+0x274
ffffb488`b51a3510 fffff806`6efeb621 : ffff9183`189c2900 ffffb488`b51a3758 ffff9183`00000040 ffff9183`0a6f6980 : nt!ObpLookupObjectName+0x78f
ffffb488`b51a36d0 fffff806`6eff4b3c : 00000000`00000001 00000000`00000000 00000000`00000000 ffff9183`0a6f6980 : nt!ObOpenObjectByNameEx+0x201
ffffb488`b51a3810 fffff806`6eff49bd : 0000007f`2a8fe660 ffffb488`b51a3b80 00000000`00000001 00000000`00000000 : nt!ObOpenObjectByName+0x5c
ffffb488`b51a3860 fffff806`6eff69df : 00000000`00000000 000001aa`8ea90970 00000000`00000000 000001aa`8ea9a158 : nt!CmOpenKey+0x29d
ffffb488`b51a3ac0 fffff806`6ebd2d18 : 00000000`00000000 ffffb488`b51a3b80 ffffb488`b51a3b80 000001aa`8fece100 : nt!NtOpenKeyEx+0xf
ffffb488`b51a3b00 00007ffe`b763e414 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000007f`2a8fe588 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`b763e414


THREAD_SHA1_HASH_MOD_FUNC:  c60f19c144f9d7dd390ce35adb8e8dcc06aff971

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d82e865cfa12e23bdd842357f7d98796f05fcb05

THREAD_SHA1_HASH_MOD:  b28610981796779b4ac02f58898fde25728a775c

FOLLOWUP_IP:
nt!HvpGetCellPaged+a2
fffff806`6f08e922 418b02          mov     eax,dword ptr [r10]

FAULT_INSTR_CODE:  41028b41

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!HvpGetCellPaged+a2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f6eba0

IMAGE_VERSION:  10.0.18362.592

STACK_COMMAND:  .cxr 0xffffb488b51a24f0 ; kb

BUCKET_ID_FUNC_OFFSET:  a2

FAILURE_BUCKET_ID:  0x3B_c0000006_nt!HvpGetCellPaged

BUCKET_ID:  0x3B_c0000006_nt!HvpGetCellPaged

PRIMARY_PROBLEM_CLASS:  0x3B_c0000006_nt!HvpGetCellPaged

TARGET_TIME:  2020-02-03T14:30:24.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-08-22 03:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME:  4bdc

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_c0000006_nt!hvpgetcellpaged

FAILURE_ID_HASH:  {68f3db38-ae8e-4bae-c37a-85819946495f}

Followup:     MachineOwner
---------
 
Kabloların hepsi yeni. Sıkıntılı olduklarını sanmıyorum.
HD Tune Pro: ADATA SU650 Health

ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 100 100 50 0 ok
(05) Retired Block Count 100 100 50 0 ok
(09) Power On Hours Count 100 100 50 2269 ok
(0C) Power Cycle Count 100 100 50 375 ok
(A0) Unknown Attribute 100 100 50 0 ok
(A1) Unknown Attribute 100 100 50 100 ok
(A3) Unknown Attribute 100 100 50 5 ok
(A4) Unknown Attribute 100 100 50 241414 ok
(A5) Unknown Attribute 100 100 50 1473 ok
(A6) Unknown Attribute 100 100 50 7 ok
(A7) Unknown Attribute 100 100 50 170 ok
(A8) Unknown Attribute 100 100 50 5050 ok
(A9) Unknown Attribute 100 100 50 97 ok
(AF) Unknown Attribute 100 100 50 0 ok
(B0) Unknown Attribute 100 100 50 0 ok
(B1) Wear Range Delta 100 100 50 0 ok
(B2) Used Reserved Block Count 100 100 50 0 ok
(B5) Program Fail Count 100 100 50 0 ok
(B6) Erase Fail Count 100 100 50 0 ok
(C0) Unsafe Shutdown Count 100 100 50 82 ok
(C2) Temperature 100 100 50 37 ok
(C3) Hardware ECC Recovered 100 100 50 0 ok
(C4) Reallocated Event Count 100 100 50 0 ok
(C5) Current Pending Sector 100 100 50 0 ok
(C6) Offline Uncorrectable 100 100 50 0 ok
(C7) Interface CRC Error Count 100 100 50 0 ok
(E8) Available Reserved Space 100 100 50 100 ok
(F1) LifeTime Writes 100 100 50 125008 ok
(F2) LifeTime Reads 100 100 50 247413 ok
(F5) Unknown Attribute 100 100 50 159520 ok

Health Status : ok

HD Tune Pro: ADATA SU650 Error Scan

Scanned data : 119 gB
Damaged Blocks : 0.0 %
Elapsed Time : 5:03
Boot Drive
HD Tune Pro: WDC WD800BD-22LRA0 Health

ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 200 200 51 0 ok
(03) Spin Up Time 167 165 21 2633 ok
(04) Start/Stop Count 98 98 0 2067 ok
(05) Reallocated Sector Count 200 200 140 0 ok
(07) Seek Error Rate 200 200 51 0 ok
(09) Power On Hours Count 96 96 0 2934 ok
(0A) Spin Retry Count 100 100 51 0 ok
(0B) Calibration Retry Count 100 100 51 0 ok
(0C) Power Cycle Count 100 100 0 828 ok
(BE) Airflow Temperature 75 54 45 25 ok
(C2) Temperature 118 97 0 25 ok
(C4) Reallocated Event Count 200 200 0 0 ok
(C5) Current Pending Sector 200 200 0 0 ok
(C6) Offline Uncorrectable 200 200 0 0 ok
(C7) Interface CRC Error Count 200 200 0 1 attention
(C8) Write Error Rate 200 200 51 0 ok

Health Status : ok


HD Tune Pro: WDC WD800BD-22LRA0 Error Scan

Scanned data : 79 gB
Damaged Blocks : 0.0 %
Elapsed Time : 26:19
İçinde dokunmadığım dosyalar var. Çoğunlukla kullanmıyorum
HD Tune Pro: WDC WD5000LPVX-22V0TT0 Health

ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 200 200 51 0 ok
(03) Spin Up Time 152 148 21 1358 ok
(04) Start/Stop Count 76 76 0 24897 ok
(05) Reallocated Sector Count 200 200 140 0 ok
(07) Seek Error Rate 200 200 0 0 ok
(09) Power On Hours Count 95 95 0 3880 ok
(0A) Spin Retry Count 100 100 0 0 ok
(0B) Calibration Retry Count 100 100 0 0 ok
(0C) Power Cycle Count 100 100 0 776 ok
(BF) G-sense Error Rate 56 56 0 44 ok
(C0) Unsafe Shutdown Count 200 200 0 166 ok
(C1) Load Cycle Count 184 184 0 48065 ok
(C2) Temperature 118 92 0 25 ok
(C4) Reallocated Event Count 200 200 0 0 ok
(C5) Current Pending Sector 200 200 0 0 ok
(C6) Offline Uncorrectable 100 253 0 0 ok
(C7) Interface CRC Error Count 200 200 0 0 ok
(C8) Write Error Rate 100 253 0 0 ok

Health Status : ok
Oyunların olduğu harddisk.

WD Blue'nun error scanı 2 saat sürer gibi geliyor. Bitince onu da postlayacağım. Quick scan'ı sorunsuz çıktı.
 
WD Blue 500GB sonuçları
 

Dosya Ekleri

  • 03-_ubat-2020_23-41.png
    03-_ubat-2020_23-41.png
    39,1 KB · Görüntüleme: 44
Aylar sonra problemi çözdüm. Problem, soğutucunun, bir köşesinde çok sıkı vidalanmasından dolayı bazı pinleri bükmesiymiş.
Bugün yeni anakart aldık ve işlemciyi yeni anakarta takarken sokete oturmadı. Üzerindeki 2-3 pinin yamuk olduğunu gördük. Pinleri maket bıçağı ile düzelttik ve soğutucuyu takarken daha dikkatli davrandık. Şu an sistem çok daha stabil çalışıyor.
 
Son düzenleme:
Uyarı! Bu konu 6 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.

Bu konuyu görüntüleyen kullanıcılar

Technopat Haberler

Geri
Yukarı