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

Page 2 of 2 FirstFirst 12

  1. Posts : 3
    Windows 10 64-bit (Home)
       19 May 2016 #11

    axe0 said: View Post
    They are generally nothing to worry about, especially the mptelemetry onces.
    Thanks once again, axe0. That's a relief to hear (read?).
    I will update this thread next Monday (Sunday evening PST).
      My ComputerSystem Spec

  2. Posts : 36
    Windows 10 64-bit (Home)
    Thread Starter
       20 May 2016 #12

    I just got a BSOD (and it's a familiar one). I wasn't able to write it all down before the PC restarted, but this is what I got:

    System Thread Exception atikm...
    Attachment 80767

    What's weird is that that BSOD error claims Windows is on the D drive.
    Windows is, without a doubt, installed on the C drive and always has been.
    Attachment 80774

    I have an SSD as the C drive and an HDD as the D drive.
    (For good measure, I double-checked D: and no "Windows" folders exist.)

    Maybe this all got messed up when I accidentally pressed the big fat "Intel Rapid Storage technology" button on the main screen in the BIOS after the Windows Reset. It hung up in the BIOS after that, and I pushed the reset button.

    Before encountering this error I had done the following:
    - Uninstalled gpu driver (because Doom wasn't detecting higher resolutions) and restarted
    - Changed primary display to i-gpu in bios
    (Had to do this to get to desktop to install the driver.)
    - Installed latest crimson driver and reconnected DVI to gpu
    - Reset PC
    - Launched Steam, uninstalled Doom, re-downloaded Doom and started surfing the web in the interim
    30 minutes later, with Doom at 80%, I got the BSOD with the aforementioned error.

    I opened up "update and security" and this is what it shows (crimson's running in the background so I brought it up to show the latest driver version):
    Attachment 80773
    Last edited by HansW; 21 May 2016 at 02:32. Reason: Tried to fix the formatting.
      My ComputerSystem Spec

  3. Posts : 36
    Windows 10 64-bit (Home)
    Thread Starter
       21 May 2016 #13

    I looked around for ways to get Windows to find to recognize it was installed on the proper drive, but had no luck.
    So, I completely formatted the C: drive (where windows was installed) and reinstalled Windows fresh like.
    I will mark this as Solved.

    I sincerely appreciate everyone taking the time to help me out!
      My ComputerSystem Spec

Page 2 of 2 FirstFirst 12

Related Threads
Hi all, Just installed Win 10 pro on a new SSD, so a clean install. Started installing all my programs etc. Everything seems to be running well, except on thing that is annoying... I have placed a few icons on the desktop via right clicking...
Hello how can I delete "saved password" and "form data" of microsoft edge manually ?! after too much search in google .... I trid to delete some value of the following registry address HKEY_CURRENT_USER\SOFTWARE\Classes\Local...
After attempting the 1511 upgrade (with disastrous results), I blew away the world and did a clean install of Windows 10, 1511 yesterday. It appears to be better - at least it'll boot consistently and be usable. Last evening, Windows popped up and...
I know there are a handful of threads with the above error message and code, but I have yet to see a thread with what was my reason for the error code. I wanted to pass on what I discovered and how I fixed it. I started with a standard Windows 7...
I have upgraded 5 machines and clean installed 3 machines. Experienced an issue with one machine with continuous corruption problems After the 3rd attempt I discovered that even with a Clean Install of Win 10 I get unrepairable errors - Sorry...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 02:17.
Find Us