Mavi ekran hatası

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff804482cde4b, The address that the exception occurred at
Arg3: ffffdf8e2d47d668, Exception Record Address
Arg4: ffffdf8e2d47cea0, Context Record Address

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 4937

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 10958

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

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff804482cde4b

BUGCHECK_P3: ffffdf8e2d47d668

BUGCHECK_P4: ffffdf8e2d47cea0

EXCEPTION_RECORD:  ffffdf8e2d47d668 -- (.exr 0xffffdf8e2d47d668)
ExceptionAddress: fffff804482cde4b (nt!RtlRbRemoveNode+0x000000000000039b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffdf8e2d47cea0 -- (.cxr 0xffffdf8e2d47cea0)
rax=00ffe187f6e72888 rbx=ffffe187eac00290 rcx=ffffe187f6e7b888
rdx=ffffe187f6e70888 rsi=0000000000000000 rdi=00ffe187f6e72888
rip=fffff804482cde4b rsp=ffffdf8e2d47d8a8 rbp=0000000000000100
 r8=ffffe187f6e5d888  r9=ffffe187f6e5d888 r10=0000000000000000
r11=ffffe187f6e74888 r12=ffffe187f6e68030 r13=ffffe187f6e68000
r14=0000000000000000 r15=ffffe187f6e70880
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!RtlRbRemoveNode+0x39b:
fffff804`482cde4b 488b07          mov     rax,qword ptr [rdi] ds:002b:00ffe187`f6e72888=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff80448cfa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80448c0f2e0: Unable to get Flags value from nt!KdVersionBlock
fffff80448c0f2e0: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 ffffffffffffffff

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

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
ffffdf8e`2d47d8a8 fffff804`482cd943     : 00000000`00000100 ffffe187`f6e6f880 00000000`00000000 ffffe187`f6e70880 : nt!RtlRbRemoveNode+0x39b
ffffdf8e`2d47d8c0 fffff804`482cd2b8     : ffffe187`eac00280 ffffe187`f6e68000 00000000`00000000 ffffdf8e`2d47d9c8 : nt!RtlpHpVsChunkCoalesce+0x183
ffffdf8e`2d47d920 fffff804`482cbc44     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpHpVsContextFree+0x188
ffffdf8e`2d47d9c0 fffff804`489b2019     : ffff928f`00000890 ffffe187`f6e70010 fffff804`48c51248 01000000`00100000 : nt!ExFreeHeapPool+0x4d4
ffffdf8e`2d47daa0 fffff804`4825ca47     : 00000000`00000100 00000000`00000000 ffffe187`f6e6f010 ffffe187`f6e70010 : nt!ExFreePool+0x9
ffffdf8e`2d47dad0 fffff804`483b8778     : 00000000`00000002 fffff804`48c51290 fffff804`48c510e0 ffffffff`ffffffff : nt!MiDeleteEmptySubsections+0xef
ffffdf8e`2d47db20 fffff804`48266dd5     : ffff928f`cc8e8080 ffff928f`cc8e8080 00000000`00000080 fffff804`483b8670 : nt!MiDereferenceSegmentThread+0x108
ffffdf8e`2d47dd50 fffff804`483fb4f8     : ffffba81`fa340180 ffff928f`cc8e8080 fffff804`48266d80 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x55
ffffdf8e`2d47dda0 00000000`00000000     : ffffdf8e`2d47e000 ffffdf8e`2d478000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!ExFreePool+9

IMAGE_NAME:  Pool_Corruption

IMAGE_VERSION:  10.0.19041.508

MODULE_NAME: Pool_Corruption

STACK_COMMAND:  .cxr 0xffffdf8e2d47cea0 ; kb

BUCKET_ID_FUNC_OFFSET:  9

FAILURE_BUCKET_ID:  AV_nt!ExFreePool

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {2ae0a97e-dcd7-47ef-dbfb-430f2cbf58a1}

Followup:     Pool_corruption
---------



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

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 8483

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 11721

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

BUGCHECK_P3: fffff307085478d0

BUGCHECK_P4: 0

CONTEXT:  fffff307085478d0 -- (.cxr 0xfffff307085478d0)
rax=0000000000190001 rbx=00ffd58f6b472190 rcx=00ffd58f6b472101
rdx=0000000000000001 rsi=0000000000000702 rdi=0000000000000001
rip=fffff807576e097c rsp=fffff307085482d0 rbp=ffffd58f633402a8
 r8=0000000000000000  r9=0000000000000001 r10=fffff807576e0960
r11=ffff777b1d200000 r12=0000000000000000 r13=0000000000000001
r14=0000000000000001 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!ExAcquireResourceExclusiveLite+0x1c:
fffff807`576e097c 0fb7431a        movzx   eax,word ptr [rbx+1Ah] ds:002b:00ffd58f`6b4721aa=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.504_none_e781e76525fb2

STACK_TEXT: 
fffff307`085482d0 fffff807`5b3bc090     : 00000000`00000001 00000000`00000000 ffffd58f`5ac57180 ffffab0e`1cf1d5a0 : nt!ExAcquireResourceExclusiveLite+0x1c
fffff307`08548360 fffff807`5b3bbe3c     : ffffd58f`633402a8 ffffab0e`1cf1d5a0 00000000`00000000 fffff807`00000001 : Ntfs!NtfsAcquireExclusiveFcb+0x90
fffff307`085483e0 fffff807`5b4cab6b     : 0000ffff`ffffff02 00000000`00000004 00000000`00000000 ffffd58f`63340201 : Ntfs!NtfsAcquireFcbWithPaging+0xac
fffff307`08548450 fffff807`5b46c493     : ffffd58f`633402a8 ffffd58f`5ac57180 ffffd58f`5ac59ac8 fffff307`085485c0 : Ntfs!NtfsTryOpenFcb+0x243
fffff307`08548520 fffff807`5b5f3f28     : ffffd58f`633402a8 ffffd58f`5ac57180 00000000`00000000 00000000`0000fffe : Ntfs!NtfsIterateMft+0x1ab
fffff307`085485b0 fffff807`5b563926     : fffff307`08548748 fffff807`5b3bc3fd 00000000`00000004 ffffd58f`61c4e4a0 : Ntfs!NtfsRepairStorageReserve+0x450
fffff307`08548690 fffff807`5b47e45d     : ffffd58f`633402a8 00000000`00000001 00000000`00000000 00000000`00000000 : Ntfs!NtfsUserFsRequest+0xe51a6
fffff307`08548710 fffff807`576d1f35     : ffffd58f`67cc9a20 fffff807`55384b46 ffffd58f`61c4e4a0 fffff307`08543000 : Ntfs!NtfsFsdFileSystemControl+0x17d
fffff307`08548830 fffff807`55386ccf     : ffffab0d`f0e00100 fffff807`576cbad2 ffffab0d`f0e00340 00000000`000000ff : nt!IofCallDriver+0x55
fffff307`08548870 fffff807`553bcaf4     : fffff307`08548900 00000000`00000000 ffffab0e`00000019 ffffd58f`5a6fba00 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f
fffff307`085488e0 fffff807`576d1f35     : 00000000`000000a7 ffffd58f`61c4e4a0 00000000`00000002 00000000`00000001 : FLTMGR!FltpFsControl+0x104
fffff307`08548940 fffff807`57aa6fb8     : fffff307`08548cc0 ffffd58f`61c4e4a0 00000000`00000001 ffffab0e`00000000 : nt!IofCallDriver+0x55
fffff307`08548980 fffff807`57aa6885     : 00000000`00000000 fffff307`08548cc0 00000000`00000000 fffff307`08548cc0 : nt!IopSynchronousServiceTail+0x1a8
fffff307`08548a20 fffff807`57a4ed76     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5e5
fffff307`08548b60 fffff807`578058b8     : 00000000`00000a78 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtFsControlFile+0x56
fffff307`08548bd0 00007ffa`b91cc4e4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000dd`6f1fd518 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`b91cc4e4


SYMBOL_NAME:  nt!ExAcquireResourceExclusiveLite+1c

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .cxr 0xfffff307085478d0 ; kb

BUCKET_ID_FUNC_OFFSET:  1c

FAILURE_BUCKET_ID:  0x3B_c0000005_nt!ExAcquireResourceExclusiveLite

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8a952d6e-9653-e332-6320-e4ba22371b9d}

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



CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a39fc1638098d58e, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 6444effe05cb5fa2, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    2a  : Type 4 pool corruption
    2b  : Modification of a function or .pdata
    2c  : Image integrity corruption
    2d  : Processor misconfiguration
    2e  : Type 5 process list corruption
    2f  : Process shadow corruption
    30  : Retpoline code page corruption
    101 : General pool corruption
    102 : Modification of win32k.sys

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 8327

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 9835

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

BUGCHECK_P1: a39fc1638098d58e

BUGCHECK_P2: 0

BUGCHECK_P3: 6444effe05cb5fa2

BUGCHECK_P4: 101

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  csrss.exe

STACK_TEXT: 
fffff989`6ed7ff68 00000000`00000000     : 00000000`00000109 a39fc163`8098d58e 00000000`00000000 6444effe`05cb5fa2 : nt!KeBugCheckEx


SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  BAD_STACK_0x109

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}

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