hello everyone... here's my BSOD minidump analysis... is the problem really as it claims (sysaudio.sys)?

i recently had to RMA my graphics card (GeForce 6800GT) and the card they sent to me was not new... i wouldn't be surprised if it was someone else's RMA'd card!

... so i'm wondering if it's really sysaudio.sys or if its the graphics card. i have been experiencing a lot of crashing out of programs (memory could not be accessed, or something like that) recently so it's not an isolated problem.

anyway, any help would be appreciated!

oh, and if it is sysaudio, how would i fix that?

here's my minidump:

//////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////////////////////////////

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini101106-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
*************************************************************************** *
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
*************************************************************************** *
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x80800000 PsLoadedModuleList = 0x8087c1a0
Debug session time: Wed Oct 11 19:07:41.938 2006 (GMT-7)
System Uptime: 11 days 3:36:05.777
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
........................................................................... .........................................................
Loading User Symbols
Loading unloaded module list
..................................................
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck C2, {40, 20000000, 80000000, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for sysaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for sysaudio.sys
*** WARNING: Unable to verify timestamp for ks.sys
*** ERROR: Module load completed but symbols could not be loaded for ks.sys
Probably caused by : sysaudio.sys ( sysaudio+4135 )

Followup: MachineOwner
---------

It could be, uninstall your audio and run the test again if the error goes then you know for sure thats the problem, trouble shooting is simply doing the obvious first then if that doesn't fix it go from there.