BSOD on Loading

[Snares]

Creative hasn't released a new driver in a very long time, and they one they did release is basically a patched Vista driver, it looks like.

It's a very poorly written driver, and many people are suggesting that it is the driver reference to 0x0 that causes many BSOD's. They took high quality hardware, but didn't take the time to hire competent software engineers. I think they should take a hint and give the job to Daniel-K.

[jaheenan77]

Don't think that has anything to do with Creative X-FI BSODs. You should probably start your own thread..

i think i fixed it, patch bf2

[Snares]

Guys, I'm fairly sure that your BSOD's will be fixed if you install Daniel K's X-Fi 2.0 support pack. He's a pretty reliable programmer, and Creative has allowed him to keep his post on his forum so I would trust his stuff.

I installed them and haven't had any BSOD's yet.

SB X-Fi Series Support Pack 2.0 (05/15/2009) - Creative Labs

[KomradePedrovsk]

Guys, I'm fairly sure that your BSOD's will be fixed if you install Daniel K's X-Fi 2.0 support pack. He's a pretty reliable programmer, and Creative has allowed him to keep his post on his forum so I would trust his stuff.

I installed them and haven't had any BSOD's yet.

SB X-Fi Series Support Pack 2.0 (05/15/2009) - Creative Labs

Tried those but it didn't help for me... even though it includes support for the Auzentech X-Fi Forte I have. I'll take it it's because he just included the default drivers for my card and just added the other stuff included in the pack... so I guess other people playing with X-Fi Forte cards are out of luck.

The ctoss2k.sys driver version for the Creative X-Fi in Daniel-K's pack are 6.0.1.1373 and for Auzentech X-Fi it's 6.0.1.1400. Too bad they aren't compatible with each other, but I'm waiting to see if there's someone who can make the older ctoss2k.sys compatible with it. Fall/Winter Pax Edtion sets. More set be added later. One Thread. - Page 11

[Snares]

Tried those but it didn't help for me... even though it includes support for the Auzentech X-Fi Forte I have. I'll take it it's because he just included the default drivers for my card and just added the other stuff included in the pack... so I guess other people playing with X-Fi Forte cards are out of luck.

The ctoss2k.sys driver version for the Creative X-Fi in Daniel-K's pack are 6.0.1.1373 and for Auzentech X-Fi it's 6.0.1.1400. Too bad they aren't compatible with each other, but I'm waiting to see if there's someone who can make the older ctoss2k.sys compatible with it. Fall/Winter Pax Edtion sets. More set be added later. One Thread. - Page 11

Yeah that's right This fix will only work with the SB X-Fi's. However, if you get a whitepaper on the Forte, you might be able to modify the inf's to work...not sure.

[K4on]

thx mate, that is the creative driver i was lookin for ! thx alot ! last two days i got 5 bluescreens >.> (pr only)

edit: installed it but 10 minutes ago i got another bsod >.>

[Comander]

Same problem resists with patch 0.9

[Pesticide]

make sure you play with audio on software setting, dont select the creative setting , its a clusterfuck of cracking and crashes and sound dissapearing.

[KomradePedrovsk]

make sure you play with audio on software setting, dont select the creative setting , its a clusterfuck of cracking and crashes and sound dissapearing.

Any mode (Hardware or Software) but Creative X-Fi loses 5.1 surround and I can't stand playing PR in 2.1 stereo, so unfortunately that is not an option...

ALchemy helps regaining 5.1 surround with Software or Hardware modes, but there was no Buffer/Duration combination I've tried that didn't give have major sound glitches or crackling.

By the way.. more and more people seem to have this issue lately. I take it it's because more people now have 64-bit OS's, specifically Win 7. Which, in combination with BF2 and Creative X-Fi, gives off these map loading BSODs...

[Pesticide]

the map loading is solely related to memory usage, independant of sound.

the creative drivers will work one day, mess up another, its random, its cause creative in its infinite wisdom decided to go against motherboard makers expressed wishes to not use so much bandwith or something. We will never see a fix for it. Its the creative hardware thats at fault.I swapped to software cause it drove me crazy and am even considering going back to my onboard realtek 5.1 sound.

[Revollucion]

Hi guys same problem here.X-Fi Fatality and WIN 7 64bit problem cause BSOD can not help just keep this thread alive with my post.I trayed Daniels pack but then my Creative Console Launcher doesnt work.I experimenting with lowerin some graphic options as well.

[KomradePedrovsk]

Seems like it's not just BF2, but UT3 as well. Check some of these threads... I'll try a couple of the suggested fixes there but not hoping much.

Win 7, X-Fi and OpenAL - Epic Games Forums
Possible solution for X-Fi and OpenAL related crashes - Epic Games Forums
Re: Creative claims no problems with UT3 and X-FI - Creative Labs

Most of the tricks seem to make it so the game uses DirectSound3D instead of OpenAL. So I guess only XP users will benefit from it.

Basically it will probably force BF2 to use Hardware mode instead of Creative X-Fi mode, which in Vista/7 OS's makes you lose 5.1 surround, since Microsoft in all their wisdom removed DirectSound support.

[sprint113]

Not sure if this is legit, but OpenAL 2.1 has been somewhat leaked, although not officially up on the OAL website.

OpenAL 2.1.0.0 now available - Creative Labs

Another thought is that with the recent beta driver test around Dec 2009 addressing audio problems in 4+GB systems, those may be related to our problem.

[Oddsodz]

Ok. Well I shall post here. I Have suffered this issue for a very long time. I Have just learned to live with it. Now I shall go out on a limb here and say it may not be the drivers at fault. But more like PR is at fault. And here is my reason why.

I Have had 2 Creative cards so far. The Audigy 2 ZS THX version and the X-Fi titanium. Both great cards. Now I use to play PR on WinXp_x64. And at the time I had 3 gigs of ram (2x 512mb sticks and 2x 1GB sticks). This was fine. But then I got 4 gigs (2x 2GB sticks) of ram and I lost 3D sound due to a driver issue (google it). So I got around that by updating to Win Vista. And everything was fine. PR ran great. I Was happy. Then there was a PR new release, Now I am guessing at the release number. I think it was somewhere around 0.7 but it was a long time ago. Now in this release there was a big fuss about new sounds. Not just sounds recorded for the mod. But a new way of making the sound effects work. Ways of making long range echoes and gun shot cracks to give the impression of long range sniper shots and so on. Now this is when I started to get the BSoD. It was in that release of PR and and has never been fixed. I have tried every fix in the book apart from one. None if it has worked out. the only way I think we can get around this is to go back to using WinXP (or WinXP_x64). But again, then there is the issue of if you have more than 3 gigs of ram. The drivers losese 3D sound. This is not to be confused with the normal 3gigs issues that WinXP has. For it is the same in WinXP_x64.

I Should have posted about this 2/3 years (has it really been that long?) ago. But I did not as I knew I would have been told. It's the drivers. When I have a feeling in my bones that it is not "just" the drivers, But PR sound coding also. I Would also like to add that upon quitting the mod. I Can not use my Creative Console to switch card modes. IE: switch from "GAME Mode" to "Entertainment Mode". It's like it's locked in place and the only way to unlock it is to restart the computer. I Bit of a pain but I have just learned to live with it as playing with 5.1 sound is just to important to lose (7.1 is even better but I don't have a 7.1 headset).

[LeChuckle]

only getting these BSODs after 0.9

[Oddsodz]

I Forgot to say that I can play vBF2 all day long with out a crash or BSoD. This is the main factor as to why I believe it is the PR Mod and not the drivers at fault here.

[sprint113]

Just a question.

Do you guys use CMSS when the BSOD happen? I unticked CMSS and haven't had a BSOD in a while.

[Oddsodz]

Just a question.

Do you guys use CMSS when the BSOD happen? I unticked CMSS and haven't had a BSOD in a while.

I Never use it. Not needed when you have 5.1 speakers/headset

[Spearhead]

Just want to add my new pain to this list. Also using Win7 + X-Fi and I tend to get those BSODs since 0.9 (never seen them before but on the other hand I didn't play that much PR on Win7 yet.

Using the standard Creative drivers from summer 09. Not sure which way I'll go from here. Putting the sound on hardware ruined my 5.1

[Jagular]

same from me
win7u x64 6gb x-fi tit fatality
only in PR in creative x-fi mode for sure