Teamspeak

markyb · 18 Aug 2006 at 13:34

What driver is the error pointing to? Is there a name displayed?

Could well be down to a USB Microphone that Teamspeak maybe using.
Have you have all the latest drivers for your sound card?

Vita · 18 Aug 2006 at 13:56

Doesn't refer to a name unfortunatley. Sound is onboard, and all drivers are updated. God knows, I'll try install again, reinstalled the motherboard drivers, see if that fix's the issue.

Thanks for your help.

EDIT: No luck, as soon as I open TS, computer reboots. Got this error report.

Error caused by a device driver

Thank you for sending an error report to Microsoft.

Error report summary

Error type : Windows stop error (A message appears on a blue screen with error code information)
Solution available? : No (see Next steps)
What does this error mean? : Windows has encountered an error from which it cannot recover and needs to restart
Cause : Unknown device driver
Computer symptoms : A message appears on a blue screen with error code information (for example: e.g. 0x0000001E, KMODE_EXCEPTION_NOT_HANDLED)
Additional steps for you to take : Important: Please continue to send error reports so analysts at Microsoft can study and try to correct the problem as quickly as possible

Information about this error

You received this message because a device driver installed on your computer caused the Windows operating system to stop unexpectedly. This type of error is referred to as a "stop error." A stop error requires you to restart your computer.

Next steps

We have analyzed your error report and at this time are unable to determine the exact cause of the error. However, Microsoft will continue to analyze this error report to try to determine the specific cause of the error. If we are able to find the cause and correct it, and you encounter the same problem, you will receive an updated response that includes instructions for resolving the problem.

L33 · 18 Aug 2006 at 14:35

Try temporarily disabling any antivirus software you may have installed, or adding the teamspeak directory/executable to the exclusion list. I'm guessing that teamspeak uses some sort of low-level driver to capture audio from the microphone? Maybe this could be causing the problem - your AV may think it is some sort of hijack attempt and stop the driver loading.

Vita · 19 Aug 2006 at 10:13

Think it was Windows Firewall Blocking it, sorted that out, now computer doesn't reboot. Thanks l33