Live Kernel Event a1000001, a2000002 and 141 shuts down PC.

Question

Live Kernel Event a1000001, a2000002 and 141 shuts down PC.

Danylo Kotenko 20

Sometimes during start up, within 10 minutes pc crashes and restarts. Sometimes it happens, sometimes doesn't. Let me know which dump files can help solve this problem, and I'll throw them in a google drive and share the link, thank you.

Anyway, here are all the details for each three, also running W11:

Source

Windows

Summary

Hardware error

Date

‎4/‎21/‎2026 12:06 PM

Status

Not reported

Description

A problem with your hardware caused Windows to stop working correctly.

Problem signature

Problem Event Name: LiveKernelEvent

Code: a1000001

Parameter 1: 1

Parameter 2: 0

Parameter 3: 0

Parameter 4: 0

OS version: 10_0_26200

Service Pack: 0_0

Product: 768_1

OS Version: 10.0.26200.2.0.0.768.101

Locale ID: 4105

Files that help describe the problem

AMD_WATCHDOG-20260421-1206.dmp

sysdata.xml

WERInternalMetadata.xml

memory.csv

sysinfo.txt

WERInternalRequest.xml

Source

Windows

Summary

Hardware error

Date

‎4/‎21/‎2026 12:06 PM

Status

Not reported

Description

A problem with your hardware caused Windows to stop working correctly.

Problem signature

Problem Event Name: LiveKernelEvent

Code: a2000002

Parameter 1: c8

Parameter 2: 0

Parameter 3: 0

Parameter 4: 0

OS version: 10_0_26200

Service Pack: 0_0

Product: 768_1

OS Version: 10.0.26200.2.0.0.768.101

Locale ID: 4105

Files that help describe the problem

AMD_REPORT_UM-20260421-1206.dmp

sysdata.xml

WERInternalMetadata.xml

memory.csv

sysinfo.txt

WERInternalRequest.xml

Source

Windows

Summary

Hardware error

Date

‎4/‎21/‎2026 12:06 PM

Status

Not reported

Description

A problem with your hardware caused Windows to stop working correctly.

Problem signature

Problem Event Name: LiveKernelEvent

Code: 141

Parameter 1: ffffe086e24f4010

Parameter 2: fffff802c48dc980

Parameter 3: 0

Parameter 4: ffffe086e2493080

OS version: 10_0_26200

Service Pack: 0_0

Product: 768_1

OS Version: 10.0.26200.2.0.0.768.101

Locale ID: 4105

Files that help describe the problem

WATCHDOG-20260421-1206.dmp

sysdata.xml

WERInternalMetadata.xml

memory.csv

sysinfo.txt

WERInternalRequest.xml

0 comments

Answer accepted by question author

David-M 114.8K Independent Advisor

Thanks for the clarifications.

I only use the dedicated though, should I disable the processor's graphics?

Yes. I recommend starting by disabling the integrated graphics card. I've seen cases where instability was caused by conflicts between the drivers for the integrated and dedicated graphics cards.

You can try disabling it through Device Manager to see if that's enough. But if the problem persists, try disabling it through the motherboard BIOS.

If the instability persists even with the integrated graphics card disabled, I suggest performing a clean installation of the AMD graphics driver. (Keep the integrated graphics card disabled.)

Download the latest driver for your graphics card from the AMD website. Then, use the free DDU tool to remove the current driver. Then, install the latest driver using the installer you downloaded.

I suggest disconnecting from the internet during the entire procedure.

(Turn off Wi-Fi or disconnect the Ethernet cable.)

DDU: https://www.guru3d.com/files-details/display-driver-uninstaller-download.html

AMD driver download: https://www.amd.com/en/support/downloads/drivers.html/graphics/radeon-rx/radeon-rx-7000-series/amd-radeon-rx-7800-xt.html

(Run the downloaded file and follow the on-screen instructions to install the driver.)

Then, see if the system will work stably after this.

If the crash occurs again after doing these two suggestions, please let me know.

If you need a tutorial for using DDU, I recommend the video below.

https://www.youtube.com/watch?v=bP-2B14Nckw

Feel free to ask any questions you may have.

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Danylo Kotenko 20 Reputation points

2026-04-21T22:55:55.9133333+00:00

Okay David, I'll try disabling integrated graphics for now, see if that solves it.
MKelly 0 Reputation points

2026-05-18T18:23:02.51+00:00

Hi David, I am having the same issues and I have tried everything listed and the issue still persists. I just completed a stress test on my system and my system handled it fine. Temps were normal. Is my only option now to reinstall windows? Please advise as I am very disappointed I have not been able to enjoy my new pc for several weeks now. Thanks

2 additional answers

Your answer

Danylo Kotenko 20 Reputation points

2026-04-21T22:55:55.9133333+00:00

Okay David, I'll try disabling integrated graphics for now, see if that solves it.
MKelly 0 Reputation points

2026-05-18T18:23:02.51+00:00

Hi David, I am having the same issues and I have tried everything listed and the issue still persists. I just completed a stress test on my system and my system handled it fine. Temps were normal. Is my only option now to reinstall windows? Please advise as I am very disappointed I have not been able to enjoy my new pc for several weeks now. Thanks

Answer 1

David-M 114.8K Independent Advisor

Hi. I'm David, and I'm happy to help you.

While the details you shared provide a good starting point, I will need more information to identify the root cause.

Please export and share the log for analysis:

Press Windows + X and select Event Viewer;
Expand Windows Logs and select System;
In the Actions panel on the right, select Filter Current Log;
In Event level, check the boxes Critical, Warning, and Error and click on Ok;
Again, in the Actions panel, select Save Filtered Log File As and save in an easily accessible place.

Then, upload the file to the cloud (OneDrive), choose to share it, and get the link.

Post the link to the file here so I can have a look.

Looking forward to your reply.

Danylo Kotenko 20 Reputation points

2026-04-21T18:06:38.11+00:00

Hello David, here is the file:
https://drive.google.com/drive/folders/1TJIQDGcYms0AZWfDSeVptxa1_f-FvNty?usp=drive_link
David-M 114.8K Reputation points Independent Advisor

2026-04-21T18:24:50.9866667+00:00

Sorry. I cannot access the file.

Check the sharing permissions of the file.

See the instructions for making the file publicly available in "Learn about public sharing & collaboration > Share a file or folder publicly" in the article below.

https://support.google.com/drive/answer/2494822#zippy=%2Cshare-a-file-or-folder-publicly

Looking forward to your reply.

Standard Disclaimer: There is a link to 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.
Danylo Kotenko 20 Reputation points

2026-04-21T18:50:09.96+00:00

Sorry about that, think I got it now
https://drive.google.com/drive/folders/1TJIQDGcYms0AZWfDSeVptxa1_f-FvNty?usp=sharing
David-M 114.8K Reputation points Independent Advisor

2026-04-21T18:58:54.5166667+00:00

No problem. Thanks.

I haven't found an error that could be related to the issue. Only the entries that say the shutdown was not expected and "Event 41 Kernel-Power". However, these entries are registered in all types of abrupt system shutdowns. Therefore, they are not entries that help identify the cause of the problem.

Please see if your computer created minidump files.

These files are in "C:\Windows\Minidump".

(If you don't have the folder or no files in it, it means that the computer didn't create the files. In this case, let me know, and I'll proceed.)

Copy any files you have to your desktop and store them in a ZIP file. Then, upload the ZIP file to the cloud (OneDrive), choose to share it, and get the link.

Post the link to the ZIP file here so I can have a look.

Looking forward to your reply.
Danylo Kotenko 20 Reputation points

2026-04-21T19:04:45.3333333+00:00

Hey David, just posted it on the drive. Thanks.
https://drive.google.com/drive/folders/1TJIQDGcYms0AZWfDSeVptxa1_f-FvNty?usp=sharing
David-M 114.8K Reputation points Independent Advisor

2026-04-21T19:15:51.4866667+00:00
Thanks.

The minidump file mentions the driver "AtihdWT6.sys" as the cause of the crash. This driver is responsible for managing sound transmitted via HDMI or DisplayPort on computers using AMD graphics cards or AMD processors.

The details you initially shared strengthen this finding. This driver must be the primary source of the crashes.

Your processor has integrated graphics. Are you using only the integrated graphics, or do you have a dedicated AMD graphics card?

If you have a dedicated AMD graphics card, please check if your monitor is plugged into the motherboard's video output rather than the dedicated AMD GPU itself. Also, verify if the integrated graphics is disabled.

If you are unsure whether the integrated graphics card is disabled, please share a screenshot of the display adapters in Device Manager.

Open "Device Manager" (Windows + X and select Device Manager);

Expand "Display adapters" and take the screenshot.

Use the shortcut "Windows + Shift + S" to use the screenshot tool.

Looking forward to your reply.
Danylo Kotenko 20 Reputation points

2026-04-21T19:28:18.4066667+00:00

That's right, both my processor and graphics card are AMD.
I only use the dedicated though, should I disable the processor's graphics?

Answer 2

The LiveKernelEvent codes shown indicate hardware- or driver-level failures that can cause unexpected restarts in Windows 11. Kernel and hardware error analysis relies on the dump files that Windows generates at the time of the crash.

For this scenario, the most relevant dump files are:

For the a1000001 event (AMD watchdog)
- AMD_WATCHDOG-20260421-1206.dmp
- This is a kernel-mode dump produced by the AMD watchdog component and is the primary file to analyze for GPU/driver-related hangs that trigger a TDR (Timeout Detection and Recovery) or similar hardware error.
For the a2000002 event (AMD user‑mode report)
- AMD_REPORT_UM-20260421-1206.dmp
- This is a user‑mode dump from the AMD driver stack. It complements the watchdog dump and can show what the user‑mode driver was doing when the error occurred.
For the 141 event (VIDEO_TDR / hardware error)
- WATCHDOG-20260421-1206.dmp
- This is the standard watchdog/TDR dump associated with LiveKernelEvent 141 and is critical for understanding whether the GPU, GPU driver, or another kernel component stopped responding.
Shared diagnostic files (supporting, but secondary)
- sysdata.xml – System configuration snapshot at the time of the error.
- sysinfo.txt – Basic system information, driver list, and environment details.
- memory.csv – Summary of memory usage and layout.
- WERInternalMetadata.xml / WERInternalRequest.xml – Windows Error Reporting metadata that can help correlate events and modules but are less important than the .dmp files for deep debugging.

For a technical root‑cause analysis in a debugger (such as WinDbg), the priority order is:

AMD_WATCHDOG-*.dmp
WATCHDOG-*.dmp
AMD_REPORT_UM-*.dmp

The XML/TXT/CSV files are useful for context but are not strictly required to identify the failing driver or module.

References:

Share via

Live Kernel Event a1000001, a2000002 and 141 shuts down PC.

Anyway, here are all the details for each three, also running W11:

2 additional answers

Your answer