How can I safely break a Windows 11 update loop after a DPC_WATCHDOG_VIOLATION?

0
2
Asked By MellowCedar47 On

My Lenovo IdeaPad running Windows 11 with a Ryzen 5 6600HS and AMD Radeon graphics crashed during a Windows update with DPC_WATCHDOG_VIOLATION (0x133). It repeatedly tries to install the update, crashes, rolls back, and eventually opens BitLocker recovery. My recovery key is accepted, but the system returns to the same update and Automatic Repair loop. Automatic Repair refers to C:WindowsSystem32LogfilesSrtSrtTrail.txt and says it cannot connect to the network.

From Windows Recovery Environment, removing the latest quality update failed. Safe Mode still triggered the pending update. DISM /Online /Cleanup-Image /RestoreHealth was run from X:WindowsSystem32 and returned Error 87, while DISM /Image:C: /Cleanup-Image /RevertPendingActions also reported that the option was not recognized. Startup Repair has not fixed anything.

I have not reset or reinstalled Windows because I want to preserve my personal files. The laptop is connected to power and external USB devices have been removed. What is the safest way to cancel the pending update, check whether the SSD or drivers are failing, and back up files from the BitLocker-encrypted drive before attempting a reset or reinstall?

3 Answers

Answered By SilverOrbit_31 On

If you can access a normal Windows or Safe Mode session long enough, look in C:WindowsMinidump for crash dumps. Those files can identify whether a particular driver is responsible, although there may be no dump if the update crashes too early. If the update remains stuck, a Windows installation USB can provide another recovery environment and may allow offline servicing or a repair installation.

After backing up the data, Reset this PC with the option to keep personal files is less destructive than formatting, but it removes installed applications and settings and is not a substitute for a backup. If the SSD diagnostics show warnings, or if copying files produces read errors, use a specialist before reinstalling.

Answered By BrightMaple62 On

A 0x133 crash can come from a storage driver, SSD firmware or controller problem, chipset software, graphics drivers, BIOS firmware, or damaged system files. It is not proof that the update itself is the only problem. Once the files are safe, check the SSD's health from the laptop manufacturer's diagnostics or a bootable hardware tool, and inspect the Windows partition with chkdsk. Avoid changing BIOS storage modes or deleting partitions unless you have a verified backup.

Answered By QuietLantern8 On

Prioritize copying your files before doing anything invasive. From WinRE, unlock the Windows volume with manage-bde, identify the correct drive letter with diskpart, and copy important folders to an external drive using robocopy or xcopy. The BitLocker volume must be unlocked first; simply booting a Linux live environment will not automatically provide access to the encrypted files.

After the backup, you can try offline repairs against the actual Windows partition, such as chkdsk /scan or chkdsk /f, followed by DISM /Image:C: /Cleanup-Image /Cleanup-Image /RevertPendingActions. Drive letters can differ in WinRE, so confirm the Windows volume before running commands. If the drive reports errors, stop repair attempts and clone or replace it first.

MellowCedar47 -

My personal files are the main concern. I only have Office and a few games installed, so backing up the data first and then reinstalling Windows is acceptable if the repair commands do not work.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.