Windows 10 Mavi Ekran Problemi

claus dedi:

Kod:Panoya kopyala

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000000, A stack-based buffer has been overrun.
Arg2: 0000000000000000, Address of the trap frame for the exception that caused the bugcheck
Arg3: 0000000000000000, Address of the exception record for the exception that caused the bugcheck
Arg4: fffff8073c2b7540, Reserved

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 29

Key : Analysis.Elapsed.Sec
Value: 107

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


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8073c2b7540

TRAP_FRAME:  0000000000000000 -- (.trap 0x0)

EXCEPTION_RECORD:  0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000

CPU_COUNT: 4

CPU_MHZ: c78

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x139

PROCESS_NAME: System

CURRENT_IRQL: 9

ANALYSIS_SESSION_HOST: DESKTOP-I8FA0KP

ANALYSIS_SESSION_TIME: 07-30-2019 16:44:45.0060

ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

LAST_CONTROL_TRANSFER: from fffff80739a5e6eb to fffff80739a55f50

STACK_TEXT:
fffff807`3c2b6d58 fffff807`39a5e6eb : 00000000`00000139 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff807`3c2b6d60 fffff807`39a5ea5f : fffff807`39d85000 fffff807`398a2000 0005bd7c`00a71000 00000000`0010001f : nt!guard_icall_handler+0x1b
fffff807`3c2b6d90 fffff807`399b73a0 : fffff807`3c2b73e0 00000000`00000000 fffff807`3c2b7300 fffff807`3c2b7cf8 : nt!RtlpExecuteHandlerForException+0xf
fffff807`3c2b6dc0 fffff807`398c4bb4 : fffff807`3c2b7cf8 fffff807`3c2b7a40 fffff807`3c2b7cf8 fffff807`38877180 : nt!RtlDispatchException+0x430
fffff807`3c2b7510 fffff807`39a678c2 : 00000000`0039637a 00000000`0039637a 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x144
fffff807`3c2b7bc0 fffff807`39a6374b : 00000000`00000000 ffffba0f`0bd47000 ffffba0f`09ae6000 fffff807`520de90e : nt!KiExceptionDispatch+0xc2
fffff807`3c2b7da0 fffff807`39a5e7c1 : fffff807`399d52f5 ffffba0f`07a9a300 ffffba0f`13fee180 00000000`00000000 : nt!KiGeneralProtectionFault+0x30b
fffff807`3c2b7f38 fffff807`399d52f5 : ffffba0f`07a9a300 ffffba0f`13fee180 00000000`00000000 00000000`00000000 : nt!guard_dispatch_icall+0x71
fffff807`3c2b7f40 fffff807`39a576df : fffff807`3c2a8a50 ffffa781`af0628c0 00000000`00000358 ffffa781`af0628c0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`3c2b7f90 fffff807`39a579a7 : 00000000`00000001 00000000`00000000 fffff807`3c2a8b00 00000000`00000000 : nt!KiInterruptSubDispatch+0x11f
fffff807`3c2a89d0 fffff807`39a59952 : 00000000`00000000 fffff807`38877180 fffff807`39e02400 ffffba0f`14dcb080 : nt!KiInterruptDispatch+0x37
fffff807`3c2a8b60 00000000`00000000 : fffff807`3c2a9000 fffff807`3c2a2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x32


THREAD_SHA1_HASH_MOD_FUNC: 855da885ced7236a90e95874e06666318d510233

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: b9009be344253cc337fcc9eb9feeffa34d622037

THREAD_SHA1_HASH_MOD: dc844b1b94baa204d070855e43bbbd27eee98b94

FOLLOWUP_IP:
nt!guard_icall_handler+1b
fffff807`39a5e6eb 90 nop

FAULT_INSTR_CODE: ccccc390

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!guard_icall_handler+1b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5ebebfaf

IMAGE_VERSION: 10.0.17763.615

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1b

FAILURE_BUCKET_ID: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_handler

BUCKET_ID: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_handler

PRIMARY_PROBLEM_CLASS: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_handler

TARGET_TIME: 2019-07-30T06:56:14.000Z

OSBUILD: 17763

OSSERVICEPACK: 615

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: 2020-05-15 19:13:35

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 1a343

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x139_0_legacy_gs_violation_nt!guard_icall_handler

FAILURE_ID_HASH: {9ac18088-8c91-40fd-01fb-5255bc467cba}

Followup:     MachineOwner

Memtest ile RAM testi yapın.

Genişletmek için tıkla...

claus dedi:

Kod:Panoya kopyala

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 47

Key : Analysis.Elapsed.Sec
Value: 102

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


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

DUMP_TYPE: 2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff802429898d5

BUGCHECK_P3: fffff083441c66b0

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.

FAULTING_IP:
nt!KiCommitThreadWait+365
fffff802`429898d5 488b0e mov rcx,qword ptr [rsi]

CONTEXT:  fffff083441c66b0 -- (.cxr 0xfffff083441c66b0)
rax=ffffa101af808548 rbx=ffffa101a73b9140 rcx=ffffdd000170e180
rdx=0000000000000000 rsi=09ffa101af808558 rdi=ffffa101af808540
rip=fffff802429898d5 rsp=fffff083441c70a0 rbp=0000000000000000
r8=0000000000000002 r9=0000008e10ed27cf r10=fffff083441c72c0
r11=fffff083441c7760 r12=0000008e10ed27cf r13=ffffa101a73b9240
r14=ffffa101af808558 r15=ffffdd000170e180
iopl=0 nv up ei ng nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287
nt!KiCommitThreadWait+0x365:
fffff802`429898d5 488b0e mov rcx,qword ptr [rsi] ds:002b:09ffa101`af808558=????????????????
Resetting default scope

BUGCHECK_STR: 0x3B_c0000005

CPU_COUNT: 4

CPU_MHZ: c78

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: nvcontainer.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-I8FA0KP

ANALYSIS_SESSION_TIME: 08-03-2019 16:10:51.0267

ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

LAST_CONTROL_TRANSFER: from fffff80242987782 to fffff802429898d5

STACK_TEXT:
fffff083`441c70a0 fffff802`42987782 : 80000000`00000001 00000000`00000000 ffffa101`00000002 fffff083`441c71c9 : nt!KiCommitThreadWait+0x365
fffff083`441c7140 fffff802`42f0deea : 00000000`00000003 fffff083`441c72c0 ffffa101`ad18ea20 fffff083`00000006 : nt!KeWaitForMultipleObjects+0x582
fffff083`441c7210 fffff802`42f0dc07 : fffff083`441c7770 ffffb34a`7b81440b fffff083`441c7758 656d6172`00000400 : nt!ObWaitForMultipleObjects+0x2aa
fffff083`441c7710 fffff802`42a75205 : 00000000`00000000 ffffa101`a8bab290 ffffa101`a73b9140 000000b4`fd9ff188 : nt!NtWaitForMultipleObjects+0xf7
fffff083`441c7990 00007fff`115602b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000b4`fd9ff168 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`115602b4


THREAD_SHA1_HASH_MOD_FUNC: daa0e3b671f931b59a41ae5f5a3124bec6408b1f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 7d2ec9a0bfb84fc5a4a5cf80712c51e30eb04c31

THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84

FOLLOWUP_IP:
nt!KiCommitThreadWait+365
fffff802`429898d5 488b0e mov rcx,qword ptr [rsi]

FAULT_INSTR_CODE: 480e8b48

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiCommitThreadWait+365

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5ebebfaf

IMAGE_VERSION: 10.0.17763.615

STACK_COMMAND: .cxr 0xfffff083441c66b0 ; kb

BUCKET_ID_FUNC_OFFSET: 365

FAILURE_BUCKET_ID: 0x3B_c0000005_nt!KiCommitThreadWait

BUCKET_ID: 0x3B_c0000005_nt!KiCommitThreadWait

PRIMARY_PROBLEM_CLASS: 0x3B_c0000005_nt!KiCommitThreadWait

TARGET_TIME: 2019-08-03T08:29:44.000Z

OSBUILD: 17763

OSSERVICEPACK: 615

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: 2020-05-15 19:13:35

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 18ed5

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_c0000005_nt!kicommitthreadwait

FAILURE_ID_HASH: {10010607-d2ee-4419-e36c-f9cdcd8c8732}

Followup:     MachineOwner

Memtest doğru olarak yaptığına ve bitene kadar beklediğine emin misin ? Eğer eminsen RAM modelleri ve değerleri birebir aynı mı ?
Düşük ihtimal ama gene de Furmark testi yapın birde.

Genişletmek için tıkla...