BSOD Errors! NEED HELP :(

My system :

intel core2duo 2.4ghz
4gb 800 Mhz dd2 XMS2 Corsair
Asus p5nsli mobo
onboard sound
geforce 8800 GTS 640mb
550watt NZXT PSU
250gb WD2500JS

I keep getting frequent BSOD errors when I play graphic intensive games. It's not an overheating issue cause I have monitors up and its clearly far below the overheating marks. Ive checked my mobo/cpu/gpu temps and they are all fine.

Ive attached 5 dump files ( all today ) . Some reason I cant get the symbols path to set properly. If someone could open them and take alook it would be much appreciated.

What i can get :

MODULE_NAME: ks

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41107ef8

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ffffffe0

CURRENT_IRQL: 2

FAULTING_IP:
ks!KsRemoveIrpFromCancelableQueue+36
b923b435 8702 xchg eax,dword ptr [edx]

CUSTOMER_CRASH_COUNT: 6

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from a1f50821 to b923b435

STACK_TEXT:
a34f4c98 a1f50821 89c3b600 89c3b704 00000001 ks!KsRemoveIrpFromCancelableQueue+0x36
WARNING: Stack unwind information not available. Following frames may be wrong.
a34f4cc4 a1f63454 89c3b6d8 000000a2 a34f4d48 kmixer+0x821
a34f4d50 a1f51e9d 8a05ccd0 89f713b0 8a05cd88 kmixer+0x13454
a34f4d84 a1f522a7 0005ccd0 00000000 00000000 kmixer+0x1e9d
a34f4dac 805ce84c 8a05ccd0 00000000 00000000 kmixer+0x22a7
a34f4ddc 8054532e a1f521f0 8a05ccd0 00000000 nt!PsRemoveCreateThreadNotifyRoutine+0x214
00000000 00000000 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x72e


STACK_COMMAND: kb

FOLLOWUP_IP:
ks!KsRemoveIrpFromCancelableQueue+36
b923b435 8702 xchg eax,dword ptr [edx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ks!KsRemoveIrpFromCancelableQueue+36

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ks.sys

BUCKET_ID: WRONG_SYMBOLS

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

I'm trying to figure out just which hardware device is the issue. I know somethings wrong, but I need help to narrow it down.

Your mindumps point to the following:

wdmaud.sys - a core driver for Windows and is a process for MMSYSTEM/MIDI API mapping; sound card driver

Ventrilo.exe - a third party driver for the Ventrilo program that from what I can gather is a voice communication program

splitter.sys - Microsoft Kernel Audio Splitter

ks.sys - another core driver for Windows and Audio

See this link: http://support.microsoft.com/kb/920872

* You have audio issues; it could be Ventrilo is the culprit here.

Google ks.sys because Microsoft has info on that as a stand-alone.

Ok , checking into that now. Thanks alot ! will post updates!

Uninstalled previous card drivers, and disabled the card in bios (onboard). Installed a brand new X-FI Xtreme Gamer card w/ current drivers and still getting some BSOD's. Could you tell me if these are still sound issues?

if so, is there some way to know if the previous drivers were properly un-installed?

see attachments

Did you recently install anything?

ks.sys once, wdmaud.sys twice, and ntkrpamp.exe once.

I suggest googling the current driver for your audio card and see if there are known issues.

I uninstalled the drivers for the onboard card, but Im still seeing the control panel for it, and other things which leads to believe its still partially installed. I don't know if its messed up in the registry or not.

I have a brand new pci card installed w/ up to date drivers but Im still getting audio issues.

Makes me wonder if i need to zero out my drive to make sure theres nothing possibly left on it? ( really dont want to)

edit ** ran msconfig and noticed that it was still loading something w/ the old sound drivesr in the startup, so i took that out and will post an update **

recent crash, still audio? :(

One of those has crashed at IRQL 1c, and this is a strong sign of a hardware problem. The major cause is RAM then CPU.

You can try running Memtest (http://www.techspot.com/vb/topic62524.html), or a better test is to only run one stick of RAM at a time. Swap them over if it still crashes, or after a period of time where it hasn't crashed.

BugCheck 1000000A, {4, 1c, 1, 805017ea} <-- IRQL 1c
Probably caused by : ntkrpamp.exe ( nt!KiTimerExpiration+88 )