Windows Update KB2267602 Failed

Stuff_and_Thangs · Aug 15, 2014

I noticed I have a failed update under my Windows Update history so I need some help getting that update installed correctly. Are the updates really different for KB2267602, or are they all the same update being "successfully" installed over and over with a different definition? Why are Windows Defender updates being shown in my Windows Update history? I don't ever remember Windows Defender updates being shown in my history before.

Go The Power · Aug 18, 2014

Hello and welcome to the forum :)

Its hard to say without looking at the contents of each update, but they could be for a few different things.

DISM Scan

Right click on the

button
Click on Command prompt (Admin) => Press Yes on the prompt
Inside the Command Prompt windows copy and paste the following command DISM /Online /Cleanup-Image /RestoreHealth
Please wait for this to Finish before continuing with rest of the steps.

SFC /SCANNOW

Right click on the

button
Click on Command prompt (Admin) => Press Yes on the prompt
Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
Please wait for this to Finish before continuing with rest of the steps.

Export CBS folder

Right click on the

button
Click on File Explorer
Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
Find and double click on the Logs folder.
Right-click on the CBS folder, and select Copy.
Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
A new file, also called CBS (CBS.zip), but this time with a different icon, will be created.
Attach this to your next post please.

Please Note:: if the file is too big to upload to you next please post please upload via Dropbox or ge.tt

Stuff_and_Thangs · Aug 18, 2014

How do i share with Dropbox?

Go The Power · Aug 19, 2014

Lets collect these logs another way:

SFCFix Collect CBS

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download SFCFix.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
On your Desktop, you should now see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now begin to upload your CBS logfiles to our server.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

If all goes well, you should see that your logfiles have now been added to your thread.

LogBot · Aug 19, 2014

Logfile submission from Stuff_and_Thangs

Logfile submission from Stuff_and_Thangs.

The logfiles are available at: https://www.sysnative.com/niemiro/fileDistribution/2014-08/606.zip

Stuff_and_Thangs · Aug 19, 2014

I followed all the steps correctly, but something doesn't look right.

Code:

SFCFix version 2.3.0.0 by niemiro.Start time: 2014-08-19 08:03:00.080
Using .txt script file at C:\Users\Admin\Desktop\SFCFixScript.txt [0]








Collect:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.3.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-08-19 08:04:56.863
Script hash: 
----------------------EOF-----------------------

Stuff_and_Thangs · Aug 19, 2014

Nevermind, i see "LogBot". lol :)

Go The Power · Aug 19, 2014

Do you get an error message when trying to run the update?

Windows Update Log

Right click on the

button
Click on Run Inside the Run box copy and paste the following command
cmd /c copy %windir%\WindowsUpdate.log "%userprofile%\Desktop\WindowsUpdate.txt"
Please go to your desktop and attach WindowsUpdate.txt to your next post

Stuff_and_Thangs · Aug 20, 2014

I went to Control Panel > System and Security > Windows Update > View update history and right clicked on the failed update and clicked View details and there is an error code 80240055

I can't attach the WindowsUpdate.txt because the file is too big.

Go The Power · Aug 20, 2014

Lets try and add it to dropbox again, here are some instructions on how to use Dropbox: https://www.dropbox.com/help/19

Stuff_and_Thangs · Aug 20, 2014

I think I got it.

https://www.dropbox.com/s/sc6ynkvqq7onzvh/WindowsUpdate.txt

Stuff_and_Thangs · Aug 20, 2014

Do I need any of the CBS folders, text files, or what you told me to download by niemiro, anymore? If i don't need any of that stuff, I'll delete it off of my desktop.

Go The Power · Aug 21, 2014

No you can delete all those files now.

Software Distribution rename

Right click on the

button -> Click on Command prompt (Admin) => Press Yes on the prompt
Enter in the following commands:
net stop wuauserv
ren %SystemRoot%\SoftwareDistribution\Download DL.bak
ren %SystemRoot%\SoftwareDistribution\DataStore DS.bak
net start wuauserv

Once completed please try and run windows update again.

Stuff_and_Thangs · Aug 21, 2014

After clicking "Check for updates" I have an error code 8024A000. To clarify, Windows Update was running fine. I just had an error with one update that i couldn't install. I may be wrong, I'm not the Windows Update expert here. I am confused though, lol! :huh:

Go The Power · Aug 21, 2014

Hello :)

Lets take a look at the event logs now:

Event Log Viewer

Please download VEW.exe from Here and save it to your desktop.
Go to your desktop and right click on VEW.exe and choose Run as Administrator
Once open set the following settings
- 'Select log to query'
  1. Tick Application
  2. Tick System
- 'Select Type to list'
  1. Tick Critical
  2. Tick Error
  3. Tick Information
  4. Tick Warning
- 'Number or date events'
  1. Tick Number of Events and set it to 20
Click on Run
Once completed a notepad file will open. Please copy and paste the contents of VEW.txt back into this thread.

Stuff_and_Thangs · Aug 21, 2014

Code:

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 21/08/2014 10:46:46 PM


Note: All dates below are in the format dd/mm/yyyy


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 22/08/2014 1:24:27 AM
Type: Error Category: 0
Event: 78 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\theHunter\launcher\launcher.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_6242a4b3ecbb55a1.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7.manifest.


Log: 'Application' Date/Time: 21/08/2014 3:10:07 AM
Type: Error Category: 0
Event: 1013 Source: MsiInstaller
Product: NVIDIA PhysX -- Installation terminated


Log: 'Application' Date/Time: 20/08/2014 11:11:10 AM
Type: Error Category: 0
Event: 1013 Source: MsiInstaller
Product: NVIDIA PhysX -- Installation terminated


Log: 'Application' Date/Time: 20/08/2014 11:09:57 AM
Type: Error Category: 0
Event: 1013 Source: MsiInstaller
Product: NVIDIA PhysX -- Installation terminated


Log: 'Application' Date/Time: 20/08/2014 10:58:20 AM
Type: Error Category: 0
Event: 78 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\theHunter\launcher\launcher.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_6242a4b3ecbb55a1.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7.manifest.


Log: 'Application' Date/Time: 20/08/2014 10:49:51 AM
Type: Error Category: 0
Event: 4107 Source: Microsoft-Windows-CAPI2
Failed extract of third-party root list from auto update cab at: <http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: The data is invalid. .


Log: 'Application' Date/Time: 18/08/2014 3:05:08 PM
Type: Error Category: 0
Event: 78 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\theHunter\launcher\launcher.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_6242a4b3ecbb55a1.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7.manifest.


Log: 'Application' Date/Time: 18/08/2014 2:57:12 PM
Type: Error Category: 0
Event: 78 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\theHunter\launcher\launcher.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_6242a4b3ecbb55a1.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7.manifest.


Log: 'Application' Date/Time: 16/08/2014 4:20:44 PM
Type: Error Category: 0
Event: 78 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\theHunter\launcher\launcher.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_6242a4b3ecbb55a1.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7.manifest.


Log: 'Application' Date/Time: 13/08/2014 5:53:05 PM
Type: Error Category: 0
Event: 78 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\theHunter\launcher\launcher.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_6242a4b3ecbb55a1.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7.manifest.


Log: 'Application' Date/Time: 11/08/2014 9:55:14 PM
Type: Error Category: 0
Event: 1013 Source: MsiInstaller
Product: NVIDIA PhysX -- Installation terminated


Log: 'Application' Date/Time: 11/08/2014 9:52:46 PM
Type: Error Category: 0
Event: 1013 Source: MsiInstaller
Product: NVIDIA PhysX -- Installation terminated


Log: 'Application' Date/Time: 11/08/2014 9:51:08 PM
Type: Error Category: 0
Event: 1013 Source: MsiInstaller
Product: NVIDIA PhysX -- Installation terminated


Log: 'Application' Date/Time: 11/08/2014 8:50:39 PM
Type: Error Category: 0
Event: 78 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\theHunter\launcher\launcher.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_6242a4b3ecbb55a1.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7.manifest.


Log: 'Application' Date/Time: 10/08/2014 7:30:07 PM
Type: Error Category: 0
Event: 78 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\theHunter\launcher\launcher.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_6242a4b3ecbb55a1.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7.manifest.


Log: 'Application' Date/Time: 10/08/2014 5:59:49 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: chromeinstall-7u67.exe, version: 7.0.670.1, time stamp: 0x53d2c4f9 Faulting module name: chromeinstall-7u67.exe, version: 7.0.670.1, time stamp: 0x53d2c4f9 Exception code: 0xc0000409 Fault offset: 0x00012635 Faulting process id: 0x10c8 Faulting application start time: 0x01cfb4c4d5ffa3ee Faulting application path: C:\Users\Admin\Desktop\chromeinstall-7u67.exe Faulting module path: C:\Users\Admin\Desktop\chromeinstall-7u67.exe Report Id: 1e821bb3-20b8-11e4-8270-40167e223795 Faulting package full name:  Faulting package-relative application ID: 


Log: 'Application' Date/Time: 10/08/2014 2:55:55 PM
Type: Error Category: 0
Event: 78 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\theHunter\launcher\launcher.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_6242a4b3ecbb55a1.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7.manifest.


Log: 'Application' Date/Time: 10/08/2014 2:45:19 PM
Type: Error Category: 0
Event: 78 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\theHunter\launcher\launcher.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_6242a4b3ecbb55a1.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7.manifest.


Log: 'Application' Date/Time: 08/08/2014 4:26:08 PM
Type: Error Category: 0
Event: 78 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\theHunter\launcher\launcher.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_6242a4b3ecbb55a1.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7.manifest.


Log: 'Application' Date/Time: 07/08/2014 3:37:37 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Watch_Dogs.exe, version: 0.1.0.1, time stamp: 0x53c5ce21 Faulting module name: nvwgf2umx.dll, version: 9.18.13.4052, time stamp: 0x53b4437c Exception code: 0xc00000fd Fault offset: 0x0000000000431dd3 Faulting process id: 0x5fc Faulting application start time: 0x01cfb2330084eb0f Faulting application path: C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Watch_Dogs\bin\Watch_Dogs.exe Faulting module path: C:\WINDOWS\SYSTEM32\nvwgf2umx.dll Report Id: c175fe57-1e48-11e4-826b-40167e223795 Faulting package full name:  Faulting package-relative application ID: 


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 22/08/2014 3:09:30 AM
Type: Information Category: 0
Event: 0 Source: gupdate
The event description cannot be found.


Log: 'Application' Date/Time: 22/08/2014 1:36:57 AM
Type: Information Category: 0
Event: 8224 Source: VSS
The VSS service is shutting down due to idle timeout. 


Log: 'Application' Date/Time: 22/08/2014 1:33:57 AM
Type: Information Category: 0
Event: 8302 Source: Microsoft-Windows-System-Restore
Scoping successfully completed for shadowcopy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1.


Log: 'Application' Date/Time: 22/08/2014 1:33:57 AM
Type: Information Category: 0
Event: 8301 Source: Microsoft-Windows-System-Restore
Scoping completed for shadowcopy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1.


Log: 'Application' Date/Time: 22/08/2014 1:33:52 AM
Type: Information Category: 0
Event: 8300 Source: Microsoft-Windows-System-Restore
Scoping started for shadowcopy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1.


Log: 'Application' Date/Time: 22/08/2014 1:33:31 AM
Type: Information Category: 0
Event: 8212 Source: System Restore
Successfully created scheduled restore point.


Log: 'Application' Date/Time: 22/08/2014 1:33:31 AM
Type: Information Category: 0
Event: 8194 Source: System Restore
Successfully created restore point (Process = C:\WINDOWS\system32\srtasks.exe ExecuteScheduledSPPCreation; Description = Scheduled Checkpoint).


Log: 'Application' Date/Time: 22/08/2014 1:31:25 AM
Type: Information Category: 1
Event: 103 Source: ESENT
svchost (4436) Instance: The database engine stopped the instance (0).    Dirty Shutdown: 0    Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.015, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.016, [11] 0.000, [12] 0.000, [13] 0.000, [14] 0.000, [15] 0.000.


Log: 'Application' Date/Time: 22/08/2014 1:31:25 AM
Type: Information Category: 1
Event: 327 Source: ESENT
svchost (4436) Instance: The database engine detached a database (1, C:\ProgramData\Microsoft\Windows\AppRepository\PackageRepository.edb). (Time=0 seconds)    Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.016, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.000, [12] 0.000.  Revived Cache: 0 0


Log: 'Application' Date/Time: 22/08/2014 1:27:52 AM
Type: Information Category: 0
Event: 258 Source: Microsoft-Windows-Defrag
The storage optimizer successfully completed boot optimization on (C:)


Log: 'Application' Date/Time: 22/08/2014 1:24:25 AM
Type: Information Category: 1
Event: 326 Source: ESENT
svchost (4436) Instance: The database engine attached a database (1, C:\ProgramData\Microsoft\Windows\AppRepository\PackageRepository.edb). (Time=0 seconds)    Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.015, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.000, [12] 0.000.  Saved Cache: 1 0


Log: 'Application' Date/Time: 22/08/2014 1:24:25 AM
Type: Information Category: 1
Event: 105 Source: ESENT
svchost (4436) Instance: The database engine started a new instance (0). (Time=0 seconds)    Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000.


Log: 'Application' Date/Time: 22/08/2014 1:24:25 AM
Type: Information Category: 1
Event: 102 Source: ESENT
svchost (4436) Instance: The database engine (6.03.9600.0000) is starting a new instance (0).


Log: 'Application' Date/Time: 22/08/2014 1:24:18 AM
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket 90422338219, type 5 Event Name: PDUWICA Response: Not available Cab Id: 0  Problem signature: P1: 101 P2: 1.4 P3: 6.3.0.0 P4: 1033 P5: 62 P6:  P7:  P8:  P9:  P10:   Attached files:  These files may be available here:   Analysis symbol:  Rechecking for solution: 0 Report Id: 08985651-299b-11e4-827e-40167e223795 Report Status: 0 Hashed bucket: ce814e80a6c7c7e41dc13d0cb78d024c


Log: 'Application' Date/Time: 22/08/2014 1:14:04 AM
Type: Information Category: 1
Event: 103 Source: ESENT
svchost (420) Instance: The database engine stopped the instance (0).    Dirty Shutdown: 0    Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.000, [12] 0.000, [13] 0.000, [14] 0.000, [15] 0.000.


Log: 'Application' Date/Time: 22/08/2014 1:14:04 AM
Type: Information Category: 1
Event: 327 Source: ESENT
svchost (420) Instance: The database engine detached a database (1, C:\ProgramData\Microsoft\Windows\AppRepository\PackageRepository.edb). (Time=0 seconds)    Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.016, [12] 0.000.  Revived Cache: 0 0


Log: 'Application' Date/Time: 22/08/2014 1:09:02 AM
Type: Information Category: 1
Event: 326 Source: ESENT
svchost (420) Instance: The database engine attached a database (1, C:\ProgramData\Microsoft\Windows\AppRepository\PackageRepository.edb). (Time=0 seconds)    Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.000, [12] 0.000.  Saved Cache: 1 0


Log: 'Application' Date/Time: 22/08/2014 1:09:02 AM
Type: Information Category: 1
Event: 105 Source: ESENT
svchost (420) Instance: The database engine started a new instance (0). (Time=0 seconds)    Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000.


Log: 'Application' Date/Time: 22/08/2014 1:09:02 AM
Type: Information Category: 1
Event: 102 Source: ESENT
svchost (420) Instance: The database engine (6.03.9600.0000) is starting a new instance (0).


Log: 'Application' Date/Time: 21/08/2014 11:22:37 PM
Type: Information Category: 1
Event: 103 Source: ESENT
svchost (152) Instance: The database engine stopped the instance (0).    Dirty Shutdown: 0    Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.000, [12] 0.000, [13] 0.000, [14] 0.000, [15] 0.000.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 21/08/2014 10:28:22 PM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (4488) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 21/08/2014 10:28:05 PM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (972) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 21/08/2014 10:25:57 PM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (2624) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 21/08/2014 3:18:19 AM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (876) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 20/08/2014 10:37:56 AM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (2508) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 19/08/2014 8:43:05 AM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (628) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 18/08/2014 10:47:54 PM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (2380) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 18/08/2014 10:47:38 PM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (4368) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 18/08/2014 10:08:51 PM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (4616) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 18/08/2014 8:35:47 PM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (4916) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 18/08/2014 8:33:51 PM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (3456) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 18/08/2014 7:29:22 PM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (2620) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 18/08/2014 6:31:55 PM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (4308) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 15/08/2014 10:05:11 PM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (2164) C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\: The shadow header page of file C:\Users\Admin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\nouser0000000000000001\120712-0049\DBStore\edb.chk was damaged. The primary header page (4096 bytes) was used instead.


Log: 'Application' Date/Time: 15/08/2014 7:24:19 PM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\explorer.exe' (pid 956) cannot be restarted - Application SID does not match Conductor SID..


Log: 'Application' Date/Time: 15/08/2014 6:54:07 PM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\splwow64.exe' (pid 3608) cannot be restarted - Application SID does not match Conductor SID..


Log: 'Application' Date/Time: 15/08/2014 6:54:07 PM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\explorer.exe' (pid 2124) cannot be restarted - Application SID does not match Conductor SID..


Log: 'Application' Date/Time: 15/08/2014 6:54:07 PM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files\NVIDIA Corporation\NvStreamSrv\nvstreamsvc.exe' (pid 1816) cannot be restarted - Application SID does not match Conductor SID..


Log: 'Application' Date/Time: 15/08/2014 6:53:20 PM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\System32\wbem\WmiPrvSE.exe' (pid 3776) cannot be restarted - Application SID does not match Conductor SID..


Log: 'Application' Date/Time: 15/08/2014 6:53:20 PM
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files\Windows Defender\MpCmdRun.exe' (pid 2244) cannot be restarted - Application SID does not match Conductor SID..


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 21/08/2014 2:21:37 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 20/08/2014 10:31:34 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 12/08/2014 4:21:00 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 11/08/2014 11:35:57 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 11/08/2014 5:18:29 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 10/08/2014 5:17:32 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 10/08/2014 12:37:44 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 09/08/2014 4:07:05 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 09/08/2014 4:29:03 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 08/08/2014 4:15:12 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 07/08/2014 11:27:25 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 06/08/2014 9:13:29 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 06/08/2014 10:13:34 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 04/08/2014 1:24:12 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 02/08/2014 12:54:18 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 02/08/2014 2:29:32 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 01/08/2014 6:23:55 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 31/07/2014 11:41:56 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 31/07/2014 11:57:59 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 31/07/2014 12:22:50 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 22/08/2014 1:25:18 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 22/08/2014 1:24:48 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 21/08/2014 2:21:48 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 8:51:51 PM on ?8/?20/?2014 was unexpected.


Log: 'System' Date/Time: 21/08/2014 2:21:30 AM
Type: Error Category: 0
Event: 29 Source: Microsoft-Windows-Kernel-Boot
Windows failed fast startup with error status 0xC00000D4.


Log: 'System' Date/Time: 20/08/2014 11:33:43 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 20/08/2014 10:31:43 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 3:53:03 AM on ?8/?19/?2014 was unexpected.


Log: 'System' Date/Time: 20/08/2014 10:31:26 AM
Type: Error Category: 0
Event: 29 Source: Microsoft-Windows-Kernel-Boot
Windows failed fast startup with error status 0xC00000D4.


Log: 'System' Date/Time: 18/08/2014 2:57:37 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 18/08/2014 2:50:31 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 18/08/2014 2:50:01 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 16/08/2014 4:21:38 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 16/08/2014 4:21:08 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 15/08/2014 7:28:39 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 15/08/2014 7:27:59 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 15/08/2014 6:52:43 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 15/08/2014 6:52:13 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 14/08/2014 6:41:23 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Steam Client Service service failed to start due to the following error:  The service did not respond to the start or control request in a timely fashion.


Log: 'System' Date/Time: 14/08/2014 6:41:23 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect.


Log: 'System' Date/Time: 13/08/2014 5:53:48 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 13/08/2014 5:53:18 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 22/08/2014 2:40:21 AM
Type: Information Category: 0
Event: 7040 Source: Service Control Manager
The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.


Log: 'System' Date/Time: 22/08/2014 1:40:51 AM
Type: Information Category: 0
Event: 7040 Source: Service Control Manager
The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.


Log: 'System' Date/Time: 22/08/2014 1:34:01 AM
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Windows\System32\WinSAT.exe (process ID:4912) reset policy scheme from {8C5E7FDA-E8BF-4A96-9A85-A6E23A8C635C} to {8C5E7FDA-E8BF-4A96-9A85-A6E23A8C635C}


Log: 'System' Date/Time: 22/08/2014 1:33:58 AM
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Windows\System32\WinSAT.exe (process ID:4912) reset policy scheme from {8C5E7FDA-E8BF-4A96-9A85-A6E23A8C635C} to {8C5E7FDA-E8BF-4A96-9A85-A6E23A8C635C}


Log: 'System' Date/Time: 22/08/2014 1:33:49 AM
Type: Information Category: 0
Event: 16 Source: Microsoft-Windows-Kernel-General
The access history in hive \??\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Users\default\ntuser.dat was cleared updating 528 keys and creating 30 modified pages.


Log: 'System' Date/Time: 22/08/2014 1:33:33 AM
Type: Information Category: 0
Event: 11 Source: Microsoft-Windows-Kernel-General
TxR init phase for hive \??\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\WINDOWS\system32\config\DRIVERS (TM: {DCC5FE3A-28D9-11E4-827E-40167E223795}, RM: {DCC5FE39-28D9-11E4-827E-40167E223795}) finished with result=0xC00000A2 (Internal code=7).


Log: 'System' Date/Time: 22/08/2014 1:33:33 AM
Type: Information Category: 0
Event: 11 Source: Microsoft-Windows-Kernel-General
TxR init phase for hive \??\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\WINDOWS\system32\config\SYSTEM (TM: {DCC5FE38-28D9-11E4-827E-40167E223795}, RM: {DCC5FE37-28D9-11E4-827E-40167E223795}) finished with result=0xC00000A2 (Internal code=7).


Log: 'System' Date/Time: 22/08/2014 1:33:30 AM
Type: Information Category: 0
Event: 98 Source: Microsoft-Windows-Ntfs
Volume ?? (\Device\HarddiskVolumeShadowCopy1) is healthy.  No action is needed.


Log: 'System' Date/Time: 22/08/2014 1:25:13 AM
Type: Information Category: 0
Event: 7040 Source: Service Control Manager
The start type of the Windows Modules Installer service was changed from auto start to demand start.


Log: 'System' Date/Time: 22/08/2014 1:24:17 AM
Type: Information Category: 0
Event: 7040 Source: Service Control Manager
The start type of the Windows Modules Installer service was changed from demand start to auto start.


Log: 'System' Date/Time: 22/08/2014 12:40:21 AM
Type: Information Category: 0
Event: 7040 Source: Service Control Manager
The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.


Log: 'System' Date/Time: 21/08/2014 11:17:33 PM
Type: Information Category: 1101
Event: 7001 Source: Microsoft-Windows-Winlogon
User Logon Notification for Customer Experience Improvement Program


Log: 'System' Date/Time: 21/08/2014 11:17:22 PM
Type: Information Category: 0
Event: 1 Source: Microsoft-Windows-Power-Troubleshooter
The system has returned from a low power state.  Sleep Time: ?2014?-?08?-?21T22:35:14.127112800Z Wake Time: ?2014?-?08?-?21T23:17:20.207706700Z  Wake Source: Unknown


Log: 'System' Date/Time: 21/08/2014 11:17:20 PM
Type: Information Category: 0
Event: 27 Source: Microsoft-Windows-Kernel-Boot
The boot type was 0x1.


Log: 'System' Date/Time: 21/08/2014 11:17:20 PM
Type: Information Category: 0
Event: 25 Source: Microsoft-Windows-Kernel-Boot
The boot menu policy was 0x1.


Log: 'System' Date/Time: 21/08/2014 11:17:20 PM
Type: Information Category: 0
Event: 32 Source: Microsoft-Windows-Kernel-Boot
The bootmgr spent 0 ms waiting for user input.


Log: 'System' Date/Time: 21/08/2014 11:17:20 PM
Type: Information Category: 0
Event: 18 Source: Microsoft-Windows-Kernel-Boot
There are 0x1 boot options on this system.


Log: 'System' Date/Time: 21/08/2014 11:17:20 PM
Type: Information Category: 0
Event: 30 Source: Microsoft-Windows-Kernel-Boot
The firmware reported boot metrics.


Log: 'System' Date/Time: 21/08/2014 11:17:19 PM
Type: Information Category: 0
Event: 2 Source: MEIx64
Intel(R) Management Engine Interface driver has started successfully.


Log: 'System' Date/Time: 21/08/2014 11:17:19 PM
Type: Information Category: 0
Event: 7040 Source: Service Control Manager
The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 21/08/2014 2:21:37 AM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&1.


Log: 'System' Date/Time: 20/08/2014 1:32:44 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&1.


Log: 'System' Date/Time: 20/08/2014 10:48:37 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name [url=http://www.netgear.com]NETGEAR[/url] timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 20/08/2014 10:48:28 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name [url=http://www.google.com]Google[/url] timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 20/08/2014 10:48:23 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name [url=http://www.netgear.com]NETGEAR[/url] timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 20/08/2014 10:48:20 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name ipinfo.io timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 20/08/2014 10:48:09 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name using.netgear.opendns.com timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 20/08/2014 10:47:48 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name win8.ipv6.microsoft.com. timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 20/08/2014 10:31:34 AM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&1.


Log: 'System' Date/Time: 18/08/2014 9:54:49 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&1.


Log: 'System' Date/Time: 18/08/2014 6:33:14 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device USB\VID_18D1&PID_4EE1\076349100061f904.


Log: 'System' Date/Time: 18/08/2014 6:33:12 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&1.


Log: 'System' Date/Time: 18/08/2014 2:57:53 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name vk.com timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 17/08/2014 3:41:52 AM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&1.


Log: 'System' Date/Time: 16/08/2014 8:24:12 PM
Type: Warning Category: 0
Event: 4230 Source: Tcpip
TCP/IP has chosen to restrict the congestion window for several connections due to a network condition.  This could be related to a problem in the TCP global or supplemental configuration and will cause  degraded throughput. 


Log: 'System' Date/Time: 15/08/2014 8:24:30 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&1.


Log: 'System' Date/Time: 15/08/2014 7:08:29 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&1.


Log: 'System' Date/Time: 15/08/2014 5:18:22 PM
Type: Warning Category: 0
Event: 134 Source: Microsoft-Windows-Time-Service
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)


Log: 'System' Date/Time: 14/08/2014 7:48:16 PM
Type: Warning Category: 0
Event: 134 Source: Microsoft-Windows-Time-Service
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)


Log: 'System' Date/Time: 14/08/2014 6:37:39 PM
Type: Warning Category: 0
Event: 36 Source: Microsoft-Windows-Time-Service
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.

Go The Power · Aug 22, 2014

before we continue here, how often does your computer suddenly turn off?

these Events are not good:

Code:

Log: 'System' Date/Time: 21/08/2014 2:21:37 AM
Type: [B][COLOR="#FF0000"]Critical Category: 63[/COLOR][/B]
[B][COLOR="#FF0000"]Event: 41[/COLOR][/B] Source: [B][COLOR="#FF0000"]Microsoft-Windows-Kernel-Power[/COLOR][/B]
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 20/08/2014 10:31:34 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 12/08/2014 4:21:00 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 11/08/2014 11:35:57 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 11/08/2014 5:18:29 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 10/08/2014 5:17:32 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 10/08/2014 12:37:44 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 09/08/2014 4:07:05 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 09/08/2014 4:29:03 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 08/08/2014 4:15:12 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 07/08/2014 11:27:25 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 06/08/2014 9:13:29 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 06/08/2014 10:13:34 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 04/08/2014 1:24:12 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 02/08/2014 12:54:18 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 02/08/2014 2:29:32 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 01/08/2014 6:23:55 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 31/07/2014 11:41:56 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 31/07/2014 11:57:59 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Log: 'System' Date/Time: 31/07/2014 12:22:50 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 22/08/2014 1:25:18 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 22/08/2014 1:24:48 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 21/08/2014 2:21:48 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 8:51:51 PM on ?8/?20/?2014 was unexpected.


Log: 'System' Date/Time: 21/08/2014 2:21:30 AM
Type: Error Category: 0
Event: 29 Source: Microsoft-Windows-Kernel-Boot
Windows failed fast startup with error status 0xC00000D4.


Log: 'System' Date/Time: 20/08/2014 11:33:43 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 20/08/2014 10:31:43 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 3:53:03 AM on ?8/?19/?2014 was unexpected.


Log: 'System' Date/Time: 20/08/2014 10:31:26 AM
Type: Error Category: 0
Event: 29 Source: Microsoft-Windows-Kernel-Boot
Windows failed fast startup with error status 0xC00000D4.


Log: 'System' Date/Time: 18/08/2014 2:57:37 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 18/08/2014 2:50:31 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 18/08/2014 2:50:01 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 16/08/2014 4:21:38 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 16/08/2014 4:21:08 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 15/08/2014 7:28:39 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 15/08/2014 7:27:59 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 15/08/2014 6:52:43 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 15/08/2014 6:52:13 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 14/08/2014 6:41:23 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Steam Client Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.


Log: 'System' Date/Time: 14/08/2014 6:41:23 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect.


Log: 'System' Date/Time: 13/08/2014 5:53:48 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 13/08/2014 5:53:18 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.

Have a read here:
https://www.sysnative.com/forums/bs...rmation/5806-event-id-41-troubleshooting.html

Stuff_and_Thangs · Aug 22, 2014

It's never done that, It's a new computer, It might be my fault. I have been flipping the switch on the back of it off after I shut it down and the fans quit spinning. Then I would turn off the Surge protector to save power. Where i live, we have had a few really bad thunderstorms and the power has went out at least once that i can remember, so that's one of them. I haven't had anything weird such as it turning of unexpectedly that i can remember, and i have pretty good memory.

Stuff_and_Thangs · Aug 22, 2014

I forgot to tell you, I think I seen another failed update in my Windows Update history, before you had me rename those folders inside the SoftwareDistribution folder.

Go The Power · Aug 22, 2014

Stuff_and_Thangs said:
It's never done that, It's a new computer, It might be my fault. I have been flipping the switch on the back of it off after I shut it down and the fans quit spinning. Then I would turn off the Surge protector to save power. Where i live, we have had a few really bad thunderstorms and the power has went out at least once that i can remember, so that's one of them. I haven't had anything weird such as it turning of unexpectedly that i can remember, and i have pretty good memory.

This error would not be from those. Except for the ThunderStorm situation. The error would appear if you went up the machine (while it was turned on) and you ripped out the power cable, as that would be an unexpected shutdown, when your turning the switch of at the back of the PC once it is shutdown wouldn't have this affect.

Did you check the following?

usasma said:
Primarily check:
Overclocking: Disable overclocking to see whether the issue occurs when the system is run at the correct speed.
Check the memory: Verify the memory by using a memory checker. Verify that each memory chip is the same speed and that it is configured correctly in the system.
Power supply: Make sure that the power supply has enough wattage to appropriately handle the installed devices. If you added memory, installed a newer processor, installed additional drives, or added external devices, such devices can require more energy than the current power supply can provide consistently.
Overheating: Check whether the system is overheating by examining the internal temperature of the hardware.
Defaults: Reset the system back to the system defaults to see whether the issues occur when the system is running in its default configuration.

Another thing to check as well is to check that the power cable for the machine is plugged in correctly, if you can swap over the power cable for a new one and try another wall power socket.

I know you want to get these WU issues fixed, but we really need to focus on these errors first as if the machine is powering down like this it could led to hardware failure\data lose.

Windows Update KB2267602 Failed

Well-known member

Senior Administrator, Windows Update Expert, Contributor

Well-known member

Senior Administrator, Windows Update Expert, Contributor

Well-known member

Well-known member

Well-known member

Senior Administrator, Windows Update Expert, Contributor

Well-known member

Senior Administrator, Windows Update Expert, Contributor

Well-known member

Well-known member

Senior Administrator, Windows Update Expert, Contributor

Well-known member

Attachments

Senior Administrator, Windows Update Expert, Contributor

Well-known member

Senior Administrator, Windows Update Expert, Contributor

Well-known member

Well-known member

Senior Administrator, Windows Update Expert, Contributor