Audio app errors

[pdsnickles]

I was getting this message every day regarding this app:

"IDT PC Audio has stoped working and was closed."

Then, in Event viewer under System logs: " The Audio Service service terminated unexpectedly. It has done this 1 time(s)."

The Event Log Online help refers me here: Event ID 7034 — Service Stop Operations which makes no sense to me, maybe someone can explain it... Seems like a hodge podge of stuff that does not relate...

And under Event viewer Application logs it says:

"Faulting application STacSV64.exe, version 1.0.6017.1, time stamp 0x4835e75e, faulting module msvcrt.dll, version 7.0.6001.18000, time stamp 0x4791ad6b, exception code 0xc0000005, fault offset 0x0000000000003237, process id 0x1e8, application start time 0x01c9c2a5a3dac46a."


Dell tech support just loaded the latest driver for this to try and fix it but that apparently did no good.


Now: The question I am asking is:
Is my turning off IDT PC Audio in the Configuration Startup apps utility CAUSING this error??? Because I don't want it in my system tray (I have enough other things there, and I"m a believer in not having things run at startup that you don't really need)...so I stopped it from loading. But that should not cause these errors, right?

My "Reliability" score is down to 6.4 because I get this error every day...

So 1) What is causing the error?
and 2) Can I turn IDT PC audio off in StartUp apps without causing this error?

Here are 4 jpg's of my error files:

 

[H2SO4]

So 1) What is causing the error?

Those data are insufficient for analysis which would result in a practical solution. The STacSV64.exe process crashed while attempting to use the 64-bit C-runtime library msvcrt.dll whose timestamp (on your machine) is "Sat, 19 Jan 2008" - correct for SP1. Based on that 0x3237 offset within the msvcrt.dll binary, the function being called at the time was being asked to compare the first 'n' characters of two strings (wcsncmp):

0:008> ln msvcrt+0x3237
(000007fe`fe923228) msvcrt!wcsncmp+0x8

At least one of the string pointers which was supplied was obviously bogus. On a code level, the cause is insufficient error checking within the STacSV64 application. An attempt is made to compare two strings, only somewhere the app's logic fails - something unanticipated happened - and the string comparison function was fed invalid data, which in turn caused the crash.

Only the people who wrote STacSV64 could give you a complete "fix" (they would add more error-checking in this location in their code), although it's possible that by updating other componentry you might avoid the conditions which lead to a crash.

and 2) Can I turn IDT PC audio off in StartUp apps without causing this error?

Dunno. That would depend on where the app's losing its marbles

Have you tested what happens if you leave "IDT PC audio" to run?

 

[pdsnickles]

Thanks for the info, though I didn't understand most of it!
Yeah, I guess my next step is to enable it again for Startup and see if that solves the problem.
When I had Creative Audio on my last computer I could stop it from loading in the system tray but maybe I can't with this built in audio thing...
I'll try enabling it again.
Thanks.

 

[pdsnickles]

Weird... I re-enabled it in my Startup Configuration panel, and no longer get the errors... AND it disappeared from my System Tray which is what I wanted, but it had no options for that... but now it has disappeared from there on its own. (???) Oh well, if it works, it works.

 

[H2SO4]

Weird... I re-enabled it in my Startup Configuration panel, and no longer get the errors... AND it disappeared from my System Tray which is what I wanted, but it had no options for that... but now it has disappeared from there on its own. (???) Oh well, if it works, it works.

Glad to hear it's working the way you wanted now.

 

[pdsnickles]

NOTE:
I found this old post in searching for an answer and I want to make it clear that the above did NOT solve my problems, it only appeared to solve them for a short time.

Actually, my IDT Audio Device has caused Application Errors and automatically closed ever since I've had my DELL XPS430.

Their Tech Support (and Windows) keep saying to install the new driver but I have and that does not solve the problem.

The error messages and closing of IDT Device do NOT affect my audio (curiously - ??) so I have let it go but today I got a Blue Screen on Start Up (1st time) and I have to suspect this Audio Device as the culprit because it's been crashing a lot lately.

What do you think the chances are that I can force Dell to give me a new (different) Audio Device to replace this one since I can document that this one has given me problems almost since Day 1?

Or, does anyone know of a fix?