[SOLVED] [10v1709b16299 x64] Cannot repair member file [l:9]'MSDTC.LOG'

D

DigitalUnicorn

Member
Joined
Jan 6, 2018
Posts
6
Hello all,

Looking through the internet seems like you guys really know your stuff!
Would really appreciate some help with my windows 10 pc.

My build :

Intel Core i7-4770 3.4ghz
MSI B85M-E45
8GB of ram
Radeon R9 270
512 HDD
128 SSD


Earlier today my screens went blank and would not display past the windows logo after a reboot. Windows fault text said: Video TDR Failure. I can successfully boot up with display active in safe mode with networking, however after several attempts at uninstalling and reinstalling various drivers on both the display adapter and Intel chipset I have been unable to boot up normally without the screen returning to black. I attempted a reset of windows, however, it never fully completes and froze at various different stages over multiple attempts. Each time I restarted it would say "undoing" then boot up with exactly the same issues. After doing a bit of research, I tried using the SFC Scannow command prompt, these were the results even after multiple reset attempts :

2018-01-06 21:27:51, Info CSI 00004f54 [SR] Cannot repair member file [l:9]'MSDTC.LOG' of Microsoft-Windows-COM-DTC-Runtime, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-01-06 21:27:51, Info CSI 00004f55@2018/1/6:21:27:51.486 Primitive installers committed for repair
2018-01-06 21:27:51, Info CSI 00004f56 Hashes for file member [l:9]'MSDTC.LOG' do not match.
Expected: {l:32 b:43886d9c8fb22be268d0326e8137ea8eae34207917164216cb201a0e314612fa}.
Actual: {l:32 b:8bb6bcc9732af84623323ea3b44455bba72c641245f36954775017e2fc51c0fb}.
2018-01-06 21:27:51, Info CSI 00004f57 [SR] Cannot repair member file [l:9]'MSDTC.LOG' of Microsoft-Windows-COM-DTC-Runtime, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-01-06 21:27:51, Info CSI 00004f58 [SR] This component was referenced by [l:144]'Microsoft-Windows-Client-Features-Package0014~31bf3856ad364e35~amd64~~10.0.16299.15.microsoft-windows-client-features-deployment00140-Deployment'
2018-01-06 21:27:51, Info CSI 00004f59@2018/1/6:21:27:51.595 Primitive installers committed for repair
2018-01-06 21:27:51, Info CSI 00004f5a [SR] Repair complete
2018-01-06 21:27:51, Info CSI 00004f5b [SR] Committing transaction
2018-01-06 21:27:51, Info CSI 00004f5c Creating NT transaction (seq 1)
2018-01-06 21:27:51, Info CSI 00004f5d Created NT transaction (seq 1) result 0x00000000, handle @0xd58
2018-01-06 21:27:51, Info CSI 00004f5e@2018/1/6:21:27:51.642 Beginning NT transaction commit...
2018-01-06 21:27:51, Info CSI 00004f5f@2018/1/6:21:27:51.845 CSI perf trace:
CSIPERF:TXCOMMIT;225620

Lots have people have come to the forum and found fixes for this, however, all the posts included warnings about the fixes being specific to that person pc, hence why I have started my own thread.

I also saw several logs like this about my Avast antivirus software:

2018-01-06 21:27:51, Info CSI 00004f60 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2018-01-06 21:27:51, Info SXS Uninstall Assembly: Avast.VC140.DebugCRT,type="win32",processorArchitecture="x86",version="14.0.23506.0",publicKeyToken="fcc99ee6193ebbca"
2018-01-06 21:27:51, Info SXS Submitting uninstall transaction
2018-01-06 21:27:52, Info CSI 00004f61 Performing 1 operations as follows:
(0) Uninstall: flags: 1 tlc: [Avast.VC140.DebugCRT, version 14.0.23506.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32']) ref: ( flgs: 00000000 guid: {2ec93463-b0c3-45e1-8364-327e96aea856} name: [l:38]'{A7BC6012-FC4E-440D-87D4-6F1C036A3A0B}' ncdata: [l:0]'')
2018-01-06 21:27:52, Info CSI 00004f62 Call to uninstall failed, the TLC is not currently installed by that installer
2018-01-06 21:27:52, Info CSI 00004f63 Creating NT transaction (seq 2)
2018-01-06 21:27:52, Info CSI 00004f64 Created NT transaction (seq 2) result 0x00000000, handle @0x914
2018-01-06 21:27:52, Info CSI 00004f65@2018/1/6:21:27:52.455 Beginning NT transaction commit...
2018-01-06 21:27:52, Info CSI 00004f66@2018/1/6:21:27:52.595 CSI perf trace:
CSIPERF:TXCOMMIT;152980


If you need any additional information or logs don't hesitate to ask.
Cheers,
Ben
 
Re: Cannot repair member file [l:9]'MSDTC.LOG'

Hello and welcome to Sysnative!

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.




SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

Re: Cannot repair member file [l:9]'MSDTC.LOG'

Thank you for the quick response:
Code: 
SFCFix version 3.0.0.0 by niemiro.Start time: 2018-01-06 23:31:11.976
Microsoft Windows 10 Build 16299 - amd64
Using .zip script file at C:\Users\Caleb\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.16299.15_none_3c3f2ed7d1276eac\MSDTC.LOG


Successfully copied file C:\Users\Caleb\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.16299.15_none_3c3f2ed7d1276eac\MSDTC.LOG to C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.16299.15_none_3c3f2ed7d1276eac\MSDTC.LOG.


Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.16299.15_none_3c3f2ed7d1276eac\MSDTC.LOG
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.16299.15_none_3c3f2ed7d1276eac\MSDTC.LOG
PowerCopy:: directive completed successfully.








Successfully processed all directives.






Failed to generate a complete zip file. Upload aborted.




SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2018-01-06 23:35:17.286
Script hash: pCH1peavVq/pwaBc1ajS6yyzJEM2KO9WWvmyIpgXl4U=
----------------------EOF-----------------------
 
Re: Cannot repair member file [l:9]'MSDTC.LOG'

yep, sorry, getting a bit ahead of myself there, looks like its still finding an error :

Code: 
2018-01-06 23:52:47, Info                  CSI    00004f38 [SR] Verify complete2018-01-06 23:52:47, Info                  CSI    00004f39 [SR] Repairing 1 components
2018-01-06 23:52:47, Info                  CSI    00004f3a [SR] Beginning Verify and Repair transaction
2018-01-06 23:52:47, Info                  CSI    00004f3b Hashes for file member [l:9]'MSDTC.LOG' do not match.
 Expected: {l:32 b:43886d9c8fb22be268d0326e8137ea8eae34207917164216cb201a0e314612fa}.
 Actual: {l:32 b:69d20d069f9331241e366f3c1869ff437a2b7aaaaf086da2ff71f39a3d726a89}.
2018-01-06 23:52:47, Info                  CSI    00004f3c [SR] Cannot repair member file [l:9]'MSDTC.LOG' of Microsoft-Windows-COM-DTC-Runtime, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-01-06 23:52:47, Info                  CSI    00004f3d@2018/1/6:23:52:47.208 Primitive installers committed for repair
2018-01-06 23:52:47, Info                  CSI    00004f3e Hashes for file member [l:9]'MSDTC.LOG' do not match.
 Expected: {l:32 b:43886d9c8fb22be268d0326e8137ea8eae34207917164216cb201a0e314612fa}.
 Actual: {l:32 b:69d20d069f9331241e366f3c1869ff437a2b7aaaaf086da2ff71f39a3d726a89}.
2018-01-06 23:52:47, Info                  CSI    00004f3f [SR] Cannot repair member file [l:9]'MSDTC.LOG' of Microsoft-Windows-COM-DTC-Runtime, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-01-06 23:52:47, Info                  CSI    00004f40 [SR] This component was referenced by [l:144]'Microsoft-Windows-Client-Features-Package0014~31bf3856ad364e35~amd64~~10.0.16299.15.microsoft-windows-client-features-deployment00140-Deployment'
2018-01-06 23:52:47, Info                  CSI    00004f41@2018/1/6:23:52:47.271 Primitive installers committed for repair
2018-01-06 23:52:47, Info                  CSI    00004f42 [SR] Repair complete
2018-01-06 23:52:47, Info                  CSI    00004f43 [SR] Committing transaction
2018-01-06 23:52:47, Info                  CSI    00004f44 Creating NT transaction (seq 1)
2018-01-06 23:52:47, Info                  CSI    00004f45 Created NT transaction (seq 1) result 0x00000000, handle @0xe88
2018-01-06 23:52:47, Info                  CSI    00004f46@2018/1/6:23:52:47.365 Beginning NT transaction commit...
2018-01-06 23:52:47, Info                  CSI    00004f47@2018/1/6:23:52:47.521 CSI perf trace:
CSIPERF:TXCOMMIT;182515
2018-01-06 23:52:47, Info                  CSI    00004f48 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
 
Re: Cannot repair member file [l:9]'MSDTC.LOG'

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.



  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.





SFC Scan



  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

Re: Cannot repair member file [l:9]'MSDTC.LOG'

Code: 
SFCFix version 3.0.0.0 by niemiro.Start time: 2018-01-07 00:00:22.691
Microsoft Windows 10 Build 16299 - amd64
Using .zip script file at C:\Users\Caleb\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.16299.15_none_3c3f2ed7d1276eac\MSDTC.LOG


WARNING: File C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.16299.15_none_3c3f2ed7d1276eac\MSDTC.LOG was not backed up as that would replace the current backup.
Successfully copied file C:\Users\Caleb\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.16299.15_none_3c3f2ed7d1276eac\MSDTC.LOG to C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.16299.15_none_3c3f2ed7d1276eac\MSDTC.LOG.


Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.16299.15_none_3c3f2ed7d1276eac\MSDTC.LOG
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.16299.15_none_3c3f2ed7d1276eac\MSDTC.LOG
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.

and the scan results

Code: 
Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.


Windows Resource Protection did not find any integrity violations.

Should i try and reboot out of safe mode?
 
Re: Cannot repair member file [l:9]'MSDTC.LOG'

Excellent! Go ahead, although I really think this can't have caused it. Are you sure your video card is not dead?
 
Re: Cannot repair member file [l:9]'MSDTC.LOG'

I'm not 100% it isn't dead no, but my display is running through its Dvi-D port in safe mode fine, ill report back with what happens
 
Re: Cannot repair member file [l:9]'MSDTC.LOG'

That's not comfirmation that it works. When you are in Safe Mode you are using Microsoft generic driver and only the 2d section of the card, so it's not under load. If you have a spare card, that's the very first thing I'd try swapping out.
 
Re: Cannot repair member file [l:9]'MSDTC.LOG'

softwaremaniac said:
That's not confirmation that it works. When you are in Safe Mode you are using Microsoft generic driver and only the 2d section of the card, so it's not under load. If you have a spare card, that's the very first thing I'd try swapping out.
Click to expand...

Hello again,

Rebooting out of safe mode didn't work, but at the moment neither does booting up with a different GPU. I borrowed a friends spare HD5770 that was functioning perfectly and put it in my tower. I have booted up in safe mode and downloaded the drivers for it. Now, same as before, I am getting an error message when I attempt to install the catalyst drivers:

Code: 
Failed to load detection drivers

The recommended fix online is to uninstall AMD software via the control panel then reinstall the full suite afterward. However, as before, I cannot uninstall the software, it's been stuck in the uninstall window for about 15 minutes now. I also cannot get access to windows update on the settings menu. Are some of these things symptoms of safe mode? Or is it some greater fault with windows installer? I'm kind of at a loss, there seem to be so many failure points in my software at the moment. Any help would be really appreciated.

P.S. Sorry I didn't mention any of those faults before I thought they were symptoms of my registry faults.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top