My Lenovo IdeaPad running Windows 11 with a Ryzen 5 6600HS and AMD Radeon graphics began crashing while installing updates. It repeatedly shows DPC_WATCHDOG_VIOLATION (0x133), tries to undo the update, and eventually enters BitLocker recovery and Automatic Repair. The BitLocker recovery key is accepted, but the system returns to the same loop. Automatic Repair references C:WindowsSystem32LogfilesSrtSrtTrail.txt and reports that it cannot connect to the network.
I have already disconnected USB devices, connected the charger, tried removing the latest quality update, attempted Safe Mode, and run Startup Repair. Removing the update failed. Safe Mode still tried to apply the pending update. From WinRE, DISM /Online /Cleanup-Image /RestoreHealth produced Error 87 because the prompt was running from X:WindowsSystem32. I then tried DISM /Image:C: /Cleanup-Image /RevertPendingActions, which also returned Error 87. I have not reset or reinstalled Windows because preserving my personal files is the priority.
What is the safest way to cancel or roll back the pending update from WinRE? Could the 0x133 error point to an SSD, storage controller, chipset, graphics driver, BIOS, or firmware problem? Which offline checks should I run on the Windows partition and SSD, and how can I unlock the BitLocker drive and copy my files to an external drive before attempting a reset or reinstall? Would Windows recovery with "Keep my files" be appropriate, or is professional repair safer at this stage?
5 Answers
For the servicing commands, make sure WinRE is targeting the real Windows installation rather than X:. DISM /Online is for a running Windows environment. In WinRE, use DISM /Image:C: /Cleanup-Image /CheckHealth or /ScanHealth after confirming the correct letter. Pending-update rollback commands can vary by Windows build, and an Error 87 often means the syntax or servicing context is not supported there. Do not keep forcing random DISM options; backing up first is safer, followed by an offline repair or installation-media repair if available.
Before trying anything destructive, prioritize a backup. From WinRE, identify the Windows volume and the external drive with diskpart and list volume. Unlock the BitLocker volume with manage-bde -unlock C: -rp YOUR-48-DIGIT-RECOVERY-KEY, replacing the drive letter if necessary. You can then use robocopy or xcopy from Command Prompt to copy important folders such as UsersYourNameDesktop, Documents, Pictures, and saved application data to the external drive. Verify that the files actually open from the backup before resetting Windows.
The 0x133 stop code means Windows detected a delayed or stuck kernel-level procedure call. It can result from a bad storage or chipset driver, SSD/controller trouble, firmware, or another kernel driver; it is not proof that the update itself is corrupt. If you can eventually boot, collect the files in C:WindowsMinidump and analyze several dumps rather than guessing from the stop code alone. After backing up, update the Lenovo BIOS and AMD/chipset and storage-related drivers using Lenovo’s support package, but avoid BIOS changes until the data is safe.
A reset or reinstall should come after the backup and basic disk checks. “Keep my files” normally preserves data in the user profile but removes installed programs, drivers, and settings, so it is not a substitute for an independent backup. If the SSD passes diagnostics and the files are copied, that option is reasonable. If BitLocker will not unlock, the drive shows hardware errors, or the backup cannot be verified, taking it to a reputable repair shop is the safer choice than continuing with resets.
Once the files are backed up, check the file system before assuming the update is the only problem. From WinRE, run chkdsk C: /scan, or chkdsk C: /f if a repair is needed and you have a verified backup. You can also inspect the disk with diskpart and confirm which letter contains the Windows folder. If the drive reports errors, disappears, or produces I/O failures, stop repeated repair attempts and check the SSD health from the manufacturer’s diagnostic tools or a service environment.
My personal files are the main concern, so I will try unlocking the volume and copying them from the recovery command prompt before attempting a reinstall.