HELP!! Video TDR Failure (atikmpag.sys)

Toggle sidebar Toggle sidebar
P

phitzbear

Apr 15, 2018
19
0
10
Good evevning everyone! I'm having some really aggravating issues with a PC that I've just built. The system itself is setup as follows:

AMD Ryzen 5 2400g
Gigabyte GA-AB350 Gaming 3 motherboard
250gb Sandisk Plus SSD
16gb Corsair Vengeance 3000mhz RAM

I had some problems with the initial RAM kit that I purchased (one of the sticks was faulty). I received a replacement kit and installed them. I also went onto the Gigabyte website and made sure that all current audio and display drivers were installed correctly. However, here is the part that has become troublesome and aggravating. Once I installed the drivers for the display, my system started randomly throwing BSOD's stating "Video TDR Failure (atikmpag.sys). This is a new issue as I didn't seem to get this when I was only running the single 8gb stick of RAM whilst waiting for the replacement kit. I've used DDU Display Driver Uninstaller to remove the aforementioned driver that I got from both Windows Update as well as the Gigabyte website. Once I remove the driver I don't seem to have any more issues with the BSOD. However, with the driver removed my HDMI monitor speakers stop working (Windows says my Digital Display Audio is unplugged) and any games I try to play are ridiculously choppy almost to the point of being unplayable, even with their settings turned down as low as possible. If I go back in and install the AMD driver, my sound works again, and the games run great until a BSOD Video TDR failure shuts me down again. I simply cannot figure this out. I've tried everything I can think of. At the moment I am typing this on the computer as I do not have the AMD drivers installed, and everything is fine (as long as I don't want to play anything with sound or try to play any games). Can anyone help me? This is quite frustrating. I really appreciate anyone that can give me ideas or solutions!

P.S. - I noticed that when the driver is installed Device Manager lists my Display Adapter as "Ryzen 5 2400g with Vega Graphics" which is correct. When the drivers are rolled back it simply states "Microsoft Basic Display Adapter". Not sure if this information helps, but I thought I'd add it.
 
Sort by date Sort by votes
Good evening bajgur,

Thanks for the response! I did try loading drivers from AMD's website. At first I ran the automatic tool that will check for drivers for you, and it came back with nothing. I then came across a forum and someone had posted a link to an AMD support article.

https://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-for-Ryzen-Desktop-Processors-with-Radeon-Vega-Graphics-Release-Notes.aspx

I tried installing the driver and for a while it seemed to work okay. This afternoon when I got home, however, it BSOD'd again with the same stop code. I also tried checking for corrupted files but nothing came back as problematic. I've heard AMD is supposed to be releasing some new drivers for this chipset but as of right now I don't see anything new. Another funny thing I noticed is that when I uninstalled the drivers last night during my trial and error sessions, the ability to put the computer to sleep went away. When I had the drivers installed, I could select sleep mode in the power off menu. Weird...
 
Upvote 0 Downvote
Good afternoon! Here is the data from the latest dump file (there were five). All of them have identical errors. I couldn't figure out how to upload the entire file itself so I just used BlueScreenView. Let me know if you need anything else.

051618-6968-01.dmp 5/16/2018 9:04:41 PM 0x00000116 ffffe489`a4893010 fffff809`c115f814 ffffffff`c0000001 00000000`00000003 dxgkrnl.sys dxgkrnl.sys+1a0e68 x64 ntoskrnl.exe+197670 C:\WINDOWS\Minidump\051618-6968-01.dmp 8 15 17134 798,788 5/16/2018 9:06:13 PM

atikmpag.sys atikmpag.sys+f814 fffff809`c1150000 fffff809`c11d6000 0x00086000 0x5a79448c 2/6/2018 2:00:44 AM
dxgkrnl.sys dxgkrnl.sys+1a0e68 fffff809`bec40000 fffff809`beef9000 0x002b9000 0xc89d0c21 8/27/2076 2:30:57 AM
ntoskrnl.exe ntoskrnl.exe+478240 fffff801`db00b000 fffff801`db970000 0x00965000 0x5ae3f148 4/27/2018 11:58:00 PM
hal.dll fffff801`db970000 fffff801`db9fc000 0x0008c000 0x4252ff42 4/5/2005 5:12:34 PM
kd.dll fffff801`dbc00000 fffff801`dbc0b000 0x0000b000 0xfc97b795 4/16/2104 11:02:45 AM
mcupdate_AuthenticAMD.dll fffff809`bd850000 fffff809`bd86f000 0x0001f000 0x84956950 6/27/2040 12:32:16 AM
msrpc.sys fffff809`bd870000 fffff809`bd8d0000 0x00060000 0xb5c08636 8/17/2066 1:56:06 PM
ksecdd.sys fffff809`bd8d0000 fffff809`bd8fa000 0x0002a000 0xdd8efef6 10/16/2087 5:48:38 AM
werkernel.sys fffff809`bd900000 fffff809`bd911000 0x00011000 0x136c293e
CLFS.SYS fffff809`bd920000 fffff809`bd984000 0x00064000 0xff43c502 9/17/2105 7:50:26 AM
tm.sys fffff809`bd990000 fffff809`bd9b4000 0x00024000 0xda2d5b6c 12/28/2085 3:20:12 PM
PSHED.dll fffff809`bd9c0000 fffff809`bd9d7000 0x00017000 0xfcf5bfc7 6/26/2104 6:50:47 PM Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 10.0.17134.1 (WinBuild.160101.0800) Microsoft Corporation C:\WINDOWS\system32\PSHED.dll
BOOTVID.dll fffff809`bd9e0000 fffff809`bd9eb000 0x0000b000 0xa81902e1 5/15/2059 4:03:45 AM Microsoft® Windows® Operating System VGA Boot Driver 10.0.17134.1 (WinBuild.160101.0800) Microsoft Corporation C:\WINDOWS\system32\BOOTVID.dll
FLTMGR.SYS fffff809`bd000000 fffff809`bd069000 0x00069000 0x8801e691 4/22/2042 8:32:17 PM
clipsp.sys fffff809`bd070000 fffff809`bd172000 0x00102000 0x5acd898b 4/11/2018 12:05:31 AM
cmimcext.sys fffff809`bd180000 fffff809`bd18e000 0x0000e000 0x1f09445a 7/2/1986 11:10:18 AM
ntosext.sys fffff809`bd190000 fffff809`bd19c000 0x0000c000 0x0477fd3f
CI.dll fffff809`bd1a0000 fffff809`bd255000 0x000b5000 0xeb1ec6ac 12/31/2094 3:38:20 PM
cng.sys fffff809`bd260000 fffff809`bd312000 0x000b2000 0x2276b997 4/28/1988 12:48:23 AM
Wdf01000.sys fffff809`bd320000 fffff809`bd404000 0x000e4000 0xbd4591f4 8/16/2070 6:19:32 PM
WDFLDR.SYS fffff809`bd410000 fffff809`bd423000 0x00013000 0x5011fb77 7/26/2012 10:22:47 PM
WppRecorder.sys fffff809`bd430000 fffff809`bd43e000 0x0000e000 0x4a47fcc6 6/28/2009 7:29:10 PM
SleepStudyHelper.sys fffff809`bd440000 fffff809`bd44f000 0x0000f000 0x5a314e91 12/13/2017 12:00:17 PM
acpiex.sys fffff809`bd450000 fffff809`bd473000 0x00023000 0xa0dba1e7 7/9/2055 8:19:51 AM
mssecflt.sys fffff809`bd480000 fffff809`bd4cf000 0x0004f000 0x6fc8fd72 6/6/2029 8:24:18 AM
SgrmAgent.sys fffff809`bd4d0000 fffff809`bd4e5000 0x00015000 0x4f2a9e0c 2/2/2012 10:30:36 AM
ACPI.sys fffff809`bd4f0000 fffff809`bd595000 0x000a5000 0xa0d961e5 7/7/2055 3:22:13 PM
WMILIB.SYS fffff809`bd5a0000 fffff809`bd5ac000 0x0000c000 0x48839438 7/20/2008 3:38:32 PM
intelpep.sys fffff809`bd5b0000 fffff809`bd5df000 0x0002f000 0x5c331bb5 1/7/2019 5:28:21 AM
WindowsTrustedRT.sys fffff809`bd5e0000 fffff809`bd5f6000 0x00016000 0x4056bf1a 3/16/2004 4:47:22 AM
WindowsTrustedRTProxy.sys fffff809`bd600000 fffff809`bd60b000 0x0000b000 0x3ae94cce 4/27/2001 6:41:18 AM
pcw.sys fffff809`bd610000 fffff809`bd624000 0x00014000 0x69e0e92e 4/16/2026 9:50:38 AM
msisadrv.sys fffff809`bd630000 fffff809`bd63b000 0x0000b000 0x008e6d72
pci.sys fffff809`bd640000 fffff809`bd6a0000 0x00060000 0xdd60cb9a 9/11/2087 4:45:14 AM
vdrvroot.sys fffff809`bd6a0000 fffff809`bd6b2000 0x00012000 0x7bf7dad8 11/28/2035 1:36:24 AM
pdc.sys fffff809`bd6c0000 fffff809`bd6e8000 0x00028000 0xe1e24b35 2/2/2090 3:33:09 AM
CEA.sys fffff809`bd6f0000 fffff809`bd709000 0x00019000 0x214e2858 9/16/1987 1:57:44 AM
partmgr.sys fffff809`bd710000 fffff809`bd73d000 0x0002d000 0x5fff5c01 1/13/2021 4:45:53 PM
spaceport.sys fffff809`bd740000 fffff809`bd7d9000 0x00099000 0x4f2123e2 1/26/2012 5:58:58 AM
volmgr.sys fffff809`bd7e0000 fffff809`bd7f9000 0x00019000 0xc540d073 11/13/2074 2:26:59 PM
volmgrx.sys fffff809`be0b0000 fffff809`be10e000 0x0005e000 0xc730c894 11/24/2075 7:17:40 PM
mountmgr.sys fffff809`be110000 fffff809`be12e000 0x0001e000 0x4c39586d 7/11/2010 1:36:45 AM
storahci.sys fffff809`be130000 fffff809`be15a000 0x0002a000 0x867fc31b 7/3/2041 11:06:03 PM
storport.sys fffff809`be160000 fffff809`be1ef000 0x0008f000 0x8cffdc75 12/17/2044 5:05:57 AM
EhStorClass.sys fffff809`bda00000 fffff809`bda1c000 0x0001c000 0x72e0fc90 1/28/2031 2:15:44 AM
fileinfo.sys fffff809`bda20000 fffff809`bda3a000 0x0001a000 0xd50d6775 4/8/2083 11:57:41 AM
Wof.sys fffff809`bda40000 fffff809`bda7b000 0x0003b000 0x7d8bb8de 9/29/2036 9:47:10 AM
Ntfs.sys fffff809`bda80000 fffff809`bdcdb000 0x0025b000 0x4b0b9c42 11/24/2009 4:41:38 AM
Fs_Rec.sys fffff809`bdce0000 fffff809`bdced000 0x0000d000 0x0359fc60
ndis.sys fffff809`bdcf0000 fffff809`bde31000 0x00141000 0x79768074 7/29/2034 2:07:48 PM
NETIO.SYS fffff809`bde40000 fffff809`bdec9000 0x00089000 0x62e4197b 7/29/2022 1:31:39 PM
ksecpkg.sys fffff809`bded0000 fffff809`bdf00000 0x00030000 0xf1b128cb 6/29/2098 6:29:31 PM
amdpsp.sys fffff809`bdf00000 fffff809`bdf22000 0x00022000 0x59f38dae 10/27/2017 3:49:02 PM
tcpip.sys fffff809`be3c0000 fffff809`be664000 0x002a4000 0xd48b6654 12/30/2082 9:18:12 PM
fwpkclnt.sys fffff809`be670000 fffff809`be6e6000 0x00076000 0x27391fb0 11/8/1990 5:04:48 AM
wfplwfs.sys fffff809`be6f0000 fffff809`be71d000 0x0002d000 0x89c47b35 3/30/2043 3:06:29 PM
aswVmm.sys fffff809`be720000 fffff809`be77b000 0x0005b000 0x5ae36cf5 4/27/2018 2:33:25 PM
aswRvrt.sys fffff809`be780000 fffff809`be794000 0x00014000 0x5ae36cf2 4/27/2018 2:33:22 PM
fvevol.sys fffff809`be200000 fffff809`be2bc000 0x000bc000 0x715003b4 3/29/2030 10:47:16 PM
volume.sys fffff809`be2c0000 fffff809`be2cb000 0x0000b000 0xbbe7f72b 11/24/2069 1:58:03 PM
volsnap.sys fffff809`be2d0000 fffff809`be337000 0x00067000 0xbc6deacd 3/6/2070 4:29:01 AM
rdyboost.sys fffff809`be340000 fffff809`be38c000 0x0004c000 0x0364df2c
mup.sys fffff809`be390000 fffff809`be3b4000 0x00024000 0x84dbf4df 8/19/2040 12:46:23 PM
iorate.sys fffff809`be7a0000 fffff809`be7b1000 0x00011000 0x9b6d3859 8/18/2052 4:38:49 PM
disk.sys fffff809`be7d0000 fffff809`be7ec000 0x0001c000 0x24d85956 8/3/1989 10:40:22 AM
CLASSPNP.SYS fffff809`bdf30000 fffff809`bdf9b000 0x0006b000 0xe3348094 10/16/2090 4:27:00 PM
aswbuniva.sys fffff809`be7f0000 fffff809`be7fe000 0x0000e000 0x5a8ebb44 2/22/2018 8:44:52 AM
aswbloga.sys fffff809`bdfa0000 fffff809`bdff0000 0x00050000 0x5a8ebb46 2/22/2018 8:44:54 AM
aswbidsha.sys fffff809`bdff0000 fffff809`be01f000 0x0002f000 0x5a8ebb45 2/22/2018 8:44:53 AM
crashdmp.sys fffff809`be040000 fffff809`be05c000 0x0001c000 0x4a400171 6/22/2009 6:10:57 PM
cdrom.sys fffff809`bf370000 fffff809`bf39e000 0x0002e000 0x2339c22a 9/22/1988 11:16:58 PM
aswSP.sys fffff809`bea00000 fffff809`bea72000 0x00072000 0x5ae36d18 4/27/2018 2:34:00 PM
aswSnx.sys fffff809`bea80000 fffff809`beb78000 0x000f8000 0x5ae36d12 4/27/2018 2:33:54 PM
ks.sys fffff809`beb80000 fffff809`bebeb000 0x0006b000 0x5c0dff35 12/10/2018 1:52:53 AM
filecrypt.sys fffff809`bebf0000 fffff809`bec04000 0x00014000 0xbde52434 12/15/2070 7:13:56 PM
tbs.sys fffff809`bec10000 fffff809`bec1d000 0x0000d000 0x81533658 10/3/2038 6:24:24 AM
Null.SYS fffff809`bec20000 fffff809`bec2a000 0x0000a000 0x00000000
Beep.SYS fffff809`bec30000 fffff809`bec3a000 0x0000a000 0xe3c311b5 2/1/2091 7:48:05 PM
watchdog.sys fffff809`bef00000 fffff809`bef14000 0x00014000 0x702f9eef 8/23/2029 4:44:31 AM
vmbkmclr.sys fffff809`bef20000 fffff809`bef3a000 0x0001a000 0xd822a885 11/27/2084 3:53:41 AM
BasicDisplay.sys fffff809`bef40000 fffff809`bef56000 0x00016000 0x22daeda6 7/13/1988 12:57:10 AM
BasicRender.sys fffff809`bef60000 fffff809`bef70000 0x00010000 0x375f6f10 6/10/1999 3:53:52 AM
Npfs.SYS fffff809`bef70000 fffff809`bef8b000 0x0001b000 0x927defe8 11/18/2047 5:55:52 PM
Msfs.SYS fffff809`bef90000 fffff809`befa0000 0x00010000 0xbd01b948 6/26/2070 7:13:12 AM
tdx.sys fffff809`befa0000 fffff809`befc3000 0x00023000 0x9f3f7265 8/30/2054 4:43:17 PM
TDI.SYS fffff809`befd0000 fffff809`befe0000 0x00010000 0x814e4748 9/29/2038 12:35:20 PM
netbt.sys fffff809`befe0000 fffff809`bf034000 0x00054000 0xca7943ca 8/23/2077 7:47:22 AM
aswRdr2.sys fffff809`bf040000 fffff809`bf05a000 0x0001a000 0x5ae36d26 4/27/2018 2:34:14 PM
afunix.sys fffff809`bf060000 fffff809`bf073000 0x00013000 0x58f61eeb 4/18/2017 10:12:59 AM Microsoft® Windows® Operating System AF_UNIX socket provider 10.0.17134.1 (WinBuild.160101.0800) Microsoft Corporation C:\WINDOWS\system32\drivers\afunix.sys
afd.sys fffff809`bf080000 fffff809`bf11e000 0x0009e000 0xe5c2c597 2/24/2092 11:03:51 PM
vwififlt.sys fffff809`bf120000 fffff809`bf13a000 0x0001a000 0xe4e7506a 9/11/2091 11:57:30 AM
pacer.sys fffff809`bf140000 fffff809`bf169000 0x00029000 0x89d4206a 4/11/2043 11:55:22 AM
netbios.sys fffff809`bf170000 fffff809`bf182000 0x00012000 0xdbd51b1c 11/15/2086 1:26:52 AM
rdbss.sys fffff809`bf190000 fffff809`bf206000 0x00076000 0x4af1dd76 11/4/2009 4:00:54 PM
csc.sys fffff809`bf210000 fffff809`bf2a0000 0x00090000 0x78ee8014 4/17/2034 10:17:56 AM
nsiproxy.sys fffff809`bf2a0000 fffff809`bf2b2000 0x00012000 0xdc8ab40c 4/1/2087 7:19:40 PM
npsvctrig.sys fffff809`bf2c0000 fffff809`bf2cd000 0x0000d000 0xe9804b86 2/20/2094 6:14:30 AM
mssmbios.sys fffff809`bf2d0000 fffff809`bf2df000 0x0000f000 0xb89da2ef 2/24/2068 3:50:07 PM
gpuenergydrv.sys fffff809`bf2e0000 fffff809`bf2ea000 0x0000a000 0xa5e021dd 3/9/2058 3:56:13 PM
dfsc.sys fffff809`bf2f0000 fffff809`bf319000 0x00029000 0xc3b07a93 1/13/2074 10:33:55 PM
fastfat.SYS fffff809`bf3a0000 fffff809`bf400000 0x00060000 0x283996c3 5/21/1991 5:53:07 PM
bam.sys fffff809`bf320000 fffff809`bf334000 0x00014000 0xf0ef718f 2/2/2098 8:00:15 PM
aswHdsKe.sys fffff809`bf800000 fffff809`bf839000 0x00039000 0x5ae3723a 4/27/2018 2:55:54 PM
aswbidsdrivera.sys fffff809`bf840000 fffff809`bf879000 0x00039000 0x5a8ebb41 2/22/2018 8:44:49 AM
aswArPot.sys fffff809`bf880000 fffff809`bf8d4000 0x00054000 0x5ae36cf2 4/27/2018 2:33:22 PM
ahcache.sys fffff809`bf8e0000 fffff809`bf925000 0x00045000 0xaab4c5e7 10/2/2060 4:17:43 PM
CompositeBus.sys fffff809`bf930000 fffff809`bf941000 0x00011000 0xe21758c8 3/14/2090 9:21:12 AM
kdnic.sys fffff809`bf950000 fffff809`bf95d000 0x0000d000 0x6e754fcc 9/21/2028 4:45:00 PM
umbus.sys fffff809`bf960000 fffff809`bf975000 0x00015000 0x05f32a4b
USBXHCI.SYS fffff809`bf980000 fffff809`bf9ef000 0x0006f000 0x20dd3918 6/22/1987 10:03:04 AM
ucx01000.sys fffff809`bf400000 fffff809`bf43c000 0x0003c000 0xf946307a 7/12/2102 1:51:54 AM
rt640x64.sys fffff809`bf470000 fffff809`bf508000 0x00098000 0x57f50107 10/5/2016 9:32:55 AM
rtwlane.sys fffff809`c09c0000 fffff809`c106a000 0x006aa000 0x591d043d 5/17/2017 10:17:33 PM
wdiwifi.sys fffff809`c1070000 fffff809`c1136000 0x000c6000 0x9e200ed1 1/24/2054 4:57:53 PM
vwifibus.sys fffff809`c1140000 fffff809`c114e000 0x0000e000 0xf93718a7 6/30/2102 3:06:15 PM
atikmdag.sys fffff809`c4800000 fffff809`c6ef0000 0x026f0000 0x5a794c49 2/6/2018 2:33:45 AM
HDAudBus.sys fffff809`c6ef0000 fffff809`c6f0d000 0x0001d000 0xa500e2b9 9/21/2057 7:51:21 AM
portcls.sys fffff809`c6f10000 fffff809`c6f74000 0x00064000 0x0d3dae7d
drmk.sys fffff809`c6f80000 fffff809`c6fa1000 0x00021000 0x5dbfba6e 11/4/2019 1:43:10 AM
amdhdaudbus.sys fffff809`c3a30000 fffff809`c3a47000 0x00017000 0x5a7174dc 1/31/2018 3:48:44 AM
amdppm.sys fffff809`c3a50000 fffff809`c3a88000 0x00038000 0x369f847d 1/15/1999 2:10:05 PM
amdgpio2.sys fffff809`c3a90000 fffff809`c3a9c000 0x0000c000 0x59a6949e 8/30/2017 6:34:06 AM
msgpioclx.sys fffff809`c3aa0000 fffff809`c3acd000 0x0002d000 0x23af5beb 12/21/1988 4:08:11 AM
wmiacpi.sys fffff809`c3ad0000 fffff809`c3adc000 0x0000c000 0x953bfbdd 5/4/2049 6:18:05 AM
UEFI.sys fffff809`c3ae0000 fffff809`c3aed000 0x0000d000 0x55bb8792 7/31/2015 10:34:58 AM
NdisVirtualBus.sys fffff809`c3af0000 fffff809`c3afd000 0x0000d000 0x9bcae864 10/28/2052 6:10:44 PM
swenum.sys fffff809`c3b00000 fffff809`c3b0c000 0x0000c000 0x2d51afcf 2/3/1994 10:15:43 PM
rdpbus.sys fffff809`c3b10000 fffff809`c3b1e000 0x0000e000 0x73e6fc15 8/14/2031 7:47:33 PM
UsbHub3.sys fffff809`c3b20000 fffff809`c3bae000 0x0008e000 0x8298c746 6/7/2039 5:09:26 AM
USBD.SYS fffff809`c3bb0000 fffff809`c3bbe000 0x0000e000 0xa9e461ec 4/27/2060 2:39:40 PM
AtihdWT6.sys fffff809`c3bc0000 fffff809`c3bde000 0x0001e000 0x5a0d1e2f 11/16/2017 1:12:15 AM
ksthunk.sys fffff809`c3be0000 fffff809`c3bef000 0x0000f000 0xeff99365 7/31/2097 8:07:01 AM
RTKVHD64.sys fffff809`c3bf0000 fffff809`c4203000 0x00613000 0x5a672a89 1/23/2018 8:28:57 AM
usbccgp.sys fffff809`c4210000 fffff809`c423f000 0x0002f000 0x8237b6ce 3/25/2039 2:09:18 PM
hidusb.sys fffff809`c4240000 fffff809`c4252000 0x00012000 0x6c1deea7 6/25/2027 1:22:47 AM
HIDCLASS.SYS fffff809`c4260000 fffff809`c4293000 0x00033000 0xcaee9942 11/20/2077 7:47:14 AM
HIDPARSE.SYS fffff809`c42a0000 fffff809`c42b3000 0x00013000 0x153ce4e8
kbdhid.sys fffff809`c42c0000 fffff809`c42d0000 0x00010000 0xd368c0f3 5/24/2082 10:15:15 AM
kbdclass.sys fffff809`c42d0000 fffff809`c42e3000 0x00013000 0x60a94cdb 5/22/2021 2:26:35 PM
mouhid.sys fffff809`c42f0000 fffff809`c42ff000 0x0000f000 0x81b3c45f 12/15/2038 12:07:59 PM
mouclass.sys fffff809`c4300000 fffff809`c4311000 0x00011000 0xec0ac493 6/28/2095 3:44:19 PM
win32k.sys ffff8c6c`104f0000 ffff8c6c`1056c000 0x0007c000 0x00000000 Microsoft® Windows® Operating System Full/Desktop Multi-User Win32 Driver 10.0.17134.1 (WinBuild.160101.0800) Microsoft Corporation C:\WINDOWS\system32\win32k.sys
win32kfull.sys ffff8c6c`0fa00000 ffff8c6c`0fd92000 0x00392000 0x00000000 Microsoft® Windows® Operating System Full/Desktop Win32k Kernel Driver 10.0.17134.48 (WinBuild.160101.0800) Microsoft Corporation C:\WINDOWS\system32\win32kfull.sys
win32kbase.sys ffff8c6c`0fda0000 ffff8c6c`0ffd4000 0x00234000 0x00000000
dump_diskdump.sys fffff809`c4570000 fffff809`c457f000 0x0000f000 0x2a6cabdf 7/21/1992 8:29:19 PM
dump_storahci.sys fffff809`c45b0000 fffff809`c45da000 0x0002a000 0x867fc31b 7/3/2041 11:06:03 PM
dump_dumpfve.sys fffff809`c4600000 fffff809`c461d000 0x0001d000 0x29a47807 2/20/1992 11:54:47 PM
dxgmms2.sys fffff809`c4620000 fffff809`c46e6000 0x000c6000 0xd256f91b 10/28/2081 6:13:47 PM
monitor.sys fffff809`c46f0000 fffff809`c4701000 0x00011000 0x8ce3b5d7 11/25/2044 8:37:43 PM
cdd.dll ffff8c6c`0ffe0000 ffff8c6c`1001f000 0x0003f000 0x00000000
luafv.sys fffff809`c4710000 fffff809`c4737000 0x00027000 0x8a309bd4 6/20/2043 3:30:28 PM
wcifs.sys fffff809`c4740000 fffff809`c4768000 0x00028000 0x6760d68e 12/16/2024 9:40:30 PM
cldflt.sys fffff809`c4770000 fffff809`c47de000 0x0006e000 0x4289562d 5/16/2005 10:25:49 PM
storqosflt.sys fffff809`c47e0000 fffff809`c47f9000 0x00019000 0x4d24b03b 1/5/2011 1:54:03 PM
aswMonFlt.sys fffff809`c6fb0000 fffff809`c6fdb000 0x0002b000 0x5ae36cf5 4/27/2018 2:33:25 PM
aswStm.sys fffff809`c4320000 fffff809`c4353000 0x00033000 0x5ae37258 4/27/2018 2:56:24 PM
lltdio.sys fffff809`c4360000 fffff809`c4376000 0x00016000 0x4cbd7998 10/19/2010 6:57:28 AM
mslldp.sys fffff809`c4380000 fffff809`c439a000 0x0001a000 0x116a02f2
rspndr.sys fffff809`c43a0000 fffff809`c43ba000 0x0001a000 0x9ef4ac0e 7/4/2054 11:29:18 PM
wanarp.sys fffff809`c43c0000 fffff809`c43db000 0x0001b000 0xd8d929b9 4/14/2085 2:17:29 PM
ndisuio.sys fffff809`c43e0000 fffff809`c43f6000 0x00016000 0xf3c01832 8/3/2099 11:03:14 AM
nwifi.sys fffff809`c4400000 fffff809`c4487000 0x00087000 0xb0be7268 12/19/2063 2:25:44 AM
condrv.sys fffff809`c4490000 fffff809`c44a2000 0x00012000 0x80baee40 6/9/2038 6:12:16 PM
vwifimp.sys fffff809`c44b0000 fffff809`c44c2000 0x00012000 0x280490bb 4/11/1991 12:37:15 PM
HTTP.sys fffff809`c0200000 fffff809`c0302000 0x00102000 0xc2cb6b10 7/24/2073 4:38:40 AM
bowser.sys fffff809`c44d0000 fffff809`c44f1000 0x00021000 0x47ed4048 3/28/2008 3:00:24 PM
mpsdrv.sys fffff809`c4500000 fffff809`c4519000 0x00019000 0x2c309431 6/29/1993 3:12:49 PM
mrxsmb.sys fffff809`c0310000 fffff809`c0392000 0x00082000 0x4bd73b92 4/27/2010 3:31:30 PM
mrxsmb20.sys fffff809`c4520000 fffff809`c455d000 0x0003d000 0xec01de9f 6/21/2095 9:45:03 PM
mmcss.sys fffff809`c6fe0000 fffff809`c6ff3000 0x00013000 0x589c62b0 2/9/2017 8:38:08 AM
AMDRyzenMasterDriver.sys fffff809`c03a0000 fffff809`c03d4000 0x00034000 0x5a0a8604 11/14/2017 1:58:28 AM
srvnet.sys fffff809`c03e0000 fffff809`c0428000 0x00048000 0xf3834140 6/18/2099 7:30:08 AM
peauth.sys fffff809`c0430000 fffff809`c04f0000 0x000c0000 0x7d74b6fa 9/11/2036 10:56:58 PM
mrxsmb10.sys fffff809`c04f0000 fffff809`c053e000 0x0004e000 0x87e93140 4/4/2042 2:44:16 AM
Ndu.sys fffff809`c3a00000 fffff809`c3a27000 0x00027000 0x9d155c46 7/6/2053 9:53:10 AM
rzpnk.sys fffff809`c0540000 fffff809`c055e400 0x0001e400 0x59c2ed32 9/20/2017 6:35:30 PM
tcpipreg.sys fffff809`c0560000 fffff809`c0573000 0x00013000 0x701528f7 8/3/2029 3:02:15 AM
srv2.sys fffff809`c0580000 fffff809`c063c000 0x000bc000 0x0ef6d275
rassstp.sys fffff809`c0640000 fffff809`c065b000 0x0001b000 0xcd5601b9 3/2/2079 2:56:57 AM
NDProxy.sys fffff809`c0660000 fffff809`c0676000 0x00016000 0x5b6e1d85 8/10/2018 7:19:33 PM
AgileVpn.sys fffff809`c0680000 fffff809`c06a7000 0x00027000 0xb96f50a5 8/1/2068 4:55:01 PM
rasl2tp.sys fffff809`c06b0000 fffff809`c06d0000 0x00020000 0xd79956b1 8/15/2084 12:04:01 AM
raspptp.sys fffff809`c06d0000 fffff809`c06ef000 0x0001f000 0xdee494f8 7/1/2088 8:11:36 AM
raspppoe.sys fffff809`c06f0000 fffff809`c070b000 0x0001b000 0xd6217902 11/3/2083 9:38:10 PM
ndistapi.sys fffff809`c0710000 fffff809`c071f000 0x0000f000 0x00868de5
ndiswan.sys fffff809`c0720000 fffff809`c0757000 0x00037000 0x211f91fd 8/11/1987 5:51:57 PM
gdrv.sys fffff809`c0760000 fffff809`c076b000 0x0000b000 0x5a20eb65 12/1/2017 1:40:53 AM


 
Upvote 0 Downvote


Woodmass yes it's frustrating. I know AMD is working on a fix from what I've heard. Hopefully a driver will be released soon.
 
Upvote 0 Downvote
Woodmass yes it's frustrating. I know AMD is working on a fix from what I've heard. Hopefully a driver will be released soon.
[/quotemsg]

That is music to my ears. Hopefully soon. Do you mind linking your sources? I'd like to know whats happening and hopefully keep up to date with amd.

Thanks
 
Upvote 0 Downvote


That is music to my ears. Hopefully soon. Do you mind linking your sources? I'd like to know whats happening and hopefully keep up to date with amd.

Thanks[/quotemsg]

I opened a ticket with AMD and they sent me an email that reads as follows...

"Thank you for the email.

I understand you are experiencing BSOD issue on
your computer with AMD Ryzen 5 2400G APU.

We have received similar reports about the issue and our
driver team is currently working on a fix for this. I request you to revert to
Microsoft basic display adapter as of now and wait
for driver release with issue fixed.

We apologize for the
inconvenience caused.

Thank you for
contacting AMD.

Thing is I tried what they suggested and while it resulted in me no longer having BSOD's, I could no longer hear any sound through my HDMI monitor speakers, all games ran like I was playing them on a mid 90's Dell Dimension using onboard integrated graphics, and I can't sleep the computer.

 
Upvote 0 Downvote
Good morning guys! Bajgur, thanks for your continued assistance with the issues that I've been having. I attempted to try the procedure that you suggested but was not able to do so (was not able to find atikmpag.sy_ anywhere on my computer). I completely wiped all drivers out through both DDU Uninstaller in safe mode as well as the AMD Removal Utility. I received another email from AMD stating that they'd released a new driver for Raven Ridge processors. I've listed the link down below. After installing this new set of drivers, at first the machine ran fine. Then, before I called it a night last night it crashed again with the Video TDR Failure like always. This morning I decided to try something completely different. First I ran a test on my RAM to make sure it wasn't faulty. MemTest64 didn't bring up any errors. I swapped the sticks around and tried running the PC as normal. It once again BSOD'd, this time before the machine even got to the Windows login screen. I turned the machine off, removed the second stick of RAM, and restarted the PC. I uninstalled the new drivers and rebooted again. This time I let Windows search for updates and it proceeded to install drivers from back in January. Right now the system seems very stable. I've not had any BSOD's for about a half hour. This leads me to another question. Could the second DIMM slot be faulty on my motherboard and cause these errors? This is my second set of RAM that I've used. The first set had a faulty stick and I had to return it. Keep in mind all of this hardware is brand new. I'm using Corsair Vengeance 3000mhz DDR4 RAM, which is supposed to be pretty reliable. I'm just curious as to if all of my issues are being caused by a bad DIMM slot. I'll update further after I've ran my system a while.

Here is the link to the new AMD drivers that were released (per an AMD support email I received)

https://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Adrenalin-Edition-Q2-2018-Release-Notes.aspx
 
Upvote 0 Downvote
1. atikmpag.sy_ supposed to be in your downloaded driver folder (not installed). youll need to extract the downloaded driver manually (using 7zip/winrar).

2. to test your ram, use memtest86 and let it run at least 8 completed passes.
 
Upvote 0 Downvote


Thanks for the information! I've tested the memory with MemTest 86 and I didn't get any errors. I wanted to make note of something that I noticed this morning when messing around with the memory though. It seems that if I run the system with just a single stick of 8gb RAM in either the first or second DIMM slot the system appears to run just fine. Whenever I get BSOD's it is with both sticks installed. This leads me to believe that something isn't right with either the RAM voltages or CPU voltage. I'm a newbie to overclocking - this, along with the near identical one I built for my wife, are probably the first true gaming rigs that I have ever built. At this moment I have my XMP turned on and my RAM running right at 3000mhs and so far so good. The question now is what is causing my system to freak out on 16gb RAM. What should the voltages be and do I need to bump up anything in my CPU settings to get it to stabilize. My motherboard will support speeds of up to 3200mhz, which is well beyond what my RAM is rated (3000mhz). My wife is running 16gb RAM at around 2900 mhz without any problem at all on her machine. I believe that I have hers setup with XMP turned on as well. I'm going to go through and take note of all of her settings and see what I can come up with. Until then lemme know what you think.
 
Upvote 0 Downvote
MERGED QUESTION
Question from phitzbear : "BSOD VIDEO_TDR_FAILURE (ATIKMPAG.SYS) when using 16GB RAM"

Good afternoon everyone,

I've ran into a bit of a problem that I need some assistance with. I recently built a new budget gaming system using the Ryzen 5 2400g processor. I also installed 16gb Corsair Vengeance DDR RAM and Gigabyte GA-AB350 Gaming 3 motherboard, which will support RAM speeds up to 3200mhz. However, whenever I try to run any games or even view web pages my PC throws a BSOD stating VIDEO_TDR_FAILURE (ATIKMPAG.SYS). Funny thing is that I can remove the second stick of memory and the system seems to be stable with just the single 8gb stick in place. I get much better framerates when using both sticks so I would much rather have them both installed. Any of you overclocking gurus out there know how I can setup this RAM so that it will run stable? I am a newbie at overclocking anything in general and right now as I am typing this I'm just running a single 8gb stick of RAM, using XMP with the clock speed set right at 3000mhz. There has to be some issue with voltages or settings that is causing the PC to throw a BSOD every time I try to run it with the full memory kit installed. Any ideas or help you guys can give me would be awesome!

**NOTE**
I have ran MemTest86 on the memory itself with no errors reported. Both sticks seem to be fine.
 
Upvote 0 Downvote


So far haven't found an issue with the RAM. I tried checking the downloaded driver folder but still can't seem to find the atikmpag.sy_ file. Right now I am running the system with just one 8gb stick installed as it runs completely fine this way. It makes no sense that it doesn't want to cooperate with the other module installed. Perhaps there is an issue with voltages or the CPU not being able to handle the extra RAM without a bump of some sort? I've saved some system information on my Microsoft OneDrive if you'd like to view it.
 
Upvote 0 Downvote
Phitzbear, did you ever remedy this situation? It sounds a lot like the problems I've been having with my Ryzen 3 build: 2 sticks of RAM causes boot loop (on previous BIOS it would boot and crash with Memory Management or something else). Runs fine on 2 old sticks or either 1 of the new sticks. And any time I install the AMD drivers I get the VIDEO_TDR_FAILURE BSOD after logging into windows. I suspect something with voltages as well. I've also been unable to change the atikmpag.sys file in the windows folder due to an access error. It says I do not have permission even though I have admin rights.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom