Random Memory Related BSOD

Question

---

• *
• Bugcheck Analysis *
• *

  ---

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801d1e13510, The address that the exception occurred at
Arg3: ffffef823984c3b8, Exception Record Address
Arg4: ffffef823984bbf0, Context Record Address

Debugging Details:

---

*** WARNING: Unable to verify timestamp for amdkmdag.sys

KEY_VALUES_STRING: 1

Key  : AV.Fault
Value: Read

Key  : Analysis.CPU.Sec
Value: 2

Key  : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-DVT0M5T

Key  : Analysis.DebugData
Value: CreateObject

Key  : Analysis.DebugModel
Value: CreateObject

Key  : Analysis.Elapsed.Sec
Value: 44

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

Key  : Analysis.System
Value: CreateObject

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff801d1e13510

BUGCHECK_P3: ffffef823984c3b8

BUGCHECK_P4: ffffef823984bbf0

EXCEPTION_RECORD: ffffef823984c3b8 -- (.exr 0xffffef823984c3b8)
ExceptionAddress: fffff801d1e13510 (amdkmdag+0x00000000018d3510)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffab8100000000
Attempt to read from address ffffab8100000000

CONTEXT: ffffef823984bbf0 -- (.cxr 0xffffef823984bbf0)
rax=ffffab81793b8010 rbx=ffffab817e526da0 rcx=ffffab81793b8010
rdx=000000000000001b rsi=0000000000000000 rdi=0000000001d7b3e3
rip=fffff801d1e13510 rsp=ffffef823984c5f0 rbp=ffffab8100000000
r8=0000000000001024 r9=0000000000000042 r10=fffff801d08e81b0
r11=ffffef823984c610 r12=0000000000000001 r13=0000000000000000
r14=ffffab8100000000 r15=0000000000000001
iopl=0 nv up ei pl nz ac pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050213
amdkmdag+0x18d3510:
fffff801d1e13510 0f104500 movups xmm0,xmmword ptr [rbp] ss:0018:ffffab8100000000=????????????????????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff8047230f390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80472224368: Unable to get Flags value from nt!KdVersionBlock
fffff80472224368: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffab8100000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffab8100000000

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffffef823984c5f0 01d7b3e383ab828d : 0000000000000001 0000000000000000 0000000000000000 ffffffffffffffff : amdkmdag+0x18d3510
ffffef823984c5f8 0000000000000001 : 0000000000000000 0000000000000000 ffffffffffffffff ffffffffffffffff : 0x01d7b3e383ab828d ffffef823984c600 0000000000000000 : 0000000000000000 ffffffffffffffff ffffffffffffffff 00000000`00000000 : 0x1

SYMBOL_NAME: amdkmdag+18d3510

MODULE_NAME: amdkmdag

IMAGE_NAME: amdkmdag.sys

STACK_COMMAND: .cxr 0xffffef823984bbf0 ; kb

BUCKET_ID_FUNC_OFFSET: 18d3510

FAILURE_BUCKET_ID: AV_VRF_amdkmdag!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {916d0769-944d-f99a-9969-cfbc03077419}

Followup: MachineOwner

---

Answer 1

Run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive:

https://www.windowsq.com/t/bsod-posting-instructions.17/
https://www.windowsq.com/resources/v2-log-collector.8/
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.

Answer 2

Will be reinstalling the OS and checking settings, will update post if issue is resolved.

Answer 3

The websites have BSOD forums and have software to collect files.
There are multiple scripts all designed to collect files for BSOD troubleshooting.
DM is the oldest script but V2 collects more useful files for troubleshooting.
There is another website with a different script to download.

.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.