Sürekli farklı kodlu mavi ekran hataları

İşletim sistemi
Windows 10

gorkem22tr

Centipat
Katılım
8 Kasım 2020
Mesajlar
25
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
Sürekli farklı hata isimleri gösterilerek mavi ekran alıyorum çözüm bulamadım yardımcı olur musunuz?
Minidump bırakıyorum asla çözemedim.
 
Son düzenleyen: Moderatör:
Kod:
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: 0000000077171cfc, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 0000000000000001, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff38f3c87db80, Call type (0 - system call, 1 - worker routine)

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3312

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 5619

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

    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: 77171cfc

BUGCHECK_P2: 0

BUGCHECK_P3: 1

BUGCHECK_P4: fffff38f3c87db80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  2

PROCESS_NAME:  Discord.exe

STACK_TEXT: 
fffff38f`3c87d948 fffff802`2e606569     : 00000000`00000001 00000000`77171cfc 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
fffff38f`3c87d950 fffff802`2e606433     : ffffe20b`21710080 00000000`0e27ef08 fffff38f`3c87daa8 00000000`105512fc : nt!KiBugCheckDispatch+0x69
fffff38f`3c87da90 00000000`77171cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000000`0e27eee8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77171cfc


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_1c0009_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b84effd5-47a1-4e08-3735-c42a94008fff}

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

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffab8f9e802a38, Virtual address for the attempted execute.
Arg2: 8700000404a3a963, PTE contents.
Arg3: fffffa8df6f025e0, (reserved)
Arg4: 0000000000000002, (reserved)

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3515

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 7907

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

    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:  fc

BUGCHECK_P1: ffffab8f9e802a38

BUGCHECK_P2: 8700000404a3a963

BUGCHECK_P3: fffffa8df6f025e0

BUGCHECK_P4: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  fffffa8df6f025e0 -- (.trap 0xfffffa8df6f025e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd70c5580e438 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000060 rsi=0000000000000000 rdi=0000000000000000
rip=ffffab8f9e802a38 rsp=fffffa8df6f02770 rbp=ffff940196340180
 r8=0000000100000100  r9=ffff940196340180 r10=ffffd70c527f4300
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
ffffab8f`9e802a38 682a809e8f      push    0FFFFFFFF8F9E802Ah
Resetting default scope

STACK_TEXT: 
fffffa8d`f6f022f8 fffff805`7c84eaa0     : 00000000`000000fc ffffab8f`9e802a38 87000004`04a3a963 fffffa8d`f6f025e0 : nt!KeBugCheckEx
fffffa8d`f6f02300 fffff805`7c708b56     : ffffab8f`9e802a38 fffffa8d`f6f02500 fffffa8d`00000000 ffff8000`00000000 : nt!MiCheckSystemNxFault+0x1ab7e8
fffffa8d`f6f02340 fffff805`7c6ea5e0     : fffffa8d`f6f024a0 00000000`00000011 fffffa8d`f6f02660 00000000`00000000 : nt!MiSystemFault+0x6c6
fffffa8d`f6f02440 fffff805`7c80275e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
fffffa8d`f6f025e0 ffffab8f`9e802a38     : ffffab8f`00000002 fffff805`00000003 00000000`00000000 ffffd70c`00000000 : nt!KiPageFault+0x35e
fffffa8d`f6f02770 ffffab8f`00000002     : fffff805`00000003 00000000`00000000 ffffd70c`00000000 ffffab8f`00000000 : 0xffffab8f`9e802a38
fffffa8d`f6f02778 fffff805`00000003     : 00000000`00000000 ffffd70c`00000000 ffffab8f`00000000 ffffd70c`55871810 : 0xffffab8f`00000002
fffffa8d`f6f02780 00000000`00000000     : ffffd70c`00000000 ffffab8f`00000000 ffffd70c`55871810 ffff9401`00000000 : 0xfffff805`00000003


SYMBOL_NAME:  nt!MiCheckSystemNxFault+1ab7e8

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  1ab7e8

FAILURE_BUCKET_ID:  0xFC_nt!MiCheckSystemNxFault

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a6ae5288-6b71-974a-9b09-23f14d998164}

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffb201a4d99e70
Arg3: 0000000000000000
Arg4: fffff80424206234

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3906

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 13379

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

    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:  7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffb201a4d99e70

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80424206234

TRAP_FRAME:  ffffb201a4d99e70 -- (.trap 0xffffb201a4d99e70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000102 rbx=0000000000000000 rcx=ffff858f4a05d480
rdx=0000000000000030 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80424206234 rsp=0000000000000000 rbp=000000000d9bf1c8
 r8=0000000000000001  r9=0000000000000001 r10=0000000000000000
r11=ffff858f4a1f1080 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiSystemServiceExit+0x274:
fffff804`24206234 c3              ret
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

STACK_TEXT: 
ffffb201`a4d99d28 fffff804`24206569     : 00000000`0000007f 00000000`00000008 ffffb201`a4d99e70 00000000`00000000 : nt!KeBugCheckEx
ffffb201`a4d99d30 fffff804`24201383     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffb201`a4d99e70 fffff804`24206234     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c3
00000000`00000000 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x274


SYMBOL_NAME:  nt!KiDoubleFaultAbort+2c3

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2c3

FAILURE_BUCKET_ID:  0x7f_8_nt!KiDoubleFaultAbort

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d1f8395a-8c58-45da-6ebf-e8bb4aad2fc5}

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

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: fffff8014a6e00bc, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000091, 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: fffff8014a6dfbc0, address which referenced memory

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4218

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 7105

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

    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:  a

BUGCHECK_P1: fffff8014a6e00bc

BUGCHECK_P2: ff

BUGCHECK_P3: 91

BUGCHECK_P4: fffff8014a6dfbc0

WRITE_ADDRESS: fffff8014b0fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8014b00f340: Unable to get Flags value from nt!KdVersionBlock
fffff8014b00f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 fffff8014a6e00bc

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

TRAP_FRAME:  ffff8003c4029530 -- (.trap 0xffff8003c4029530)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000003d5 rbx=0000000000000000 rcx=c1cdd348ca8be67d
rdx=fffff8014a6e00bc rsi=0000000000000000 rdi=0000000000000000
rip=fffff8014a6dfbc0 rsp=ffff8003c40296c0 rbp=0000000000000001
 r8=0000000000000020  r9=fffff8014a6e008c r10=000000000000a518
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na po nc
nt!KiSwapThread+0x120:
fffff801`4a6dfbc0 48890a          mov     qword ptr [rdx],rcx ds:fffff801`4a6e00bc=c1cdd348ca8b4165
Resetting default scope

STACK_TEXT: 
ffff8003`c40293e8 fffff801`4a806569     : 00000000`0000000a fffff801`4a6e00bc 00000000`000000ff 00000000`00000091 : nt!KeBugCheckEx
ffff8003`c40293f0 fffff801`4a802869     : ffffd281`d3880180 fffff801`4a7fb7b2 000f8067`b4bbbdff 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffff8003`c4029530 fffff801`4a6dfbc0     : ffffe50f`f590f080 fffff801`00000000 ffffe50f`ea010100 fffff801`00000001 : nt!KiPageFault+0x469
ffff8003`c40296c0 fffff801`4a6df4cf     : ffff900b`61b13310 fffff801`5448d272 00000000`00000000 ffffe50f`00000000 : nt!KiSwapThread+0x120
ffff8003`c4029770 fffff801`4a6e2e03     : ffffe50f`00000000 ffffe50f`00000000 00000000`00000000 00000000`00000001 : nt!KiCommitThreadWait+0x14f
ffff8003`c4029810 fffff801`4a6e2838     : ffffe50f`f5aab680 00000000`00000001 ffffe50f`f5a23200 fffff801`00000000 : nt!KeRemoveQueueEx+0x263
ffff8003`c40298b0 fffff801`4aa5ee3d     : 00000000`00000000 00000000`00000000 ffffd281`d3880180 fffff801`4a6c4bca : nt!IoRemoveIoCompletion+0x98
ffff8003`c40299e0 fffff801`4a805fb8     : ffffe50f`f5ad60c0 00000000`0dc1ec58 ffff8003`c4029aa8 00000000`0c202b1c : nt!NtRemoveIoCompletion+0x13d
ffff8003`c4029a90 00000000`77651cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0dc1ec38 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77651cfc


SYMBOL_NAME:  nt!KiSwapThread+120

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  120

FAILURE_BUCKET_ID:  AV_nt!KiSwapThread

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3a5eca23-a992-0c0e-a0ce-d48add0d8eda}

Followup:     MachineOwner
---------
 
Kod:
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: 0000000077171cfc, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 0000000000000001, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff38f3c87db80, Call type (0 - system call, 1 - worker routine)

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3312

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 5619

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

    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: 77171cfc

BUGCHECK_P2: 0

BUGCHECK_P3: 1

BUGCHECK_P4: fffff38f3c87db80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  2

PROCESS_NAME:  Discord.exe

STACK_TEXT:
fffff38f`3c87d948 fffff802`2e606569     : 00000000`00000001 00000000`77171cfc 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
fffff38f`3c87d950 fffff802`2e606433     : ffffe20b`21710080 00000000`0e27ef08 fffff38f`3c87daa8 00000000`105512fc : nt!KiBugCheckDispatch+0x69
fffff38f`3c87da90 00000000`77171cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000000`0e27eee8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77171cfc


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_1c0009_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b84effd5-47a1-4e08-3735-c42a94008fff}

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

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffab8f9e802a38, Virtual address for the attempted execute.
Arg2: 8700000404a3a963, PTE contents.
Arg3: fffffa8df6f025e0, (reserved)
Arg4: 0000000000000002, (reserved)

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3515

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 7907

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

    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:  fc

BUGCHECK_P1: ffffab8f9e802a38

BUGCHECK_P2: 8700000404a3a963

BUGCHECK_P3: fffffa8df6f025e0

BUGCHECK_P4: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  fffffa8df6f025e0 -- (.trap 0xfffffa8df6f025e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd70c5580e438 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000060 rsi=0000000000000000 rdi=0000000000000000
rip=ffffab8f9e802a38 rsp=fffffa8df6f02770 rbp=ffff940196340180
r8=0000000100000100  r9=ffff940196340180 r10=ffffd70c527f4300
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
ffffab8f`9e802a38 682a809e8f      push    0FFFFFFFF8F9E802Ah
Resetting default scope

STACK_TEXT:
fffffa8d`f6f022f8 fffff805`7c84eaa0     : 00000000`000000fc ffffab8f`9e802a38 87000004`04a3a963 fffffa8d`f6f025e0 : nt!KeBugCheckEx
fffffa8d`f6f02300 fffff805`7c708b56     : ffffab8f`9e802a38 fffffa8d`f6f02500 fffffa8d`00000000 ffff8000`00000000 : nt!MiCheckSystemNxFault+0x1ab7e8
fffffa8d`f6f02340 fffff805`7c6ea5e0     : fffffa8d`f6f024a0 00000000`00000011 fffffa8d`f6f02660 00000000`00000000 : nt!MiSystemFault+0x6c6
fffffa8d`f6f02440 fffff805`7c80275e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
fffffa8d`f6f025e0 ffffab8f`9e802a38     : ffffab8f`00000002 fffff805`00000003 00000000`00000000 ffffd70c`00000000 : nt!KiPageFault+0x35e
fffffa8d`f6f02770 ffffab8f`00000002     : fffff805`00000003 00000000`00000000 ffffd70c`00000000 ffffab8f`00000000 : 0xffffab8f`9e802a38
fffffa8d`f6f02778 fffff805`00000003     : 00000000`00000000 ffffd70c`00000000 ffffab8f`00000000 ffffd70c`55871810 : 0xffffab8f`00000002
fffffa8d`f6f02780 00000000`00000000     : ffffd70c`00000000 ffffab8f`00000000 ffffd70c`55871810 ffff9401`00000000 : 0xfffff805`00000003


SYMBOL_NAME:  nt!MiCheckSystemNxFault+1ab7e8

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  1ab7e8

FAILURE_BUCKET_ID:  0xFC_nt!MiCheckSystemNxFault

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a6ae5288-6b71-974a-9b09-23f14d998164}

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffb201a4d99e70
Arg3: 0000000000000000
Arg4: fffff80424206234

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3906

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 13379

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

    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:  7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffb201a4d99e70

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80424206234

TRAP_FRAME:  ffffb201a4d99e70 -- (.trap 0xffffb201a4d99e70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000102 rbx=0000000000000000 rcx=ffff858f4a05d480
rdx=0000000000000030 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80424206234 rsp=0000000000000000 rbp=000000000d9bf1c8
r8=0000000000000001  r9=0000000000000001 r10=0000000000000000
r11=ffff858f4a1f1080 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiSystemServiceExit+0x274:
fffff804`24206234 c3              ret
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

STACK_TEXT:
ffffb201`a4d99d28 fffff804`24206569     : 00000000`0000007f 00000000`00000008 ffffb201`a4d99e70 00000000`00000000 : nt!KeBugCheckEx
ffffb201`a4d99d30 fffff804`24201383     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffb201`a4d99e70 fffff804`24206234     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c3
00000000`00000000 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x274


SYMBOL_NAME:  nt!KiDoubleFaultAbort+2c3

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2c3

FAILURE_BUCKET_ID:  0x7f_8_nt!KiDoubleFaultAbort

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d1f8395a-8c58-45da-6ebf-e8bb4aad2fc5}

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

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: fffff8014a6e00bc, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000091, 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: fffff8014a6dfbc0, address which referenced memory

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4218

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 7105

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

    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:  a

BUGCHECK_P1: fffff8014a6e00bc

BUGCHECK_P2: ff

BUGCHECK_P3: 91

BUGCHECK_P4: fffff8014a6dfbc0

WRITE_ADDRESS: fffff8014b0fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8014b00f340: Unable to get Flags value from nt!KdVersionBlock
fffff8014b00f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
fffff8014a6e00bc

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

TRAP_FRAME:  ffff8003c4029530 -- (.trap 0xffff8003c4029530)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000003d5 rbx=0000000000000000 rcx=c1cdd348ca8be67d
rdx=fffff8014a6e00bc rsi=0000000000000000 rdi=0000000000000000
rip=fffff8014a6dfbc0 rsp=ffff8003c40296c0 rbp=0000000000000001
r8=0000000000000020  r9=fffff8014a6e008c r10=000000000000a518
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na po nc
nt!KiSwapThread+0x120:
fffff801`4a6dfbc0 48890a          mov     qword ptr [rdx],rcx ds:fffff801`4a6e00bc=c1cdd348ca8b4165
Resetting default scope

STACK_TEXT:
ffff8003`c40293e8 fffff801`4a806569     : 00000000`0000000a fffff801`4a6e00bc 00000000`000000ff 00000000`00000091 : nt!KeBugCheckEx
ffff8003`c40293f0 fffff801`4a802869     : ffffd281`d3880180 fffff801`4a7fb7b2 000f8067`b4bbbdff 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffff8003`c4029530 fffff801`4a6dfbc0     : ffffe50f`f590f080 fffff801`00000000 ffffe50f`ea010100 fffff801`00000001 : nt!KiPageFault+0x469
ffff8003`c40296c0 fffff801`4a6df4cf     : ffff900b`61b13310 fffff801`5448d272 00000000`00000000 ffffe50f`00000000 : nt!KiSwapThread+0x120
ffff8003`c4029770 fffff801`4a6e2e03     : ffffe50f`00000000 ffffe50f`00000000 00000000`00000000 00000000`00000001 : nt!KiCommitThreadWait+0x14f
ffff8003`c4029810 fffff801`4a6e2838     : ffffe50f`f5aab680 00000000`00000001 ffffe50f`f5a23200 fffff801`00000000 : nt!KeRemoveQueueEx+0x263
ffff8003`c40298b0 fffff801`4aa5ee3d     : 00000000`00000000 00000000`00000000 ffffd281`d3880180 fffff801`4a6c4bca : nt!IoRemoveIoCompletion+0x98
ffff8003`c40299e0 fffff801`4a805fb8     : ffffe50f`f5ad60c0 00000000`0dc1ec58 ffff8003`c4029aa8 00000000`0c202b1c : nt!NtRemoveIoCompletion+0x13d
ffff8003`c4029a90 00000000`77651cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0dc1ec38 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77651cfc


SYMBOL_NAME:  nt!KiSwapThread+120

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  120

FAILURE_BUCKET_ID:  AV_nt!KiSwapThread

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3a5eca23-a992-0c0e-a0ce-d48add0d8eda}

Followup:     MachineOwner
---------
Memtest yaptım, bir sorun çıkmadı. BIOS güncellemede attığın dosyaya bastığımda fotoğraf görüntüleyicisi açılıyor nasıl yapmam gerektiğini bilmiyorum sanırım. Sistemi alalı 1 ay olmadı..
 
@gorkem22tr BIOS güncelleme için bu rehbere bakabilirsiniz:
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.


MemTest86 sırasında XMP açık mıydı?
 
@gorkem22tr BIOS güncelleme için bu rehbere bakabilirsiniz:
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.


Memtest86 sırasında XMP açık mıydı?


Windows Memory test yaptım ben Memtest'i de beceremedim sanırım güncellemeyi deneyip dönüş yapacağım.
 
Windows Memory test yaptım ben Memtest'i de beceremedim sanırım güncellemeyi deneyip dönüş yapacağım.
BIOS'unu güncelliyormuşsun, bu güzel. Bellek testi konusunda Windows Bellek Tanılama yetersiz kalıyor. Testi Memtest86 ile yapmalısın. @yika38'in attığı linkteki videoya bakarsan çok basit ve anlaşılır bir işlem zaten, açtıktan sonra sonuna kadar bitmesini beklemelisin. Umarım testi yaparsın, geri dönüş yapmayı unutma.
 
BIOS'unu güncelliyormuşsun, bu güzel. Bellek testi konusunda Windows bellek tanılama yetersiz kalıyor. Testi Memtest86 ile yapmalısın. @yika38'in attığı linkteki videoya bakarsan çok basit ve anlaşılır bir işlem zaten, açtıktan sonra sonuna kadar bitmesini beklemelisin. Umarım testi yaparsın, geri dönüş yapmayı unutma.

BIOS güncellememi yaptım. Memtest'i de az önce bitirdim hiçbir sorun çıkmadı. Bir süre kullandıktan sonra tekrar geri dönüş yaparım görünen o ki sorun BIOS güncellemesiymiş. Sorun çıkması durumunda sizi etiketleyip tekrardan minidump dosyamı paylaşırım. Şimdilik iyi günler. İki üç gün içinde geri dönüş yapacağım.
BIOS'unu güncelliyormuşsun, bu güzel. Bellek testi konusunda Windows bellek tanılama yetersiz kalıyor. Testi Memtest86 ile yapmalısın. @yika38'in attığı linkteki videoya bakarsan çok basit ve anlaşılır bir işlem zaten, açtıktan sonra sonuna kadar bitmesini beklemelisin. Umarım testi yaparsın, geri dönüş yapmayı unutma.

Bugün tekrardan farklı bir sorunla mavi ekran hatası aldım PUBG oynarken... Yardımcı olursan sevinirim minidump bırakıyorum.
En son tekrardan görseldeki hatayı aldım sorun maalesef hala çözülmedi.

@gorkem22tr BIOS güncelleme için bu rehbere bakabilirsiniz:
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.


Memtest86 sırasında XMP açık mıydı?


BIOS'unu güncelliyormuşsun, bu güzel. Bellek testi konusunda Windows Bellek Tanılama yetersiz kalıyor. Testi Memtest86 ile yapmalısın. @yika38'in attığı linkteki videoya bakarsan çok basit ve anlaşılır bir işlem zaten, açtıktan sonra sonuna kadar bitmesini beklemelisin. Umarım testi yaparsın, geri dönüş yapmayı unutma.
 

Dosya Ekleri

  • a7fcc748-640d-45a9-be08-cc83f530ea7c.jpg
    a7fcc748-640d-45a9-be08-cc83f530ea7c.jpg
    97,3 KB · Görüntüleme: 65
Son düzenleme:
BIOS güncellememi yaptım. Memtest'i de az önce bitirdim hiçbir sorun çıkmadı. Bir süre kullandıktan sonra tekrar geri dönüş yaparım görünen o ki sorun BIOS güncellemesiymiş. Sorun çıkması durumunda sizi etiketleyip tekrardan minidump dosyamı paylaşırım. Şimdilik iyi günler. İki üç gün içinde geri dönüş yapacağım.


Bugün tekrardan farklı bir sorunla mavi ekran hatası aldım PUBG oynarken... Yardımcı olursan sevinirim minidump bırakıyorum.
En son tekrardan görseldeki hatayı aldım sorun maalesef hala çözülmedi.
Tahminimce sürücü hatası, aygıt yöneticisinden SSD ya da HDD her neyse sürücüyü kaldırıp tekrar kurdurun ve firmware güncellemesi yapın.
 
Tüm öneriler dışında kendim bir çözüm yolu denedim. Ramlerimin çalışma hızı 3200 MHz idi. Bir forumda fazla çalışan RAM sebebiyle de mavi ekran hatası alabileceğimi gördüm ve RAM hızını 2666 MHz'e düşürdüm. Yaklaşık 6 saattir aktif kullanıyorum ve bir sıkıntı çıkmadı, eğer 2 gün içinde de çıkmazsa sorunu çözüldü olarak görüyorum. Tabi bu bir varsayım 8 saat sonra da mavi ekran verdiği olmuştu.
 
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.

Technopat Haberler

Yeni konular

Geri
Yukarı