Conexant driver spam in event log

[Morten_Hapro]

Hello,

I've noticed the Conexant driver is logging a lot of junk to the event log.

This is probably debug related, just like the infamous keyloggers.

Is there any plans to release a new driver with this junk turned off, or is it possible to force it off using some hidden setting?

Among the messages, this set of information messages appears every 90 seconds;

CxService::AliveTimer_Elapsed

CxService::WakeUpApps +

CxService::WakeUpApps User Account = [REDACTED]

CxService::ProcessExist Process NameMicTray64, Process SessionId = 1, Process User Name = [REDACTED]

CxService::ProcessExist Process NameSmartAudio3, Process SessionId = 1, Process User Name = [REDACTED]

CxService::ProcessExist Process NameFLOW, Process SessionId = 1, Process User Name = [REDACTED]

FlowTray path = C:\Program Files\CONEXANT\Flow\FlowTray.exe

CxService::WakeUpApps - 

When I lock/unlock or sleep/wakeup/boot my computer, it will also log some messages as Warning:

CxService::OnSessionChange ChangeSessionId = 1, SessionId = 1

CxService::OnSessionChange ChangeSessionId = 1, SessionId = 0

CxProcess::ProcessStartByUserContext() = false

CxService::OnStart: launchedNgen = 0

CxService::OnStart: Ngen + 

CxService::OnShutdown

CxService::OnSessionChange ChangeSessionId = 1, SessionId = 1

CxService::OnPowerEvent PowerStatus = PowerStatusChange

And also seeing some error messages:

CxService::GetCurrentUserToken: WTSQueryUserToken error=1008

The error is one thing, but most of those warnings are clearly not actual warnings.

All of these messages get logged to a application/service log named CxAudioSvcLog

In my opinion, this events should only be logged if the user/admin has specifically turned them on, as they are obviously meant for debugging purposes.

I feel like this, along with the prior incidents with the keyloggers, bare witness to a lack of quality control at HP and/or Conexant and I sincerely hope this will be addressed in a better manner than it previously has been.

Regards, Morten

[Dragon-Fur]

@Morten_Hapro

It is not actually "spam" -- the log is set to include "informational" events by default.

Have you tried filtering the log?

Event Viewer > Applications and Services Logs

Click on CXAudioSvcLog

Under Actions (right side)

Create Custom View

Select "Event level" type(s)

Click OK to save

Enter a name for your Custom Log

Event Viewer > Applications and Services Logs

Click on CXAudioSvcLog

Under Actions (right side or along top ribbon)

Filter Current Log

Select desired "Event level" type(s)

Click OK to save

and / or

Event Viewer > Applications and Services Logs

Click on CXAudioSvcLog

Under Actions (right side)

Properties

Reduce the maximum log size to less than the current size as desired

Click OK to save

Not sure if this will achieve all that you desire -- it gives you options and a place to start looking at your Event Viewer setup(s).

Click Thumbs Up on a post to say Thank You!

Answered? Click post "Accept as Solution" to help others find it.

[Morten_Hapro]

Hello,

I disagree, this is spam.

The informational messages are one thing, but the warnings are what concern me the most.

The logged warnings should not be warnings, if logged at all, they should be informational.

Creating a custom view does not solve anything.

The spam warnings show up in administrative events, obscuring real warnings.

Regards, Morten

[Dragon-Fur]

@Morten_Hapro

If you like, create a custom view of multiple logs at the Applications and Services Log level.

Choose any number of logs / events you like - be aware of the warnings about resource (memory and processor) that shows up if you select more than ten logs.

Custom View filters, regardless of the number of logs monitored, still requires that you view that log (set) to manage / view the data.

I cannot engage with you on the question of the usefulness (or readability) of the logged information.

Commentary (not to be confused with actual fact)

Event Viewer is a Microsoft Windows software -- I would guess it is a tool directed at IT personnel as opposed to the home administrator.  Obscurity is a hallmark of many tools of this type.

What else to try?

• Ignore suggestions thus far provided for your consideration
• Ask your question at the Windows forum
• Use your favorite search engine for information on how to manage and filter logs in the Event Viewer

Thank you for participating in the HP Community Forum.

We are a world community of HP enthusiasts dedicated to supporting HP technology.

[PanurgyTech]

The problem is not Windows Event Viewer.  It is that developers and driver creators are sending informational event in such a way that they are being logged as warning or errors.  This causes the Administrative Events to fill up with useless informational messages instead of usefull errors or warning.  You cannot just create a new view or filter to block out all of these useless messages.  The driver here is not the only event creator that does this; I have seen it on many servers in addition to workstations.  

The Windows Event viewer has a built in view call the 'Administrative Events' which aggregates all warning and error so that users and techs can see and respons appropiately to the issues on the system they are reviewing.  There is no way to modify this view or create a new one that would filter out all the informational events being logged as errors or warnings.  It is up to the developers and driver writers to create software and drivers that log informational events correctly.