Mavi ekran hatası

Ted Kaczynski dedi:

Minidump Dosyalarını Paylaşın

Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...

www.technopat.net

Minidump dosyanı paylaş.

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

Assecreed dedi:

Memtest86 ile bellek testi yapınız.
HDD Sentinel ile diskinizin sağlık durumunu paylaşınız.

Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.

Üçüncü taraf çerezlerini kabul et

Sürprizbozan: Hata kodu

Kod:Panoya kopyala

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7531

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-J7A11VA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 33395

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8028161a876

BUGCHECK_P3: ffffca0062ff5920

BUGCHECK_P4: 0

CONTEXT:  ffffca0062ff5920 -- (.cxr 0xffffca0062ff5920)
rax=ffff9a05545d9ee8 rbx=ffff9a05513e3080 rcx=9a05545d9eb03a5d
rdx=0000000000000000 rsi=0000000000000000 rdi=ffff9a05545d9ee0
rip=fffff8028161a876 rsp=ffffda03be5b8940 rbp=ffffda03be5b8a01
r8=0000000000000000  r9=000001152a550b14 r10=0000000000000002
r11=fffff780000003b0 r12=0000000000000000 r13=9a05545d9eb03a5d
r14=0000000000000000 r15=ffff9a05513e31c0
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050282
nt!KeAbPreWait+0x6:
fffff802`8161a876 0fb64120        movzx   eax,byte ptr [rcx+20h] ds:002b:9a05545d`9eb03a7d=??
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  EpicGamesLauncher.exe

BAD_STACK_POINTER:  ffffca0062ff5018

STACK_TEXT:
ffffda03`be5b8940 fffff802`8186e51b     : ffffca00`000000c4 fffff802`81aefe11 000f8067`b4bbbd01 ffff9a05`513e31c0 : nt!KeAbPreWait+0x6
ffffda03`be5b8970 fffff802`81af1531     : ffff9a05`545d9ee0 00000000`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x18f9db
ffffda03`be5b8a60 fffff802`81af15da     : ffff9a05`513e3080 00000082`bb16fca8 00000000`00000000 00000000`00000000 : nt!ObWaitForSingleObject+0x91
ffffda03`be5b8ac0 fffff802`81805fb8     : 00000000`00000000 00000000`00000000 ffffda03`be5b8b18 ffffffff`fffe7960 : nt!NtWaitForSingleObject+0x6a
ffffda03`be5b8b00 00007ffd`10febe14     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000082`bb16fc78 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`10febe14


SYMBOL_NAME:  nt!KeAbPreWait+6

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .cxr 0xffffca0062ff5920 ; kb

BUCKET_ID_FUNC_OFFSET:  6

FAILURE_BUCKET_ID:  0x3B_c0000005_STACKPTR_ERROR_nt!KeAbPreWait

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ddcb9656-083d-2ea8-831a-b13145df4ef7}

Followup:     MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8006ecfb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 8233

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-J7A11VA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 26940

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8006ecfb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffffc08091f708e0 -- (.trap 0xffffc08091f708e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=8e00000fffffffff rbx=0000000000000000 rcx=0000000000000492
rdx=00000000000000ea rsi=0000000000000000 rdi=0000000000000000
rip=fffff8006e343c88 rsp=ffffc08091f70a70 rbp=ffffc08091f70bc8
r8=ffffde0000002800  r9=0000000000000000 r10=0000000000353b9c
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiZeroLargePages+0x688:
fffff800`6e343c88 498b4718        mov     rax,qword ptr [r15+18h] ds:00000000`00000018=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffb080`ddce8e18 fffff800`6e487a98     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`6ecfb320 : nt!KeBugCheckEx
ffffb080`ddce8e20 fffff800`6e326993     : 000082b5`11722626 ffffb080`ddccf180 00000000`00000000 ffffb080`ddccf180 : nt!KeAccumulateTicks+0x15dda8
ffffb080`ddce8e80 fffff800`6e32647a     : ffffc68f`c80c89a0 ffffc080`91f70960 ffffdb00`0c113b00 00000000`0000009c : nt!KeClockInterruptNotify+0x453
ffffb080`ddce8f30 fffff800`6e22ecd5     : ffffc68f`c80c89a0 00000000`00000000 00000000`00000000 ffff35c8`96f5907d : nt!HalpTimerClockIpiRoutine+0x1a
ffffb080`ddce8f60 fffff800`6e3f604a     : ffffc080`91f70960 ffffc68f`c80c89a0 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffb080`ddce8fb0 fffff800`6e3f65b7     : 00000000`674b159a 00000000`00000003 ffffc68f`c80ba7d0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffc080`91f708e0 fffff800`6e343c88     : ffffc68f`c80ba7d0 00000000`00000001 fffff800`6ec50c00 ffffc68f`c80b7c20 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffc080`91f70a70 fffff800`6e3b0968     : ffffc68f`c80ba7d0 ffffc080`00000003 fffff800`00000000 5a5a5a5a`00000008 : nt!MiZeroLargePages+0x688
ffffc080`91f70b60 fffff800`6e2a2ae5     : 00000000`00000000 ffffc68f`c80b7c20 ffffde00`00007000 fffff800`6ec50c00 : nt!MiZeroLargePageThread+0x88
ffffc080`91f70c10 fffff800`6e3fbbf8     : ffffb080`ddd89180 ffffc68f`c8224080 fffff800`6e2a2a90 5a5a5a5a`5a5a5a5a : nt!PspSystemThreadStartup+0x55
ffffc080`91f70c60 00000000`00000000     : ffffc080`91f71000 ffffc080`91f6b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!KeAccumulateTicks+15dda8

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  15dda8

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup:     MachineOwner
---------*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00007ff9b4dcbe14, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 0000000000000001, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffdd827c0e6b80, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5875

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-J7A11VA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 14991

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1

BUGCHECK_P1: 7ff9b4dcbe14

BUGCHECK_P2: 0

BUGCHECK_P3: 1

BUGCHECK_P4: ffffdd827c0e6b80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  EpicGamesLauncher.exe

STACK_TEXT:
ffffdd82`7c0e69b8 fffff800`62806569     : 00000000`00000001 00007ff9`b4dcbe14 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
ffffdd82`7c0e69c0 fffff800`62806433     : 00000000`00000000 00000000`00000000 ffffdd82`7c0e6b18 ffffffff`fffe7960 : nt!KiBugCheckDispatch+0x69
ffffdd82`7c0e6b00 00007ff9`b4dcbe14     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000008`24d3fcf8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`b4dcbe14


SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x1_SysCallNum_4_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {52cd694c-15ec-48c3-924a-3539560711db}

Followup:     MachineOwner
---------*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 0000000076f01cfc, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffaf0c59b31b80, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5609

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-J7A11VA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 28790

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1

BUGCHECK_P1: 76f01cfc

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: ffffaf0c59b31b80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MicrosoftEdgeUpdate.exe

STACK_TEXT:
ffffaf0c`59b319b8 fffff806`04006569     : 00000000`00000001 00000000`76f01cfc 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffffaf0c`59b319c0 fffff806`04006433     : ffffb105`6878e000 00000000`00000000 ffffaf0c`59b31b80 ffffb105`00000000 : nt!KiBugCheckDispatch+0x69
ffffaf0c`59b31b00 00000000`76f01cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000000`0072eae8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f01cfc


SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x1_SysCallNum_3000f_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {024efe4b-9d98-6387-839a-7c206b5a3695}

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

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