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

The "-softwareaudio" did not fix the Bluescreen on Alt-Tab with my Soundblaster X-Fi Titanium. But the Regedit fix did work!

However later in the game i got another portctl.sys blue screen just playing regularly.
Had 2-3 blue screens yesterday, tried a few of the fixes but haven't played long enough to see if they worked really. Hopefully not an issue anymore because it is so annoying to have to open all my programs again.
this has fixed my issue for now will see after a day or two

edit: upon entering Dark Forest i still got a BSOD
Last edited by Choilicious on Jan 24, 2013, 1:26:26 PM
Hey, thanks so far for this fix. Will try it myself and report back afterwards.
Have fun playing, all of you :)
I've never had any BSOD issues with my X-Fi and PoE in the year that I've played it.

Course, it's the XtremeGamer, so it doesn't have XRAM.

Every day I'm glad I don't have problems with my sound card; but I always hate the fact that mine is PCI, possibly reducing performance (due to patent issues with PCI prefetching and it being removed from some boards). I still sit here wondering if switching to a PCI-E card will have any benefit at all.
I don't mean to sound rude, but I can't help the way people interpret my words.
Also facing these errors and they are obviously x-fi driver related.

this is a bugcheck analysis of a kernel memory dump of a PoE BSOD

"
BugCheck 50, {ffffffff80680000, 0, fffff8000309bb38, 5}

Unable to load image \SystemRoot\system32\drivers\ctoss2k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ctoss2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctoss2k.sys

Could not read faulting driver name
Probably caused by : ctoss2k.sys ( ctoss2k+5cea )

Followup: MachineOwner


The ctoss2k.sys is a Creative OS Services Driver.

I use the following audio devices:
Creative SB X-Fi XtremeGamer Fatal1ty Pro (Driverversion: 2.18.15(current))
Logitech G930 Headset

Other Detail:
Windows 7 Enterprise x64 SP1
Intel C2Duo E8400
4 GB RAM
Geforce GTX 560 Ti (Driverversion: 306.02)

In-detail analysis:

Spoiler
"
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffff80680000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000309bb38, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032af100
ffffffff80680000

FAULTING_IP:
nt!MmProbeAndLockPages+118
fffff800`0309bb38 410fb601 movzx eax,byte ptr [r9]

MM_INTERNAL_CODE: 5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: Client.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88016429480 -- (.trap 0xfffff88016429480)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000980 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000980 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000309bb38 rsp=fffff88016429610 rbp=fffff880164297b0
r8=fffffa8008e31030 r9=ffffffff80680000 r10=000000000000097f
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe nc
nt!MmProbeAndLockPages+0x118:
fffff800`0309bb38 410fb601 movzx eax,byte ptr [r9] ds:2d48:ffffffff`80680000=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800030268af to fffff8000307ffc0

STACK_TEXT:
fffff880`16429318 fffff800`030268af : 00000000`00000050 ffffffff`80680000 00000000`00000000 fffff880`16429480 : nt!KeBugCheckEx
fffff880`16429320 fffff800`0307e0ee : 00000000`00000000 ffffffff`80680000 00000000`00000000 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x437c1
fffff880`16429480 fffff800`0309bb38 : fffff880`08355cc0 00000000`000007ff fffffa80`0870b3b0 00000000`00000020 : nt!KiPageFault+0x16e
fffff880`16429610 fffff880`069b1cea : fffffa80`08e31000 00000000`00000000 00000000`00000002 ffffffff`80680000 : nt!MmProbeAndLockPages+0x118
fffff880`16429720 fffffa80`08e31000 : 00000000`00000000 00000000`00000002 ffffffff`80680000 00000000`000006a6 : ctoss2k+0x5cea
fffff880`16429728 00000000`00000000 : 00000000`00000002 ffffffff`80680000 00000000`000006a6 00000000`00000010 : 0xfffffa80`08e31000


STACK_COMMAND: kb

FOLLOWUP_IP:
ctoss2k+5cea
fffff880`069b1cea ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: ctoss2k+5cea

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ctoss2k

IMAGE_NAME: ctoss2k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4be16b4a

FAILURE_BUCKET_ID: X64_0x50_ctoss2k+5cea

BUCKET_ID: X64_0x50_ctoss2k+5cea

Followup: MachineOwner
---------
This didn't made any difference on a Audigy 2 zs card.
i solved that problem with using an USB-headset, editing the registry didnt help
FIXED!

this seems to have resolved my Xfi Titanium PCIE blue screen issue.

before alt+tab positive crash within 30 seconds.
also random crash at launcher.

all working beautifully...

thank you thank you thank you
Hey guys, for any one still having BSOD with their creative cards i noticed (before this fix) that i was getting more BSOD if there was any background non PoE sounds.
For example i would get a BSOD instantly as soon as some one would talk to me on steam.
Exit or disable the sounds on any instant messaging progams, don't play music in the background, don't voice chat, basicly disable anything that could possibly make a sound while you are playing PoE.
Also as you should know don't Alt Tab out of the game, and if you run the game through steam as a non steam game like i do don't use the overlay.


The regedit fix seems to have fixed the problem for me
I'm using a Titanium PCI-E card.

Report Forum Post

Report Account:

Report Type

Additional Info