Sorry, I don't have a Win 7 computer but I noticed your post <here> in the Vista board so I'll add a few suggestions in this thread. What is the make/model of your computer, do you have a 32-bit or 64-bit Win 7 OS and what type of CPU processor do you have? If you have a discrete graphics card (e.g., AMD Radeon, NVIDIA GeForce, etc.) what is the make/model and current graphics driver version. Post back if you need assistance finding this information.
Have you been seeing these "0x000000C4" stop errors and BSODs every time you boot your computer since Windows Update applied KB4056894 back in January 2018? The KB4056894 (2018-01 Security Monthly Quality Rollup for Windows 7; January 9, 2018) bug that caused machines with older AMD processors to become unbootable was released back in January 2018 and has been superseded/replaced by KB4074598 (2018-02 Security Monthly Quality Rollup for Windows 7; February 13, 2018). Your post # 50 in the thread I'm stuck in an update/system repair loop! indicates that your system was booting correctly on 28-Mar-2018, so if the only issue you see now is a "0x000000C4" stop error after running the System File Checker (sfc /scannow) then I'm not sure that uninstalling KB4074598 at this late date is going to fix your problem.
Can you confirm that KB4056894 is still listed in your installed updates? Go to Control Panel | Programs and Features | View Installed Updates and enter the full KB number in the search box (e.g., "KB4056894" and not a partial string like "4056894"). You stated "I was able to partially be able to get my pc up and functional but some effects of the damage remains" and that suggests to me that you already uninstalled KB4056894 back in January 2018. If your system boots up normally then you should be able to uninstall buggy Windows Update patches from View Installed Updates.
The DISM command you're trying to run uninstalls KB4056894 and is intended for users who cannot boot into normal mode and are launching the command prompt from inside the emergency Windows Recovery Environment (i.e., from Repair Your Computer from the Advanced Boot options). When you are in the Windows Recovery Environment you are using a special Windows image and your Windows drive letter usually isn't your regular "C:\" drive. Note that the DISM command you've been using assumes your recovery image is on D:\ drive, not C:\drive. If you are running this command from outside the Windows Recovery Environment or your recovery image does not default to D:\ drive then that could be why you are seeing an error about an unmounted image. The step-by-step instructions in the ghacks.net article Fix Windows 7 BSOD 0x000000c4 after installing KB4056894 note that you should type in the command dir d: first to check that the Windows drive is mapped before running the DISM command.
The "0x000000C4" stop error is usually associated with a DRIVER_VERIFIER_DETECTED_VIOLATION issue on computers that have the Driver Verifier tool enabled. System File Checker (sfc /scannow) only checks the integrity of your Windows system files and it's possible that the buggy driver causing the BSODs is a hardware driver (e.g., a driver for a graphics card) that can't be fixed with System File Checker. The Desktop Window Manager (dwm.exe) that was flagged by your System File Checker enables the use of hardware acceleration to render the graphical user interface of Windows and might be pointing to a minor issue with graphics rendering.
There are free utilities like Nirsoft's BlueScreenView or Resplendence's Who Crashed that can interpret and summarize the Bug Check (BC) codes in your recent Windows mini-dump files. These free utilities aren't as accurate as an analysis of your full dump files with WinDbg (Windows Debugger) tool the experts in BleepingComputer's Windows Crashes, BSOD, and Hangs Help and Support board use because these free utilities only show the drivers loaded in the crash stack at the time of your BSOD, but I was able to fix intermittent BSODs on my Vista SP2 computer a few years ago after BlueScreenView pointed to a problem with an out-of-date driver for my NVIDIA graphics card. See the instructions in caweclark's thread BSOD if you'd like to post a BlueScreenView diagnostic logs in your next reply and I'll see if I can at least point you in the right direction.
32-bit Vista Home Premium SP2 * Firefox ESR v52.8.1 * Norton Security v188.8.131.52 * Malwarebytes 3.5.1
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS
Edited by lmacri, 21 June 2018 - 12:13 PM.