What version of the old AMD driver are you using?
Page Fault In Non Paged Area triggered by amdkmdag.sys
Hey, so recently one of my OS disk had windows confused and it basically broke so I reinstalled windows on a whole new SSD and it works great.
For some reason i randomly get BSoD's with the same error as the title but not even in game. When i exit a fullscreen, read a video file .. that's when it is most likely to crash, but it's unpredictable .
Before learning about minidumps, i verified disks with chkdsk, checked my ram with a memory diagnosis, of course no errors came out.
Then I learned about minidumps. It took me a while to find out with windows debugger that it was a driver problem (AMD) as said in the title, so I used DDU and then installed an older driver that was said to be more stable than the most recent one (the most recent causes crashes even when reinstalled).
For now it hasn't crashed since, i just wanted to share my minidump analysis to see if it could be something else since i'm not an expert at all concerning Windows.
And it's also to be certain that the issue will be fixed because it kinda makes me anxious to know i could crash randomly xD
GPU : Sapphire Pulse Radeon 6800XT
CPU : Ryzen 9 5900X
I have more minidumps if necessary
Thank you
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffe613ae838f00, memory referenced.
Arg2: 0000000000000002, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff8011f44b1db, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
*** WARNING: Unable to verify timestamp for amdkmdag.sys
KEY_VALUES_STRING: 1
Key : AV.Type
Value: Write
Key : Analysis.CPU.mSec
Value: 1686
Key : Analysis.Elapsed.mSec
Value: 2879
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: 1436
Key : Analysis.Init.Elapsed.mSec
Value: 11279
Key : Analysis.Memory.CommitPeak.Mb
Value: 94
Key : Bugcheck.Code.LegacyAPI
Value: 0x50
Key : Dump.Attributes.AsUlong
Value: 21808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
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\_W\_(null)\_amdkmdag!unknown\_function
Key : Failure.Hash
Value: {62e34d33-e524-302e-8f57-324e4cc24377}
Key : Hypervisor.Enlightenments.ValueHex
Value: 7497cf94
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: 24a10ef
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
BUGCHECK_CODE: 50
BUGCHECK_P1: ffffe613ae838f00
BUGCHECK_P2: 2
BUGCHECK_P3: fffff8011f44b1db
BUGCHECK_P4: 2
FILE_IN_CAB: 032125-11015-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump
READ_ADDRESS: fffff8017d7c34b0: 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
ffffe613ae838f00
MM_INTERNAL_CODE: 2
IMAGE_NAME: amdkmdag.sys
MODULE_NAME: amdkmdag
FAULTING_MODULE: fffff8011dd00000 amdkmdag
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffff9c8017825a50 -- (.trap 0xffff9c8017825a50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe60a3c7746b0 rbx=0000000000000000 rcx=000000003c738200
rdx=000000012e418a00 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8011f44b1db rsp=ffff9c8017825be0 rbp=ffffe60a3c735308
r8=ffffe60a1483c000 r9=ffffe60a3c773ee0 r10=ffffe60a3c738200
r11=ffffe60a13910000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
amdkmdag+0x174b1db:
fffff8011f44b1db 41c744d12009000000 mov dword ptr [r9+rdx*8+20h],9 ds:ffffe613ae838f00=????????
Resetting default scope
STACK_TEXT:
ffff9c80178257e8 fffff8017cac9301 : 0000000000000050 ffffe613ae838f00 0000000000000002 ffff9c8017825a50 : nt!KeBugCheckEx
ffff9c80178257f0 fffff8017ca8ebdf : ffffe613ae838f00 0000000000001000 0000000000000002 fffff8017c800000 : nt!MiSystemFault+0x735
ffff9c80178258e0 fffff8017ce880cb : ffff9c8017826150 fffff8011f42c57a 0000000000000000 0000000000000003 : nt!MmAccessFault+0x2ff
ffff9c8017825a50 fffff8011f44b1db : 0000000000000000 0000000000000006 ffffe60a3c77495c fffff8011f420a14 : nt!KiPageFault+0x38b
ffff9c8017825be0 0000000000000000 : 0000000000000006 ffffe60a3c77495c fffff8011f420a14 ffffe60a3c7746b4 : amdkmdag+0x174b1db
SYMBOL_NAME: amdkmdag+174b1db
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 174b1db
FAILURE_BUCKET_ID: AV_W_(null)_amdkmdag!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {62e34d33-e524-302e-8f57-324e4cc24377}
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.
2 answers
Sort by: Most helpful
-
Anonymous
2025-04-12T15:35:22+00:00 -
Anonymous
2025-03-22T09:09:58+00:00 Hello Zeshikrom,
Thanks for reaching out here in the Microsoft Answers Community.
The "amdkmdag" driver is indeed part of the AMD GPU drivers. Since the debugging information has been removed by the driver, we are unable to determine the exact cause.
Since you have mentioned that the issue is gone after installing an older driver, I recommend using this troubleshooter to hide the GPU driver updates, and wait for a new stable driver.
Thanks for your patience and understanding.
Best Regards,
Sheng G. - MSFT | Microsoft Community Support Specialist