[hmp3]

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 06/12/2021 20:39:17

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 06/12/2021 17:14:17
Type: Error Category: 0
Event: 100 Source: RIM MDNS
804: ERROR: read_msg errno 0 (The operation completed successfully.)

Log: 'Application' Date/Time: 06/12/2021 17:14:17
Type: Error Category: 0
Event: 100 Source: RIM MDNS
ERROR: mDNSPlatformReadTCP - recv: 10053


Log: 'Application' Date/Time: 06/12/2021 15:55:35
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: wmiprvse.exe, version: 6.1.7601.17514, time stamp: 0x4ce79d42 Faulting module name: ntdll.dll, version: 6.1.7601.24545, time stamp: 0x5e0eb67f Exception code: 0xc0000374 Fault offset: 0x00000000000bf262 Faulting process id: 0x17e0 Faulting application start time: 0x01d7eab867819d71 Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: f2ad20a1-56ac-11ec-9c07-00e04c6b0b03

Log: 'Application' Date/Time: 06/12/2021 15:37:31
Type: Error Category: 0
Event: 100 Source: RIM MDNS
804: ERROR: read_msg errno 0 (The operation completed successfully.)

Log: 'Application' Date/Time: 06/12/2021 15:37:31
Type: Error Category: 0
Event: 100 Source: RIM MDNS
ERROR: mDNSPlatformReadTCP - recv: 10053


Log: 'Application' Date/Time: 06/12/2021 03:00:25
Type: Error Category: 0
Event: 0 Source: DragonLog
The event description cannot be found.

Log: 'Application' Date/Time: 06/12/2021 03:00:25
Type: Error Category: 0
Event: 0 Source: DragonLog
The event description cannot be found.

Log: 'Application' Date/Time: 06/12/2021 02:00:28
Type: Error Category: 0
Event: 0 Source: DragonLog
The event description cannot be found.

Log: 'Application' Date/Time: 06/12/2021 02:00:26
Type: Error Category: 0
Event: 0 Source: DragonLog
The event description cannot be found.

Log: 'Application' Date/Time: 06/12/2021 00:01:26
Type: Error Category: 0
Event: 0 Source: DragonLog
The event description cannot be found.

Log: 'Application' Date/Time: 06/12/2021 00:01:25
Type: Error Category: 0
Event: 0 Source: DragonLog
The event description cannot be found.

Log: 'Application' Date/Time: 05/12/2021 20:22:40
Type: Error Category: 0
Event: 100 Source: RIM MDNS
764: ERROR: read_msg errno 0 (The operation completed successfully.)

Log: 'Application' Date/Time: 05/12/2021 20:22:40
Type: Error Category: 0
Event: 100 Source: RIM MDNS
ERROR: mDNSPlatformReadTCP - recv: 10053


Log: 'Application' Date/Time: 05/12/2021 17:40:11
Type: Error Category: 0
Event: 100 Source: RIM MDNS
652: ERROR: read_msg errno 0 (The operation completed successfully.)

Log: 'Application' Date/Time: 05/12/2021 17:40:11
Type: Error Category: 0
Event: 100 Source: RIM MDNS
ERROR: mDNSPlatformReadTCP - recv: 10053


Log: 'Application' Date/Time: 05/12/2021 17:40:11
Type: Error Category: 0
Event: 100 Source: RIM MDNS
612: ERROR: read_msg errno 0 (The operation completed successfully.)

Log: 'Application' Date/Time: 05/12/2021 17:40:11
Type: Error Category: 0
Event: 100 Source: RIM MDNS
ERROR: mDNSPlatformReadTCP - recv: 10053


Log: 'Application' Date/Time: 05/12/2021 15:50:36
Type: Error Category: 0
Event: 100 Source: RIM MDNS
804: ERROR: read_msg errno 0 (The operation completed successfully.)

Log: 'Application' Date/Time: 05/12/2021 15:50:36
Type: Error Category: 0
Event: 100 Source: RIM MDNS
ERROR: mDNSPlatformReadTCP - recv: 10053


Log: 'Application' Date/Time: 05/12/2021 15:50:36
Type: Error Category: 0
Event: 100 Source: RIM MDNS
836: ERROR: read_msg errno 0 (The operation completed successfully.)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 06/12/2021 20:31:16
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 20:16:16
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 20:01:16
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 19:46:16
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 19:31:18
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 19:16:16
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 19:01:16
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 18:46:16
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 18:31:16
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 18:16:18
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 17:16:16
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 17:01:18
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 16:46:16
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 16:31:16
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 16:16:16
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 16:01:17
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 06/12/2021 15:47:00
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The SamsungMagicianSVC service terminated unexpectedly.  It has done this 1 time(s).

Log: 'System' Date/Time: 06/12/2021 15:46:31
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 47.

Log: 'System' Date/Time: 06/12/2021 15:46:15
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 47.

Log: 'System' Date/Time: 06/12/2021 15:46:15
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 47.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 06/12/2021 17:14:58
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name ledger.bt.co timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 06/12/2021 17:14:56
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name imap-mail.outlook.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 06/12/2021 17:14:22
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.Home timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 06/12/2021 16:53:28
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name 21.63.146.156.in-addr.arpa timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 06/12/2021 15:47:26
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.Home timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 06/12/2021 15:46:03
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Log: 'System' Date/Time: 06/12/2021 15:30:49
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name dns.msftncsi.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 06/12/2021 15:28:34
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Log: 'System' Date/Time: 06/12/2021 04:44:37
Type: Warning Category: 0
Event: 2 Source: HidBth
Bluetooth HID device (08:b7:38:13:7f:9c) either went out of range or became unresponsive.

Log: 'System' Date/Time: 06/12/2021 03:35:00
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.ethealing.nl timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 05/12/2021 21:21:34
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.Home timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 05/12/2021 20:47:50
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.Home timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 05/12/2021 20:22:45
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.Home timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 05/12/2021 20:19:28
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.Home timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 05/12/2021 20:19:26
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.Home timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 05/12/2021 20:19:25
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.Home timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 05/12/2021 18:09:25
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.Home timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 05/12/2021 18:09:20
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name prod-3-realtime-lb-840806869.us-east-1.elb.amazonaws.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 05/12/2021 18:06:52
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad.Home timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 05/12/2021 17:38:51
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name ipv6.aykutcevik.com timed out after none of the configured DNS servers responded.

 

[Advertisements]

Start, All Programs, Accessories then right click on Command Prompt and Run as Administrator.  Then type (with an Enter after each line).

sfc  /scannow

(This will check your critical system files. Does this finish without complaint?  IF it says it couldn't fix everything then:

Copy the next two lines:

findstr  /c:"[SR]"  \windows\logs\cbs\cbs.log  >  %UserProfile%\desktop\junk.txt
notepad %UserProfile%\desktop\junk.txt

Start, All Programs, Accessories, right click on Command Prompt and Run as Administrator, Continue.  Right click and Paste or Edit then Paste and the copied line should appear.
Hit Enter. Copy and paste the text from notepad or if it is too big, just attach the file.)

 

[RKinner]

Start, All Programs, Accessories then right click on Command Prompt and Run as Administrator.  Then type (with an Enter after each line).

sfc  /scannow

(This will check your critical system files. Does this finish without complaint?  IF it says it couldn't fix everything then:

Copy the next two lines:

findstr  /c:"[SR]"  \windows\logs\cbs\cbs.log  >  %UserProfile%\desktop\junk.txt
notepad %UserProfile%\desktop\junk.txt

Start, All Programs, Accessories, right click on Command Prompt and Run as Administrator, Continue.  Right click and Paste or Edit then Paste and the copied line should appear.
Hit Enter. Copy and paste the text from notepad or if it is too big, just attach the file.)

 

[hmp3]

No integrity viollations found.

[RKinner]

OK.  Doubt you can reinstall Windows Defender these days.  Perhaps you should let Comodo handle the anti-virus too.

 

Do the search Registry thing with FRST and let's see if we can fix that at least.

[hmp3]

I already reinstalled Comodo without AV and then disabled AV module.

[hmp3]

I don't want to stop using MSE as my AV if that's what you mean.

[RKinner]

OK.  Let's try
Windows Repair all in one

http://www.tweaking....all_in_one.html

Download the Portable version and save it.  Then right click on the file and Extract All.  Open the folder and find  Repair_Windows.exe then run it (right click and run as admin).

 

Jump to Repairs.  It's going to complain that you are not in Safe Mode but I've never found it necessary.  Up to you.

Make sure all of these are checked before hitting Start:

Items 1-12, 25 & 26.  (It won't hurt to do them all but takes longer to run)

 

Reboot when done.

 

See what Windows Defender says now.

[hmp3]

I saw too many 'file already in use' issues, so I restarted to safe mode, and the fixes happened without these errors in the ongoing logs. I restarted after the fixes.

Defender starts, but soon stops in the GUI. I click to start again and it freezes.

I want to use MSE as my AV, COMODO for Firewall and MBAM for anti-Malware. Don't use Defender. So it's getting in the way of our goal to fix the audio issue.

[RKinner]

OK.  Perhaps the file belongs to MSE instead.  Make sure you pause MSE and then run Latency Monitor.

[hmp3]

I disabled FireWire drivers and MSE, then saw MBAM as highest Hard Fault:

StatsV3

DriversV3

ProcessesV3

 

So I then disabled MBAM and ran again, to see no Processes with Hard Faults, so I only screenshotted Drivers:

StatsV4

DriversV4

[RKinner]

Looking at your drivers I see hal.dll as a major player.  On my PC hal.dll has no hits.  Wondering if your BIOS is out of date?

 

Speccy says you have:

BIOS

Brand American Megatrends Inc.

Version 1201

Date 24/02/10

 

If I got the right support site the latest version is 

1408

https://www.asus.com.../HelpDesk_BIOS/

 

Also go back into ShellExView and see if you can now delete the three entries that have no files.  If not run the FRST Search Registry as I asked you earlier.

[hmp3]

How would I install that zip file and can I make a backup of the BIOS driver first?

[hmp3]

[bleep]. Mouse Issue returned. MSE installed an update earlier today.

And in Event Viewer there are many occurrences of the same Sandboxie error:

"SBIE1406 Missing or invalid expansion for SystemDrive [C0000189]"

 

Correction:

It's not just 1406 errors, but 1412 also:

"SBIE1412 In text: [NAME OF SANDBOX] \??\%SystemDrive%\Sandbox\%USER%\%SANDBOX%"

Edited by hmp3, 09 December 2021 - 02:08 PM.

[RKinner]

To install BIOS use one of the three methods on

https://www.asus.com...ort/FAQ/1044348

 

No need to back up old BIOS.  Same Bios version is available on page with the latest BIOS.  You might prepare a USB with the old BIOS (Use 3rd method)  in case something goes wrong.

 

Did the problem happen before or after MSE update?

[hmp3]

After.

But I've deleted all content from all my sandboxes and the relapse hasn't occurred yet. I'm monitoring to see if that's the cause.

I'll look into the BIOS update later. Thanks