POSSIBLE BSOD Portcls fix for Creative X-fi's--NEEDS TESTING.

I have two folders in that directory:

PCI&VEN_1102&DEV_0005
PCI&VEN_1102&DEV_000B

Which folder do I want to make the change to? 000B already has a "DisableXRAMOnASIO" entry in it, 0005 has DoS3LockupFix entry.

Edit: Nvm ._. Just woke up, apparently I can't read yet. XD

Edit 2: Just got a BSOD after applying this change with restart. So apparently it doesnt work for everyone. The only thing that works for me so far is --nosound, which sucks. :(

As I haven't used this fix specifically as such I think it would be unnecessary to make a new thread about this. But it has some relevance to this fix.

I decided to try PoE out during the last open weekend and I got sick of the BSOD's quickly and researched for it to be PoE. Tried looking for fixes, didn't find any. However, I read that Daniel K's drivers could solve the problem and so I uninstalled the official drivers from Creative and the sodding system drive just decided to die on me.
The point of this short story is that I installed Daniel K's driver on a brand spanking new system with only drivers and windows updates on it and I have yet to get ANY BSOD's WITH sound, music disabled however.
What is relevant to this fix however is that I have found a variable in the registry editor that says the following.
DisableXRAMOnASIO
And that has a value set to 1, so I reckon it's disabled. I did not add this, I found it like this.

System setup below for reference. Do note that all drivers should be the latest, including BIOS.

Processor: AMD Phenom II 955BE @ 3.6GHz
Motherboard: ASUS M4A79 XTD EVO
Graphics: Two Radeon HD5850 cards with Crossfire enabled. 12.7 beta drivers
Memory: Corsair 8GB 1333 MHz
Sound card: Creative X-Fi XtremeGamer with Daniel K's SB X-Fi Series Support Pack 2.5

Tried the registry fix, rebooted.. Didn't stop the BSOD.

I did however get positive results using the beta drivers from creative (XFTI_PCDRVBETA_US_2_17_0008C.exe) mentioned here: http://www.pathofexile.com/forum/view-thread/23875/page/9 Seems to have stopped the BSOD.

I do however have an X-fi titanium, but it might be worth a shot if others can find beta drivers for their cards.

The link for the X-fi Titanium drivers is

http://support.creative.com/Downloads/searchdownloads.aspx?nOS=10&nlanguagelocale=1033&strstring=XFTI_PCDRVBETA_US_2_17_0008C.exe&showdetails=1

"

Jmodix wrote:

Tried the registry fix, rebooted.. Didn't stop the BSOD.

I did however get positive results using the beta drivers from creative (XFTI_PCDRVBETA_US_2_17_0008C.exe) mentioned here: http://www.pathofexile.com/forum/view-thread/23875/page/9 Seems to have stopped the BSOD.

I do however have an X-fi titanium, but it might be worth a shot if others can find beta drivers for their cards.

The link for the X-fi Titanium drivers is

http://support.creative.com/Downloads/searchdownloads.aspx?nOS=10&nlanguagelocale=1033&strstring=XFTI_PCDRVBETA_US_2_17_0008C.exe&showdetails=1

This so far has been working for me too, the registry fix did not.

X-Fi Fatal1ty Titanium Professional card.

"

Kjuors wrote:

As I haven't used this fix specifically as such I think it would be unnecessary to make a new thread about this. But it has some relevance to this fix.

I decided to try PoE out during the last open weekend and I got sick of the BSOD's quickly and researched for it to be PoE. Tried looking for fixes, didn't find any. However, I read that Daniel K's drivers could solve the problem and so I uninstalled the official drivers from Creative and the sodding system drive just decided to die on me.
The point of this short story is that I installed Daniel K's driver on a brand spanking new system with only drivers and windows updates on it and I have yet to get ANY BSOD's WITH sound, music disabled however.
What is relevant to this fix however is that I have found a variable in the registry editor that says the following.
DisableXRAMOnASIO
And that has a value set to 1, so I reckon it's disabled. I did not add this, I found it like this.

System setup below for reference. Do note that all drivers should be the latest, including BIOS.

Processor: AMD Phenom II 955BE @ 3.6GHz
Motherboard: ASUS M4A79 XTD EVO
Graphics: Two Radeon HD5850 cards with Crossfire enabled. 12.7 beta drivers
Memory: Corsair 8GB 1333 MHz
Sound card: Creative X-Fi XtremeGamer with Daniel K's SB X-Fi Series Support Pack 2.5

I'm running the exact same drivers as yourself on my X-Fi - XtremeGamer and my game will not actually start as long as I have my audio device set to my speakers rather than headset.

Any ideas? :(

Hi guys:
I wanted to say that this fix (which apparently isnt working for everyone, although it has worked for some) requires that you have the latest Titanium or older PCI (non titanium) beta drivers installed, and yes, the "DisableXRAM=1" goes in the same location as you found the ASIO field too.

I don't know if this works for the Titanium HD cards or not.

For those using Xtremegamer cards:
I thought those do NOT have xram on them? That might explain why you may be having issues, though I'm surprised the BSOD would happen on a non-xram card.

I personally have a Titanium Champion series (with the front panel), and disabling the Xram completely stopped all BSOD's in my case. So this should hopefully work for all people who have a Titanium professional, Titanium champion, FPS Fatal1ty, Professional or Elite pro, and similar models that have 4 MB or more of Xram on the card. It also fixed the BSOD when you run the game, alt tab, open windows explorer, and mouse click on any drive or folder.

Daniel K's drivers contained a newer build of the Creative drivers which allowed turning off the X-ram, which is why you noticed the ASIO field as well (All the creative x-fi drivers which were released after the huge UT3 complaints thread had the ASIO field).

If you still are getting the BSOD after trying this and have updated your drivers, if you happen to have Unreal Tournament 3 installed, run UT3 with the -log command and check the OpenAL text. If it says "EAX_RAM" then it means xram is being detected. If it does not, and it says XRAM:NO, then you successfully disabled the xram.

There may be other non x-ram issues causing BSOD's, though, and that I can't help with :( But Xram+OpenAL is an almost 100% chance of a BSOD happening.

Titanium HD user here, I don't have to much hope for beta driver fix. 3rd party drivers were a no go, willing to try this registry fix but with other titanium users saying no fix im skeptical. Really hope i can use sound in this game soon.

"

Jmodix wrote:

Tried the registry fix, rebooted.. Didn't stop the BSOD.

I did however get positive results using the beta drivers from creative (XFTI_PCDRVBETA_US_2_17_0008C.exe) mentioned here: http://www.pathofexile.com/forum/view-thread/23875/page/9 Seems to have stopped the BSOD.

I do however have an X-fi titanium, but it might be worth a shot if others can find beta drivers for their cards.

The link for the X-fi Titanium drivers is

http://support.creative.com/Downloads/searchdownloads.aspx?nOS=10&nlanguagelocale=1033&strstring=XFTI_PCDRVBETA_US_2_17_0008C.exe&showdetails=1

The beta drivers seem to be working for me, too. Played for several hours with no BSODs at all, which is a first. I had the XFTI_PCDRVBETA_US_2_17_0008B drivers before this. I did not attempt the registry hack. I have the X-Fi Titanium Fatal1ty Champion. (The one with the front break-out box.)

Can confirm registry fix does not work for Titanium HD

edit update: just bsod, was a good run....had sound for a few hours....sigh

"

Falkentyne wrote:

Hi guys:
I wanted to say that this fix (which apparently isnt working for everyone, although it has worked for some) requires that you have the latest Titanium or older PCI (non titanium) beta drivers installed

Just for giggles, I went back and checked the registry settings just now, this is after I cleaned the registry of the entries you mentioned and installed the beta drivers. Oddly enough the drivers have the same disable Xram entry already in place that you mentioned. Seems like creative knows something is buggy there.