cancel
Showing results for 
Search instead for 
Did you mean: 

Drivers & Software

maytic
Journeyman III

atikmdag.sys causing bsod

Ive tried everything 

specs 

PrimeA320M-K motherboard 

ryzen 1300x 

rx 570 

8gb ram

ram test show now errors 

DMP File:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17763 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff803`11a98000 PsLoadedModuleList = 0xfffff803`11eb3ad0
Debug session time: Sat Feb 2 21:16:44.452 2019 (UTC - 5:00)
System Uptime: 0 days 1:25:31.159
*******************************************************************************

Bugcheck Analysis

*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffb5f994e00000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80320ec3381, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


Could not read faulting driver name
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffb5f994e00000

FAULTING_IP:
atikmdag+13381
fffff803`20ec3381 488b02 mov rax,qword ptr [rdx]

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffffa0811444550 -- (.trap 0xfffffa0811444550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffdff000 rbx=0000000000000000 rcx=ffffb5f990c00000
rdx=ffffb5f994e00000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80320ec3381 rsp=fffffa08114446e0 rbp=ffffdb8ff9256000
r8=0000000000000000 r9=0000000000008040 r10=ffffb5f994e00000
r11=ffffb5f990c00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po cy
atikmdag+0x13381:
fffff803`20ec3381 488b02 mov rax,qword ptr [rdx] ds:ffffb5f9`94e00000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80311c7ae9b to fffff80311c4b440

STACK_TEXT:
fffffa08`11444268 fffff803`11c7ae9b : 00000000`00000050 ffffb5f9`94e00000 00000000`00000000 fffffa08`11444550 : nt!KeBugCheckEx
fffffa08`11444270 fffff803`11b9f957 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffb5f9`94e00000 : nt!MiSystemFault+0x1ac1db
fffffa08`114443b0 fffff803`11c58f83 : fffff803`62bdc000 fffff803`62bdc000 ffffdb8f`f65f6c30 00000000`00000002 : nt!MmAccessFault+0x327
fffffa08`11444550 fffff803`20ec3381 : ffffdb8f`eada1020 ffffdb8f`eada1000 00000000`00000000 fffffa08`114447b4 : nt!KiPageFault+0x343
fffffa08`114446e0 ffffdb8f`eada1020 : ffffdb8f`eada1000 00000000`00000000 fffffa08`114447b4 ffffdb8f`f66676b0 : atikmdag+0x13381
fffffa08`114446e8 ffffdb8f`eada1000 : 00000000`00000000 fffffa08`114447b4 ffffdb8f`f66676b0 fffff803`20efdaf9 : 0xffffdb8f`eada1020
fffffa08`114446f0 00000000`00000000 : fffffa08`114447b4 ffffdb8f`f66676b0 fffff803`20efdaf9 ffffdb8f`eada1000 : 0xffffdb8f`eada1000


STACK_COMMAND: kb

FOLLOWUP_IP:
atikmdag+13381
fffff803`20ec3381 488b02 mov rax,qword ptr [rdx]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: atikmdag+13381

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5c368cf5

FAILURE_BUCKET_ID: X64_AV_atikmdag+13381

BUCKET_ID: X64_AV_atikmdag+13381

Followup: MachineOwner
---------


This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)
Show DivCrash Code Links
Show DivInformation About Address 0xffffb5f994e00000

0 Likes
0 Replies