audigy causing bsod in winXP (at least i think)

[dum]

my computer has given me a bsod 4 times since last friday. The first time was a problem with my video driver so i updated to the latest nvidia drivers. The last 3 times the dump info says the problem is with win32k.sys.

I checked the STOP code through the MS knowledge base and it matches a code for a problem with the audigy cards usually discovered when upgrading from win2k to winXP. They say the message is:

A "STOP: 0x1000008E In Emupia2k.sys" Error Message Appears After You Upgrade from Windows 2000

STOP: 0x1000008E (c0000005, f80ef98c, f02f3b94, 00000000)In EMUPIA2K.SYS

the message i'm getting is basically:

STOP: 0x1000008e (c0000005, bf85e524, f187f0f4, 00000000) in win32k.sys


I did not upgrade from win2k, I did a clean install with winXP Pro. I installed the audigy drivers for my platinum off the driver CD and then updated them with the update that Creative Asia just released the other day.

Am I right in assuming that this is a problem with my audigy?


EDIT: if it matters, my system specs are

amd thunderbird 1.33
abit KG7-RAID
1GB crucial PC2100
Leadtek GeForce 2 Pro
Audigy Platinum

 

[dum]

^

 

[NogginBoink]

There's really not enough information to tell.

Your machine crashed at address f187f0f4, which is in win32k.sys. However, just about every driver on your machine will make calls into win32k.sys, and if someone makes an API call with bad data, the OS will crash in win32k.sys.

Best test is to roll back the Audigy drivers and see if system becomes stable.