Errors shown in reliability monitor

Question

Wondering if anyone can decipher what the issue is in these dmp files?

I've only noticed some minor hiccups in my PC recently but thought to make sure.

I put all the minidump and live kernel files I have just in case more issues are spotted. The ones that initially alerted me are under the watchdog folder for 1/12.

Link: https://1drv.ms/f/c/83fdb953e49fea8c/IgDfxg8cIEZeQ4wWj0fHQvpXAaO4o67T3WGwVtkzPdmI5WM

(Some of the dmp files were probably made when I had to uninstall and reinstall GPU drivers.)

Answer 1

Hi Moretti, yes, upon checking all the DMP files, it is all pointing to the AMD Graphics driver.

Answer 2

Hi, I'm Bernard, a fellow Windows user. I'm happy to help!

Upon analyzing and checking the DMP files, the error you have is amdkmdag.sys. This is your AMD Graphics driver. In this case, let us run a clean installation of the Nvidia driver. This will remove all entries and replace them with compatible ones. Kindly follow the steps from the link below:

 

Step 1. Completely uninstall the AMD GPU Driver using the steps from this link:

https://www.amd.com/en/resources/support-articles/faqs/GPU-601.html

 

Step 2. Reinstall the AMD Graphics driver using the steps from the link below:

Install the AMD Radeon and automatically detect the AMD driver:

https://www.amd.com/en/resources/support-articles/faqs/GPU-131.html

 

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

 

Additional note: If the issue persists, I suggest removing the GPU and placing it into another PCIe port available (This is only applicable if you are using a Desktop PC or an external GPU). However, if all fails, I suggest contacting a local technician to physically check the device for any hardware-related issues.

Answer 3

To analyze the issues reflected in your minidump and live kernel dump files, you would typically look for specific error codes or messages that can indicate the nature of the problem. Since you mentioned that the files are located under the watchdog folder, it is likely that they are related to timeout issues with the system's operations.

Kernel live dumps can capture data when something is taking too long to complete, and they can help diagnose problems where the system is not technically failing but is experiencing delays. For example, if a watchdog timer expires, a live dump can be created to analyze the call stack and related wait chains to determine why an operation did not complete in the expected timeframe.

If you are experiencing minor hiccups, it may be beneficial to check the specific error codes in your dump files against known kernel live dump codes. For instance, codes like 0x00000156 (WINSOCK_DETECTED_HUNG_CLOSESOCKET_LIVEDUMP) or 0x0000015C (PDC_WATCHDOG_TIMEOUT_LIVEDUMP) might be relevant if you are facing issues related to network operations or hardware timeouts.

To further troubleshoot, you can view live dump related events in the Windows Event Viewer under Applications and Services Logs -> Microsoft -> Windows -> Kernel-Livedump -> Operational. If you do not find any logs, you may need to enable the analytic channel as described in the documentation.

If you continue to experience issues, consider reviewing the specific contents of the dump files using debugging tools to identify the root cause of the hiccups you are observing.