JetAudio Media Center Causes BSoD on startup!

[SilentMage]

I recently downloaded the latest version of JetAudio VX from the jetaudio website (7.0.2). After attempting to run the Media Center for the first time, I get the BSoD with a "BAD_POOL_CALLER" error!

I looked up what this meant and I found this definition: "A kernel-mode process or driver incorrectly attempted to perform memory operations. Typically, a faulty driver or buggy software causes this."

I do not know what exactly the problem is, even with this description above, as everything else on my system works just fine and my much older version of JetAudio worked fine prior to this upgrade. Has anyone else ever encountered this error after installing version 7.0 of JetAudio?

Note that if I load one of the other JetAudio programs, such as Video Converter, I have no problems -- it seems that only when I load up Media Center does my system give the BSoD.

Thanks in Advance,

~SilentMage

EDIT - Here are my PC stats:
My Heavily-Modded Alienware Desktop (purchased in June 2003):
AMD Athlon 2700+
2.16Ghz (overclocked to 2.7Ghz)
1.5GB DDR-SDRAM (1GB x1, 256MB x2)
Nvidia GeForce 7800 GS
Microsoft Windows XP SP2
Creative SB Audigy 2
Logitec MX518 Performance Mouse

[doniago]

Did you try uninstalling and reinstalling?

[SilentMage]

Did you try uninstalling and reinstalling?
Yes, tried that twice, as well as rebooting manually after installing it (as some programs ask you to do that, although JetAudio didn't).

I still got the same error... any other suggestions? [confused]

[GSV3MiaC]

Update your Creative sound card drivers? Creative software causes me more hassle than any other 6 manufacturers combined.... to say nothing of the amount of rubbish laoded at startup.

Does the BSOD screen (or the system's event logs) not give any idea of which particular driver was at fault?

[SilentMage]

Update your Creative sound card drivers? Creative software causes me more hassle than any other 6 manufacturers combined.... to say nothing of the amount of rubbish laoded at startup.

Does the BSOD screen (or the system's event logs) not give any idea of which particular driver was at fault?
I updated my sound drivers (haven't done so in about a year, so I was definitely overdue), but unfortunately that didn't resolve the problem, which hasn't changed at all since my first post.

The BSoD screen doesn't give much information that is helpful -- I'm sure you've seen at least one on WinXP before. The only thing they provide is the error type (in this case, BAD_POOL_CALLER) followed by a bunch of things that could be done to resolve the problem, although none of the solutions given I don't think would help because they don't apply to the cause: I haven't installed any new hardware or hardware drivers in a while (exception for the sound drivers) and I'm pretty sure there's nothing wrong in my BIOS such that I'd have to disable something like shadowing (not sure what that means, but I'm sure it's not adversely affecting my PC).

I'm sorry if I'm not being too helpful... I haven't found any posts similar to this one so I take it my problem is a rare one. [sad]

~SilentMage