*******************************************************************************
* *
* 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: fffff78000481020, 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: fffff80530e8b5c6, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1405
Key : Analysis.Elapsed.mSec
Value: 2509
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: 202
Key : Analysis.Init.Elapsed.mSec
Value: 2525
Key : Analysis.Memory.CommitPeak.Mb
Value: 136
Key : Bugcheck.Code.LegacyAPI
Value: 0xa
Key : Failure.Bucket
Value: AV_nt!KiExecuteAllDpcs
Key : Failure.Hash
Value: {b88a28a0-fcde-99e9-6174-619833d00ab9}
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: a
BUGCHECK_P1: fffff78000481020
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80530e8b5c6
FILE_IN_CAB: 060423-4359-01.dmp
READ_ADDRESS: fffff805318fb390: 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
fffff78000481020
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: linpack.exe
DPC_STACK_BASE: FFFFD18F81A97FB0
TRAP_FRAME: ffffd18f81a97a20 -- (.trap 0xffffd18f81a97a20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000003e6ed3bea91 rbx=0000000000000000 rcx=270e3f5381ad0000
rdx=000003e600000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80530e8b5c6 rsp=ffffd18f81a97bb0 rbp=ffffd18f81a97cb0
r8=0000000000000020 r9=00000000000034d2 r10=0000000000000000
r11=3fcc83fdd96f31e3 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiExecuteAllDpcs+0x356:
fffff805`30e8b5c6 a12003000080f7ffff mov eax,dword ptr [FFFFF78000000320h] ds:fffff780`00000320=????????
Resetting default scope
STACK_TEXT:
ffffd18f`81a978d8 fffff805`31010029 : 00000000`0000000a fffff780`00481020 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd18f`81a978e0 fffff805`3100bbe3 : fffff681`befaf86d ffffc080`1bd59180 00000000`00000000 ffff8105`628a8d50 : nt!KiBugCheckDispatch+0x69
ffffd18f`81a97a20 fffff805`30e8b5c6 : ffffc080`1bd5c240 ffff8105`62cd2000 ffffd18f`81a97e70 ffffc080`00000002 : nt!KiPageFault+0x463
ffffd18f`81a97bb0 fffff805`30e8a864 : ffffc080`1bd59180 00005b01`00000000 00000000`00000002 00000000`00000004 : nt!KiExecuteAllDpcs+0x356
ffffd18f`81a97d20 fffff805`310044b5 : 00001a03`70fedc01 ffffc080`1bd59180 ffff8105`62938ec0 00000000`0000001c : nt!KiRetireDpcList+0x1f4
ffffd18f`81a97fb0 fffff805`310042a0 : ffff8105`6d415080 fffff805`30ef625a ffffffff`fffffffe fffff805`3100f652 : nt!KxRetireDpcList+0x5
ffffd18f`827fb9c0 fffff805`31003a25 : 00000000`0000001c fffff805`30ffe7a1 00000225`ba836e70 00000000`00000001 : nt!KiDispatchInterruptContinue
ffffd18f`827fb9f0 fffff805`30ffe7a1 : 00000225`ba836e70 00000000`00000001 00000000`00000000 ffff8105`00000000 : nt!KiDpcInterruptBypass+0x25
ffffd18f`827fba00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
SYMBOL_NAME: nt!KiExecuteAllDpcs+356
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.3031
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 356
FAILURE_BUCKET_ID: AV_nt!KiExecuteAllDpcs
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {b88a28a0-fcde-99e9-6174-619833d00ab9}
Followup: MachineOwner
---------
Minidump'ta sürücü hatası var. Ama tam olarak neyin hata verdiği görünmüyor. Böyle durumlarda driver verifier devreye girebilir. Ama o da sancılı bir süreç. Başta tüm yöntemleri denemiştiniz, açıkta kalan bir şey yoktu. Hata zaten donanımsal bir hata olma yoluna girmişti. Bu yöne bakmaktansa önceki sayfalarda da konuşulduğu gibi donanıma bakmak daha mantıklı bir süre sonra. OCCT'ye göre işlemcide problemler var, evet. Ancak net konuşamıyorum bu konuda, fazla hakim değilim. Herhangi bir overclock vs. yoktu değil mi? BIOS Default'ta yani? Anakart veya işlemci suçlu gibi görünüyor. Arıza donanımsalsa Minidump'ta kaynağı belli olmayan bir sürücü hatası görmemizin sebebi bu olabilir.
Sistem kaç yıllık bu arada? Ne zamandır hata alıyorsunuz?
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: fffff78000481020, 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: fffff80530e8b5c6, address which referenced memory. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1405. Key : Analysis.Elapsed.mSec Value: 2509. 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: 202. Key : Analysis.Init.Elapsed.mSec Value: 2525. Key : Analysis.Memory.CommitPeak.Mb Value: 136. Key : Bugcheck.Code.LegacyAPI Value: 0xa. Key : Failure.Bucket Value: AV_nt!KiExecuteAllDpcs Key : Failure.Hash Value: {b88a28a0-fcde-99e9-6174-619833d00ab9} Key : WER.OS.Branch Value: vb_release. Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: a BUGCHECK_P1: fffff78000481020. BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff80530e8b5c6. FILE_IN_CAB: 060423-4359-01.dmp READ_ADDRESS: fffff805318fb390: 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 fffff78000481020. BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: linpack.exe DPC_STACK_BASE: FFFFD18F81A97FB0. TRAP_FRAME: ffffd18f81a97a20 -- (.trap 0xffffd18f81a97a20) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000003e6ed3bea91 rbx=0000000000000000 rcx=270e3f5381ad0000 rdx=000003e600000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80530e8b5c6 rsp=ffffd18f81a97bb0 rbp=ffffd18f81a97cb0 r8=0000000000000020 r9=00000000000034d2 r10=0000000000000000 r11=3fcc83fdd96f31e3 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc. nt!KiExecuteAllDpcs+0x356: fffff805`30e8b5c6 a12003000080f7ffff mov eax,dword ptr [FFFFF78000000320h] ds:fffff780`00000320=???????? Resetting default scope. STACK_TEXT: ffffd18f`81a978d8 fffff805`31010029 : 00000000`0000000a fffff780`00481020 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffd18f`81a978e0 fffff805`3100bbe3 : fffff681`befaf86d ffffc080`1bd59180 00000000`00000000 ffff8105`628a8d50 : nt!KiBugCheckDispatch+0x69 ffffd18f`81a97a20 fffff805`30e8b5c6 : ffffc080`1bd5c240 ffff8105`62cd2000 ffffd18f`81a97e70 ffffc080`00000002 : nt!KiPageFault+0x463 ffffd18f`81a97bb0 fffff805`30e8a864 : ffffc080`1bd59180 00005b01`00000000 00000000`00000002 00000000`00000004 : nt!KiExecuteAllDpcs+0x356 ffffd18f`81a97d20 fffff805`310044b5 : 00001a03`70fedc01 ffffc080`1bd59180 ffff8105`62938ec0 00000000`0000001c : nt!KiRetireDpcList+0x1f4 ffffd18f`81a97fb0 fffff805`310042a0 : ffff8105`6d415080 fffff805`30ef625a ffffffff`fffffffe fffff805`3100f652 : nt!KxRetireDpcList+0x5 ffffd18f`827fb9c0 fffff805`31003a25 : 00000000`0000001c fffff805`30ffe7a1 00000225`ba836e70 00000000`00000001 : nt!KiDispatchInterruptContinue ffffd18f`827fb9f0 fffff805`30ffe7a1 : 00000225`ba836e70 00000000`00000001 00000000`00000000 ffff8105`00000000 : nt!KiDpcInterruptBypass+0x25 ffffd18f`827fba00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1 SYMBOL_NAME: nt!KiExecuteAllDpcs+356 MODULE_NAME: nt. IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.3031 STACK_COMMAND: .cxr; .ecxr ; kb. BUCKET_ID_FUNC_OFFSET: 356. FAILURE_BUCKET_ID: AV_nt!KiExecuteAllDpcs OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release. OSPLATFORM_TYPE: x64. OSNAME: Windows 10. FAILURE_ID_HASH: {b88a28a0-fcde-99e9-6174-619833d00ab9} Followup: MachineOwner. ---------
Evet RAM XMP açık şekilde deneyebilirsiniz.
Zaten işlemci kaynaklı bir problem gibi görünüyor. İşlemcideki O.C. Ortadan kalktığında nasıl bir sonuç olacak diye deneyebilirsiniz.
Evet olabilir ama 5 yıldır sistem benimle, son 2 yılı 5 ghz stabil kullandım hiç bir mavi ekran yada sorunla karşılaşmadan kaldı ki anakartım 8700K için çok iyi diye biliyorum.. Donanım haber anakartımı tanıtıyordu bir videosunda 8700K İçin 5 ghz rahatlıkla çalıştırabilir gibi bir şeylerden bahsediyordu. Belki de 5 ghz de artık stabil çalışamıyor da olabilir. Deniyorum hala, güncelleyerek size bildireceğim. Her yolu deniyorumBendeki 8700K 4.8 GHz'i geçemiyordu. Ne kadar yüksek voltaj versem de stabil olmuyordu. Sorunun büyük ihtimal OC.
NMI_HARDWARE_FAILURE (80)
ve GenuineIntel.sys
NMI_HARDWARE_FAILURE (80)
This is typically due to a hardware malfunction. The hardware supplier should
be called.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NMI_HARDWARE_FAILURE (80)
This is typically due to a hardware malfunction. The hardware supplier should
be called.
Arguments:
Arg1: 00000000004f4454, 'TDO'
Arg2: 0000000000000000, Status Byte
Arg3: 0000000000000000
Arg4: 0000000000000000
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: Record ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1671
Key : Analysis.Elapsed.mSec
Value: 3804
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: 171
Key : Analysis.Init.Elapsed.mSec
Value: 1735
Key : Analysis.Memory.CommitPeak.Mb
Value: 139
Key : Bugcheck.Code.LegacyAPI
Value: 0x80
Key : Failure.Bucket
Value: 0x80_4F4454_GenuineIntel_NOERRREC_IMAGE_GenuineIntel.sys
Key : Failure.Hash
Value: {d5ef3836-2107-b7ec-b4d4-4d2ae9fc0e02}
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 80
BUGCHECK_P1: 4f4454
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 060423-4546-01.dmp
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Corsair.Service.exe
STACK_TEXT:
ffffab81`c93fcb38 fffff802`372b775a : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffab81`c93fcb40 fffff802`347415b0 : 00000000`00000000 ffffd504`2e479728 fffff802`37a507e0 ffffd504`2e479728 : nt!HalBugCheckSystem+0x7a
ffffab81`c93fcb80 fffff802`373b9a8e : 00000000`00000000 ffffab81`c93fcc29 ffffd504`2e479728 fffff802`37a507e0 : PSHED!PshedBugCheckSystem+0x10
ffffab81`c93fcbb0 fffff802`372bbe12 : 00000000`0000003c 00000000`0000003c fffff802`37a507e0 00000000`0000005c : nt!WheaReportHwError+0x46e
ffffab81`c93fcc90 fffff802`37310fb2 : 00000000`00000001 ffffab81`c93fcd10 00000000`00000000 fffff802`37323900 : nt!HalHandleNMI+0x142
ffffab81`c93fccc0 fffff802`37208e42 : ffffd504`387b2080 ffffab81`c93fced0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x132
ffffab81`c93fcd10 fffff802`37208c12 : ffffd504`387b2080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffffab81`c93fce50 fffff802`374884af : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x212
ffffbd02`bef279d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtDelayExecution+0x4f
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x80_4F4454_GenuineIntel_NOERRREC_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {d5ef3836-2107-b7ec-b4d4-4d2ae9fc0e02}
Followup: MachineOwner
---------
Bu attığınız konudaki gibi bende de o zaman OC'den hocam, bildiğiniz üzere 5 ghz de kullanıyordum OC li iken. Onu 4.7'ye çektim ve OCCT testlerinde problem olmadı. Şimdi oyunlarda deniyeceğim. Bugün yarın yada başka bir zaman yine mavi ekran yersem yine size bildireceğim. Hakkınızı ödeyemem. Çok çok teşekkürler. Hangi yazınızı çözüm olarak işaretleyeyim ?NMI_HARDWARE_FAILURE (80)
veGenuineIntel.sys
Kod:NMI_HARDWARE_FAILURE (80) This is typically due to a hardware malfunction. The hardware supplier should be called.
* Donanım hatası. İşlemci veya anakart arızalı oluyor genelde.
Aşağıda da bir benzeri var, O.C. sonucu olabiliyor.
NMI_HARDWARE_FAILURE hatası
Merhabalar, oyun oynarken 10 dakika arayla iki kez bu hatayı aldım. Sorun nedir? @Enes3078 @Assecreed @KojiroHyuga04 https://drive.google.com/file/d/1W-IvRy_cjG1WZJrHD16JGKAkbHwyq2tw/view?usp=sharingwww.technopat.net
Kod:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NMI_HARDWARE_FAILURE (80) This is typically due to a hardware malfunction. The hardware supplier should be called. Arguments: Arg1: 00000000004f4454, 'TDO' Arg2: 0000000000000000, Status Byte Arg3: 0000000000000000 Arg4: 0000000000000000 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: Record *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1671 Key : Analysis.Elapsed.mSec Value: 3804 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: 171 Key : Analysis.Init.Elapsed.mSec Value: 1735 Key : Analysis.Memory.CommitPeak.Mb Value: 139 Key : Bugcheck.Code.LegacyAPI Value: 0x80 Key : Failure.Bucket Value: 0x80_4F4454_GenuineIntel_NOERRREC_IMAGE_GenuineIntel.sys Key : Failure.Hash Value: {d5ef3836-2107-b7ec-b4d4-4d2ae9fc0e02} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 80 BUGCHECK_P1: 4f4454 BUGCHECK_P2: 0 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FILE_IN_CAB: 060423-4546-01.dmp BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: Corsair.Service.exe STACK_TEXT: ffffab81`c93fcb38 fffff802`372b775a : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx ffffab81`c93fcb40 fffff802`347415b0 : 00000000`00000000 ffffd504`2e479728 fffff802`37a507e0 ffffd504`2e479728 : nt!HalBugCheckSystem+0x7a ffffab81`c93fcb80 fffff802`373b9a8e : 00000000`00000000 ffffab81`c93fcc29 ffffd504`2e479728 fffff802`37a507e0 : PSHED!PshedBugCheckSystem+0x10 ffffab81`c93fcbb0 fffff802`372bbe12 : 00000000`0000003c 00000000`0000003c fffff802`37a507e0 00000000`0000005c : nt!WheaReportHwError+0x46e ffffab81`c93fcc90 fffff802`37310fb2 : 00000000`00000001 ffffab81`c93fcd10 00000000`00000000 fffff802`37323900 : nt!HalHandleNMI+0x142 ffffab81`c93fccc0 fffff802`37208e42 : ffffd504`387b2080 ffffab81`c93fced0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x132 ffffab81`c93fcd10 fffff802`37208c12 : ffffd504`387b2080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82 ffffab81`c93fce50 fffff802`374884af : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x212 ffffbd02`bef279d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtDelayExecution+0x4f MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel.sys STACK_COMMAND: .cxr; .ecxr ; kb FAILURE_BUCKET_ID: 0x80_4F4454_GenuineIntel_NOERRREC_IMAGE_GenuineIntel.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {d5ef3836-2107-b7ec-b4d4-4d2ae9fc0e02} Followup: MachineOwner ---------
Estağfurullah, rica ederim.Hakkınızı ödeyemem. Çok çok teşekkürler. Hangi yazınızı çözüm olarak işaretleyeyim ?