AnsweredAssumed Answered

AMD Radeon 5700 failure in atikmdag.sys - Integer overflow

Question asked by kreuzerkrieg on Apr 20, 2020

Hi,

I started to get failures which leads to machine restart and memory dump with my brand new 5700.

When opening the MEMORY.DMP with WinGDB I get following stack trace

STACK_TEXT: 
ffffb007`1f7f6980 fffff804`22abac26 : ffffb301`770479e0 ffffe38c`1d310000 00000000`00000000 fffff804`22e56fe0 : atikmdag+0x15fc0a
ffffb007`1f7f69c0 fffff804`22b55f34 : ffffe38c`1949e9ec ffffb007`1f7f6e30 00000000`00201004 ffffb007`1f7f6e30 : atikmdag+0x21ac26
ffffb007`1f7f69f0 fffff804`22b26b81 : 00000000`00000000 ffffe38c`1ef8d000 00000000`00000000 ffffe38c`1c267020 : atikmdag+0x2b5f34
ffffb007`1f7f6d40 fffff804`228c5683 : 00000000`00000000 ffffb007`1f7f6e70 ffffb007`1f7f7170 00000000`00000000 : atikmdag+0x286b81
ffffb007`1f7f6d70 fffff804`1dad04fa : 00000000`00000001 fffff804`1d099b94 ffffb007`1f7f7170 fffff804`1dad0557 : atikmdag+0x25683
ffffb007`1f7f6f50 fffff804`1d184371 : ffffe38c`1b28e680 00000000`00000000 ffffe38c`20df4700 ffffb301`7708d670 : atikmpag+0x104fa
ffffb007`1f7f6fa0 fffff804`1d099a59 : 00000000`209e7701 ffffe38c`1a7d0820 ffffb007`1f7f71d0 00000000`00000886 : dxgkrnl!ADAPTER_RENDER::DdiBuildPagingBuffer+0x171
ffffb007`1f7f7050 fffff804`1e9128c0 : 00000000`00000886 00000003`00000000 00000000`00000001 00000000`00000000 : dxgkrnl!ADAPTER_RENDER_DdiBuildPagingBuffer+0x9
ffffb007`1f7f7080 fffff804`1e97f249 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000884 : dxgmms2!ADAPTER_RENDER::DdiBuildPagingBuffer+0x18
ffffb007`1f7f70b0 fffff804`1e97e12b : 00000000`00886000 ffffb301`7708d670 ffffb007`1f7f7350 ffffb301`746e0ba0 : dxgmms2!VIDMM_GLOBAL::FlushGpuVaTlb+0x1a9
ffffb007`1f7f72f0 fffff804`1e988df2 : ffffb301`7fe72738 00000000`00000003 00000000`00000030 ffffb301`7fe72720 : dxgmms2!CVirtualAddressAllocator::UncommitVirtualAddressRange+0x1ab
ffffb007`1f7f7420 fffff804`1e987cb1 : ffffe38c`20f14000 ffffe38c`00000000 ffffb007`1f7f7700 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::FlushPagingBufferInternal+0x732
ffffb007`1f7f7670 fffff804`1e997ee4 : 00000000`00000001 00000000`00989680 ffffb301`7f5280d0 00000000`00000001 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0x661
ffffb007`1f7f78e0 fffff804`1e997029 : ffffb301`746f8610 ffff9701`8fbed201 ffffe38c`1b28e600 00000000`00000000 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xea4
ffffb007`1f7f7ae0 fffff804`0666bcd5 : ffffe38c`1b28e680 fffff804`1e997020 ffffb301`746f8610 000024ef`b59bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffb007`1f7f7b10 fffff804`067c9998 : ffff9701`8fbdc180 ffffe38c`1b28e680 fffff804`0666bc80 00680067`0063006d : nt!PspSystemThreadStartup+0x55
ffffb007`1f7f7b60 00000000`00000000 : ffffb007`1f7f8000 ffffb007`1f7f1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

 

The full session attached.

 

Any ideas? Drivers are latest. No special scenario, like, machine is under heavy load. It may happen even when I browse using chrome.

 

Any ideas?

Attachments

Outcomes