[SOLVED] Non-working audio and CNBJ2530.DPB and prncacla.inf Corruption 8.1

[Verde]

Hi,

After the last Update (11/11/14) the machine became unresponsive while restarting but eventually finished the process without apparent problems, except for the Audio Controller not working (Red line across the speaker). I tried to troubleshoot it from windows and the troubleshooter was unable to do anything except point that it couldn't get the audio service started.

I went to the audio service and it mentioned that there was a particular type of error ('Error code 0x800706cc: The endpoint is a duplicate') I went looking for an answer to that and that pointed me in the direction of SFC, I ran sfc /scannow and CNBJ2530.DPB came to be faulty, a hash verification problem.

I tried to fix it with DCIM and that didn't work

I downloaded SFCFix, ran it and while the first run mentioned it had completely solved the problem (the log says so), the audio had not com back, but not only that, now if I try to troubleshoot the audio controller from the speaker icon I get a new error (0x80070005)

At this point I ran a malaware detection program from microsoft (Microsoft Safety Scanner) and that came out clean.

I ran SFCFix again and now I got a different message about adding a source file to the program.

Now when I try to test again with sfc /scannow the prompt remains inactive.

Additional issues arising from this morning: The inability to access the Control Panel or the Windows Update Panel or the Program Removal Panel, other sections of the Control Panel remain accessible (i.e. System Info)

I have come to the end of what I think I can do.

Any/all help is welcome

In case this helps the machine I am running has: 64-bit windows 8.1 and it is an i3 version of Notebooks & Ultrabooks - ASUS ZENBOOK UX32A - ASUS

 

[Go The Power]

Hello Verde and welcome to Sysnative :)

Lets get a new SFC scan to see whats going on.

SFC /SCANNOW

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

Convert CBS.log to CBS.txt

1. Right click on the
   
   button
2. Click on Run => Inside the run box copy and paste the following command:
   

   cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

3. Press Enter
4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread

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

 

[Verde]

Hi,

Thanks for the welcome and the quick response.

One question, I had tried sfc /scannow (all in lowercase and that did not work) but SFC /SCANNOW (All caps) worked, why?

Anyways, It did work, here is the cbs.txt file

The hash mismatch seems to still be present.

I will wait further instructions

 

[Go The Power]

Hello again :)

Not sure about running sfc with caps or not. AFAIK it shouldn't make a difference. The file reported was the same as the earlier one:

2014-09-12 09:02:11, Info                  CSI    00000855 Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
  Found: {l:32 b:oXVhjVgIuk7RBJQuIVBUHT7WYmN9hAmVGFkUg7a20FU=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}

Lets get this repaired.

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 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 /SCANNOW

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

Convert CBS.log to CBS.txt

1. Right click on the
   
   button
2. Click on Run => Inside the run box copy and paste the following command:
   

   cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

3. Press Enter
4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread

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

 

[Verde]

Here are the results of the SFCFix.zip script

SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-09-12 21:52:46.210
Using .zip script file at C:\Users\Verde\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully  took permissions for file or folder  C:\WINDOWS\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB

Line blocked (SFCFix.txt): "C:\Users\Verde\AppData\Local\niemiro\Archive\SFCFix.txt" C:\WINDOWS\SFCFix.txt.
Successfully  copied file  C:\Users\Verde\AppData\Local\niemiro\Archive\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB  to  C:\WINDOWS\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB.

Successfully  restored ownership for  C:\WINDOWS\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB
Successfully  restored permissions on  C:\WINDOWS\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2014-09-12 21:52:49.108
Script hash: XIC1Er1KzGrU+FdWpLeiRuWUZM5Lv0f/LaVWSUnMfgI=
----------------------EOF-----------------------

Everything went ok with that part, however, SFC /SCANNOW does not seem to respond, upon hitting enter the cursor just flashes underneath the command prompt idly.

 

[Verde]

It seems Tweetdeck was interfering with the Command Prompt, SCANNOW is now running, will get the log up as soon as it finishes

 

[Verde]

Here is the new CBS log https://dl.dropboxusercontent.com/u/11921723/cbs.txt

 

[Verde]

REstarted the machine after the las SFC /SCANNNOW to see if I had regained the audio, but it still doesn't work and I still get an error trying to troubleshoot it: 0x80070005

 

[Verde]

Also, after the last restart, scannow won't run (and I don't have any other programs running)

 

[Go The Power]

Hello,

That file has now been repaired which is start. What troubleshooter are you trying to run? 0x80070005 = Access Denied.

Are you running it as admin?

Event Log Viewer

1. Please download VEW.exe from Here and save it to your desktop.
2. Go to your desktop and right click on VEW.exe and choose Run as Administrator
3. 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
4. Click on Run
5. Once completed a notepad file will open. Please copy and paste the contents of VEW.txt back into this thread.

 

[Verde]

Here is the text from the VEW.txt file

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 13/09/2014 00:56:56

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 12/09/2014 22:38:05
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledSPRetry 2531

Log: 'Application' Date/Time: 12/09/2014 22:38:05
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledEvent 2531

Log: 'Application' Date/Time: 12/09/2014 22:38:05
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: Continuously busy for more than a second

Log: 'Application' Date/Time: 12/09/2014 22:38:04
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledSPRetry 1250

Log: 'Application' Date/Time: 12/09/2014 22:38:04
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledEvent 1250

Log: 'Application' Date/Time: 12/09/2014 22:38:04
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: Continuously busy for more than a second

Log: 'Application' Date/Time: 12/09/2014 21:27:58
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

Log: 'Application' Date/Time: 12/09/2014 17:56:58
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledSPRetry 54625

Log: 'Application' Date/Time: 12/09/2014 17:56:58
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledEvent 54625

Log: 'Application' Date/Time: 12/09/2014 17:56:58
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: Continuously busy for more than a second

Log: 'Application' Date/Time: 12/09/2014 17:56:57
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledSPRetry 53578

Log: 'Application' Date/Time: 12/09/2014 17:56:57
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledEvent 53578

Log: 'Application' Date/Time: 12/09/2014 17:56:57
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: Continuously busy for more than a second

Log: 'Application' Date/Time: 12/09/2014 17:56:56
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledSPRetry 52485

Log: 'Application' Date/Time: 12/09/2014 17:56:56
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledEvent 52485

Log: 'Application' Date/Time: 12/09/2014 17:56:56
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: Continuously busy for more than a second

Log: 'Application' Date/Time: 12/09/2014 17:56:55
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledSPRetry 51407

Log: 'Application' Date/Time: 12/09/2014 17:56:55
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledEvent 51407

Log: 'Application' Date/Time: 12/09/2014 17:56:55
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: Continuously busy for more than a second

Log: 'Application' Date/Time: 12/09/2014 17:56:54
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledSPRetry 50360

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 13/09/2014 05:52:07
Type: Information Category: 0
Event: 9009 Source: Desktop Window Manager
The Desktop Window Manager has exited with code (0xd00002fe)

Log: 'Application' Date/Time: 13/09/2014 05:52:06
Type: Information Category: 0
Event: 4004 Source: Microsoft-Windows-Winlogon
The Windows logon process has failed to terminate the currently logged on user's processes.

Log: 'Application' Date/Time: 13/09/2014 05:36:12
Type: Information Category: 0
Event: 903 Source: Microsoft-Windows-Security-SPP
The Software Protection service has stopped. 

Log: 'Application' Date/Time: 13/09/2014 05:36:12
Type: Information Category: 0
Event: 16384 Source: Microsoft-Windows-Security-SPP
Successfully scheduled Software Protection service for re-start at 2114-08-20T05:36:12Z. Reason: RulesEngine.

Log: 'Application' Date/Time: 13/09/2014 05:35:45
Type: Information Category: 0
Event: 16 Source: SecurityCenter
The Windows Security Center Service could not stop Windows Defender.

Log: 'Application' Date/Time: 13/09/2014 05:35:45
Type: Information Category: 0
Event: 16 Source: SecurityCenter
The Windows Security Center Service could not stop Windows Defender.

Log: 'Application' Date/Time: 13/09/2014 05:35:45
Type: Information Category: 3
Event: 2000 Source: UNS
User Notification Service started.


Log: 'Application' Date/Time: 13/09/2014 05:35:42
Type: Information Category: 0
Event: 1 Source: SecurityCenter
The Windows Security Center Service has started.

Log: 'Application' Date/Time: 13/09/2014 05:35:42
Type: Information Category: 0
Event: 902 Source: Microsoft-Windows-Security-SPP
The Software Protection service has started. 6.3.9600.16497

Log: 'Application' Date/Time: 13/09/2014 05:35:42
Type: Information Category: 0
Event: 1003 Source: Microsoft-Windows-Security-SPP
The Software Protection service has completed licensing status check. Application Id=55c92734-d682-4d71-983e-d6ec3f16059f Licensing Status=
1: 0cdc4d08-6df6-4eb4-b5b4-a373c3e351e7, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
2: 12788d53-9337-42dc-88c9-413b553ba71c, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
3: 1bb82acd-c4ad-4566-813c-55840d559460, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
4: 71f411ae-7b4b-41bd-b68c-c519c499f950, 1, 1 [(0 [0x00000000, 1, 0], [(?)( 1 0x00000000)(?)( 2 0x00000000 0 0 msft:rm/algorithm/hwid/4.0 0x00000000 0)(?)(?)( 10 0x00000000 msft:rm/algorithm/flags/1.0)(?)])(1 )(2 )]
5: 9e4b231b-3e45-41f4-967f-c914f178b6ac, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
6: a25f4cc7-4bd1-4124-a4b8-4e6508dbbab8, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
7: b0f8a518-2c58-4eb8-9319-084f0eb4ddc4, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
8: bbc56067-37f8-49dd-87b2-a418a9ba130a, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
9: bea5bfff-b61d-45e5-bc61-4fca1d85b501, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
10: c72c6a1d-f252-4e7e-bdd1-3fca342acb35, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
11: e2ca509a-a2f4-498b-ba09-297685d369ac, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
12: 4a8149bb-7d61-49f4-8822-82c7bf88d64b, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]



Log: 'Application' Date/Time: 13/09/2014 05:35:42
Type: Information Category: 0
Event: 1066 Source: Microsoft-Windows-Security-SPP
Initialization status for service objects. C:\WINDOWS\system32\sppwinob.dll, msft:spp/windowsfunctionality/agent/7.0, 0x00000000, 0x00000000
C:\WINDOWS\system32\sppobjs.dll, msft:rm/algorithm/inherited/1.0, 0x00000000, 0x00000000
C:\WINDOWS\system32\sppobjs.dll, msft:rm/algorithm/phone/1.0, 0x00000000, 0x00000000
C:\WINDOWS\system32\sppobjs.dll, msft:rm/algorithm/pkey/detect, 0x00000000, 0x00000000
C:\WINDOWS\system32\sppobjs.dll, msft:spp/ActionScheduler/1.0, 0x00000000, 0x00000000
C:\WINDOWS\system32\sppobjs.dll, msft:spp/TaskScheduler/1.0, 0x00000000, 0x00000000
C:\WINDOWS\system32\sppobjs.dll, msft:spp/statecollector/pkey, 0x00000000, 0x00000000
C:\WINDOWS\system32\sppobjs.dll, msft:spp/volume/services/kms/1.0, 0x00000000, 0x00000000
C:\WINDOWS\system32\sppobjs.dll, msft:spp/volume/services/kms/activationinfo/1.0, 0x00000000, 0x00000000


Log: 'Application' Date/Time: 13/09/2014 05:35:38
Type: Information Category: 0
Event: 900 Source: Microsoft-Windows-Security-SPP
The Software Protection service is starting. Parameters:<none>

Log: 'Application' Date/Time: 13/09/2014 05:35:37
Type: Information Category: 0
Event: 0 Source: LMS
LMS started

Log: 'Application' Date/Time: 13/09/2014 05:35:34
Type: Information Category: 0
Event: 0 Source: Intel(R) ME Service
The event description cannot be found.

Log: 'Application' Date/Time: 13/09/2014 05:35:34
Type: Information Category: 0
Event: 0 Source: Intel(R) ME Service
The event description cannot be found.

Log: 'Application' Date/Time: 13/09/2014 05:35:32
Type: Information Category: 0
Event: 7303 Source: IAStorDataMgrSvc
Started event manager
Started event manager

Log: 'Application' Date/Time: 13/09/2014 05:35:32
Type: Information Category: 0
Event: 0 Source: IAStorDataMgrSvc
Service started successfully.

Log: 'Application' Date/Time: 13/09/2014 05:35:26
Type: Information Category: 0
Event: 0 Source: BTHSSecurityMgr
The event description cannot be found.

Log: 'Application' Date/Time: 13/09/2014 05:35:26
Type: Information Category: 0
Event: 0 Source: gupdate
The event description cannot be found.

Log: 'Application' Date/Time: 13/09/2014 05:35:25
Type: Information Category: 0
Event: 0 Source: Bluetooth OBEX Service
The event description cannot be found.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 13/09/2014 05:35:21
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.

Log: 'Application' Date/Time: 13/09/2014 04:38:17
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.

Log: 'Application' Date/Time: 12/09/2014 04:55:12
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.

Log: 'Application' Date/Time: 12/09/2014 01:58:06
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.

Log: 'Application' Date/Time: 11/09/2014 21:18:28
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.

Log: 'Application' Date/Time: 11/09/2014 19:17:34
Type: Warning Category: 0
Event: 8303 Source: Microsoft-Windows-System-Restore
Scoping unsuccessful for shadowcopy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4 with error 0x80070057.

Log: 'Application' Date/Time: 11/09/2014 17:17:38
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.

Log: 'Application' Date/Time: 11/09/2014 16:33:56
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.

Log: 'Application' Date/Time: 11/09/2014 16:26:29
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.

Log: 'Application' Date/Time: 11/09/2014 16:15:37
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.

Log: 'Application' Date/Time: 11/09/2014 15:15:02
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\explorer.exe' (pid 1980) cannot be restarted - Application SID does not match Conductor SID..

Log: 'Application' Date/Time: 11/09/2014 15:14:56
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\explorer.exe' (pid 1980) cannot be restarted - Application SID does not match Conductor SID..

Log: 'Application' Date/Time: 07/09/2014 16:40:12
Type: Warning Category: 7
Event: 507 Source: ESENT
LiveComm (3284) C:\Users\Verde\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\5485950f90b47e44\120712-0049\: A request to read from the file "C:\Users\Verde\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\5485950f90b47e44\120712-0049\DBStore\livecomm.edb" at offset 4931584 (0x00000000004b4000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (31 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Log: 'Application' Date/Time: 02/09/2014 17:14:29
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.

Log: 'Application' Date/Time: 02/09/2014 14:40:26
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\explorer.exe' (pid 1452) cannot be restarted - Application SID does not match Conductor SID..

Log: 'Application' Date/Time: 02/09/2014 14:40:26
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files (x86)\AVG\AVG2014\avgui.exe' (pid 4964) cannot be restarted - Application SID does not match Conductor SID..

Log: 'Application' Date/Time: 31/08/2014 16:39:50
Type: Warning Category: 7
Event: 507 Source: ESENT
LiveComm (8128) C:\Users\Verde\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\5485950f90b47e44\120712-0049\: A request to read from the file "C:\Users\Verde\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\5485950f90b47e44\120712-0049\DBStore\livecomm.edb" at offset 1499136 (0x000000000016e000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (24 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Log: 'Application' Date/Time: 28/08/2014 18:07:11
Type: Warning Category: 7
Event: 509 Source: ESENT
LiveComm (3516) C:\Users\Verde\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\5485950f90b47e44\120712-0049\: A request to read from the file "C:\Users\Verde\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\5485950f90b47e44\120712-0049\DBStore\livecomm.edb" at offset 4939776 (0x00000000004b6000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (26 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 2 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Log: 'Application' Date/Time: 28/08/2014 18:07:10
Type: Warning Category: 7
Event: 507 Source: ESENT
LiveComm (3516) C:\Users\Verde\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\5485950f90b47e44\120712-0049\: A request to read from the file "C:\Users\Verde\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\5485950f90b47e44\120712-0049\DBStore\livecomm.edb" at offset 4931584 (0x00000000004b4000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (16 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Log: 'Application' Date/Time: 26/08/2014 04:10:56
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 11/09/2014 21:14:50
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/09/2014 16:30:46
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/09/2014 16:10:28
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: 26/08/2014 04:08:09
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: 19/08/2014 15:47:47
Type: Critical Category: 64
Event: 10115 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device GT-I9300 (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device 5 more times in its own process.  Please contact the device manufacturer for more information about this problem.

Log: 'System' Date/Time: 19/08/2014 15:47:47
Type: Critical Category: 64
Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.

Log: 'System' Date/Time: 19/08/2014 15:46:47
Type: Critical Category: 64
Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device Light Sensor (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process.  Please contact the device manufacturer for more information about this problem.

Log: 'System' Date/Time: 19/08/2014 15:46:47
Type: Critical Category: 64
Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device GT-I9300 (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process.  Please contact the device manufacturer for more information about this problem.

Log: 'System' Date/Time: 19/08/2014 15:46:47
Type: Critical Category: 64
Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.

Log: 'System' Date/Time: 09/08/2014 03:51:28
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 03:08:34
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 17:43:33
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: 18/07/2014 14:49:08
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/07/2014 21:13:29
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: 03/07/2014 22:56:42
Type: Critical Category: 64
Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device Light Sensor (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process.  Please contact the device manufacturer for more information about this problem.

Log: 'System' Date/Time: 03/07/2014 22:56:42
Type: Critical Category: 64
Event: 10116 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device GT-I9300 (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process.  Please contact the device manufacturer for more information about this problem.

Log: 'System' Date/Time: 03/07/2014 22:56:42
Type: Critical Category: 64
Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.

Log: 'System' Date/Time: 26/06/2014 18:21:35
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: 24/06/2014 16:30:08
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: 23/06/2014 20:57:57
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: 13/09/2014 05:57:21
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Network List Service service terminated with the following error:  The specified procedure could not be found.

Log: 'System' Date/Time: 13/09/2014 05:57:21
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 13/09/2014 05:55:21
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Network List Service service terminated with the following error:  The specified procedure could not be found.

Log: 'System' Date/Time: 13/09/2014 05:55:21
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 13/09/2014 05:54:18
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Audio service terminated with the following error:  The endpoint is a duplicate.

Log: 'System' Date/Time: 13/09/2014 05:53:21
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Network List Service service terminated with the following error:  The specified procedure could not be found.

Log: 'System' Date/Time: 13/09/2014 05:53:21
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 13/09/2014 05:51:21
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Network List Service service terminated with the following error:  The specified procedure could not be found.

Log: 'System' Date/Time: 13/09/2014 05:51:21
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 13/09/2014 05:49:21
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Network List Service service terminated with the following error:  The specified procedure could not be found.

Log: 'System' Date/Time: 13/09/2014 05:49:21
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 13/09/2014 05:47:21
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Network List Service service terminated with the following error:  The specified procedure could not be found.

Log: 'System' Date/Time: 13/09/2014 05:47:21
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 13/09/2014 05:45:21
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Network List Service service terminated with the following error:  The specified procedure could not be found.

Log: 'System' Date/Time: 13/09/2014 05:45:21
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 13/09/2014 05:43:21
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Network List Service service terminated with the following error:  The specified procedure could not be found.

Log: 'System' Date/Time: 13/09/2014 05:43:21
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 13/09/2014 05:41:21
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Network List Service service terminated with the following error:  The specified procedure could not be found.

Log: 'System' Date/Time: 13/09/2014 05:41:21
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 13/09/2014 05:39:21
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Network List Service service terminated with the following error:  The specified procedure could not be found.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 13/09/2014 05:51:30
Type: Information Category: 0
Event: 1074 Source: User32
The process C:\WINDOWS\Explorer.EXE (GUAJOLOTEVERDE) has initiated the power off of computer GUAJOLOTEVERDE on behalf of user guajoloteverde\Verde for the following reason: Other (Unplanned)  Reason Code: 0x0  Shutdown Type: power off  Comment: 

Log: 'System' Date/Time: 13/09/2014 05:51:19
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:49:59
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:49:56
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:49:40
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:49:36
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:47:40
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:47:30
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:46:17
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:46:14
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:45:46
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:45:36
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:45:14
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:45:10
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:44:53
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:44:43
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:43:31
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:43:26
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:40:26
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

Log: 'System' Date/Time: 13/09/2014 05:40:23
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Program Files (x86)\ASUS\ASUS Smart Gesture\AsTPCenter\x64\AsusTPCenter.exe (process ID:4940) reset policy scheme from {DF011ED9-9131-49B9-8090-46963CFB65CE} to {DF011ED9-9131-49B9-8090-46963CFB65CE}

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 13/09/2014 05:52:06
Type: Warning Category: 0
Event: 1073 Source: User32
The attempt by user GUAJOLOTEVERDE\Verde to restart/shutdown computer GUAJOLOTEVERDE failed

Log: 'System' Date/Time: 13/09/2014 05:36:14
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name 4.zhaowenxian.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 13/09/2014 05:34:00
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

Log: 'System' Date/Time: 13/09/2014 05:34:00
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

Log: 'System' Date/Time: 13/09/2014 05:34:00
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

Log: 'System' Date/Time: 13/09/2014 05:34:00
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

Log: 'System' Date/Time: 13/09/2014 05:32:43
Type: Warning Category: 0
Event: 264 Source: Win32k
A multi-touch device reported inconsistent contact information.

Log: 'System' Date/Time: 13/09/2014 05:32:23
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device ACPI\ACPI0008\2&daba3ff&2.

Log: 'System' Date/Time: 13/09/2014 05:31:44
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped.  Module Path: C:\WINDOWS\System32\IWMSSvc.dll 

Log: 'System' Date/Time: 13/09/2014 04:37:15
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

Log: 'System' Date/Time: 13/09/2014 04:37:15
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

Log: 'System' Date/Time: 13/09/2014 04:37:15
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

Log: 'System' Date/Time: 13/09/2014 04:37:15
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

Log: 'System' Date/Time: 13/09/2014 04:36:03
Type: Warning Category: 0
Event: 264 Source: Win32k
A multi-touch device reported inconsistent contact information.

Log: 'System' Date/Time: 13/09/2014 04:35:45
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device ACPI\ACPI0008\2&daba3ff&2.

Log: 'System' Date/Time: 13/09/2014 04:35:03
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped.  Module Path: C:\WINDOWS\System32\IWMSSvc.dll 

Log: 'System' Date/Time: 13/09/2014 04:30:33
Type: Warning Category: 0
Event: 258 Source: Win32k
A pointer device reported a bad angular logical range.

Log: 'System' Date/Time: 13/09/2014 04:30:33
Type: Warning Category: 0
Event: 257 Source: Win32k
A pointer device reported a bad angular physical range.

Log: 'System' Date/Time: 13/09/2014 04:30:33
Type: Warning Category: 0
Event: 265 Source: Win32k
A pointer device did not report a valid unit of angular measurement.

Log: 'System' Date/Time: 13/09/2014 04:30:32
Type: Warning Category: 0
Event: 258 Source: Win32k
A pointer device reported a bad angular logical range.

 

[Verde]

More info. I also ran Malawarebytes (came back clean) but whenever I try to shut the computer down the following happens:

 

[Go The Power]

Do you have issues with your computer randomly turning off? There is a lot of these errors.

[B][COLOR="#FF0000"]Log: 'System' Date/Time: 11/09/2014 21:14:50
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.[/COLOR][/B]

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

 

[Verde]

I've had it shut down on me a few times in the past. The most recent entries are of the second kind you mention on the link: me pressing down on the power button. The restarting and shutting down were taking far longer than they usually did (hangs of minutes when it takes less than 30 seconds).

Still all of the original issues raised at the beginning of this thread remain. The audio service cannot start and it is still due to the same endpoint error.

How do I proceed?

 

[Verde]

I couldn't get SFC /SCANNOW to run, so I ran SFCFix again, without the script, here is the log of that:

SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-09-13 10:10:35.309
Not using a script file.




AutoAnalysis::
FIXED: Performed DISM repair on file Amd64\CNBJ2530.DPB of version 6.3.9600.16384.



SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     -1
   CBS & SFC total unimportant corruption count:  0
   CBS & SFC total fixed corruption count:        1
   SURT total detected corruption count:          0
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2014-09-13 11:46:13.364
----------------------EOF-----------------------

 

[Verde]

I also ran a chkdsk /r but it has not restored neither the ability tu run sfc /scannow, nor the Audio controller problem

 

[Go The Power]

Something doesn't look quite right in the Event log.

License Information (Windows 8)

1. Right click on the
   
   button
2. Click on Command prompt =>
3. Inside the Command Prompt windows copy and paste the following command
   licensingdiag.exe -report "%userprofile%\Desktop\report.txt" -log "%userprofile%\Desktop\repfiles.cab"
   
4. Once finished please go to your desktop -> You will see two files report.txt and repfiles.cab -> Please select both files and add them into a zip file
5. Upload this zip file to your next reply

 

[Verde]

I couldn't wait any longer for the Audio Service issue to get resolved (I use a lot of the audio properties on my computer) so I had to go a different route and applied a system refresh on my machine. It has been painful, but I got the audio back up. Currently having to install all my software again, but at least the random issues seem to have stopped. I do want to thank you for your time and patience and I will be back should anything else go wrong (i.e. Windows update is still working on the last 34 updates it needs to be up to date)

 

[Go The Power]

A lot of the time this approach is the quickest and most effective, I normally don't recommend it unless its a last resort.

Let me know if you have any more issues with the updates.