Arama butonu
Bu konudaki kullanıcılar: 1 misafir, 1 mobil kullanıcı
18
Cevap
1092
Tıklama
0
Öne Çıkarma
sürekli mavi ekran hatası alıyorum minidump dosyalarını okuyabilen varmı
R
9 yıl
Teğmen
Konu Sahibi

arkadaşlar son günlerden sürekli mavi ekran hatası alıyorum herhangi bir işlem yapmazken bile bilgisayar kapanıyor
son minidump dosyasını açılmış halini buraya kopyalıyorum yardımcı olursanız sevinirim
delirtmek üzere bu hata


not : bugün 2 defa daha mavi ekran yedim. raporları ilk raporun altına ekledim lütfen biri bana yardım etsin




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


Loading Dump File [C:\Windows\Minidump\072116-11031-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.494.amd64fre.th2_release_sec.160630-1736
Machine Name:
Kernel base = 0xfffff801`83005000 PsLoadedModuleList = 0xfffff801`832e2cf0
Debug session time: Thu Jul 21 14:10:22.301 2016 (UTC + 3:00)
System Uptime: 0 days 20:36:20.963
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
...............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffe021ac336158, 2, 0, fffff801830e0219}

Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+f9 )

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

6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffe021ac336158, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff801830e0219, address which referenced memory

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.494.amd64fre.th2_release_sec.160630-1736

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: ffffe021ac336158

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff801830e0219

READ_ADDRESS: fffff80183382520: Unable to get MiVisibleState
ffffe021ac336158

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRestoreTransitionPte+f9
fffff801`830e0219 488b09 mov rcx,qword ptr [rcx]

CPU_COUNT: 8

CPU_MHZ: dac

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST:

ANALYSIS_SESSION_TIME: 07-21-2016 14:19:02.0551

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

TRAP_FRAME: ffffd000205db870 -- (.trap 0xffffd000205db870)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000020 rbx=0000000000000000 rcx=ffffe021ac336158
rdx=ffffe021ac336158 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801830e0219 rsp=ffffd000205dba00 rbp=0000000000000000
r8=0000000000000003 r9=0000000000000000 r10=0000000080000000
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MiRestoreTransitionPte+0xf9:
fffff801`830e0219 488b09 mov rcx,qword ptr [rcx] ds:ffffe021`ac336158=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff801831524e9 to fffff80183147940

STACK_TEXT:
ffffd000`205db728 fffff801`831524e9 : 00000000`0000000a ffffe021`ac336158 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`205db730 fffff801`83150cc7 : fffff801`83301100 00000001`00000001 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffffd000`205db870 fffff801`830e0219 : fffffa80`0b5c94a0 00000000`00000000 00000000`00000001 fffffa80`01365450 : nt!KiPageFault+0x247
ffffd000`205dba00 fffff801`83107374 : fffffa80`0b5c94a0 00000000`00000000 00000000`003c986e fffff801`83301488 : nt!MiRestoreTransitionPte+0xf9
ffffd000`205dba80 fffff801`831e3ab4 : 0000000f`ffffffff 00000000`00000000 00000580`00000000 00000000`00000001 : nt!MiRemoveLowestPriorityStandbyPage+0x184
ffffd000`205dbb10 fffff801`830d7359 : fffffd80`00003d10 ffffe003`fee09300 fffff801`831e3a28 fffff801`833020a8 : nt!MiRebalanceZeroFreeLists+0x8c
ffffd000`205dbb80 fffff801`8304ba45 : 00000000`00000000 00000000`00000080 ffffe001`ab0a1040 ffffe003`fee09300 : nt!ExpWorkerThread+0xe9
ffffd000`205dbc10 fffff801`8314cae6 : ffffd000`20bc0180 ffffe003`fee09300 fffff801`8304ba04 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffd000`205dbc60 00000000`00000000 : ffffd000`205dc000 ffffd000`205d6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: afc99d74fabb790594359c77fc25cd274dfbcd2f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ae6ac87160f203a938d667924c482cbf96bff796

THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe

FOLLOWUP_IP:
nt!MiRestoreTransitionPte+f9
fffff801`830e0219 488b09 mov rcx,qword ptr [rcx]

FAULT_INSTR_CODE: e8098b48

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiRestoreTransitionPte+f9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5775e2f5

IMAGE_VERSION: 10.0.10586.494

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: f9

FAILURE_BUCKET_ID: AV_nt!MiRestoreTransitionPte

BUCKET_ID: AV_nt!MiRestoreTransitionPte

PRIMARY_PROBLEM_CLASS: AV_nt!MiRestoreTransitionPte

TARGET_TIME: 2016-07-21T11:10:22.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

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: 2016-07-01 06:26:45

BUILDDATESTAMP_STR: 160630-1736

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.494.amd64fre.th2_release_sec.160630-1736

ANALYSIS_SESSION_ELAPSED_TIME: 2eb

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!mirestoretransitionpte

FAILURE_ID_HASH: {37d4886d-fd49-86e8-3405-f2978c32f33e}

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



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


Loading Dump File [C:\Windows\Minidump\072216-11296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.494.amd64fre.th2_release_sec.160630-1736
Machine Name:
Kernel base = 0xfffff800`9d613000 PsLoadedModuleList = 0xfffff800`9d8f0cf0
Debug session time: Fri Jul 22 20:46:39.635 2016 (UTC + 3:00)
System Uptime: 0 days 0:16:58.300
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 135, {ffffffffc0000005, ffffd0015a3582d0, ffeff8010a9ce5c0, ffffc001693e2180}

Probably caused by : win32kbase.sys ( win32kbase!DrvUpdateGraphicsDeviceList+13a )

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

7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

REGISTRY_FILTER_DRIVER_EXCEPTION (135)
This bugcheck is caused by an unhandled exception in a registry filtering driver.
This bugcheck indicates that a registry filtering driver didn't handle exception inside
its notification routine. One can identify the driver by the 3rd parameter.
Arguments:
Arg1: ffffffffc0000005, ExceptionCode
Arg2: ffffd0015a3582d0, Address of the context record for the exception that caused the bugcheck
Arg3: ffeff8010a9ce5c0, The driver's callback routine address
Arg4: ffffc001693e2180, Internal

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.494.amd64fre.th2_release_sec.160630-1736

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7821

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: V1.9

BIOS_DATE: 07/21/2014

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z87-G45 GAMING (MS-7821)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: ffffd0015a3582d0

BUGCHECK_P3: ffeff8010a9ce5c0

BUGCHECK_P4: ffffc001693e2180

CPU_COUNT: 8

CPU_MHZ: dac

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x135

PROCESS_NAME: MSIAfterburner

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST:

ANALYSIS_SESSION_TIME: 07-22-2016 20:49:53.0613

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

TRAP_FRAME: ffffc0016928e000 -- (.trap 0xffffc0016928e000)
Unable to read trap frame at ffffc001`6928e000

LAST_CONTROL_TRANSFER: from fffff8009dbee3d0 to fffff8009d755940

STACK_TEXT:
ffffd001`5a357a88 fffff800`9dbee3d0 : 00000000`00000135 ffffffff`c0000005 ffffd001`5a3582d0 ffeff801`0a9ce5c0 : nt!KeBugCheckEx
ffffd001`5a357a90 fffff800`9db6b276 : ffffe003`1f5246f0 ffffe003`1f5246f0 ffffd001`5a357f60 fffff801`09c0d3b8 : nt!CmpFatalFilter+0x24
ffffd001`5a357ad0 fffff800`9d74523f : ffffd001`5a357cb0 fffff800`9ddde1ce 00000000`00000000 ffffd001`5a357cb0 : nt! ?? ::NNGAKEGL::`string'+0x24a6
ffffd001`5a357b00 fffff800`9d75b9ed : 00000000`00000000 ffffd001`5a357ca0 00000000`000003ab 00000000`00000000 : nt!_C_specific_handler+0x9f
ffffd001`5a357b70 fffff800`9d67d469 : 00000000`00000000 ffffd001`5a358b00 ffffd001`5a358170 fffff800`9d681723 : nt!RtlpExecuteHandlerForException+0xd
ffffd001`5a357ba0 fffff800`9d704ffc : ffffd001`5a358ab8 ffffd001`5a3587d0 ffffd001`5a358ab8 00000000`00000001 : nt!RtlDispatchException+0x429
ffffd001`5a3582a0 fffff800`9d7605c2 : 00000000`00000000 ffffd001`5a358ac4 ffffc001`6928e000 00000000`00000003 : nt!KiDispatchException+0x144
ffffd001`5a358980 fffff800`9d75ea7d : 00000000`00000001 fffff800`00000000 ffffd001`00000000 ffffd001`5a358ba8 : nt!KiExceptionDispatch+0xc2
ffffd001`5a358b60 fffff800`9dabc5ab : ffffd001`5a358fd0 ffffd001`5a358ee0 ffffc001`6d598d60 ffffd001`00000000 : nt!KiGeneralProtectionFault+0xfd
ffffd001`5a358cf0 fffff800`9dab53c3 : ffffc001`0000001c ffffd001`5a358fd0 ffffc001`80f83501 ffffe000`0000001d : nt!CmpCallCallBacks+0x3ab
ffffd001`5a358dd0 fffff800`9dac1e32 : fffff800`9d613000 fffff800`9d613000 00000000`00000000 ffffd001`5a359201 : nt!CmpParseKey+0x373
ffffd001`5a3590e0 fffff800`9dac30dc : ffffe000`cb980000 ffffd001`5a3592d0 ffffd001`00000240 ffffe000`c9fb7a70 : nt!ObpLookupObjectName+0x992
ffffd001`5a359260 fffff800`9da55986 : ffffd001`00000001 ffffe000`c9fb7a70 ffffd001`5a359820 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1ec
ffffd001`5a359380 fffff800`9da54c72 : 00000000`00000001 00000000`00000000 ffffc001`6ef0a9c0 ffffe000`c9e765b0 : nt!CmOpenKey+0x2a6
ffffd001`5a359530 fffff800`9d7601a3 : 00000000`00000000 ffffd001`00000000 ffffd001`5a359690 00000000`00000000 : nt!NtOpenKey+0x12
ffffd001`5a359570 fffff800`9d758830 : fffff800`9da34ace 00000000`00000000 ffffd001`5a359769 ffffd001`5a359820 : nt!KiSystemServiceCopyEnd+0x13
ffffd001`5a359708 fffff800`9da34ace : 00000000`00000000 ffffd001`5a359769 ffffd001`5a359820 00000000`00000000 : nt!KiServiceLinkage
ffffd001`5a359710 fffff800`9da3419f : fffff960`6e01da80 ffffd001`5a3599c0 ffffd001`5a359a00 fffff800`9dacda21 : nt!RtlpgetRegistryHandle+0x116
ffffd001`5a3597d0 fffff800`9da3415a : 00000000`00000000 00000000`00000000 ffffd001`5a359a00 00000000`00000000 : nt!RtlpQueryRegistryValues+0x3f
ffffd001`5a3598b0 fffff960`6dfb023a : 00000000`00000000 ffffd001`5a359950 00000000`00000000 00000000`00000000 : nt!RtlQueryRegistryValues+0xe
ffffd001`5a3598f0 fffff960`6dfb00d9 : 00000000`00000000 00000000`00000001 ffffd001`5a359ad0 fffff800`9dad22c5 : win32kbase!DrvUpdateGraphicsDeviceList+0x13a
ffffd001`5a359a70 fffff960`6dfaf121 : ffffe003`1f085080 00000000`0019f1e8 00000000`00000000 00000000`00000000 : win32kbase!UpdateGraphicsDeviceList+0x29
ffffd001`5a359aa0 fffff800`9d7601a3 : ffffe003`1f085080 ffffd001`5a359b80 00000000`00000000 00000000`00000020 : win32kbase!NtUserEnumDisplayDevices+0x51
ffffd001`5a359b00 00000000`764e5624 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0009e6a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x764e5624


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 9240e56d199041b2107a5c843439709291268bde

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3016cf3540f903fb2e9ba6a42cb5132fdbe8f904

THREAD_SHA1_HASH_MOD: 73ad65ce43f4b5e6053bcc239ee55f2da4c7452d

FOLLOWUP_IP:
win32kbase!DrvUpdateGraphicsDeviceList+13a
fffff960`6dfb023a b9ffff0000 mov ecx,0FFFFh

FAULT_INSTR_CODE: ffffb9

SYMBOL_STACK_INDEX: 14

SYMBOL_NAME: win32kbase!DrvUpdateGraphicsDeviceList+13a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5775e673

IMAGE_VERSION: 10.0.10586.494

BUCKET_ID_FUNC_OFFSET: 13a

FAILURE_BUCKET_ID: 0x135_win32kbase!DrvUpdateGraphicsDeviceList

BUCKET_ID: 0x135_win32kbase!DrvUpdateGraphicsDeviceList

PRIMARY_PROBLEM_CLASS: 0x135_win32kbase!DrvUpdateGraphicsDeviceList

TARGET_TIME: 2016-07-22T17:46:39.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

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: 2016-07-01 06:26:45

BUILDDATESTAMP_STR: 160630-1736

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.494.amd64fre.th2_release_sec.160630-1736

ANALYSIS_SESSION_ELAPSED_TIME: 2af

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x135_win32kbase!drvupdategraphicsdevicelist

FAILURE_ID_HASH: {dcb6b117-2106-21fb-b715-3c756104fab6}

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



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


Loading Dump File [C:\Windows\Minidump\072216-11046-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.494.amd64fre.th2_release_sec.160630-1736
Machine Name:
Kernel base = 0xfffff802`f3675000 PsLoadedModuleList = 0xfffff802`f3952cf0
Debug session time: Fri Jul 22 20:28:10.559 2016 (UTC + 3:00)
System Uptime: 0 days 1:13:55.224
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff802f7278d38, fffff802f7278550, 0, 0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff802f7278d38
Arg2: fffff802f7278550
Arg3: 0000000000000000
Arg4: 0000000000000000

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.494.amd64fre.th2_release_sec.160630-1736

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7821

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: V1.9

BIOS_DATE: 07/21/2014

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z87-G45 GAMING (MS-7821)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: fffff802f7278d38

BUGCHECK_P2: fffff802f7278550

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CONTEXT: fffff802f7278d38 -- (.cxr 0xfffff802f7278d38)
Unable to read context, Win32 error 0n30

CPU_COUNT: 8

CPU_MHZ: dac

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: ZEROED_STACK_0x3D

BUGCHECK_STR: 0x3D

PROCESS_NAME: System

CURRENT_IRQL: 7

ANALYSIS_SESSION_HOST:

ANALYSIS_SESSION_TIME: 07-22-2016 20:55:00.0015

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff802f37b7940

STACK_TEXT:
fffff802`f7277da8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

BUCKET_ID: ZEROED_STACK_0x3D

PRIMARY_PROBLEM_CLASS: ZEROED_STACK

FAILURE_BUCKET_ID: ZEROED_STACK_0x3D

TARGET_TIME: 2016-07-22T17:28:10.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

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: 2016-07-01 06:26:45

BUILDDATESTAMP_STR: 160630-1736

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.494.amd64fre.th2_release_sec.160630-1736

ANALYSIS_SESSION_ELAPSED_TIME: 29e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:zeroed_stack_0x3d

FAILURE_ID_HASH: {3c99bd6f-05a9-e447-046b-fda8917b91e5}

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff802f7278d38
Arg2: fffff802f7278550
Arg3: 0000000000000000
Arg4: 0000000000000000

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.494.amd64fre.th2_release_sec.160630-1736

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7821

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: V1.9

BIOS_DATE: 07/21/2014

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z87-G45 GAMING (MS-7821)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: fffff802f7278d38

BUGCHECK_P2: fffff802f7278550

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CONTEXT: fffff802f7278d38 -- (.cxr 0xfffff802f7278d38)
Unable to read context, Win32 error 0n30

CPU_COUNT: 8

CPU_MHZ: dac

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: ZEROED_STACK_0x3D

BUGCHECK_STR: 0x3D

PROCESS_NAME: System

CURRENT_IRQL: 7

ANALYSIS_SESSION_HOST:

ANALYSIS_SESSION_TIME: 07-22-2016 20:55:00.0687

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff802f37b7940

STACK_TEXT:
fffff802`f7277da8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

BUCKET_ID: ZEROED_STACK_0x3D

PRIMARY_PROBLEM_CLASS: ZEROED_STACK

FAILURE_BUCKET_ID: ZEROED_STACK_0x3D

TARGET_TIME: 2016-07-22T17:28:10.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

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: 2016-07-01 06:26:45

BUILDDATESTAMP_STR: 160630-1736

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.494.amd64fre.th2_release_sec.160630-1736

ANALYSIS_SESSION_ELAPSED_TIME: 29d

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:zeroed_stack_0x3d

FAILURE_ID_HASH: {3c99bd6f-05a9-e447-046b-fda8917b91e5}

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

DH forumlarında vakit geçirmekten keyif alıyor gibisin ancak giriş yapmadığını görüyoruz.

Üye olduğunda özel mesaj gönderebilir, beğendiğin konuları favorilerine ekleyip takibe alabilir ve daha önce gezdiğin konulara hızlıca erişebilirsin.

Üye Ol Şimdi Değil





< Bu mesaj bu kişi tarafından değiştirildi rhrhrh -- 22 Temmuz 2016; 21:00:12 >

S
9 yıl
Yüzbaşı

system 32 yi silmeni öneriririm


Bu mesaja 1 cevap geldi.
R
9 yıl
Teğmen
Konu Sahibi

quote:

Orijinalden alıntı: sancaryum

system 32 yi silmeni öneriririm

system 32 derken tüm sistem dosyalarını mı


Bu mesaja 1 cevap geldi.
S
9 yıl
Yüzbaşı

evet komple


Bu mesaja 1 cevap geldi.

Bu mesajda bahsedilenler: @rhrhrh
R
9 yıl
Teğmen
Konu Sahibi

quote:

Orijinalden alıntı: sancaryum

evet komple

o zaman windows tamamen kullanılmaz hale gelmeyecekmi
ayrıca neden böyle birşey yapmam gerekiyor ne gördünüzde böyle birşey söylüyorsunuz


Bu mesaja 1 cevap geldi.
N
9 yıl
Çavuş

ramleri söküp teker teker deneyin, muhtemelen birinde hata çıakcaktır

olmadı ramlere memtest86 ile tarayın

olmadı eğer yakın zamanda driver güncellemesi yapmışsanız bir önceki driver güncellemesine geri dönün

olmadı hddtune ile hdd yi tarayın.


Bu mesaja 1 cevap geldi.
R
9 yıl
Teğmen
Konu Sahibi

quote:

Orijinalden alıntı: Neo Nesil

ramleri söküp teker teker deneyin, muhtemelen birinde hata çıakcaktır

olmadı ramlere memtest86 ile tarayın

olmadı eğer yakın zamanda driver güncellemesi yapmışsanız bir önceki driver güncellemesine geri dönün

olmadı hddtune ile hdd yi tarayın.

yani sorun her yerde olabilir diyorsunuz
bir deneyelim bakalım


Bu mesaja 1 cevap geldi.
R
9 yıl
Teğmen
Konu Sahibi

ramleri ve hdd yi test ettim birşey çıkmadı ama hala sorun devam ediyor
lütfen biri yardım etsin bugün yine mavi ekran aldım.



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


Loading Dump File [C:\Windows\Minidump\072216-11296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.494.amd64fre.th2_release_sec.160630-1736
Machine Name:
Kernel base = 0xfffff800`9d613000 PsLoadedModuleList = 0xfffff800`9d8f0cf0
Debug session time: Fri Jul 22 20:46:39.635 2016 (UTC + 3:00)
System Uptime: 0 days 0:16:58.300
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 135, {ffffffffc0000005, ffffd0015a3582d0, ffeff8010a9ce5c0, ffffc001693e2180}

Probably caused by : win32kbase.sys ( win32kbase!DrvUpdateGraphicsDeviceList+13a )

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

7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

REGISTRY_FILTER_DRIVER_EXCEPTION (135)
This bugcheck is caused by an unhandled exception in a registry filtering driver.
This bugcheck indicates that a registry filtering driver didn't handle exception inside
its notification routine. One can identify the driver by the 3rd parameter.
Arguments:
Arg1: ffffffffc0000005, ExceptionCode
Arg2: ffffd0015a3582d0, Address of the context record for the exception that caused the bugcheck
Arg3: ffeff8010a9ce5c0, The driver's callback routine address
Arg4: ffffc001693e2180, Internal

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.494.amd64fre.th2_release_sec.160630-1736

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7821

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: V1.9

BIOS_DATE: 07/21/2014

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z87-G45 GAMING (MS-7821)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: ffffd0015a3582d0

BUGCHECK_P3: ffeff8010a9ce5c0

BUGCHECK_P4: ffffc001693e2180

CPU_COUNT: 8

CPU_MHZ: dac

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x135

PROCESS_NAME: MSIAfterburner

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST:

ANALYSIS_SESSION_TIME: 07-22-2016 20:49:53.0613

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

TRAP_FRAME: ffffc0016928e000 -- (.trap 0xffffc0016928e000)
Unable to read trap frame at ffffc001`6928e000

LAST_CONTROL_TRANSFER: from fffff8009dbee3d0 to fffff8009d755940

STACK_TEXT:
ffffd001`5a357a88 fffff800`9dbee3d0 : 00000000`00000135 ffffffff`c0000005 ffffd001`5a3582d0 ffeff801`0a9ce5c0 : nt!KeBugCheckEx
ffffd001`5a357a90 fffff800`9db6b276 : ffffe003`1f5246f0 ffffe003`1f5246f0 ffffd001`5a357f60 fffff801`09c0d3b8 : nt!CmpFatalFilter+0x24
ffffd001`5a357ad0 fffff800`9d74523f : ffffd001`5a357cb0 fffff800`9ddde1ce 00000000`00000000 ffffd001`5a357cb0 : nt! ?? ::NNGAKEGL::`string'+0x24a6
ffffd001`5a357b00 fffff800`9d75b9ed : 00000000`00000000 ffffd001`5a357ca0 00000000`000003ab 00000000`00000000 : nt!_C_specific_handler+0x9f
ffffd001`5a357b70 fffff800`9d67d469 : 00000000`00000000 ffffd001`5a358b00 ffffd001`5a358170 fffff800`9d681723 : nt!RtlpExecuteHandlerForException+0xd
ffffd001`5a357ba0 fffff800`9d704ffc : ffffd001`5a358ab8 ffffd001`5a3587d0 ffffd001`5a358ab8 00000000`00000001 : nt!RtlDispatchException+0x429
ffffd001`5a3582a0 fffff800`9d7605c2 : 00000000`00000000 ffffd001`5a358ac4 ffffc001`6928e000 00000000`00000003 : nt!KiDispatchException+0x144
ffffd001`5a358980 fffff800`9d75ea7d : 00000000`00000001 fffff800`00000000 ffffd001`00000000 ffffd001`5a358ba8 : nt!KiExceptionDispatch+0xc2
ffffd001`5a358b60 fffff800`9dabc5ab : ffffd001`5a358fd0 ffffd001`5a358ee0 ffffc001`6d598d60 ffffd001`00000000 : nt!KiGeneralProtectionFault+0xfd
ffffd001`5a358cf0 fffff800`9dab53c3 : ffffc001`0000001c ffffd001`5a358fd0 ffffc001`80f83501 ffffe000`0000001d : nt!CmpCallCallBacks+0x3ab
ffffd001`5a358dd0 fffff800`9dac1e32 : fffff800`9d613000 fffff800`9d613000 00000000`00000000 ffffd001`5a359201 : nt!CmpParseKey+0x373
ffffd001`5a3590e0 fffff800`9dac30dc : ffffe000`cb980000 ffffd001`5a3592d0 ffffd001`00000240 ffffe000`c9fb7a70 : nt!ObpLookupObjectName+0x992
ffffd001`5a359260 fffff800`9da55986 : ffffd001`00000001 ffffe000`c9fb7a70 ffffd001`5a359820 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1ec
ffffd001`5a359380 fffff800`9da54c72 : 00000000`00000001 00000000`00000000 ffffc001`6ef0a9c0 ffffe000`c9e765b0 : nt!CmOpenKey+0x2a6
ffffd001`5a359530 fffff800`9d7601a3 : 00000000`00000000 ffffd001`00000000 ffffd001`5a359690 00000000`00000000 : nt!NtOpenKey+0x12
ffffd001`5a359570 fffff800`9d758830 : fffff800`9da34ace 00000000`00000000 ffffd001`5a359769 ffffd001`5a359820 : nt!KiSystemServiceCopyEnd+0x13
ffffd001`5a359708 fffff800`9da34ace : 00000000`00000000 ffffd001`5a359769 ffffd001`5a359820 00000000`00000000 : nt!KiServiceLinkage
ffffd001`5a359710 fffff800`9da3419f : fffff960`6e01da80 ffffd001`5a3599c0 ffffd001`5a359a00 fffff800`9dacda21 : nt!RtlpGetRegistryHandle+0x116
ffffd001`5a3597d0 fffff800`9da3415a : 00000000`00000000 00000000`00000000 ffffd001`5a359a00 00000000`00000000 : nt!RtlpQueryRegistryValues+0x3f
ffffd001`5a3598b0 fffff960`6dfb023a : 00000000`00000000 ffffd001`5a359950 00000000`00000000 00000000`00000000 : nt!RtlQueryRegistryValues+0xe
ffffd001`5a3598f0 fffff960`6dfb00d9 : 00000000`00000000 00000000`00000001 ffffd001`5a359ad0 fffff800`9dad22c5 : win32kbase!DrvUpdateGraphicsDeviceList+0x13a
ffffd001`5a359a70 fffff960`6dfaf121 : ffffe003`1f085080 00000000`0019f1e8 00000000`00000000 00000000`00000000 : win32kbase!UpdateGraphicsDeviceList+0x29
ffffd001`5a359aa0 fffff800`9d7601a3 : ffffe003`1f085080 ffffd001`5a359b80 00000000`00000000 00000000`00000020 : win32kbase!NtUserEnumDisplayDevices+0x51
ffffd001`5a359b00 00000000`764e5624 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0009e6a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x764e5624


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 9240e56d199041b2107a5c843439709291268bde

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3016cf3540f903fb2e9ba6a42cb5132fdbe8f904

THREAD_SHA1_HASH_MOD: 73ad65ce43f4b5e6053bcc239ee55f2da4c7452d

FOLLOWUP_IP:
win32kbase!DrvUpdateGraphicsDeviceList+13a
fffff960`6dfb023a b9ffff0000 mov ecx,0FFFFh

FAULT_INSTR_CODE: ffffb9

SYMBOL_STACK_INDEX: 14

SYMBOL_NAME: win32kbase!DrvUpdateGraphicsDeviceList+13a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5775e673

IMAGE_VERSION: 10.0.10586.494

BUCKET_ID_FUNC_OFFSET: 13a

FAILURE_BUCKET_ID: 0x135_win32kbase!DrvUpdateGraphicsDeviceList

BUCKET_ID: 0x135_win32kbase!DrvUpdateGraphicsDeviceList

PRIMARY_PROBLEM_CLASS: 0x135_win32kbase!DrvUpdateGraphicsDeviceList

TARGET_TIME: 2016-07-22T17:46:39.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

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: 2016-07-01 06:26:45

BUILDDATESTAMP_STR: 160630-1736

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.494.amd64fre.th2_release_sec.160630-1736

ANALYSIS_SESSION_ELAPSED_TIME: 2af

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x135_win32kbase!drvupdategraphicsdevicelist

FAILURE_ID_HASH: {dcb6b117-2106-21fb-b715-3c756104fab6}

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



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


Loading Dump File [C:\Windows\Minidump\072216-11046-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.494.amd64fre.th2_release_sec.160630-1736
Machine Name:
Kernel base = 0xfffff802`f3675000 PsLoadedModuleList = 0xfffff802`f3952cf0
Debug session time: Fri Jul 22 20:28:10.559 2016 (UTC + 3:00)
System Uptime: 0 days 1:13:55.224
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff802f7278d38, fffff802f7278550, 0, 0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff802f7278d38
Arg2: fffff802f7278550
Arg3: 0000000000000000
Arg4: 0000000000000000

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.494.amd64fre.th2_release_sec.160630-1736

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7821

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: V1.9

BIOS_DATE: 07/21/2014

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z87-G45 GAMING (MS-7821)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: fffff802f7278d38

BUGCHECK_P2: fffff802f7278550

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CONTEXT: fffff802f7278d38 -- (.cxr 0xfffff802f7278d38)
Unable to read context, Win32 error 0n30

CPU_COUNT: 8

CPU_MHZ: dac

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: ZEROED_STACK_0x3D

BUGCHECK_STR: 0x3D

PROCESS_NAME: System

CURRENT_IRQL: 7

ANALYSIS_SESSION_HOST: HÜSAMETTINRABIA

ANALYSIS_SESSION_TIME: 07-22-2016 20:55:00.0015

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff802f37b7940

STACK_TEXT:
fffff802`f7277da8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

BUCKET_ID: ZEROED_STACK_0x3D

PRIMARY_PROBLEM_CLASS: ZEROED_STACK

FAILURE_BUCKET_ID: ZEROED_STACK_0x3D

TARGET_TIME: 2016-07-22T17:28:10.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

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: 2016-07-01 06:26:45

BUILDDATESTAMP_STR: 160630-1736

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.494.amd64fre.th2_release_sec.160630-1736

ANALYSIS_SESSION_ELAPSED_TIME: 29e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:zeroed_stack_0x3d

FAILURE_ID_HASH: {3c99bd6f-05a9-e447-046b-fda8917b91e5}

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff802f7278d38
Arg2: fffff802f7278550
Arg3: 0000000000000000
Arg4: 0000000000000000

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.494.amd64fre.th2_release_sec.160630-1736

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7821

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: V1.9

BIOS_DATE: 07/21/2014

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z87-G45 GAMING (MS-7821)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: fffff802f7278d38

BUGCHECK_P2: fffff802f7278550

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CONTEXT: fffff802f7278d38 -- (.cxr 0xfffff802f7278d38)
Unable to read context, Win32 error 0n30

CPU_COUNT: 8

CPU_MHZ: dac

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: ZEROED_STACK_0x3D

BUGCHECK_STR: 0x3D

PROCESS_NAME: System

CURRENT_IRQL: 7

ANALYSIS_SESSION_HOST:

ANALYSIS_SESSION_TIME: 07-22-2016 20:55:00.0687

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff802f37b7940

STACK_TEXT:
fffff802`f7277da8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

BUCKET_ID: ZEROED_STACK_0x3D

PRIMARY_PROBLEM_CLASS: ZEROED_STACK

FAILURE_BUCKET_ID: ZEROED_STACK_0x3D

TARGET_TIME: 2016-07-22T17:28:10.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

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: 2016-07-01 06:26:45

BUILDDATESTAMP_STR: 160630-1736

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.494.amd64fre.th2_release_sec.160630-1736

ANALYSIS_SESSION_ELAPSED_TIME: 29d

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:zeroed_stack_0x3d

FAILURE_ID_HASH: {3c99bd6f-05a9-e447-046b-fda8917b91e5}

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


Bu mesaja 1 cevap geldi.
S
9 yıl
Çavuş

Mavi ekranı hangi aşamada aldığın belli mi? Oyun açarken mi? Oynarken mi? Pc boştayken mi? İnternette gezerken mi?Önce bunu tesbit et bence.Sonra tesbit etmeye çalışalım.


Bu mesaja 1 cevap geldi.
R
9 yıl
Teğmen
Konu Sahibi

quote:

Orijinalden alıntı: sihirlix

Mavi ekranı hangi aşamada aldığın belli mi? Oyun açarken mi? Oynarken mi? Pc boştayken mi? İnternette gezerken mi?Önce bunu tesbit et bence.Sonra tesbit etmeye çalışalım.

herhangi bir anda alabiliyorum genelliklede boşta ve internette gezinirken
oyun oynarken çok az hatta son zamanlarda hiç olmadı sanırım
ama dediğim gibi özellikle boşta iken çok oluyor masaüstünde hiçbir program açık değilken bırakıyorum yarım saat sonra geliyorum pc kapanıp açılmış





< Bu mesaj bu kişi tarafından değiştirildi rhrhrh -- 22 Temmuz 2016; 21:21:56 >
Bu mesaja 3 cevap geldi.
S
9 yıl
Çavuş

Elinde yedek ram varsa ya da bir arkadaşından geçici alabiliyorsan farklı ramla dene bir de.
Eskiden olsa mavi ekran direk ram hatasıdır der dim.Fakat teknoloji o kadar ilerledeki hata çeşitleride buna göre çoğaldı ve farklılaştı.Sistem dosyalarından birinin bozuk olmasıda buna sebeb olabiliyor.


Bu mesaja 1 cevap geldi.
O
9 yıl
Yüzbaşı

Sag alt kısımda saatin yanında hangi programlar açık hocam .Arka planda çalışan programlar çakışıyor olabilir.


Bu mesaja 1 cevap geldi.
R
9 yıl
Teğmen
Konu Sahibi

çok fazla bir program çalışmıyor görev yöneticisinden kapalı çoğu

sadece torrent, ashampoo backup, soundblaster sinema, ccleaner, ati, realtek hd audio




< Resime gitmek için tıklayın >




Bu mesajda bahsedilenler: @Owwshet
R
9 yıl
Teğmen
Konu Sahibi

elimde şu an ram yok ama ramleri tek tek deneyip sorun varmı diye bakabilrim.




Bu mesajda bahsedilenler: @sihirlix
N
9 yıl
Çavuş

yakın zamanlarda driver güncellemesi yaptın mı peki veya program?

şayet yaptı isen bi önceki driver sürümünü geri yükle...


Bu mesaja 1 cevap geldi.

Bu mesajda bahsedilenler: @rhrhrh
D
9 yıl
Teğmen

Ramleri temizle,driver güncelle,windows yeniden kur, yada ram az geliyordur ondan mavi ekran veriyordur


Bu mesaja 1 cevap geldi.
R
9 yıl
Teğmen
Konu Sahibi

Windows güncellemeleri dışında bir güncelleme yapmadım ram 16gb yetersiz kalacağını sanmıyorum ama tankerin 8 GB bir bölümünü ramdisk programı ile hardisk yapıp sanal bellek olarak tanıttım sisteme
şimdi düşünüyorum acaba sanal bellek (8+16hardisk c) parçalanmış olması bir sorun yaratırmı





< Bu mesaj bu kişi tarafından değiştirildi rhrhrh -- 24 Temmuz 2016; 12:52:50 >

< Bu ileti mobil sürüm kullanılarak atıldı >

R
9 yıl
Teğmen
Konu Sahibi

quote:

Orijinalden alıntı: dordi11

Ramleri temizle,driver güncelle,windows yeniden kur, yada ram az geliyordur ondan mavi ekran veriyordur

dediklerinizi yaptım sorun devam ediyor

daha önceden de başka bir hardisk üzerine win 10 dual boot Yapacak şekilde sıfırdan kurdum iki sistemde de ( biri win7 yükseltmesi) aynı sorunu yaşanıyor



< Bu ileti mobil sürüm kullanılarak atıldı >

D
9 yıl
Teğmen

windows 10 değilde 8.1 yada 8 kurun eğer hala veriyorsa win10 dosyası yanlış yazılmıştır bidaha yazdırın öyle deneyin




Bu mesajda bahsedilenler: @rhrhrh
DH Mobil uygulaması ile devam edin. Mobil tarayıcınız ile mümkün olanların yanı sıra, birçok yeni ve faydalı özelliğe erişin. Gizle ve güncelleme çıkana kadar tekrar gösterme.