CBS log reporting error with "msdelta.dll" that sfc /scannow can't fix

Edit: My last post on this thread contains all the most recent information regarding the current state of my machine and Windows 10 installation.

Random hangs (not BSOD) once every 1~3 days while gaming.
Thought it related to OC so decided to incrementally lower the clock and voltage.
Tested stability with aida64 and it hung mid-test with a BSOD). That BSOD rendered Windows completely unstable.

After that I got random BSODs (Unexpected Kernel Mode Trap, among others - they seemed different each time), and other strange behavior (namely USB drive folder opening and closing automatically).

I installed Sandra HW monitoring app before testing stability.

Using a restore point BSOD frequency decreased a bit, but it'd still happen seemingly randomly (once within 6 minutes of simple usage like opening folders).

Trying to run sfc /scannow, dos reported the command as not recognized. I used this tutorial to to run sfc scannow in dos boot and it still reported corrupt files...)


Current State:
I chose to reset the PC and to keep personal files.
PC seems stable now but sfc /scannow is still reporting corrupt files (I ran it with nothing other than malwarebytes running).

Note: After resetting, I only installed MBAM (pro) and Firefox. Windows automatically installed an AMD driver (I think).

I'd like to know if the BSODs I was experiencing is the cause of scannow not working.

According to the CBS log msdelta and amd64_microsoft-windows-deltacompressionengine are errant.

List of all the devices I've connected to the PC at some point.
-logitech webcam (almost always connected but never used)
-wacom bamboo tablet (almost always disconnected)
-fostex headphone amplifier (always connected often used)
-steam controller (always connected not often used)

Any help would be extremely appreciated!
(I'll gladly post this in a different section if someone could tell me which is appropriate.)

(Update) Just got another BSOD. Kernel Security Check Failure

It happened after this:

I tried to run sfc /scannow again (going for the 3rd time's a charm)
It got stuck at 32% for 30 minutes, so I killed it.

Went to try to restart PC in safe mode and found Windows had the update and restart option, so I let it, without holding shift.

It installed the updates, and then I went to try to restart again in safe mode. Clicking on the windows key and hovering the mouse cursore over the Power option BSOD'd it.

Hello lifetec,

Sorry for not supplying a dump file. I just checked it (it was set to dump type "automatic").
It's over 600MB so I zipped it to 120MB.

Initially I had the drivers installed for the steam controller before resetting the PC.

I left the USB receiver for it plugged in the whole time (from when the first stability crash happened, until now). I did not intentionally install drivers for it. It's possible old ones remain or Windows or Steam installed default generic drivers for it after reset. I have no idea how to delete, remove, replace or install them.

Oh I just now remembered. When my PC hanged while playing games, the steam controller was on and then got forcibly turned off. Maybe its drivers got corrupted and they still remain after the reset?

Sorry, I forgot I installed Steam as well. So, currently installed programs: steam, firefox, malwarebytes.
I will try to run scannow 3 times in a row when I get home (10 hours from now).

Thank you very much for the help, lifetec.

Update: Using the information lifetec found out for me, where the steam controller is a likely culprit, I looked into a thread about uninstalling steam controller drivers on windows 10 and found this.

In short, I
- uninstalled all the HID devices (via Device Manager) that appear when attaching the Steam Controller USB dongle.
- ran sfc /scannow twice in normal Windows 10
- ran sfc /scannow twice in Windows 10 safe mode with networking

No errors were reported, unlike before where it would either freeze up or display a message about corrupted data that couldn't be fixed.

I'll update this if I get another BSOD. If it's OK I'd request that this thread stay open for a week or so.

Thanks a ton for checking out that CBS log, lifetec. Granted the culprit is inconclusive, I never thought the steam controller (driver) could be a cause of a BSOD.

Edit: Cool! That error Lifetec found is in dxdiag.txt. (I never knew dxdiag reported that kind of info.)
I'll check it when I get home and update if it's still erring.

(I am the OP. Forgot my password so I created another account to access from work.)
Might anyone know how Lifetec got this information?

Device Name: Steam Controller
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x28DE, 0x1142

I checked my previous uploaded zipfile and searched for "Windows Error Reporting:" in each file (except for dxdiag.txt...) but got no hits.

I'm thinking I should probably rerun it to see if that driver issue is resolved...

Thanks in advance!

In the dxdiag.txt file you can find the WER reports, just go to the end of the file and you'll see them :)

This is an update regarding the steam controller being the cause of the BSOD.

Having uninstalled the HID devices related to the steam controller, and then reinstalling it via steam I haven't experienced any crashes yet.

I have some 10 other conflicts (3 distinct) reported in dxdiag, though. (I attached the new, post-uninstall dm_log_collector.) I tried googling around for them. What I found was XP or Windows 7 related, so I figured I should hold off.

I was wondering if some kind soul could tell me if they're negligible, because I'd like to prevent a BSOD or hang from occurring and causing more "damage".

In short, they are:
- MpTelemetry (P1: 2152759308, P3: ScanFile P5: Windows Defender)
- APPCRASH (P1:UE4-TestGame, P4:UE4Editor-MeshPaint.dll)
- MpTelemetry (P1: 2152759308, P3: ScanFile P5: Windows Defender)
- APPCRASH (P1:UE4-TestGame, P4:UE4Editor-MeshPaint.dll)
- APPCRASH (P1:UE4-TestGame, P4:UE4Editor-MeshPaint.dll)
- APPCRASH (P1:UE4-TestGame, P4:UE4Editor-MeshPaint.dll)
- MpTelemetry (P1: 2152759308, P3: ScanFile P5: Windows Defender)
- APPCRASH (P1:UE4-TestGame, P4:UE4Editor-MeshPaint.dll)
- MpTelemetry (P1: 2152759308, P5: Windows Defender)
- RADAR_PRE_LEAK_WOW64 (P1: firefox.exe)

(I assume the UE4 one's are negligible, because I've never experienced a BSOD while UE4 is running.)

I will mark this thread as solved if I can get through the weekend without a BSOD.

Thank you so much lifetec and Axe0 for you help!

They are generally nothing to worry about, especially the mptelemetry onces.