APC_INDEX_MISMATCH mavi ekran hatası

İşletim sistemi
Windows 10
BIOS üzerinden XMP özelliğini kapatıp tekrar Memtest86 testi yapabilir misin?

XMP özelliğini bir süre kapalı kalsın.

Ek olarak ekran kartı sürücünü güncel değil ise güncelle.

Diskine HD Tune yazılımı ile "error scan" testi ve "health" sekmesini paylaş.

"sfc /scannow" rehberini uygula.
 
BIOS üzerinden XMP özelliğini kapatıp tekrar Memtest86 testi yapabilir misin?

XMP özelliğini bir süre kapalı kalsın.

Ek olarak ekran kartı sürücünü güncel değil ise güncelle.

Diskine HD Tune yazılımı ile "error scan" testi ve "health" sekmesini paylaş.

"SFC /scannow" rehberini uygula.

Dediklerini yapmaya gideyim ben, bu arada az önce de mavi ekran verdi.

Kod:
Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`59800000 PsLoadedModuleList = 0xfffff803`5a42a490
Debug session time: Fri Apr 2 00:26:12.574 2021 (UTC + 3:00)
System Uptime: 0 days 0:06:53.196
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
................................
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`59bf5db0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe604`a5d23950=0000000000000001
3: kd> !analyze -v
*******************************************************************************
* *
* 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: 00007ffccba4cef4, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffe604a5d23b80, Call type (0 - system call, 1 - worker routine)

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3062

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 54881

Key : Analysis.Init.CPU.mSec
Value: 531

Key : Analysis.Init.Elapsed.mSec
Value: 140287

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

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

BUGCHECK_CODE: 1

BUGCHECK_P1: 7ffccba4cef4

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: ffffe604a5d23b80

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

PROCESS_NAME: WMIADAP.exe

STACK_TEXT:
ffffe604`a5d23948 fffff803`59c07d69 : 00000000`00000001 00007ffc`cba4cef4 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffffe604`a5d23950 fffff803`59c07c33 : 00000000`00000080 00000000`00014c81 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffe604`a5d23a90 00007ffc`cba4cef4 : 00007ffc`c954efef 00000000`00000000 000000ed`876ef098 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
000000ed`876eec68 00007ffc`c954efef : 00000000`00000000 000000ed`876ef098 00000000`00000000 00000000`00000000 : ntdll!NtQueryValueKey+0x14
000000ed`876eec70 00007ffc`c954e9a3 : 000000ed`876ef068 00007ffc`c13aa128 00007ffc`c13aa198 000000ed`876ef0a8 : KERNELBASE!LocalBaseRegQueryValue+0x17f
000000ed`876eefb0 00007ffc`c135e7a1 : 00000000`00000174 00000000`00000174 00000000`00000004 000000ed`876ef0c8 : KERNELBASE!RegQueryValueExW+0xf3
000000ed`876ef050 00000000`00000174 : 00000000`00000174 00000000`00000004 000000ed`876ef0c8 000000ed`876ef0ac : wbemcomn!Throttle+0x1a1
000000ed`876ef058 00000000`00000174 : 00000000`00000004 000000ed`876ef0c8 000000ed`876ef0ac 000000ed`876ef0a8 : 0x174
000000ed`876ef060 00000000`00000004 : 000000ed`876ef0c8 000000ed`876ef0ac 000000ed`876ef0a8 0000027b`8e1f0000 : 0x174
000000ed`876ef068 000000ed`876ef0c8 : 000000ed`876ef0ac 000000ed`876ef0a8 0000027b`8e1f0000 000000ed`876ef149 : 0x4
000000ed`876ef070 000000ed`876ef0ac : 000000ed`876ef0a8 0000027b`8e1f0000 000000ed`876ef149 0000000a`00000000 : 0x000000ed`876ef0c8
000000ed`876ef078 000000ed`876ef0a8 : 0000027b`8e1f0000 000000ed`876ef149 0000000a`00000000 0000012c`00000002 : 0x000000ed`876ef0ac
000000ed`876ef080 0000027b`8e1f0000 : 000000ed`876ef149 0000000a`00000000 0000012c`00000002 00000000`00000000 : 0x000000ed`876ef0a8
000000ed`876ef088 000000ed`876ef149 : 0000000a`00000000 0000012c`00000002 00000000`00000000 00000001`00000004 : 0x0000027b`8e1f0000
000000ed`876ef090 0000000a`00000000 : 0000012c`00000002 00000000`00000000 00000001`00000004 00000064`00989680 : 0x000000ed`876ef149
000000ed`876ef098 0000012c`00000002 : 00000000`00000000 00000001`00000004 00000064`00989680 00000000`00000174 : 0x0000000a`00000000
000000ed`876ef0a0 00000000`00000000 : 00000001`00000004 00000064`00989680 00000000`00000174 00000000`00000008 : 0x0000012c`00000002

SYMBOL_NAME: nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1fe

FAILURE_BUCKET_ID: 0x1_SysCallNum_17_nt!KiSystemServiceExitPico

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {23f7ad48-43c8-00ca-9cb7-932ab9140c73}

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

HD Tune ile tarama yaptım sıkıntı çıkmadı, health kısmını da SS aldım ama RAM testi yaptığım için telefondan yazıyorum şu an. XMP özelliği de kapalıymış zaten

BIOS üzerinden XMP özelliğini kapatıp tekrar Memtest86 testi yapabilir misin?

XMP özelliğini bir süre kapalı kalsın.

Ek olarak ekran kartı sürücünü güncel değil ise güncelle.

Diskine HD Tune yazılımı ile "error scan" testi ve "health" sekmesini paylaş.

"SFC /scannow" rehberini uygula.

Test sonuçları.
 

Dosya Ekleri

  • 02-Nisan-2021_01-27.png
    02-Nisan-2021_01-27.png
    61,1 KB · Görüntüleme: 47
  • 2021-04-02 at 08.55.59.jpeg
    2021-04-02 at 08.55.59.jpeg
    35,4 KB · Görüntüleme: 39
  • 2021-04-02 at 08.56.00 .jpeg
    2021-04-02 at 08.56.00 .jpeg
    71,6 KB · Görüntüleme: 37
Tam olarak sorunu belirleyemedim.

Olay görüntüleyicisi raporunu paylaş.

"DISM" rehberini uygula.

Ekran kartı sürücün güncelliğini kontrol eder misin? Güncel değil ise güncelle.

Sürücüleri her zaman güncel tutun.
 
Tam olarak sorunu belirleyemedim.

Olay görüntüleyicisi raporunu paylaş.

"DISM" rehberini uygula.

Ekran kartı sürücün güncelliğini kontrol eder misin? Güncel değil ise güncelle.

Sürücüleri her zaman güncel tutun.
son mavi ekran,

olay görüntüleyicisi raporu,

ekran kartını 'nvidia experience' den güncelledim 2 gün önce. Diğer sürücüler de güncel olması lazım ama ben sürekli mavi ekran alıyorum. Pc başında olmadığım her zaman
 
Benzer sorun.

Acaba işlemcin kronik sorunlu mu? Çünkü R5 3500X kullanan birisi her türlü şeyi denedi ve çözemedi. İşlemciyi değiştirince sorunun çözülmüştü. Hatta o konu ile ben ilgilenmiştim.

MEMORY.dmp dosyasını paylaşabilir misin? Minidump dosyaların bulunduğu yerlerde olmalı. Biraz oralara bakın, bulacağınıza eminim.

Yonga seti sürücünü güncelle.
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.
 
Benzer sorun.

Acaba işlemcin kronik sorunlu mu? Çünkü R5 3500X kullanan birisi her türlü şeyi denedi ve çözemedi. İşlemciyi değiştirince sorunun çözülmüştü. Hatta o konu ile ben ilgilenmiştim.

MEMORY.dmp dosyasını paylaşabilir misin? Minidump dosyaların bulunduğu yerlerde olmalı. Biraz oralara bakın, bulacağınıza eminim.

Yonga seti sürücünü güncelle.
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.
3 gün önce Windowsu sıfırladım. Mavi ekran almadım o zamandan beri, yine de çok teşekkürler yardımlarınız için.
Benzer sorun.

Acaba işlemcin kronik sorunlu mu? Çünkü R5 3500X kullanan birisi her türlü şeyi denedi ve çözemedi. İşlemciyi değiştirince sorunun çözülmüştü. Hatta o konu ile ben ilgilenmiştim.

MEMORY.dmp dosyasını paylaşabilir misin? Minidump dosyaların bulunduğu yerlerde olmalı. Biraz oralara bakın, bulacağınıza eminim.

Yonga seti sürücünü güncelle.
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.

Sıfırlamadan sonra tekrar mavi ekran yedim ikisi de visual studio programındayken oldu bakabilir misin?
 
Sisteme takılı SSD'yi değişirseniz sorun çözülecektir. Başka bir sorunuz var mı?

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: fffff8073aa35968, The address that the exception occurred at
Arg3: ffff8b0ff2a12a78, Exception Record Address
Arg4: ffff8b0ff2a122b0, Context Record Address

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


KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 10483

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 24253

Key : Analysis.Init.CPU.mSec
Value: 1093

Key : Analysis.Init.Elapsed.mSec
Value: 3458

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

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


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8073aa35968

BUGCHECK_P3: ffff8b0ff2a12a78

BUGCHECK_P4: ffff8b0ff2a122b0

EXCEPTION_RECORD: ffff8b0ff2a12a78 -- (.exr 0xffff8b0ff2a12a78)
ExceptionAddress: fffff8073aa35968 (nt!MmEnumerateAddressSpaceAndReferenceImages+0x0000000000000128)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000002c194b660
Attempt to read from address 00000002c194b660

CONTEXT: ffff8b0ff2a122b0 -- (.cxr 0xffff8b0ff2a122b0)
rax=0000000000000000 rbx=ffffc80d66f03570 rcx=ffffe404c579b6e0
rdx=0000000000000003 rsi=ffffe404c19502a0 rdi=00000002c194b660
rip=fffff8073aa35968 rsp=ffff8b0ff2a12cb0 rbp=ffffe404c6814040
r8=00000000ffffffff r9=7fffe404c2a72168 r10=7ffffffffffffffc
r11=ffffe404c3f90000 r12=ffffe404c4116b10 r13=ffffc80d66f03000
r14=ffffe404bfe78080 r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00050206
nt!MmEnumerateAddressSpaceAndReferenceImages+0x128:
fffff807`3aa35968 48390f cmp qword ptr [rdi],rcx ds:002b:00000002`c194b660=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: NVIDIA Web Helper.exe

READ_ADDRESS: fffff8073b0fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
00000002c194b660

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: 00000002c194b660

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffff8b0f`f2a12cb0 fffff807`3aa38b03 : ffffe404`c4feda01 00000000`00000000 fffff807`3ab80501 00000000`00000001 : nt!MmEnumerateAddressSpaceAndReferenceImages+0x128
ffff8b0f`f2a12d40 fffff807`3ab807a9 : ffffe404`bfe78080 fffff807`3ab80501 ffffe404`bfe78080 ffff8b0f`f2a12fe0 : nt!EtwpEnumerateAddressSpace+0x15f
ffff8b0f`f2a12ef0 fffff807`3a9eeb9b : ffffe404`c68e6080 fffff807`3ab805b0 ffffe404`bfe78080 ffff8b0f`f2a13118 : nt!EtwpProcessEnumCallback+0x1f9
ffff8b0f`f2a12f90 fffff807`3ab80554 : 00000000`00002000 ffff8b0f`f2a13030 ffff8b0f`f2a13118 ffffe404`00000000 : nt!PsEnumProcesses+0x37
ffff8b0f`f2a12fc0 fffff807`3ab80340 : 00000000`00000000 ffff8b0f`f2a13118 00000000`00000001 ffffe404`c4feda40 : nt!EtwpProcessThreadImageRundown+0xc0
ffff8b0f`f2a13050 fffff807`3ab80189 : ffff8b0f`f2a131a0 00000000`00000000 00000000`0000001f ffffe404`c4fedd00 : nt!EtwpKernelTraceRundown+0x98
ffff8b0f`f2a130c0 fffff807`3ab7ff3b : 27a408e6`449f6c82 44e68b61`fcf23a83 ffffe404`c4feda40 00000000`00000005 : nt!EtwpUpdateGroupMasks+0x22d
ffff8b0f`f2a13180 fffff807`3aa7a3b5 : 00000000`0000001f ffffe404`00000000 ffffc80d`621d3800 00000000`0000001f : nt!EtwpUpdateLoggerGroupMasks+0x73
ffff8b0f`f2a131e0 fffff807`3aba1031 : ffffc80d`bfd34050 ffffc80d`bfd34104 ffffc80d`bfd34050 00000000`00000000 : nt!EtwpStartLogger+0xad9
ffff8b0f`f2a13350 fffff807`3aba0399 : fffff807`3abca1f0 ffffc80d`c5b07dd0 00000000`000000c0 fffff807`3abca1f0 : nt!EtwStartAutoLogger+0x9f5
ffff8b0f`f2a13b00 fffff807`3aba13e4 : 00000000`00000007 fffff807`3aba12c0 ffffe404`b4869ca0 ffffe404`b4869ca0 : nt!PerfDiagpStartPerfDiagLogger+0xdd
ffff8b0f`f2a13b30 fffff807`3a625975 : ffffe404`00000000 ffffe404`c6814040 ffffe404`b4869ca0 ffffe404`00000000 : nt!PerfDiagpProxyWorker+0x124
ffff8b0f`f2a13b70 fffff807`3a717e85 : ffffe404`c6814040 00000000`00000080 ffffe404`b4889040 00000000`00000000 : nt!ExpWorkerThread+0x105
ffff8b0f`f2a13c10 fffff807`3a7fd408 : fffff807`38599180 ffffe404`c6814040 fffff807`3a717e30 00000000`00da8250 : nt!PspSystemThreadStartup+0x55
ffff8b0f`f2a13c60 00000000`00000000 : ffff8b0f`f2a14000 ffff8b0f`f2a0e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nt!MmEnumerateAddressSpaceAndReferenceImages+128

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.906

STACK_COMMAND: .cxr 0xffff8b0ff2a122b0 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 128

FAILURE_BUCKET_ID: AV_nt!MmEnumerateAddressSpaceAndReferenceImages

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3158f380-acfe-21f7-ef14-eca155652c23}

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

*******************************************************************************
* *
* 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: 0000007800000001, 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: fffff80539c4ee6b, address which referenced memory

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 10577

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 31654

Key : Analysis.Init.CPU.mSec
Value: 1140

Key : Analysis.Init.Elapsed.mSec
Value: 3480

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

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


BUGCHECK_CODE: a

BUGCHECK_P1: 7800000001

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80539c4ee6b

READ_ADDRESS: fffff8053a6fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000007800000001

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff10356a37710 -- (.trap 0xfffff10356a37710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007800000001 rbx=0000000000000000 rcx=fffff10356a45948
rdx=ffff8f054bf14788 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80539c4ee6b rsp=fffff10356a378a8 rbp=0000000000000000
r8=fffff10356a45948 r9=fffff10356a45948 r10=0000000000000000
r11=fffff10356a45948 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!RtlRbRemoveNode+0x39b:
fffff805`39c4ee6b 488b07 mov rax,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

STACK_TEXT:
fffff103`56a375c8 fffff805`39e07d69 : 00000000`0000000a 00000078`00000001 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff103`56a375d0 fffff805`39e04069 : 00000000`00000000 00000000`0000000f 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff103`56a37710 fffff805`39c4ee6b : 00000000`00000048 ffff8f05`4bf14770 fffff805`39c43215 00000000`00000000 : nt!KiPageFault+0x469
fffff103`56a378a8 fffff805`39c43215 : 00000000`00000000 ffff8f05`4bf147f2 00000000`00000000 fffff805`3a631dc0 : nt!RtlRbRemoveNode+0x39b
fffff103`56a378c0 fffff805`39c43060 : ffff8f05`4bf14788 00000000`00000003 00000000`00000005 ffff8f05`4bf14788 : nt!KiRemoveTimer2+0x95
fffff103`56a37910 fffff805`39c07184 : 00000000`00000000 00000000`00000000 00000000`00000008 00000000`001e179f : nt!KiTimer2Expiration+0x200
fffff103`56a379d0 fffff805`39df991e : ffffffff`00000000 ffffc501`11b40180 ffffc501`11b4b1c0 ffff8f05`540c50c0 : nt!KiRetireDpcList+0x874
fffff103`56a37c60 00000000`00000000 : fffff103`56a38000 fffff103`56a32000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: nt!RtlRbRemoveNode+39b

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.906

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 39b

FAILURE_BUCKET_ID: AV_nt!RtlRbRemoveNode

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9b43c07a-2da2-b63c-46ab-1c788c8a28c1}

Followup: MachineOwner
---------[/CODE]
 

Geri
Yukarı