R5 3500X sistemde mavi ekran hatası

İşletim sistemi
Windows 10

kaan2255

Centipat
Katılım
1 Mayıs 2024
Mesajlar
6
Daha fazla  
Cinsiyet
Erkek
Minidump Rapor Linki
https://drive.google.com/file/d/10n78ZbRgAOUbFCR4HZDJMIYUy1hv-5tQ/view?usp=sharing
RAM
GSkill 16 GB
SSD veya HDD modeli
Sandisk SSD Plus 240 gb HDD : ST1000DM003-9YN162
Ekran kartı
RX580 8 GB
Anakart
B450 MS2H
İşlemci
R5 3500X
Ryzen 5 3500X RX 580 8 GB.
Oyun oynarken hata almazken masaüstünde herhangi bir şey yaparken sürekli olarak alıyorum.

Minidump mevcut. Ne yapabilirim?
 
Son düzenleyen: Moderatör:
  • Ekran kartı sürücüleri.
  • Ağ kartı sürücüleri.
  • Ses kartı sürücüleri.
  • Anakart ve çipset sürücüleri.
Bu sürücüler güncel değilse güncelleyin. Güncel olmayan sürücüleri biliyorsanız uygun sürücüleri paylaşalım.

Sürücüler güncelse sfc/scannow ile sistemi tarayın.

Son zamanlarda sisteme yeni bir donanım eklediyseniz donanımın uyumlu olduğundan ve doğru şekilde takıldığını teyit edin.

Memtest86 ile RAM'leri test edin.


Bu adımları tek tek deneyip sonucu gözlemleyin bakalım.
 
  • Ekran kartı sürücüleri.
  • Ağ kartı sürücüleri.
  • Ses kartı sürücüleri.
  • Anakart ve çipset sürücüleri.
Bu sürücüler güncel değilse güncelleyin. Güncel olmayan sürücüleri biliyorsanız uygun sürücüleri paylaşalım.

Sürücüler güncelse sfc/scannow ile sistemi tarayın.

Son zamanlarda sisteme yeni bir donanım eklediyseniz donanımın uyumlu olduğundan ve doğru şekilde takıldığını teyit edin.

Memtest86 ile RAM'leri test edin.


Bu adımları tek tek deneyip sonucu gözlemleyin bakalım.

Hocam her mavi ekran sürücü kaynaklı olmuyor. Lm komutunu girerek hangi modüller sıkıntılı ise onları söylemeniz daha mantıklı olur. Çünkü dedikleriniz ile pek alakası yok durumun.

Özellikle RAM kısmında hardware RAM veya MEMORY_MANAGEMENT dışında genelde RAM kaynaklı hata olmaz. Belirtmek istedim.

Ekran kartı sürücüsünün güncelliğini kontrol etmek için;

NVIDIA ise: lmvm nvlddmkm.
AMD ise: lmvm amdkmdag.
Intel ise: lmvm igdkmdn64.

Komutunu girmeniz yeterli. Sürücü tarihini son çıkan ile karşılaştırıp dönüt verebilirsiniz.

Ryzen 5 3500X RX 580 8 GB.
Oyun oynarken hata almazken masaüstünde herhangi bir şey yaparken sürekli olarak alıyorum.

Minidump mevcut. Ne yapabilirim?

Kullandığın SSD kronik sorunlu ondan kaynaklı yapıyor muhtemelen. CrystalDiskMark ile okuma yazma testi yapın.
 
@GFYT hocam yönetim görevi nedeniyle geç döndüm.

Deneyim elde etme amaçlı konulara girişmek istedim.

Minidump dosyalarını atayım, incelemem gereken yeri daha iyi açıklarsanız doğrusunu öğrenip konu sahibine de yardımcı oluruz beraber.

AMD ise: Lmvm amdkmdag.

Teşekkürler hocam. ntkrnlmp.exe (kernel sürücüsü) tespit ettim. Anakart BIOS'unu son sürüme yükselterek deneme yapılabilir.

Anakart markası yazılmadığından uygun sürücüyü paylaşamıyorum.

Kod:
*******************************************************************************
* *
* 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: 000000000000003f, memory referenced.
Arg2: 0000000000000002, IRQL.
Arg3: 0000000000000001, 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: fffff8034d238a72, address which referenced memory.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1781.

 Key : Analysis.Elapsed.mSec
 Value: 2534.

 Key : Analysis.IO.Other.Mb
 Value: 0

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 0

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

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0xa.

 Key : Bugcheck.Code.TargetModel
 Value: 0xa.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Failure.Bucket
 Value: AV_nt!KiSwapThread

 Key : Failure.Hash
 Value: {3a5eca23-a992-0c0e-a0ce-d48add0d8eda}

BUGCHECK_CODE: a

BUGCHECK_P1: 3f.

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8034d238a72.

FILE_IN_CAB: 061924-8593-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

WRITE_ADDRESS: fffff8034dcfb390: 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
 000000000000003f.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Discord.exe

TRAP_FRAME: ffff990720d4f530 -- (.trap 0xffff990720d4f530)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000003f
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8034d238a72 rsp=ffff990720d4f6c0 rbp=0000000000000000
 r8=0000000000000020 r9=0000000000000001 r10=0000000000000480
r11=ffffb20052b69180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc.
nt!KiSwapThread+0x542:
fffff803`4d238a72 488901 mov qword ptr [rcx],rax ds:00000000`0000003f=????????????????
Resetting default scope.

STACK_TEXT:
ffff9907`20d4f3e8 fffff803`4d4123a9 : 00000000`0000000a 00000000`0000003f 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffff9907`20d4f3f0 fffff803`4d40dd78 : ffffc483`3f4f7080 fffff803`4d406a18 ffffb200`52b69180 ffffffff`ffffffff : nt!KiBugCheckDispatch+0x69
ffff9907`20d4f530 fffff803`4d238a72 : ffffb200`52b69180 fffff803`ffffffff ffff0c00`0d0d7200 ffffc483`4046fbf0 : nt!KiPageFault+0x478
ffff9907`20d4f6c0 fffff803`4d237f5f : ffff9907`00000001 ffff9907`00000003 00000000`0000003f 00000000`00000000 : nt!KiSwapThread+0x542
ffff9907`20d4f770 fffff803`4d210d03 : ffffc483`00000000 fffff803`00000000 ffffb200`52f9e100 00000000`00000001 : nt!KiCommitThreadWait+0x14f
ffff9907`20d4f810 fffff803`4d210738 : ffffc483`400d7200 00000000`00000001 00006709`00000000 00000000`00000000 : nt!KeRemoveQueueEx+0x263
ffff9907`20d4f8b0 fffff803`4d6c895d : 00000000`00000000 ffffb200`52b69180 ffffc483`404e4080 00000000`00000000 : nt!IoRemoveIoCompletion+0x98
ffff9907`20d4f9e0 fffff803`4d411b05 : ffffc483`3f4f7080 00000001`defff0a8 ffff9907`20d4faa8 00006709`002e4d80 : nt!NtRemoveIoCompletion+0x13d
ffff9907`20d4fa90 00007ffa`3f9ad684 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000001`defff088 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`3f9ad684

SYMBOL_NAME: nt!KiSwapThread+542

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.4522

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 542.

FAILURE_BUCKET_ID: AV_nt!KiSwapThread

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled.
Arg2: 0000525a000c2990, The address that the exception occurred at.
Arg3: 0000000000000008, Parameter 0 of the exception.
Arg4: 0000525a000c2990, Parameter 1 of the exception.

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: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: ContextRecord ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 2656.

 Key : Analysis.Elapsed.mSec
 Value: 2662.

 Key : Analysis.IO.Other.Mb
 Value: 0

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 0

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

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x1e.

 Key : Bugcheck.Code.TargetModel
 Value: 0x1e.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Failure.Bucket
 Value: AV_nt!KiDispatchException

 Key : Failure.Hash
 Value: {00781d15-b897-afab-75cd-f83221cbf387}

BUGCHECK_CODE: 1e.

BUGCHECK_P1: ffffffffc0000005.

BUGCHECK_P2: 525a000c2990.

BUGCHECK_P3: 8

BUGCHECK_P4: 525a000c2990.

FILE_IN_CAB: 061924-7937-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

EXCEPTION_PARAMETER1: 0000000000000008.

EXCEPTION_PARAMETER2: 0000525a000c2990.

WRITE_ADDRESS: fffff8001a4fb390: 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
 0000525a000c2990.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Discord.exe

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
ffffe502`0ee75d98 fffff800`19c9d1f7 : 00000000`0000001e ffffffff`c0000005 0000525a`000c2990 00000000`00000008 : nt!KeBugCheckEx
ffffe502`0ee75da0 fffff800`19c124ec : 00000000`00001000 ffffe502`0ee76640 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x13fb37
ffffe502`0ee76460 fffff800`19c0dd52 : ffffd50a`2935f080 00000000`00000000 ffffe781`26f69180 ffffd50a`29b56988 : nt!KiExceptionDispatch+0x12c
ffffe502`0ee76640 0000525a`000c2990 : 00000000`00000001 00000000`00000000 00000000`00000000 ffffd50a`29c1d5d0 : nt!KiPageFault+0x452
ffffe502`0ee767d0 00000000`00000001 : 00000000`00000000 00000000`00000000 ffffd50a`29c1d5d0 00000000`00000002 : 0x0000525a`000c2990
ffffe502`0ee767d8 00000000`00000000 : 00000000`00000000 ffffd50a`29c1d5d0 00000000`00000002 fffff800`19bf2504 : 0x1.

SYMBOL_NAME: nt!KiDispatchException+13fb37

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.4522

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 13fb37.

FAILURE_BUCKET_ID: AV_nt!KiDispatchException

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {00781d15-b897-afab-75cd-f83221cbf387}

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

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption.
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffff9a8226899560, Address of the trap frame for the exception that caused the BugCheck.
Arg3: ffff9a82268994b8, Address of the exception record for the exception that caused the BugCheck.
Arg4: 0000000000000000, Reserved.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1686.

 Key : Analysis.Elapsed.mSec
 Value: 1705.

 Key : Analysis.IO.Other.Mb
 Value: 0

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 0

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

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x139.

 Key : Bugcheck.Code.TargetModel
 Value: 0x139.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : FailFast.Name
 Value: CORRUPT_LIST_ENTRY.

 Key : FailFast.Type
 Value: 3

 Key : Failure.Bucket
 Value: 0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiInsertTimerTable

 Key : Failure.Hash
 Value: {f89e8bcc-9d62-a3aa-7602-6fa1ac774850}

BUGCHECK_CODE: 139.

BUGCHECK_P1: 3

BUGCHECK_P2: ffff9a8226899560.

BUGCHECK_P3: ffff9a82268994b8.

BUGCHECK_P4: 0

FILE_IN_CAB: 061924-8359-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

TRAP_FRAME: ffff9a8226899560 -- (.trap 0xffff9a8226899560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffdc0df6aee1a0 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffdc0df33351a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8031ae2f29f rsp=ffff9a82268996f0 rbp=0000000a0aa70269
 r8=0000000a06a751c6 r9=fffff803167de1f0 r10=fffff803167daac0
r11=ffff9a8226899800 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc.
nt!KiInsertTimerTable+0x1f543f:
fffff803`1ae2f29f cd29 int 29h.
Resetting default scope.

EXCEPTION_RECORD: ffff9a82268994b8 -- (.exr 0xffff9a82268994b8)
ExceptionAddress: fffff8031ae2f29f (nt!KiInsertTimerTable+0x00000000001f543f)
 ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
 ExceptionFlags: 00000001.
NumberParameters: 1
 Parameter[0]: 0000000000000003.
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: chrome.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y n tabanl bir arabelle in ta t n alg lad . Bu ta ma, k t niyetli bir kullan c n n bu uygulaman n denetimini ele ge irmesine olanak verebilir.

EXCEPTION_CODE_STR: c0000409.

EXCEPTION_PARAMETER1: 0000000000000003.

EXCEPTION_STR: 0xc0000409.

STACK_TEXT:
ffff9a82`26899238 fffff803`1ae123a9 : 00000000`00000139 00000000`00000003 ffff9a82`26899560 ffff9a82`268994b8 : nt!KeBugCheckEx
ffff9a82`26899240 fffff803`1ae12950 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffff6`00000007 : nt!KiBugCheckDispatch+0x69
ffff9a82`26899380 fffff803`1ae107f2 : 00000000`00000000 00000000`00000000 ffff9a82`26899590 ffff9a82`26899588 : nt!KiFastFailDispatch+0xd0
ffff9a82`26899560 fffff803`1ae2f29f : 00000000`00000000 ffffdc0d`ec54cd90 00000000`00000000 fffff803`1ac2d3f5 : nt!KiRaiseSecurityCheckFailure+0x332
ffff9a82`268996f0 fffff803`1ac381cd : ffffdc0d`f6aee080 ffffdc0e`00c5d990 00000000`00000000 ffffffff`ffffff00 : nt!KiInsertTimerTable+0x1f543f
ffff9a82`26899770 fffff803`1ac10d03 : 00000000`000000a9 fffff803`00000000 ffffdc0e`03b25201 00000000`00000001 : nt!KiCommitThreadWait+0x3bd
ffff9a82`26899810 fffff803`1ac10738 : ffffdc0d`f3357080 00000000`00000001 00002e80`00000000 00000000`00000002 : nt!KeRemoveQueueEx+0x263
ffff9a82`268998b0 fffff803`1b0c895d : 00000000`00000001 00000000`00000000 00000000`00000000 ffffdace`44f776a0 : nt!IoRemoveIoCompletion+0x98
ffff9a82`268999e0 fffff803`1ae11b05 : ffffdc0d`f6aee080 00000063`875ff3e8 ffff9a82`26899aa8 00002e80`078c4440 : nt!NtRemoveIoCompletion+0x13d
ffff9a82`26899a90 00007ffa`5302d684 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000063`875ff3c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`5302d684

SYMBOL_NAME: nt!KiInsertTimerTable+1f543f

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.4522

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 1f543f.

FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiInsertTimerTable

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {f89e8bcc-9d62-a3aa-7602-6fa1ac774850}

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: 00007fff43995ac4, Address of system call function or worker routine.
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 00000000ffff0000, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffd301dbfe2b80, Call type (0 - system call, 1 - worker routine)

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 2046.

 Key : Analysis.Elapsed.mSec
 Value: 2071.

 Key : Analysis.IO.Other.Mb
 Value: 0

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 0

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

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x1.

 Key : Bugcheck.Code.TargetModel
 Value: 0x1.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Failure.Bucket
 Value: 0x1_SysCallNum_1254_nt!KiSystemServiceExitPico

 Key : Failure.Hash
 Value: {5dcea0ef-c2cf-e842-f8d6-9d0dc2f5b655}

BUGCHECK_CODE: 1

BUGCHECK_P1: 7fff43995ac4.

BUGCHECK_P2: 0

BUGCHECK_P3: ffff0000.

BUGCHECK_P4: ffffd301dbfe2b80.

FILE_IN_CAB: 062024-7359-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffffd301`dbfe29b8 fffff804`228123a9 : 00000000`00000001 00007fff`43995ac4 00000000`00000000 00000000`ffff0000 : nt!KeBugCheckEx
ffffd301`dbfe29c0 fffff804`2281224d : ffffb90b`dc1c4540 ffffb90b`dc1c4540 00000238`63e4c638 00000000`00000020 : nt!KiBugCheckDispatch+0x69
ffffd301`dbfe2b00 00007fff`43995ac4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x361
00000058`4397f2b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`43995ac4

SYMBOL_NAME: nt!KiSystemServiceExitPico+361

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.4522

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 361.

FAILURE_BUCKET_ID: 0x1_SysCallNum_1254_nt!KiSystemServiceExitPico

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {5dcea0ef-c2cf-e842-f8d6-9d0dc2f5b655}

Followup: MachineOwner.
---------
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled.
Arg2: 0000000000000000, The address that the exception occurred at.
Arg3: 0000000000000008, Parameter 0 of the exception.
Arg4: 0000000000000000, Parameter 1 of the exception.

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: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: ContextRecord ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 2827.

 Key : Analysis.Elapsed.mSec
 Value: 2890.

 Key : Analysis.IO.Other.Mb
 Value: 0

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 0

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

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x1e.

 Key : Bugcheck.Code.TargetModel
 Value: 0x1e.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Failure.Bucket
 Value: AV_nt!KiDispatchException

 Key : Failure.Hash
 Value: {00781d15-b897-afab-75cd-f83221cbf387}

BUGCHECK_CODE: 1e.

BUGCHECK_P1: ffffffffc0000005.

BUGCHECK_P2: 0

BUGCHECK_P3: 8

BUGCHECK_P4: 0

FILE_IN_CAB: 062024-8109-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: chrome.exe

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
ffffb780`5928ad78 fffff800`2149d1f7 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
ffffb780`5928ad80 fffff800`214124ec : 00000000`00001000 ffffb780`5928b620 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x13fb37
ffffb780`5928b440 fffff800`2140dd52 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c
ffffb780`5928b620 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffa586`da63bcd8 : nt!KiPageFault+0x452

SYMBOL_NAME: nt!KiDispatchException+13fb37

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.4522

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 13fb37.

FAILURE_BUCKET_ID: AV_nt!KiDispatchException

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {00781d15-b897-afab-75cd-f83221cbf387}

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

KMODE_EXCEPTION_NOT_HANDLED (1e) hatasının analizinde sürücü kaynaklı hata olabileceğine değinilmiş. O yüzden öncelikli olarak sürücülerin teyit edilmesini istedim. 2 kez tekrarlandığı için göz ardı edilemeyeceğini varsaydım.

APC_INDEX_MISMATCH (1) çekirdek içi bir hata olduğunu biliyorum ve genellikle bir dosya sistemi veya sürücünün APC'leri (asynchronous procedure calls) devre dışı bırakma ve yeniden etkinleştirme çağrılarının uyumsuz olması nedeniyle oluşuyor diye biliyorum.

Genel çözüm sunma mâbında sürücülerden girilmesini, olmazsa teyit etme amaçlı analizin içine daha fazla girecektim.

RAM testinden girmesini isteme sebebim, ucu ister istemez dokunuyor ve son ihtimal olarak bakılmasını önermede zarar görmedim.

Eksik bir şey söylediysem rapor üzerinde belirtir misiniz? Bir yandan eksiğimi kapatır, bir yandan da konu sahibinin sorununu çözeriz.
 

Technopat Haberler

Yeni konular

Geri
Yukarı