BSOD When Clicking On Video Links for WMP and a Couple Games...

I think is related to my sound card drivers, but this happens on both my
Sound Blaster X-Fi card and my mobo's onboard sound, so I'm wondering if
Vista x64 is responsible for this too.

Whenever I click on a link that brings up WMP, it wil give me a BSOD and
reboot the computer. The same thing happens when I go to play Battlefield 2
and Battlefield 2142. If I go to Device Manager and disable the sound
completely, I no BSOD's from BF2142 or BF2 and I can click on as many online
videos that I want to and it doesn't give me a blue screen.

It has to be related to sound card drivers somehow, but what I don't
understand is why it affects both my onboard sound and my X-Fi card?
Here are my system specs:
Core 2 Quad Q6600, Asus P5B-E mobo, 4GB of Corsair PC5400 XMS DDR2 RAM,
GeForce 8800 GTX, Sound Blaster X-Fi XtremeGamer Fatal1ty sound card, Corsair
HX620 PSU. I'm also dual booting with WinXP Pro w/SP2 and Windows Vista HP
64-bit.

Other than those two things, Vista is running great, but it's really
bothering me that I get these BSOD's with WMP and those two games. Sure
BF2142 says that it's only been tested with 32-bit OS's but I know the game
works with some people and like I said, I can get it to work fine if I
disable the sound completely. Also, in XP, everything works perfect with no
problems whatsoever so this only occurs in Vista x64.

I have all the latest patches to the games (other games work fine BTW) and I
have the latest BIOS to my mobo and everything else is up to day. I'm not
overclocking anything either. I'd greatly appreciate any input anyone has to
say.

Someone on the Creative forums mentioned that the latest X-Fi drivers
creates an IRQ conflict and I've tried earlier drivers and they do the same
thing; however, when I first install the drivers, I can sometimes load BF2142
completely and actually play. If I exit the game and try to come back
though, it crashes. Thing is, if it's a driver problem with the X-Fi card,
then why does it still occur with my onboard sound which has nothing to do
with Creative?

Kevin wrote :
> I think is related to my sound card drivers, but this happens on both
> my Sound Blaster X-Fi card and my mobo's onboard sound, so I'm
> wondering if Vista x64 is responsible for this too.
>
> Whenever I click on a link that brings up WMP, it wil give me a BSOD
> and reboot the computer. The same thing happens when I go to play
> Battlefield 2 and Battlefield 2142. If I go to Device Manager and
> disable the sound completely, I no BSOD's from BF2142 or BF2 and I
> can click on as many online videos that I want to and it doesn't
> give me a blue screen.
>
> It has to be related to sound card drivers somehow, but what I don't
> understand is why it affects both my onboard sound and my X-Fi card?
> Here are my system specs:
> Core 2 Quad Q6600, Asus P5B-E mobo, 4GB of Corsair PC5400 XMS DDR2
> RAM, GeForce 8800 GTX, Sound Blaster X-Fi XtremeGamer Fatal1ty sound
> card, Corsair HX620 PSU. I'm also dual booting with WinXP Pro w/SP2
> and Windows Vista HP 64-bit.
>
> Other than those two things, Vista is running great, but it's really
> bothering me that I get these BSOD's with WMP and those two games.
> Sure BF2142 says that it's only been tested with 32-bit OS's but I
> know the game works with some people and like I said, I can get it
> to work fine if I disable the sound completely. Also, in XP,
> everything works perfect with no problems whatsoever so this only
> occurs in Vista x64.
>
> I have all the latest patches to the games (other games work fine
> BTW) and I have the latest BIOS to my mobo and everything else is up
> to day. I'm not overclocking anything either. I'd greatly
> appreciate any input anyone has to say.
>
> Someone on the Creative forums mentioned that the latest X-Fi drivers
> creates an IRQ conflict and I've tried earlier drivers and they do
> the same thing; however, when I first install the drivers, I can
> sometimes load BF2142 completely and actually play. If I exit the
> game and try to come back though, it crashes. Thing is, if it's a
> driver problem with the X-Fi card, then why does it still occur with
> my onboard sound which has nothing to do with Creative?

In order to check this properly, you have to completely uninstall the
X-FI drivers, if you just disable this device, the drivers are still
loaded.

--
Mamamegs.

I reject your reality and substitute my own.
(Adam Savage)

www.vistabits.nl

MSN:
_*mamamegs@gmail.com*_

I've done that, to no avail and they are still uninstalled. I've currently
also got the onboard sound disabled in the BIOS so it doesn't show up in
Vista at all.

I just had another BSOD occur from something else for the first time. I was
chatting with a friend on Windows Live Messenger and a BSOD occurred...from
the sound I'm sure. So, now it's not just limited to WMP and certain games!
The weird thing is, I've been talking with him on Messenger for around 30
minutes or so and it just decided to conflict. It makes it difficult to
diagnose the problem!

I wish I knew whether this was Vista or the X-Fi driver, but then I've got a
feeling that the onboard sound driver would have done the exact same thing.



"Mamamegs" wrote:


> In order to check this properly, you have to completely uninstall the
> X-FI drivers, if you just disable this device, the drivers are still
> loaded.
>
> --
> Mamamegs.
>
> I reject your reality and substitute my own.
> (Adam Savage)
>
> www.vistabits.nl
>
> MSN:
> _*mamamegs@gmail.com*_
>
>
>

Kevin wrote on 4-5-2007 :
> I've done that, to no avail and they are still uninstalled. I've
> currently also got the onboard sound disabled in the BIOS so it
> doesn't show up in Vista at all.
>
> I just had another BSOD occur from something else for the first time.
> I was chatting with a friend on Windows Live Messenger and a BSOD
> occurred...from the sound I'm sure. So, now it's not just limited
> to WMP and certain games! The weird thing is, I've been talking
> with him on Messenger for around 30 minutes or so and it just
> decided to conflict. It makes it difficult to diagnose the problem!
>
> I wish I knew whether this was Vista or the X-Fi driver, but then
> I've got a feeling that the onboard sound driver would have done the
> exact same thing.

Can you give the error code for the stop error? (eg stop 0x0000007e)

--
Mamamegs.

I reject your reality and substitute my own.
(Adam Savage)

www.vistabits.nl

MSN:
_*mamamegs@gmail.com*_

Yup, it just did it again as I was going to say I would. It happened when my
friend responded to me and the tone Messenger makes when someone responds.
Anyway, here's the code. Stop: 0X00000124

Hope you can tell me something because Vista says it's either my CPU, RAM,
PSU...ironically it doesn't mention sound...then again, I don't think it's
actually a hardware problem, because like I said before....if it were, this
would happen in XP too and it doesn't and it would happen in Vista when the
sound is disabled and it doesn't!

"Mamamegs" wrote:


> Can you give the error code for the stop error? (eg stop 0x0000007e)
>
> --
> Mamamegs.
>
> I reject your reality and substitute my own.
> (Adam Savage)
>
> www.vistabits.nl
>
> MSN:
> _*mamamegs@gmail.com*_
>
>
>

From what I read in this discussion, there could be a solution in using
the lastest NVIDIA drivers (158.18) although it doesn't seem to work
for everyone.
http://forums.microsoft.com/TechNet/...PostID=1551415


Kevin wrote :
> Yup, it just did it again as I was going to say I would. It happened
> when my friend responded to me and the tone Messenger makes when
> someone responds. Anyway, here's the code. Stop: 0X00000124
>
> Hope you can tell me something because Vista says it's either my CPU,
> RAM, PSU...ironically it doesn't mention sound...then again, I don't
> think it's actually a hardware problem, because like I said
> before....if it were, this would happen in XP too and it doesn't and
> it would happen in Vista when the sound is disabled and it doesn't!
>
> "Mamamegs" wrote:
>
>
>> Can you give the error code for the stop error? (eg stop 0x0000007e)
>>

--
Mamamegs.

I reject your reality and substitute my own.
(Adam Savage)

www.vistabits.nl

MSN:
_*mamamegs@gmail.com*_

Thanx, I found the solution. I found the same page as well. When you asked
me for the stop code, I thought to myself, why don't I look for that
too..DUH! Anyway, it wasn't the driver (in my case) but it's the 3rd one
down from the bottom on the first page.

I disabled the C1E in the BIOS. It has something to do with regulating the
CPU voltage when in hibernation mode. How this has anything to do with the
sound is beyond me but it must interfere with it somehow. Anyway I can't say
that it's fixed for certain, but all the previous things I've done before
like playing WMP and BF2142 and Windows Messenger that would cause it to
crash no longer does. I've not had a BSOD since I've disabled the C1E in the
BIOS! So far, but I've played BF2142 over and over and so far anyway, it
hasn't given me a blue screen.

Thanks again because had I not looked it up myself, you would have turned me
on to the right page. Either way you helped me by reminding me to look up
the STOP code myself....thanks a bunch!

Do you happen to have any problems that I might be able to help you out with?



"Mamamegs" wrote:

> From what I read in this discussion, there could be a solution in using
> the lastest NVIDIA drivers (158.18) although it doesn't seem to work
> for everyone.
> http://forums.microsoft.com/TechNet/...PostID=1551415
>
>
>>

Kevin used his keyboard to write :
> Thanx, I found the solution. I found the same page as well. When
> you asked me for the stop code, I thought to myself, why don't I
> look for that too..DUH! Anyway, it wasn't the driver (in my case)
> but it's the 3rd one down from the bottom on the first page.
>
> I disabled the C1E in the BIOS. It has something to do with
> regulating the CPU voltage when in hibernation mode. How this has
> anything to do with the sound is beyond me but it must interfere
> with it somehow. Anyway I can't say that it's fixed for certain,
> but all the previous things I've done before like playing WMP and
> BF2142 and Windows Messenger that would cause it to crash no longer
> does. I've not had a BSOD since I've disabled the C1E in the BIOS!
> So far, but I've played BF2142 over and over and so far anyway, it
> hasn't given me a blue screen.
>
> Thanks again because had I not looked it up myself, you would have
> turned me on to the right page. Either way you helped me by
> reminding me to look up the STOP code myself....thanks a bunch!
>
> Do you happen to have any problems that I might be able to help you
> out with?
>

Just glad to help! I'll add this solution to my site.

--
Mamamegs.

I reject your reality and substitute my own.
(Adam Savage)

www.vistabits.nl

MSN:
_*mamamegs@gmail.com*_

Great to hear. I noticed this didn't work for other people though, so it may
only work for users who have Core 2 Duo or Core 2 Quad's like myself.

I'm still a little unsure of why this works or rather why voltage regulation
would interfere with Vista's sound. You'd think that it wouldn't matter if
the sound was enabled or disabled and it would just throw up a BSOD randomly.
I like to understand why a fix works....that is how this corrects something
and I don't understand this.

If a BSOD occurred when Vista goes into hibernation, then that makes sense
but I don't see how the sound subsystem has anything to do with voltage
regulation?



"Mamamegs" wrote:

> Kevin used his keyboard to write :
> > Thanx, I found the solution. I found the same page as well. When
> > you asked me for the stop code, I thought to myself, why don't I
> > look for that too..DUH! Anyway, it wasn't the driver (in my case)
> > but it's the 3rd one down from the bottom on the first page.
> >
> > I disabled the C1E in the BIOS. It has something to do with
> > regulating the CPU voltage when in hibernation mode. How this has
> > anything to do with the sound is beyond me but it must interfere
> > with it somehow. Anyway I can't say that it's fixed for certain,
> > but all the previous things I've done before like playing WMP and
> > BF2142 and Windows Messenger that would cause it to crash no longer
> > does. I've not had a BSOD since I've disabled the C1E in the BIOS!
> > So far, but I've played BF2142 over and over and so far anyway, it
> > hasn't given me a blue screen.
> >
> > Thanks again because had I not looked it up myself, you would have
> > turned me on to the right page. Either way you helped me by
> > reminding me to look up the STOP code myself....thanks a bunch!
> >
> > Do you happen to have any problems that I might be able to help you
> > out with?
> >
>
> Just glad to help! I'll add this solution to my site.
>
> --
> Mamamegs.
>
> I reject your reality and substitute my own.
> (Adam Savage)
>
> www.vistabits.nl
>
> MSN:
> _*mamamegs@gmail.com*_
>
>
>