DISM Help
DISM Help
Hey! For some reason, my computer has a habit of suddenly freezing (deadlock) while gaming. When it freezes, I just force shut down the computer (by holding the power button) and manually turning it on again then running "sfc /scannow" and "dism /online /cleanup-image /restorehealth" in Powershell that is ran as an administrator. Running the SFC command seemed fine however, when running the DISM command, I noticed that it goes from 0% to 50% then suddenly jumps to 100% saying that the restore operation completed successfully. Is this normal? I have even done a clean installation of windows in my machine but the percentage still jumps. I have looked at its logs (CBS.log) and this is what the summary says: 022-08-23 17:22:16, Info CBS Appl:Feature On Demand package without explicit comparator, using GE on build version 2022-08-23 17:22:16, Info CBS Appl:Feature On Demand package without explicit comparator, using GE on build version 2022-08-23 17:22:19, Info CBS Package Format: PSFX 2022-08-23 17:22:19, Info CBS Package Format: PSFX 2022-08-23 17:22:19, Info CBS Appl:LCU package and revision compare set to explicit 2022-08-23 17:22:19, Info CBS Package Format: PSFX 2022-08-23 17:22:19, Info CBS Repr: Staged package check completes 2022-08-23 17:22:19, Info CBS Exec:Only CSI metadata corruption found, Process CSI repair. 2022-08-23 17:22:19, Info CBS FLOW: Entering stage: RepairCsi 2022-08-23 17:22:20, Info CSI 00000009 Creating NT transaction (seq 1) 2022-08-23 17:22:20, Info CSI 0000000a Created NT transaction (seq 1) result 0x00000000, handle @0x12328 2022-08-23 17:22:20, Info CSI 0000000b Transaction UoW: {b76d982c-22b8-11ed-89b6-9c5c8e886673} for BeginTransaction 2022-08-23 17:22:20, Info CSI 0000000c@2022/8/23:09:22:20.111 Beginning NT transaction commit... 2022-08-23 17:22:20, Info CSI 0000000d Transaction UoW: {b76d982c-22b8-11ed-89b6-9c5c8e886673} for CommitTransaction 2022-08-23 17:22:20, Info CSI 0000000e@2022/8/23:09:22:20.271 CSI perf trace: CSIPERF:TXCOMMIT;160144 2022-08-23 17:22:20, Info CSI 0000000f StoreCorruptionRepair transaction completed. 2022-08-23 17:22:20, Info CBS Repr: Finished repairing CSI store. 2022-08-23 17:22:20, Info CBS FLOW: Entering stage: RemoveStagedPackages 2022-08-23 17:22:20, Info CBS 2022-08-23 17:22:20, Info CBS ================================= 2022-08-23 17:22:20, Info CBS Checking System Update Readiness. 2022-08-23 17:22:20, Info CBS 2022-08-23 17:22:20, Info CBS 2022-08-23 17:22:20, Info CBS Summary: 2022-08-23 17:22:20, Info CBS Operation: Detect and Repair 2022-08-23 17:22:20, Info CBS Operation result: 0x0 2022-08-23 17:22:20, Info CBS Last Successful Step: Remove staged packages completes. 2022-08-23 17:22:20, Info CBS Total Detected Corruption: 0 2022-08-23 17:22:20, Info CBS CBS Manifest Corruption: 0 2022-08-23 17:22:20, Info CBS CBS Metadata Corruption: 0 2022-08-23 17:22:20, Info CBS CSI Manifest Corruption: 0 2022-08-23 17:22:20, Info CBS CSI Metadata Corruption: 0 2022-08-23 17:22:20, Info CBS CSI Payload Corruption: 0 2022-08-23 17:22:20, Info CBS Total Repaired Corruption: 0 2022-08-23 17:22:20, Info CBS CBS Manifest Repaired: 0 2022-08-23 17:22:20, Info CBS CSI Manifest Repaired: 0 2022-08-23 17:22:20, Info CBS CSI Payload Repaired: 0 2022-08-23 17:22:20, Info CBS CSI Store Metadata refreshed: True 2022-08-23 17:22:20, Info CBS Staged Packages: 2022-08-23 17:22:20, Info CBS CBS Staged packages: 0 2022-08-23 17:22:20, Info CBS CBS Staged packages removed: 0 2022-08-23 17:22:20, Info CBS 2022-08-23 17:22:20, Info CBS Total Operation Time: 1236 seconds. 2022-08-23 17:22:20, Info CBS Ensure CBS corruption flag is clear 2022-08-23 17:22:20, Info CBS Ensure WCP corruption flag is clear 2022-08-23 17:22:20, Info CBS All CSI corruption was fixed, ensure CorruptionDetectedDuringAcr is clear 2022-08-23 17:22:20, Info CBS Failed to clear CorruptionDetectedDuringAcr store corrupt flag (slow mode trigger). [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2022-08-23 17:22:20, Info CBS CheckSur: hrStatus: 0x0 [S_OK], download results: <none> 2022-08-23 17:22:20, Info CBS Count of times corruption detected: 0 2022-08-23 17:22:20, Info CBS Seconds between initial corruption detections: -1 2022-08-23 17:22:20, Info CBS Seconds between corruption and repair: -1 2022-08-23 17:22:20, Info CBS Reboot mark cleared 2022-08-23 17:22:20, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications 2022-08-23 17:22:20, Info CBS Winlogon: Deregistering for CreateSession notifications 2022-08-23 17:22:20, Info CBS Exec: Processing complete, session(Corruption Repairing): 30979790_4155204696 [HRESULT = 0x00000000 - S_OK] 2022-08-23 17:22:20, Info CBS Session: 30979790_4155204696 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK] 2022-08-23 17:22:20, Info CBS Deleting directory: \\?\C:\Windows\CbsTemp\30979790_4155204696\ 2022-08-23 17:22:20, Info CBS Moving directory from \\?\C:\Windows\CbsTemp\30979790_4155204696\ to \\?\C:\Windows\CbsTemp\30979790_4155204696\{48B3CC4A-4FD8-490D-BB81-16511F3032FA} 2022-08-23 17:22:20, Info CBS Failed to move \\?\C:\Windows\CbsTemp\30979790_4155204696\ to temp directory \\?\C:\Windows\CbsTemp\30979790_4155204696\{48B3CC4A-4FD8-490D-BB81-16511F3032FA} [HRESULT = 0x80070020 - ERROR_SHARING_VIOLATION] 2022-08-23 17:22:20, Info CBS Failed moving directory: \\?\C:\Windows\CbsTemp\30979790_4155204696\ to temp, will delete in-place instead [HRESULT = 0x80070020 - ERROR_SHARING_VIOLATION] 2022-08-23 17:22:20, Info CBS Deletion of: \\?\C:\Windows\CbsTemp\30979790_4155204696\ successful 2022-08-23 17:22:20, Info CBS Session: 30979793_3637159422 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null) It clearly says that the operation was Detect and repair however, the last successful step was "Remove staged packages". Also looking at the summary, Seconds between initial corruption detections and Seconds between corruption and repair is -1 and I believe this isn't normal. I have searched the web for answers but it doesn't seem that there is a solution that is the same as my problem. I hope that anyone could give some advices on what to do. Cheers! NOTE: and yes, all my of drivers are updated and I have tried other troubleshooting methods to solve my deadlock problem but it doesn't seem to work for me. Edited August 23, 2022 by Jownjown Forgot to attach image
Avoid any actions with your RAM stick while the computer is running. If this causes the system to freeze, consider cleaning the RAM connections and slot.
Typically I use an eraser or a sheet of paper to remove debris from the contact and camera lens blower, ensuring the slot is free of dust before reinserting the RAM.