nsiproxy.sys
diye bir dosya sebep olmuş. Ne olduğu araştırdım ancak net bir bilgi bulamadığımdan bir şey demeyeceğim.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: 00007ff92890be14, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffb48e705e9b80, Call type (0 - system call, 1 - worker routine)
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3593
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: 3585
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
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: 7ff92890be14
BUGCHECK_P2: 0
BUGCHECK_P3: ffff
BUGCHECK_P4: ffffb48e705e9b80
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: chrome.exe
STACK_TEXT:
ffffb48e`705e99b8 fffff806`44806569 : 00000000`00000001 00007ff9`2890be14 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffffb48e`705e99c0 fffff806`44806433 : ffffcf0d`e6aa3080 ffffcf0d`e7618080 ffffb48e`705e9b18 ffffffff`fffd67f0 : nt!KiBugCheckDispatch+0x69
ffffb48e`705e9b00 00007ff9`2890be14 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000082`e1fff7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`2890be14
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
---------
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: ffffce0d435185f0, Address of the IRP
Arg2: 0000000000001232
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3592
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: 6547
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: 44
BUGCHECK_P1: ffffce0d435185f0
BUGCHECK_P2: 1232
BUGCHECK_P3: 0
BUGCHECK_P4: 0
IRP_ADDRESS: ffffce0d435185f0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Dragon.exe
STACK_TEXT:
ffffb887`79a2e688 fffff805`0c865934 : 00000000`00000044 ffffce0d`435185f0 00000000`00001232 00000000`00000000 : nt!KeBugCheckEx
ffffb887`79a2e690 fffff805`0c6c2fd7 : 00000000`00000000 00000000`00000002 00000000`00000070 ffffce0d`43518628 : nt!IopfCompleteRequest+0x1a2944
ffffb887`79a2e780 fffff805`1bb12714 : 00000000`00000000 ffffce0d`435186c0 ffffce0d`435185f0 0000004e`66eff5c0 : nt!IofCompleteRequest+0x17
ffffb887`79a2e7b0 fffff805`0c6cd805 : 00000000`00000002 00000000`00000000 ffffce0d`44954800 ffffce0d`3e37f060 : nsiproxy!NsippDispatch+0xb4
ffffb887`79a2e800 fffff805`0cac2528 : ffffce0d`435185f0 00000000`00000000 00000000`00000000 00000000`00000001 : nt!IofCallDriver+0x55
ffffb887`79a2e840 fffff805`0cac1df5 : 00000000`00000000 ffffb887`79a2eb80 00000000`00040800 ffffb887`79a2eb80 : nt!IopSynchronousServiceTail+0x1a8
ffffb887`79a2e8e0 fffff805`0cac17f6 : 00000000`00000001 00000000`00000dbc 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5e5
ffffb887`79a2ea20 fffff805`0c805fb8 : ffffce0d`4427f080 0000004e`66eff4a8 ffffb887`79a2eaa8 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
ffffb887`79a2ea90 00007ffe`1830be74 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000004e`66eff538 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`1830be74
SYMBOL_NAME: nsiproxy!NsippDispatch+b4
MODULE_NAME: nsiproxy
IMAGE_NAME: nsiproxy.sys
IMAGE_VERSION: 10.0.19041.1124
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: b4
FAILURE_BUCKET_ID: 0x44_nsiproxy!NsippDispatch
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {4fb9d960-49ca-744e-ae5b-568d82c21f53}
Followup: MachineOwner
---------
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: 00007ff83b0abe14, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffff900e0e995b80, Call type (0 - system call, 1 - worker routine)
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3468
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: 6354
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
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: 7ff83b0abe14
BUGCHECK_P2: 0
BUGCHECK_P3: ffff
BUGCHECK_P4: ffff900e0e995b80
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: EpicGamesLauncher.exe
STACK_TEXT:
ffff900e`0e9959b8 fffff803`5e006569 : 00000000`00000001 00007ff8`3b0abe14 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffff900e`0e9959c0 fffff803`5e006433 : 00000000`00000000 ffffc501`574bc860 ffff900e`0e995b18 ffffffff`fffe7960 : nt!KiBugCheckDispatch+0x69
ffff900e`0e995b00 00007ff8`3b0abe14 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000034`440cf918 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`3b0abe14
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
---------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8005aac1c9f, Address of the instruction which caused the bugcheck
Arg3: ffffaa89a08d0ee0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4671
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: 25018
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
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: fffff8005aac1c9f
BUGCHECK_P3: ffffaa89a08d0ee0
BUGCHECK_P4: 0
CONTEXT: ffffaa89a08d0ee0 -- (.cxr 0xffffaa89a08d0ee0)
rax=ffffe78800000000 rbx=00000000889922c0 rcx=0000000000000001
rdx=0000000000000000 rsi=ffffe788115bcc60 rdi=ffffe7881193edc0
rip=fffff8005aac1c9f rsp=ffffaa89a08d18e0 rbp=ffffaa89a08d1b80
r8=0000000000000204 r9=000000000000000c r10=ffffe7880713beb0
r11=ffffd70712b2eb40 r12=0000000000000000 r13=0000000000000000
r14=ffffe788115bcd78 r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
nt!IopXxxControlFile+0x48f:
fffff800`5aac1c9f 8b4030 mov eax,dword ptr [rax+30h] ds:002b:ffffe788`00000030=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Dragon.exe
STACK_TEXT:
ffffaa89`a08d18e0 fffff800`5aac17f6 : 00000000`00000001 00000000`00000614 00000000`00000000 00000223`1aeb27e8 : nt!IopXxxControlFile+0x48f
ffffaa89`a08d1a20 fffff800`5a805fb8 : 00000000`00000000 000000a4`df23f118 ffffaa89`00000000 ffffe788`127262e0 : nt!NtDeviceIoControlFile+0x56
ffffaa89`a08d1a90 00007ffc`18e8be74 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000a4`df23f628 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`18e8be74
SYMBOL_NAME: nt!IopXxxControlFile+48f
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.572
STACK_COMMAND: .cxr 0xffffaa89a08d0ee0 ; kb
BUCKET_ID_FUNC_OFFSET: 48f
FAILURE_BUCKET_ID: 0x3B_c0000005_nt!IopXxxControlFile
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {657bb511-7f5c-7ddc-acd3-e126b6d359c8}
Followup: MachineOwner
---------
Tüm işlemleri uyguladıktan sonra tekrar alırsanız sadece yeni minidump dosyanızı paylaşırsınız. Yarına kadar ise tekrar hata almazsanız lütfen tekrar gelip sorununuzun çözüldüğünü belirtmeyi unutmayın.
Tüm işlemleri uyguladıktan sonra tekrar alırsanız sadece yeni minidump dosyanızı paylaşırsınız. Yarına kadar ise tekrar hata almazsanız lütfen tekrar gelip sorununuzun çözüldüğünü belirtmeyi unutmayın.
Bu sitenin çalışmasını sağlamak için gerekli çerezleri ve deneyiminizi iyileştirmek için isteğe bağlı çerezleri kullanıyoruz.