Error Code

Question

Here is the minidump file if you dont mind letting me know or what happened that caused the crash?

https://drive.google.com/file/d/1UKMIl1WATjFOvEgzbR7xm3jFgXRKWslh/view?usp=sharing

Answer 1

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, we actually need to reinstall the AMD Graphics driver. Kindly follow the steps 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 2

The contents of that specific minidump file are not available in the provided context, so the exact cause of the crash cannot be determined here.

To find out what caused the crash, open and analyze the minidump locally using one of these supported methods:

1. Analyze the minidump with Visual Studio
   1. Open Visual Studio.
   2. Select File > Open > Project/Solution.
   3. In Files of type, choose Dump Files.
   4. Browse to the .dmp file, select it, and choose Open.
   5. Start debugging (e.g., press F5). Visual Studio creates a simulated process and stops at the instruction that caused the crash.
   6. If needed, configure symbols so the call stack is meaningful:
      • Go to Debug > Options > Debugging > Symbols.
      • Add the Microsoft public symbol server and a local cache directory.
      • Make sure Search the above locations only when symbols are loaded manually is not selected if automatic loading is desired.
2. Analyze the minidump with WinDbg (Debugging Tools for Windows)
   1. Install Debugging Tools for Windows.
   2. Open a Command Prompt.
   3. Change to the Debugging Tools folder, for example:

            cd "C:\Program Files\Debugging Tools for Windows"
      

   4. Run WinDbg or KD with your dump, symbol path, and image path. Example:

            windbg -y srv*C:\Symbols*https://msdl.microsoft.com/download/symbols -i C:\Windows\i386 -z C:\Windows\Minidump\minidump.dmp
      

      Replace the paths with the actual location of the symbols, Windows binaries, and the .dmp file.
   5. In the debugger, run these commands to understand the crash:
      • !analyze -show – shows the bug check (Stop) code and parameters.
      • !analyze -v – provides verbose analysis, including likely cause and involved driver/module.
      • lm N T – lists loaded modules and their paths, useful to see which driver or module is implicated.
3. Optional: simplify with a batch file After identifying the correct command, create a batch file (for example, dump.bat) in the Debugging Tools folder:

      cd "C:\Program Files\Debugging Tools for Windows"
      kd -y srv*C:\Symbols*https://msdl.microsoft.com/download/symbols -i C:\Windows\i386 -z %1
   

   Then run:

      dump C:\Windows\Minidump\yourdump.dmp
   

   to open any dump quickly.
4. Verify the dump file itself If there are issues opening the dump, use Dumpchk.exe to verify that the file is valid. If Dumpchk.exe reports errors, the dump is corrupt and cannot be analyzed.

Once !analyze -v has been run with correct symbols, the debugger output will show the bug check code, the faulting module (for example, a driver or DLL), and a call stack that indicates what caused the crash.

---

References:

• Crash Dump Analysis
• Minidump Files
• How to read the small memory dump file that is created by Windows if a crash occurs
• User-mode dump files