Share via

how to fix DRIVER_IRQL_NOT_LESS_OR_EQUAL amdkmdag.sys

Anonymous
2023-12-09T15:36:07+00:00

Recently Ive been getting BSOD (about 4 times in different dates) while just browsing the web or doing non intensive normal laptop use. The latest error read stop code: DRIVER_IRQL_NOT_LESS_OR_EQUAL what failed: amdkmdag.sys I recently upgraded C drive and RAM and Im wondering whether that is the issue. However I have ran memory check utility, and it found no problems with memory. I as well ran check disk f/r/ .. checked for driver updates (it tells me I have the best version already installed). I ran the scannow utility and it fixed some corrupted files... but so far Im not sure the issue is fixed. Any idea of what may be going on based on error code or dump?

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: 0000000000000068, memory referenced Arg2: 000000000000000b, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff8048a6f4304, address which referenced memory

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 5281

Key  : Analysis.Elapsed.mSec
Value: 10602

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0xd1

Key  : Failure.Bucket
Value: AV\_amdkmdag!unknown\_function

Key  : Failure.Hash
Value: {c753a2f9-94a6-448f-1d0e-e079b3442215}

Key  : Hypervisor.Enlightenments.ValueHex
Value: 149fcf96

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: 0

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: 4722927

Key  : Hypervisor.Flags.ValueHex
Value: 4810ef

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: 3f7

Key  : WER.OS.Branch
Value: ni\_release

Key  : WER.OS.Version
Value: 10.0.22621.1

BUGCHECK_CODE: d1

BUGCHECK_P1: 68

BUGCHECK_P2: b

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8048a6f4304

FILE_IN_CAB: 120923-13046-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

READ_ADDRESS: fffff8045f31d470: 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 0000000000000068

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff80464143960 -- (.trap 0xfffff80464143960) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000060 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8048a6f4304 rsp=fffff80464143af0 rbp=fffff80464143b89 r8=fffff8048ab3dd38 r9=fffff8048aad38e8 r10=00000000000000b5 r11=00000000ff000380 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc amdkmdag+0x214304: fffff8048a6f4304 488b4008 mov rax,qword ptr [rax+8] ds:0000000000000068=???????????????? Resetting default scope

STACK_TEXT:
fffff80464143818 fffff8045ea2c1a9 : 000000000000000a 0000000000000068 000000000000000b 0000000000000000 : nt!KeBugCheckEx fffff80464143820 fffff8045ea27834 : ffff020000000000 0000000000000000 0000000000000000 fffff80489ae8580 : nt!KiBugCheckDispatch+0x69 fffff80464143960 fffff8048a6f4304 : fffff80464143b50 ffffd28b109ca000 0000000000000000 0000000000000000 : nt!KiPageFault+0x474 fffff80464143af0 fffff80464143b50 : ffffd28b109ca000 0000000000000000 0000000000000000 ffffd28b109cdfa0 : amdkmdag+0x214304 fffff80464143af8 ffffd28b109ca000 : 0000000000000000 0000000000000000 ffffd28b109cdfa0 fffff8048a6dc054 : 0xfffff80464143b50 fffff80464143b00 0000000000000000 : 0000000000000000 ffffd28b109cdfa0 fffff8048a6dc054 0000000000000000 : 0xffffd28b109ca000

SYMBOL_NAME: amdkmdag+214304

MODULE_NAME: amdkmdag

IMAGE_NAME: amdkmdag.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 214304

FAILURE_BUCKET_ID: AV_amdkmdag!unknown_function

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c753a2f9-94a6-448f-1d0e-e079b3442215}

Followup: MachineOwner

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-01-10T03:36:20+00:00

    Hello Dyari,

    I hope you had a great start to the new year.
    Thank you for your attentiveness to my issue, I decided to troubleshoot by reversing the upgrades I had recently performed on my machine, even though the info I found said RAM could be expanded up to 32gb, this turned out not to be the case, I believe I can attribute the BSOD to the new RAM modules causing perhaps electrical issues of some sort, as the BSOD has not happen again since I removed the upgrades, everything is now back to normal and the machine runs smooth as before. I will continue to observe it and report if any incidents take place again.

    Again thank you so much for your great disposition and assistance.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2023-12-09T18:57:16+00:00

    Thank a lot, this is very good advice, I will make sure to refer to my laptops manufacturer for any updates.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-12-09T18:56:31+00:00

    Hi Dyari,
    Thank you for your response, so what I mean by upgrade drive is that I acquired a new drive, cloned my original C drive to it and then replaced the original with the new cloned drive. It was an attempt to get more space as my original C drive was full. I believe the OS was installed on my original drive so I assumed there would not be any issue. I'm not much of a technical user but, could it be that the Graphics card driver is having compatibility issues with the new C drive? Should I look for drivers that are compatible with the new hardware, or are those two things unrelated?
    I will follow your instructions above and see if my problem goes away. I hope this fixes the issue.

    Was this answer helpful?

    0 comments
  4. DYARI BARHAM 34,266 Reputation points Independent Advisor
    2023-12-09T18:11:07+00:00

    Hi ,

    I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

    The minidump analysis indicates amdkmdag.sys as a cause of the BSOD which is related to the AMD graphics card device driver.

    If your computer encounters BSOD again, uninstall the current AMD graphics card driver completely using this DDU free utility, then download/install the latest graphics card driver or a driver that is compatible with your computer only from the manufacturer's official website:

    https://www.guru3d.com/files-details/display-dr...

    You mentioned that you upgraded the C drive and RAM, have you performed a clean install or what do you mean by upgrading the C drive?

    ____________________________________________________________

    Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-12-09T16:37:11+00:00

    Run that Laptop makers update utility, do not update from any other source, other than win11 critical updates

    Was this answer helpful?

    0 comments