F5F Stay Refreshed Hardware Desktop Question DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD in specific games

Question DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD in specific games

Question DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD in specific games

_
_ErikThePanda_
Posting Freak
Find
807
11-23-2025, 06:47 PM
#1
Hello community, can anyone please analyze what driver/s caused this BSOD in this certain dump, and what I could do to troubleshoot these problems? It happens whenever I play large games. It's been happening for a long time now, and I have tried conventional methods of finding solutions. Unfortunately, none of them worked. I think It has something to do with the drivers having conflict with certain software, I use a debugging tool, I couldn't figure out the exact drivers that are causing this issue. I am not experienced enough with our current technology and help from professionals would definitely be appreciated!
Here is the analysis of the dump (Generated 9/12/2025 7:24 PM)
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.344 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 45
Microsoft ® Windows Debugger Version 10.0.27920.1001 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\091225-6531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 26100 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff807`8f200000 PsLoadedModuleList = 0xfffff807`900f4e70
Debug session time: Fri Sep 12 19:24:06.240 2025 (UTC + 8:00)
System Uptime: 0 days 2:08:13.040
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`8f6f9280 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa600`d76b1b20=000000000000000a
1: kd> !analyze -v
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffff830e6754d2b8, memory referenced
Arg2: 000000000000000b, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8073314fdc0, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for amdkmdag.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1437
Key : Analysis.Elapsed.mSec
Value: 11462
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 906
Key : Analysis.Init.Elapsed.mSec
Value: 34707
Key : Analysis.Memory.CommitPeak.Mb
Value: 109
Key : Analysis.Version.DbgEng
Value: 10.0.27920.1001
Key : Analysis.Version.Description
Value: 10.2506.23.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2506.23.1
Key : Bugcheck.Code.LegacyAPI
Value: 0xd1
Key : Bugcheck.Code.TargetModel
Value: 0xd1
Key : Dump.Attributes.AsUlong
Value: 0x21808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0x0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: AV_amdkmdag!unknown_function
Key : Failure.Exception.IP.Address
Value: 0xfffff8073314fdc0
Key : Failure.Exception.IP.Module
Value: amdkmdag
Key : Failure.Exception.IP.Offset
Value: 0x20efdc0
Key : Failure.Hash
Value: {c753a2f9-94a6-448f-1d0e-e079b3442215}
Key : Hypervisor.Enlightenments.ValueHex
Value: 0x7497cf94
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 1
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 38408431
Key : Hypervisor.Flags.ValueHex
Value: 0x24a10ef
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 0x3f7
Key : Stack.Pointer
Value: ISR
Key : WER.System.BIOSRevision
Value: 5.17.0.0
BUGCHECK_CODE: d1
BUGCHECK_P1: ffff830e6754d2b8
BUGCHECK_P2: b
BUGCHECK_P3: 0
BUGCHECK_P4: fffff8073314fdc0
FILE_IN_CAB: 091225-6531-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump
FAULTING_THREAD: ffff830e47624080
READ_ADDRESS: fffff807901c44c0: 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
ffff830e6754d2b8
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffa600`d76b1b18 fffff807`8f8b39e9 : 00000000`0000000a ffff830e`6754d2b8 00000000`0000000b 00000000`00000000 : nt!KeBugCheckEx
ffffa600`d76b1b20 fffff807`8f8aeca8 : 00000001`00000002 00000000`00000000 ffff830e`4f9d0a30 fffff807`3312904f : nt!KiBugCheckDispatch+0x69
ffffa600`d76b1c60 fffff807`3314fdc0 : fffff807`3313d659 ffff830e`4f9d0000 000006ff`2e228150 ffff830e`4f9d0a30 : nt!KiPageFault+0x468
ffffa600`d76b1df8 fffff807`3313d659 : ffff830e`4f9d0000 000006ff`2e228150 ffff830e`4f9d0a30 fffff807`372627c8 : amdkmdag+0x20efdc0
ffffa600`d76b1e00 ffff830e`4f9d0000 : 000006ff`2e228150 ffff830e`4f9d0a30 fffff807`372627c8 ffffa600`d76b2501 : amdkmdag+0x20dd659
ffffa600`d76b1e08 000006ff`2e228150 : ffff830e`4f9d0a30 fffff807`372627c8 ffffa600`d76b2501 00000000`00000000 : 0xffff830e`4f9d0000
ffffa600`d76b1e10 ffff830e`4f9d0a30 : fffff807`372627c8 ffffa600`d76b2501 00000000`00000000 00000000`00000000 : 0x000006ff`2e228150
ffffa600`d76b1e18 fffff807`372627c8 : ffffa600`d76b2501 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff830e`4f9d0a30
ffffa600`d76b1e20 ffffa600`d76b2501 : 00000000`00000000 00000000`00000000 00000000`00000000 ef6b1500`00000000 : amdkmdag+0x62027c8
ffffa600`d76b1e28 00000000`00000000 : 00000000`00000000 00000000`00000000 ef6b1500`00000000 00000000`00000000 : 0xffffa600`d76b2501
SYMBOL_NAME: amdkmdag+20efdc0
MODULE_NAME: amdkmdag
IMAGE_NAME: amdkmdag.sys
STACK_COMMAND: .process /r /p 0xfffff807901cef80; .thread 0xffff830e47624080 ; kb
BUCKET_ID_FUNC_OFFSET: 20efdc0
FAILURE_BUCKET_ID: AV_amdkmdag!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c753a2f9-94a6-448f-1d0e-e079b3442215}
Followup: MachineOwner
---------
1: kd> lmvm amdkmdag
Browse full module list
start end module name
fffff807`31060000 fffff807`3765a000 amdkmdag T (no symbols)
Loaded symbol image file: amdkmdag.sys
Image path: amdkmdag.sys
Image name: amdkmdag.sys
Browse all global symbols functions data Symbol Reload
Timestamp: Wed Jun 18 03:42:42 2025 (6851C532)
CheckSum: 065A9C1B
ImageSize: 065FA000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
My specs:
Device name DESKTOP-IVHRL9V
Processor AMD Ryzen 5 5600G with Radeon Graphics (3.90 GHz)
Installed RAM 16.0 GB (15.4 GB usable)
Device ID FB3EB39D-7727-41FD-88C6-E51A0A38BF7C
Product ID 00330-80000-00000-AA889
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Reply
Reply
_
_ErikThePanda_
11-23-2025, 06:47 PM #1

Hello community, can anyone please analyze what driver/s caused this BSOD in this certain dump, and what I could do to troubleshoot these problems? It happens whenever I play large games. It's been happening for a long time now, and I have tried conventional methods of finding solutions. Unfortunately, none of them worked. I think It has something to do with the drivers having conflict with certain software, I use a debugging tool, I couldn't figure out the exact drivers that are causing this issue. I am not experienced enough with our current technology and help from professionals would definitely be appreciated!
Here is the analysis of the dump (Generated 9/12/2025 7:24 PM)
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.344 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 45
Microsoft ® Windows Debugger Version 10.0.27920.1001 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\091225-6531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 26100 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff807`8f200000 PsLoadedModuleList = 0xfffff807`900f4e70
Debug session time: Fri Sep 12 19:24:06.240 2025 (UTC + 8:00)
System Uptime: 0 days 2:08:13.040
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`8f6f9280 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa600`d76b1b20=000000000000000a
1: kd> !analyze -v
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffff830e6754d2b8, memory referenced
Arg2: 000000000000000b, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8073314fdc0, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for amdkmdag.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1437
Key : Analysis.Elapsed.mSec
Value: 11462
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 906
Key : Analysis.Init.Elapsed.mSec
Value: 34707
Key : Analysis.Memory.CommitPeak.Mb
Value: 109
Key : Analysis.Version.DbgEng
Value: 10.0.27920.1001
Key : Analysis.Version.Description
Value: 10.2506.23.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2506.23.1
Key : Bugcheck.Code.LegacyAPI
Value: 0xd1
Key : Bugcheck.Code.TargetModel
Value: 0xd1
Key : Dump.Attributes.AsUlong
Value: 0x21808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0x0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: AV_amdkmdag!unknown_function
Key : Failure.Exception.IP.Address
Value: 0xfffff8073314fdc0
Key : Failure.Exception.IP.Module
Value: amdkmdag
Key : Failure.Exception.IP.Offset
Value: 0x20efdc0
Key : Failure.Hash
Value: {c753a2f9-94a6-448f-1d0e-e079b3442215}
Key : Hypervisor.Enlightenments.ValueHex
Value: 0x7497cf94
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 1
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 38408431
Key : Hypervisor.Flags.ValueHex
Value: 0x24a10ef
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 0x3f7
Key : Stack.Pointer
Value: ISR
Key : WER.System.BIOSRevision
Value: 5.17.0.0
BUGCHECK_CODE: d1
BUGCHECK_P1: ffff830e6754d2b8
BUGCHECK_P2: b
BUGCHECK_P3: 0
BUGCHECK_P4: fffff8073314fdc0
FILE_IN_CAB: 091225-6531-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump
FAULTING_THREAD: ffff830e47624080
READ_ADDRESS: fffff807901c44c0: 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
ffff830e6754d2b8
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffa600`d76b1b18 fffff807`8f8b39e9 : 00000000`0000000a ffff830e`6754d2b8 00000000`0000000b 00000000`00000000 : nt!KeBugCheckEx
ffffa600`d76b1b20 fffff807`8f8aeca8 : 00000001`00000002 00000000`00000000 ffff830e`4f9d0a30 fffff807`3312904f : nt!KiBugCheckDispatch+0x69
ffffa600`d76b1c60 fffff807`3314fdc0 : fffff807`3313d659 ffff830e`4f9d0000 000006ff`2e228150 ffff830e`4f9d0a30 : nt!KiPageFault+0x468
ffffa600`d76b1df8 fffff807`3313d659 : ffff830e`4f9d0000 000006ff`2e228150 ffff830e`4f9d0a30 fffff807`372627c8 : amdkmdag+0x20efdc0
ffffa600`d76b1e00 ffff830e`4f9d0000 : 000006ff`2e228150 ffff830e`4f9d0a30 fffff807`372627c8 ffffa600`d76b2501 : amdkmdag+0x20dd659
ffffa600`d76b1e08 000006ff`2e228150 : ffff830e`4f9d0a30 fffff807`372627c8 ffffa600`d76b2501 00000000`00000000 : 0xffff830e`4f9d0000
ffffa600`d76b1e10 ffff830e`4f9d0a30 : fffff807`372627c8 ffffa600`d76b2501 00000000`00000000 00000000`00000000 : 0x000006ff`2e228150
ffffa600`d76b1e18 fffff807`372627c8 : ffffa600`d76b2501 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff830e`4f9d0a30
ffffa600`d76b1e20 ffffa600`d76b2501 : 00000000`00000000 00000000`00000000 00000000`00000000 ef6b1500`00000000 : amdkmdag+0x62027c8
ffffa600`d76b1e28 00000000`00000000 : 00000000`00000000 00000000`00000000 ef6b1500`00000000 00000000`00000000 : 0xffffa600`d76b2501
SYMBOL_NAME: amdkmdag+20efdc0
MODULE_NAME: amdkmdag
IMAGE_NAME: amdkmdag.sys
STACK_COMMAND: .process /r /p 0xfffff807901cef80; .thread 0xffff830e47624080 ; kb
BUCKET_ID_FUNC_OFFSET: 20efdc0
FAILURE_BUCKET_ID: AV_amdkmdag!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c753a2f9-94a6-448f-1d0e-e079b3442215}
Followup: MachineOwner
---------
1: kd> lmvm amdkmdag
Browse full module list
start end module name
fffff807`31060000 fffff807`3765a000 amdkmdag T (no symbols)
Loaded symbol image file: amdkmdag.sys
Image path: amdkmdag.sys
Image name: amdkmdag.sys
Browse all global symbols functions data Symbol Reload
Timestamp: Wed Jun 18 03:42:42 2025 (6851C532)
CheckSum: 065A9C1B
ImageSize: 065FA000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
My specs:
Device name DESKTOP-IVHRL9V
Processor AMD Ryzen 5 5600G with Radeon Graphics (3.90 GHz)
Installed RAM 16.0 GB (15.4 GB usable)
Device ID FB3EB39D-7727-41FD-88C6-E51A0A38BF7C
Product ID 00330-80000-00000-AA889
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

Reply
Reply
G
GauteZEL
Member
Find
173
11-23-2025, 06:47 PM
#2
Welcome to the forums, newcomer! Please share .dmp files so we can examine them. The host mentioned files on a service similar to DropBox and then provided a link for us to review.

For troubleshooting, you might try using DDU. Launch the application in Safe Mode, remove all GPU drivers (Intel, Nvidia, AMD), then restart. After that, manually install the newest GPU driver via an elevated command—right-click the installer and select Run as Administrator.

Here are my specifications:
Device name: DESKTOP-IVHRL9V
Processor: AMD Ryzen 5 5600G with Radeon Graphics (3.90 GHz)
Installed RAM: 16.0 GB (15.4 GB available)
Device ID: FB3EB39D-7727-41FD-88C6-E51A0A38BF7C
Product ID: 00330-80000-00000-AA889
System type: 64-bit OS, x64-based processor
Pen and touch: No input available for this display
Reply
Reply
G
GauteZEL
11-23-2025, 06:47 PM #2

Welcome to the forums, newcomer! Please share .dmp files so we can examine them. The host mentioned files on a service similar to DropBox and then provided a link for us to review.

For troubleshooting, you might try using DDU. Launch the application in Safe Mode, remove all GPU drivers (Intel, Nvidia, AMD), then restart. After that, manually install the newest GPU driver via an elevated command—right-click the installer and select Run as Administrator.

Here are my specifications:
Device name: DESKTOP-IVHRL9V
Processor: AMD Ryzen 5 5600G with Radeon Graphics (3.90 GHz)
Installed RAM: 16.0 GB (15.4 GB available)
Device ID: FB3EB39D-7727-41FD-88C6-E51A0A38BF7C
Product ID: 00330-80000-00000-AA889
System type: 64-bit OS, x64-based processor
Pen and touch: No input available for this display

Reply
Reply
X
XxTBretzxX
Member
Find
134
11-23-2025, 06:47 PM
#3
Based on my observations, IRQL NOT LESS OR EQUAL was consistently linked to memory problems or hardware connection issues. Taking out and putting back graphics cards (if possible) along with reinserting system memory would be a simple initial action without cost. This is especially useful if you’ve been handling the device and might have disturbed it, or if you recently relocated your computer. Heavy GPU sag can also lead to unstable PCIe connections. If DDU doesn’t resolve the problem, running memtest86 can help verify if the system memory is intact. For the memory itself, either the iGPU’s memory is failing or the GPU’s VRAM is deteriorating. There are some VRAM testing tools available; I haven’t used them yet and am unsure of their effectiveness. Memtest vulkan seems to show potential.
Reply
Reply
X
XxTBretzxX
11-23-2025, 06:47 PM #3

Based on my observations, IRQL NOT LESS OR EQUAL was consistently linked to memory problems or hardware connection issues. Taking out and putting back graphics cards (if possible) along with reinserting system memory would be a simple initial action without cost. This is especially useful if you’ve been handling the device and might have disturbed it, or if you recently relocated your computer. Heavy GPU sag can also lead to unstable PCIe connections. If DDU doesn’t resolve the problem, running memtest86 can help verify if the system memory is intact. For the memory itself, either the iGPU’s memory is failing or the GPU’s VRAM is deteriorating. There are some VRAM testing tools available; I haven’t used them yet and am unsure of their effectiveness. Memtest vulkan seems to show potential.

Reply
Reply