F5F Stay Refreshed Software Operating Systems Error encountered: "INTERRUPT_EXCEPTION_NOT_HANDLED" for ntkrnlmp.exe.

Error encountered: "INTERRUPT_EXCEPTION_NOT_HANDLED" for ntkrnlmp.exe.

Error encountered: "INTERRUPT_EXCEPTION_NOT_HANDLED" for ntkrnlmp.exe.

Pages (2): 1 2 Next
R
RainbowLeader
Member
Find
56
12-29-2025, 01:38 AM
#1
Hi!
My PC is crashing whenever i play games, its weird as
it only happenes when i play games
.
Here are the minidump file:
https://www.mediafire.com/file/2f71scv88...Y.zip/file
my specs are:
https://spec-ify.com/profile/5bb0e9a2
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
The exception handler for the kernel interrupt object interrupt management was
not able to handle the generated exception.
Arguments:
Arg1: fffff8035a938c68, Exception Record (When Available)
Arg2: fffff8035a938480, Context Record (When Available)
Arg3: 0000000000000000, Not used
Arg4: 0000000000000000, Not used
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2265
Key : Analysis.Elapsed.mSec
Value: 3861
Key : Analysis.IO.Other.Mb
Value: 20
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 30
Key : Analysis.Init.CPU.mSec
Value: 1093
Key : Analysis.Init.Elapsed.mSec
Value: 33673
Key : Analysis.Memory.CommitPeak.Mb
Value: 96
Key : Bugcheck.Code.LegacyAPI
Value: 0x3d
Key : Bugcheck.Code.TargetModel
Value: 0x3d
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x3D_C000001D_BAD_IP_nt!KeClockInterruptNotify
Key : Failure.Hash
Value: {91cb89d4-4490-fed9-6884-a077c795d11a}
BUGCHECK_CODE: 3d
BUGCHECK_P1: fffff8035a938c68
BUGCHECK_P2: fffff8035a938480
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 071124-18359-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
EXCEPTION_RECORD: fffff8035a938c68 -- (.exr 0xfffff8035a938c68)
ExceptionAddress: fffff80354d290c6 (nt!KeClockInterruptNotify+0x0000000000000206)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: fffff80354d6dec0
CONTEXT: fffff8035a938480 -- (.cxr 0xfffff8035a938480)
rax=000000000000000f rbx=0000000000000000 rcx=000000000000000f
rdx=ffffffffffffffff rsi=fffff803529aa180 rdi=0000000000000000
rip=fffff80354d290c6 rsp=fffff8035a938ea0 rbp=ffffa800674d1800
r8=0000000000000000 r9=0000000000000000 r10=fffff80354d6dec0
r11=0000000000008000 r12=0000000000000002 r13=fffff80355641a18
r14=fffff803529b3090 r15=0000000000000000
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!KeClockInterruptNotify+0x206:
fffff803`54d290c6 0f8402010000 je nt!KeClockInterruptNotify+0x30e (fffff803`54d291ce) [br=0]
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: VALORANT-Win64
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
EXCEPTION_CODE_STR: c000001d
EXCEPTION_STR: 0xc000001d
FAILED_INSTRUCTION_ADDRESS:
nt!KeClockInterruptNotify+206
fffff803`54d290c6 0f8402010000 je nt!KeClockInterruptNotify+0x30e (fffff803`54d291ce)
STACK_TEXT:
fffff803`5a938ea0 fffff803`54d28a7a : fffff803`5565ffa8 ffffa800`674d1830 ffffa800`674d1830 00000000`00000002 : nt!KeClockInterruptNotify+0x206
fffff803`5a938f40 fffff803`54c44b7c : 00000003`51b358c2 fffff803`5570d430 fffff803`5570d4e0 fffff803`54e17d9b : nt!HalpTimerClockInterrupt+0x10a
fffff803`5a938f70 fffff803`54e17ffa : fffff803`5a930ef0 fffff803`5570d430 ffff8004`12960000 00000000`02000002 : nt!KiCallInterruptServiceRoutine+0x9c
fffff803`5a938fb0 fffff803`54e188c7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff803`5a930e70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
SYMBOL_NAME: nt!KeClockInterruptNotify+206
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.3880
STACK_COMMAND: .cxr 0xfffff8035a938480 ; kb
BUCKET_ID_FUNC_OFFSET: 206
FAILURE_BUCKET_ID: 0x3D_C000001D_BAD_IP_nt!KeClockInterruptNotify
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {91cb89d4-4490-fed9-6884-a077c795d11a}
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
The exception handler for the kernel interrupt object interrupt management was
not able to handle the generated exception.
Arguments:
Arg1: fffff8035a938c68, Exception Record (When Available)
Arg2: fffff8035a938480, Context Record (When Available)
Arg3: 0000000000000000, Not used
Arg4: 0000000000000000, Not used
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2109
Key : Analysis.Elapsed.mSec
Value: 2131
Key : Analysis.IO.Other.Mb
Value: 20
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 30
Key : Analysis.Init.CPU.mSec
Value: 3453
Key : Analysis.Init.Elapsed.mSec
Value: 37630
Key : Analysis.Memory.CommitPeak.Mb
Value: 96
Key : Bugcheck.Code.LegacyAPI
Value: 0x3d
Key : Bugcheck.Code.TargetModel
Value: 0x3d
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x3D_C000001D_BAD_IP_nt!KeClockInterruptNotify
Key : Failure.Hash
Value: {91cb89d4-4490-fed9-6884-a077c795d11a}
BUGCHECK_CODE: 3d
BUGCHECK_P1: fffff8035a938c68
BUGCHECK_P2: fffff8035a938480
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 071124-18359-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
EXCEPTION_RECORD: fffff8035a938c68 -- (.exr 0xfffff8035a938c68)
ExceptionAddress: fffff80354d290c6 (nt!KeClockInterruptNotify+0x0000000000000206)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: fffff80354d6dec0
CONTEXT: fffff8035a938480 -- (.cxr 0xfffff8035a938480)
rax=000000000000000f rbx=0000000000000000 rcx=000000000000000f
rdx=ffffffffffffffff rsi=fffff803529aa180 rdi=0000000000000000
rip=fffff80354d290c6 rsp=fffff8035a938ea0 rbp=ffffa800674d1800
r8=0000000000000000 r9=0000000000000000 r10=fffff80354d6dec0
r11=0000000000008000 r12=0000000000000002 r13=fffff80355641a18
r14=fffff803529b3090 r15=0000000000000000
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!KeClockInterruptNotify+0x206:
fffff803`54d290c6 0f8402010000 je nt!KeClockInterruptNotify+0x30e (fffff803`54d291ce) [br=0]
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: VALORANT-Win64
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
EXCEPTION_CODE_STR: c000001d
EXCEPTION_STR: 0xc000001d
FAILED_INSTRUCTION_ADDRESS:
nt!KeClockInterruptNotify+206
fffff803`54d290c6 0f8402010000 je nt!KeClockInterruptNotify+0x30e (fffff803`54d291ce)
STACK_TEXT:
fffff803`5a938ea0 fffff803`54d28a7a : fffff803`5565ffa8 ffffa800`674d1830 ffffa800`674d1830 00000000`00000002 : nt!KeClockInterruptNotify+0x206
fffff803`5a938f40 fffff803`54c44b7c : 00000003`51b358c2 fffff803`5570d430 fffff803`5570d4e0 fffff803`54e17d9b : nt!HalpTimerClockInterrupt+0x10a
fffff803`5a938f70 fffff803`54e17ffa : fffff803`5a930ef0 fffff803`5570d430 ffff8004`12960000 00000000`02000002 : nt!KiCallInterruptServiceRoutine+0x9c
fffff803`5a938fb0 fffff803`54e188c7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff803`5a930e70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
SYMBOL_NAME: nt!KeClockInterruptNotify+206
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.3880
STACK_COMMAND: .cxr 0xfffff8035a938480 ; kb
BUCKET_ID_FUNC_OFFSET: 206
FAILURE_BUCKET_ID: 0x3D_C000001D_BAD_IP_nt!KeClockInterruptNotify
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {91cb89d4-4490-fed9-6884-a077c795d11a}
Followup: MachineOwner
---------
0: kd> lmvm nt
Browse full module list
start end module name
fffff803`54a00000 fffff803`55a47000 nt (pdb symbols) C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\EEFAC795A46ECB8E8267C6C0ABAF1CE91\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: C:\ProgramData\Dbg\sym\ntkrnlmp.exe\6B71A1881047000\ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 6B71A188 (This is a reproducible build file hash, not a timestamp)
CheckSum: 00B8D4DE
ImageSize: 01047000
File version: 10.0.22621.3880
Product version: 10.0.22621.3880
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 10.0.22621.3880
FileVersion: 10.0.22621.3880 (WinBuild.160101.0800)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
Reply
Reply
R
RainbowLeader
12-29-2025, 01:38 AM #1

Hi!
My PC is crashing whenever i play games, its weird as
it only happenes when i play games
.
Here are the minidump file:
https://www.mediafire.com/file/2f71scv88...Y.zip/file
my specs are:
https://spec-ify.com/profile/5bb0e9a2
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
The exception handler for the kernel interrupt object interrupt management was
not able to handle the generated exception.
Arguments:
Arg1: fffff8035a938c68, Exception Record (When Available)
Arg2: fffff8035a938480, Context Record (When Available)
Arg3: 0000000000000000, Not used
Arg4: 0000000000000000, Not used
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2265
Key : Analysis.Elapsed.mSec
Value: 3861
Key : Analysis.IO.Other.Mb
Value: 20
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 30
Key : Analysis.Init.CPU.mSec
Value: 1093
Key : Analysis.Init.Elapsed.mSec
Value: 33673
Key : Analysis.Memory.CommitPeak.Mb
Value: 96
Key : Bugcheck.Code.LegacyAPI
Value: 0x3d
Key : Bugcheck.Code.TargetModel
Value: 0x3d
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x3D_C000001D_BAD_IP_nt!KeClockInterruptNotify
Key : Failure.Hash
Value: {91cb89d4-4490-fed9-6884-a077c795d11a}
BUGCHECK_CODE: 3d
BUGCHECK_P1: fffff8035a938c68
BUGCHECK_P2: fffff8035a938480
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 071124-18359-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
EXCEPTION_RECORD: fffff8035a938c68 -- (.exr 0xfffff8035a938c68)
ExceptionAddress: fffff80354d290c6 (nt!KeClockInterruptNotify+0x0000000000000206)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: fffff80354d6dec0
CONTEXT: fffff8035a938480 -- (.cxr 0xfffff8035a938480)
rax=000000000000000f rbx=0000000000000000 rcx=000000000000000f
rdx=ffffffffffffffff rsi=fffff803529aa180 rdi=0000000000000000
rip=fffff80354d290c6 rsp=fffff8035a938ea0 rbp=ffffa800674d1800
r8=0000000000000000 r9=0000000000000000 r10=fffff80354d6dec0
r11=0000000000008000 r12=0000000000000002 r13=fffff80355641a18
r14=fffff803529b3090 r15=0000000000000000
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!KeClockInterruptNotify+0x206:
fffff803`54d290c6 0f8402010000 je nt!KeClockInterruptNotify+0x30e (fffff803`54d291ce) [br=0]
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: VALORANT-Win64
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
EXCEPTION_CODE_STR: c000001d
EXCEPTION_STR: 0xc000001d
FAILED_INSTRUCTION_ADDRESS:
nt!KeClockInterruptNotify+206
fffff803`54d290c6 0f8402010000 je nt!KeClockInterruptNotify+0x30e (fffff803`54d291ce)
STACK_TEXT:
fffff803`5a938ea0 fffff803`54d28a7a : fffff803`5565ffa8 ffffa800`674d1830 ffffa800`674d1830 00000000`00000002 : nt!KeClockInterruptNotify+0x206
fffff803`5a938f40 fffff803`54c44b7c : 00000003`51b358c2 fffff803`5570d430 fffff803`5570d4e0 fffff803`54e17d9b : nt!HalpTimerClockInterrupt+0x10a
fffff803`5a938f70 fffff803`54e17ffa : fffff803`5a930ef0 fffff803`5570d430 ffff8004`12960000 00000000`02000002 : nt!KiCallInterruptServiceRoutine+0x9c
fffff803`5a938fb0 fffff803`54e188c7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff803`5a930e70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
SYMBOL_NAME: nt!KeClockInterruptNotify+206
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.3880
STACK_COMMAND: .cxr 0xfffff8035a938480 ; kb
BUCKET_ID_FUNC_OFFSET: 206
FAILURE_BUCKET_ID: 0x3D_C000001D_BAD_IP_nt!KeClockInterruptNotify
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {91cb89d4-4490-fed9-6884-a077c795d11a}
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
The exception handler for the kernel interrupt object interrupt management was
not able to handle the generated exception.
Arguments:
Arg1: fffff8035a938c68, Exception Record (When Available)
Arg2: fffff8035a938480, Context Record (When Available)
Arg3: 0000000000000000, Not used
Arg4: 0000000000000000, Not used
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2109
Key : Analysis.Elapsed.mSec
Value: 2131
Key : Analysis.IO.Other.Mb
Value: 20
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 30
Key : Analysis.Init.CPU.mSec
Value: 3453
Key : Analysis.Init.Elapsed.mSec
Value: 37630
Key : Analysis.Memory.CommitPeak.Mb
Value: 96
Key : Bugcheck.Code.LegacyAPI
Value: 0x3d
Key : Bugcheck.Code.TargetModel
Value: 0x3d
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x3D_C000001D_BAD_IP_nt!KeClockInterruptNotify
Key : Failure.Hash
Value: {91cb89d4-4490-fed9-6884-a077c795d11a}
BUGCHECK_CODE: 3d
BUGCHECK_P1: fffff8035a938c68
BUGCHECK_P2: fffff8035a938480
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 071124-18359-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
EXCEPTION_RECORD: fffff8035a938c68 -- (.exr 0xfffff8035a938c68)
ExceptionAddress: fffff80354d290c6 (nt!KeClockInterruptNotify+0x0000000000000206)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: fffff80354d6dec0
CONTEXT: fffff8035a938480 -- (.cxr 0xfffff8035a938480)
rax=000000000000000f rbx=0000000000000000 rcx=000000000000000f
rdx=ffffffffffffffff rsi=fffff803529aa180 rdi=0000000000000000
rip=fffff80354d290c6 rsp=fffff8035a938ea0 rbp=ffffa800674d1800
r8=0000000000000000 r9=0000000000000000 r10=fffff80354d6dec0
r11=0000000000008000 r12=0000000000000002 r13=fffff80355641a18
r14=fffff803529b3090 r15=0000000000000000
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!KeClockInterruptNotify+0x206:
fffff803`54d290c6 0f8402010000 je nt!KeClockInterruptNotify+0x30e (fffff803`54d291ce) [br=0]
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: VALORANT-Win64
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
EXCEPTION_CODE_STR: c000001d
EXCEPTION_STR: 0xc000001d
FAILED_INSTRUCTION_ADDRESS:
nt!KeClockInterruptNotify+206
fffff803`54d290c6 0f8402010000 je nt!KeClockInterruptNotify+0x30e (fffff803`54d291ce)
STACK_TEXT:
fffff803`5a938ea0 fffff803`54d28a7a : fffff803`5565ffa8 ffffa800`674d1830 ffffa800`674d1830 00000000`00000002 : nt!KeClockInterruptNotify+0x206
fffff803`5a938f40 fffff803`54c44b7c : 00000003`51b358c2 fffff803`5570d430 fffff803`5570d4e0 fffff803`54e17d9b : nt!HalpTimerClockInterrupt+0x10a
fffff803`5a938f70 fffff803`54e17ffa : fffff803`5a930ef0 fffff803`5570d430 ffff8004`12960000 00000000`02000002 : nt!KiCallInterruptServiceRoutine+0x9c
fffff803`5a938fb0 fffff803`54e188c7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff803`5a930e70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
SYMBOL_NAME: nt!KeClockInterruptNotify+206
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.3880
STACK_COMMAND: .cxr 0xfffff8035a938480 ; kb
BUCKET_ID_FUNC_OFFSET: 206
FAILURE_BUCKET_ID: 0x3D_C000001D_BAD_IP_nt!KeClockInterruptNotify
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {91cb89d4-4490-fed9-6884-a077c795d11a}
Followup: MachineOwner
---------
0: kd> lmvm nt
Browse full module list
start end module name
fffff803`54a00000 fffff803`55a47000 nt (pdb symbols) C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\EEFAC795A46ECB8E8267C6C0ABAF1CE91\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: C:\ProgramData\Dbg\sym\ntkrnlmp.exe\6B71A1881047000\ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 6B71A188 (This is a reproducible build file hash, not a timestamp)
CheckSum: 00B8D4DE
ImageSize: 01047000
File version: 10.0.22621.3880
Product version: 10.0.22621.3880
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 10.0.22621.3880
FileVersion: 10.0.22621.3880 (WinBuild.160101.0800)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.

Reply
Reply
L
Lapeluche
Member
Find
211
12-29-2025, 01:38 AM
#2
Windows 11 may not be up to date because it hasn't been released for all users yet, or because some systems are still using older versions.
Reply
Reply
L
Lapeluche
12-29-2025, 01:38 AM #2

Windows 11 may not be up to date because it hasn't been released for all users yet, or because some systems are still using older versions.

Reply
Reply
B
benson_jr
Junior Member
Find
15
12-29-2025, 01:38 AM
#3
I haven't installed the newest version yet because I'm still working through the steps to resolve this computer crashing/BSOD issue.
Reply
Reply
B
benson_jr
12-29-2025, 01:38 AM #3

I haven't installed the newest version yet because I'm still working through the steps to resolve this computer crashing/BSOD issue.

Reply
Reply
K
KanayOne
Member
Find
212
12-29-2025, 01:38 AM
#4
The two uploads you provided are the same, both failing due to an illegal instruction execution attempt. In each case, the problematic instruction is identical, yet it's a valid command. The issue involves a clock interrupt notify; processors are often interrupted by these interrupts, which is normal in Windows operation, but something disrupted this process. The root cause isn't evident from the dumps, as the problem likely occurred before the clock interrupt happened. Therefore, we must rely on experience and knowledge to identify what might be responsible.
Reply
Reply
K
KanayOne
12-29-2025, 01:38 AM #4

The two uploads you provided are the same, both failing due to an illegal instruction execution attempt. In each case, the problematic instruction is identical, yet it's a valid command. The issue involves a clock interrupt notify; processors are often interrupted by these interrupts, which is normal in Windows operation, but something disrupted this process. The root cause isn't evident from the dumps, as the problem likely occurred before the clock interrupt happened. Therefore, we must rely on experience and knowledge to identify what might be responsible.

Reply
Reply
X
xNorfy4G
Junior Member
Find
16
12-29-2025, 01:38 AM
#5
Hello!
I just played Overwatch with Vanguard disabled, and the issue remains unchanged.
Here are the dumpfiles:
https://www.mediafire.com/file/6zpehfrt6...1.dmp/file
[Mod Edit]
I also checked BlueScreenView, which indicated that ntoskrnl.exe+56f4d5 might be the cause.
Reply
Reply
X
xNorfy4G
12-29-2025, 01:38 AM #5

Hello!
I just played Overwatch with Vanguard disabled, and the issue remains unchanged.
Here are the dumpfiles:
https://www.mediafire.com/file/6zpehfrt6...1.dmp/file
[Mod Edit]
I also checked BlueScreenView, which indicated that ntoskrnl.exe+56f4d5 might be the cause.

Reply
Reply
Q
Questiero
Member
Find
215
12-29-2025, 01:38 AM
#6
BlueScreenView and WhoCrashed offer little practical help at this point. The ntoskrnl.exe module wasn't responsible for this crash because it's part of the Windows kernel. Typically, an error from a third-party driver or DLL isn't caught until the system reverts to the kernel, which then triggers a BSOD. In the dump files, you'll find the kernel identified as the faulty module. The ntoskrnl.exe+56f4d5 entry appears in BlueScreenView.

The vgk.sys driver is still loading, and it's visible in the dump you provided among the modules unloaded right before the capture...

Rich (BB code):
Unloaded modules:
fffff801`63220000 fffff801`63267000 MpKslDrv.sys
fffff801`63200000 fffff801`63213000 MSKSSRV.sys
fffff801`4b800000 fffff801`4de3e000 vgk.sys
fffff801`630a0000 fffff801`630b3000 MSKSSRV.sys
fffff801`3e2b0000 fffff801`3e2c2000 dump_storpor
fffff801`41e90000 fffff801`42a73000 dump_iaStorA
fffff801`42aa0000 fffff801`42abf000 dump_dumpfve
fffff801`41c00000 fffff801`41c21000 dam.sys
fffff801`41c30000 fffff801`41c40000 KMPDC.sys
fffff801`29f90000 fffff801`29f9c000 WdBoot.sys
fffff801`2bd60000 fffff801`2bd72000 hwpolicy.sys

It seems you might want to remove Vanguard to confirm it isn't causing these crashes.
Reply
Reply
Q
Questiero
12-29-2025, 01:38 AM #6

BlueScreenView and WhoCrashed offer little practical help at this point. The ntoskrnl.exe module wasn't responsible for this crash because it's part of the Windows kernel. Typically, an error from a third-party driver or DLL isn't caught until the system reverts to the kernel, which then triggers a BSOD. In the dump files, you'll find the kernel identified as the faulty module. The ntoskrnl.exe+56f4d5 entry appears in BlueScreenView.

The vgk.sys driver is still loading, and it's visible in the dump you provided among the modules unloaded right before the capture...

Rich (BB code):
Unloaded modules:
fffff801`63220000 fffff801`63267000 MpKslDrv.sys
fffff801`63200000 fffff801`63213000 MSKSSRV.sys
fffff801`4b800000 fffff801`4de3e000 vgk.sys
fffff801`630a0000 fffff801`630b3000 MSKSSRV.sys
fffff801`3e2b0000 fffff801`3e2c2000 dump_storpor
fffff801`41e90000 fffff801`42a73000 dump_iaStorA
fffff801`42aa0000 fffff801`42abf000 dump_dumpfve
fffff801`41c00000 fffff801`41c21000 dam.sys
fffff801`41c30000 fffff801`41c40000 KMPDC.sys
fffff801`29f90000 fffff801`29f9c000 WdBoot.sys
fffff801`2bd60000 fffff801`2bd72000 hwpolicy.sys

It seems you might want to remove Vanguard to confirm it isn't causing these crashes.

Reply
Reply
S
SableRose
Member
Find
52
12-29-2025, 01:38 AM
#7
Sure, I can uninstall rn and attempt to play Overwatch once more.
Alternatively, is there any way to prevent Vanguard from causing issues while you also want to play Valorant?
Reply
Reply
S
SableRose
12-29-2025, 01:38 AM #7

Sure, I can uninstall rn and attempt to play Overwatch once more.
Alternatively, is there any way to prevent Vanguard from causing issues while you also want to play Valorant?

Reply
Reply
_
_PandaCraft_
Member
Find
58
12-29-2025, 01:38 AM
#8
You would have to contact Riot Games, as Vanguard is their offering.
Reply
Reply
_
_PandaCraft_
12-29-2025, 01:38 AM #8

You would have to contact Riot Games, as Vanguard is their offering.

Reply
Reply
F
fuzzypickle55
Junior Member
Find
46
12-29-2025, 01:38 AM
#9
I've noticed the issue persists in Valorant despite fixing it in other titles, specifically related to the bugcheck interrupt_exception_not_handled (3d).
Reply
Reply
F
fuzzypickle55
12-29-2025, 01:38 AM #9

I've noticed the issue persists in Valorant despite fixing it in other titles, specifically related to the bugcheck interrupt_exception_not_handled (3d).

Reply
Reply
S
SuperEster04
Junior Member
Find
13
12-29-2025, 01:38 AM
#10
New dumpfile available with driver verifier at the provided link.
Reply
Reply
S
SuperEster04
12-29-2025, 01:38 AM #10

New dumpfile available with driver verifier at the provided link.

Reply
Reply
Pages (2): 1 2 Next