View Single Post
30 Nov 2009  
athanatos875

Windows 7 RTM Ultimate
 
 

Quote   Quote: Originally Posted by torrentg View Post
You're welcome.

Actually, symbols aren't even needed to see what happened with this one. Even debugging without symbols, you can still see the cause: ctaud2k.sys
and see what drivers you have running with the appropriate command.

If you'd like to know, my symbol command in the debugger is this so it connects to Microsoft and stores the cache of whatever it downloads to my HDD:
Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by athanatos875 View Post
Thank you for the quick reply! I will update those drivers. What symbols are you using to get this report?

Hi athan and welcome

He is either using windb (sybols downloaded from MS) or blue screen view.

either will do.

Kenn J++
I have windbg but I did not know about getting the symbols from online. That will save me from downloading several symbol packages if this happens again. I did a simple google search and I found that several people are having this issue with the Auzentech drivers (which use a modified Creative driver). There is a solution to this problem. Thank you for all of your help guys!
My System SpecsSystem Spec