Xiansue BSOD portcls.sys X-Fi@Ultra High

[Jorgee!]

Hi, I get BSOD every time I press Deploy after selecting weapon in all maps i've tried. It didn't happen any time in the beta.

What could it be? Too much sounds loaded in the ram? :S

[DrProctor]

I'm getting the same problem.

[Jevski]

Ive started to have this problem too in recent weeks, Ive tried to disable onboard soundcard, no luck

[p477y]

Having the same issue. Bluescreen with "portcls.sys" when pressing "deploy", directly after mapload. BSOD only occurs when using X-FI@Ultra High. Before PR 1.0x I had no issues playing @Ultra settings. This is NOT the random bluescreen with X-FI cards from earlier threads (this has been fixed). Game simply does not work on ultra-settings anymore.

Hardware: X-FI Titanium PCIe
OS: Win7 64 SP1

Drivers: All (currently 6.0.240.8 of feb2014, tried everything, also PAX 2013, 2014, ... editions) - none work

Also tried fresh windows re-install -> same issue. As of PR 1.x I simply can?t play on Ultra mode anymore.

- tried the OpenAL file exchange and other stuff too. Either it didn?t work or PR Launcher couldn?t verify the files anymore... It has to be something with the sound engine changes introduced with 1.0, maybe PR Mumble?

[JohnnyPissoff]

Jorgee, You are spot on about your ram but not; "too much sound loaded on Ram". Let me try and explain.

A BSOD = a memory dump. This happens most often in games when there's an incompatibility with drivers but it can also happen with Operating System/Program incompatibility. Or even two or more programs incompatible with one another (sound card/graphics card?) All that info is "dumped" into ram as a file called; (MEMORY.DMP). The reason that shit happens is to keep from further messing something up. So it ends the function and dumps the info for analyzing. Kind of makes the dread BSOD sound worthy....heh.

You can access the dump file itself and analyze the last entry/s that may have caused the dump. There are actually 3 types of dump files. And you will have to configure which one to access. Most PC's are configured to access the minidump located at: C:\\Windows\\Minidump That'll be the most pertinent info. Hopefully this is as far as you need to go. But if you need more information you can also configure for a Kernel dump or a complete dump by going to: Control Panel\System Properties\Startup and Recovery\ then click settings (or it might say depending on OS; "write debugging information") then chose your dump file options.

If it was indeed a windows driver issue just delete the bad windows driver, go to; Programs\windows update\check for updates. Windows will automatically update. If it was a vendor driver, delete the bad driver and update from the vendor. But chances are windows will at least update to a generic windows driver for the program if you chose to use windows update.

To p477y and to be specific as to thread title regarding portcls.sys, I used to do some audio engineering and have run into portcls.sys (port class systems) problems running midi devices. port.sys is basically one of many support .dll files for your audio driver package. The complication is it's broken into three groups; IMiniportWaveRT, IMiniportDMus, and IMiniportTopology interfaces. You would have to analyze all three. You did a reinstall of windows so you're most likely right, it's probably an isolated issue with program incompatibility (mumble?). Or maybe check Microsoft Support for a hot fix if it is an OS issue. I used a hotfix for WinXP for port.sys once and it worked out. So be sure and check that out.

Because of your settings (ultra) issue, this a long shot but try setting your sound preference at BF2 sound options from x-fi to hardware sound. Maybe eliminating the need to load port.sys related drivers might at least get you back in game.