Error 0x15 for amdkmdap in Events viewer

2019-10-26

Question

_{Saturday, October 26, 2019 7:27 PM}

Hello, I have a RX 460 4GB GPU. Whenever I try to install any driver version for it, I get a error in events viewer. The error code is 0x15. It says that my display adapter had a problem starting. I have a AB350M GAMING 3 Motherboard with up to date BIOS. Also I have replaced my card with another RX 460 under RMA. However the error is still there. I have re-installed windows and all its updates. Also I have upgraded my RAM to 16GB dual channel. Nothing helped to solve the error. In AMD folder containing driver installation log it reports that the DGPU failed to turn on and there was a error in setup.cfg file in GPU drivers. My chipset drivers are up to date. Please help. I have windows 10 version 1903.

All replies (15)

_{Saturday, October 26, 2019 11:37 PM}

Uninstall the graphic card via Device Manager along with application if any.

Suggestions:

#Once done reboot and let OS detect the hardware, get things updated this time via Windows Update. Do you find any difference?

# Try to install driver in Safe mode.

# Open an AMD Online Support Ticket: Online Service Request

S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP

_{Sunday, October 27, 2019 2:54 AM}

I have tried all of these steps earlier. Windows update does not install updates correctly. It does not install the latest version and it does not install radeon settings. Is it a motherboard hardware issue? Motherboard is the only thing left which I did not RMA.

_{Sunday, October 27, 2019 5:15 AM}

https://drive.google.com/open?id=1pGulpu3Wgc_bUX_wngzSs9dL1Gl_IFxq

https://drive.google.com/open?id=1elmnVW1a72DFh4XkX7meavyVAXdBJv8V

https://drive.google.com/open?id=1kGqZGHdCxK232nwLWR9EKxuzTQD289nJ

https://drive.google.com/open?id=1x-ozvfsgJKhgRYP3AHi8W6rv1WEe0e7T

https://drive.google.com/open?id=1aRsADZLfpYI9dh6jELhZ-fnO9sRYlgVL

https://drive.google.com/open?id=1NzpPwhonurdwOARIBHgoXhOQ1KHsuRnp

https://drive.google.com/open?id=1T8_cQkxY1nHspKxKnECmZ5qrssLKN7KF

_{Sunday, October 27, 2019 7:52 AM}

Multiple files were missing.

Please follow the instructions in the prior post: Post just one share link with all of the requested files.

Make sure Msinfo32 is included and saved as NFO.

Make sure dxdiag is included in the share link.

Make sure the event viewer files are saved as a txt file and that this file is included in the single share link.

What was seen in device manager?

_{Sunday, October 27, 2019 8:22 AM}

I did not see any exclamation masks in device manager.

Here is a single link-https://drive.google.com/open?id=1RqqyvsIssQNLa0QGJ8gYfUTrOKouY1wC

The .nfo file is not recognised by onedrive.

_{Sunday, October 27, 2019 9:31 AM}

An hour was spent making a reply.

The website flagged it as spam and deleted the post.

I'm going to bed.

All the work was for nothing.

The website keeps flagging entries as spam and you don't know when it could happen.

This was reported many times has not been fixed.

_{Sunday, October 27, 2019 11:08 AM}

What??? But still you can tell me the solution I guess?

_{Monday, October 28, 2019 5:45 AM}

Here is my boot log file if you need it-https://drive.google.com/open?id=1weGFnxuIuVoQ0zF41ie3CVFYw_hJfExD

_{Monday, October 28, 2019 7:29 PM}

Here is all the log reports and system info-https://drive.google.com/open?id=1RqqyvsIssQNLa0QGJ8gYfUTrOKouY1wC

_{Monday, October 28, 2019 8:23 PM}

Have you tried putting the card in the other PCI slot? Have you gone into the BIOS and made sure that these slots aren't disabled? It sounds like you've completely narrowed it down to a motherboard/chipset issue and if you are sure both are up to date there may be a hardware fault.

-Aaron

_{Monday, October 28, 2019 11:47 PM}

The logs displayed video TDR problems (atikmpag.sys) earlier this year.

Live kernel events were 141, 144, and 1b.

The last BSOD seen in the logs was on 9/14.

The bugcheck was 3B.

The BIOS is old.

The last crash or unexpected shutdown / restart was on 10/22

Please perform the following steps:

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) bcdedit /enum {badmemory}

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
Make sure that there is no over clocking while troubleshooting.

12) The BIOS Version/Date American Megatrends Inc. F31, 06-05-2019

Upgrade the BIOS: F31 > F42d

https://www.gigabyte.com/us/Motherboard/GA-AB350M-Gaming-3-rev-1x/support#support-dl-bios

13) Make a new restore point:

https://www.tenforums.com/tutorials/4571-create-system-restore-point-windows-10-a.html

14) Read this link on Windows driver verifier: (do not use the tool until it is communicated in the thread):

(learn the commands to stop or recover from using the tool)

https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

15) If possible uninstall vbox during the troubleshooting process

The driver detected an internal driver error on \Device\VBoxNetLwf.

.
.
.
.
.

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

_{Tuesday, October 29, 2019 5:32 AM}

I have tried the first 6 commands earlier and the results of all those were that they could not find any defect. As for the rest of the commands, here is the result-

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\DESKTOP-1MLM6IA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\WINDOWS|\Device\Harddisk0\Partition4"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\DESKTOP-1MLM6IA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\WINDOWS|\Device\Harddisk0\Partition4"'
Property(s) update successful.

C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects

identifier {badmemory}

Should I RMA my motherboard??

_{Tuesday, October 29, 2019 5:41 AM}

When available please update the progress with steps #11 to #15.

Usually other problems are ruled in / ruled out leaving the motherboard as likely problem before RMA.

_{Tuesday, October 29, 2019 5:47 AM}

Thanks for the help. First I will try steps from 11-15 and report back. If they do not help I will RMA the motherboard.

_{Tuesday, October 29, 2019 6:15 AM}

When running Windows driver verifier it will be customized to stress test all non-Microsoft drivers.

There will be 3 customized tests at the start and this may be increased.

The tool will be ran for approximately 48 hours and then for an additional 36 hours after the last BSOD.

https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

After each BSOD run the administrative command prompt command to collect new files.

And post a separate share link for C:\windows\memory.dmp if the file size is < 1.5 GB.

The dump files will be debugged.

Identified problematic should be updated.

Some may be uninstalled and reinstalled.

And others may need to be rolled back.

While running the tool there can be performance problems and or slow boot.

The number and types of simultaneous tests may need to be modified.

After the BIOS is upgraded and another restore point is made you can turn on the tool.

Share via

Error 0x15 for amdkmdap in Events viewer

Question

All replies (15)

Additional resources