BSOD with only POE

Wow, I just personally got a BSOD with portcls.sys message. I was simply standing in an area, and the game instantly BSOD'd upon hitting F12 to take a Steam Screenshot.

I played the Beta up to level 30 character but was waiting for the full release to avoid bugs! Ironic since this is my second day playing the full release. The only issues I had during the beta were crashes relating to .ogg files, which I believe GGG did fix at some point.

I understand that GGG claims it is a Creative driver problem, but like everyone else, I play about 300 other PC games and have NEVER had a BSOD for literally years, literally.

Assuming Creative is to blame, then the solution is GGG needs to make a workaround, like not using certain driver calls or scripts or the .ogg files that they claimed had issues before. I find it dubious that pretty much all other PC developers can avoid this Creative issue except GGG...

My system:

Intel i5 2500k CPU
GeForce 680
Creative X-Fi Titanium (using XFTI_PCDRVBETA_US_2_17_0008C.exe driver package)

I will update to the new 2.17.0009 Creative driver, although that is mostly a Windows 8 fix package I believe. I doubt updating will fix the issue.

Anyway, thanks for the great free game, even if it cause BSODs, which is pretty much the most egregious offense possible.

"

Brumbek wrote:

Wow, I just personally got a BSOD with portcls.sys message. I was simply standing in an area, the game instantly BSOD'd upon hitting F12 to take a Steam Screenshot.

I played the Beta up to level 30 character but was waiting for the full release to avoid bugs! This is my second day playing the full release.

I understand that GGG claims it is a Creative driver problem, but like everyone else, I play about 300 other PC games and have NEVER had a BSOD for literally years, literally.

I'm trying to avoid raging, but assuming Creative is to blame, then the solution is GGG needs to make a workaround, like not using certain driver calls or scripts or the .ogg files that they claimed had issues before.

My system:

Intel i5 2500k CPU
GeForce 680
Creative X-Fi Titanium (using XFTI_PCDRVBETA_US_2_17_0008C.exe driver package)

I will update to the new 2.17.0009 Creative driver, although that is mostly a Windows 8 fix package I believe. I doubt updating will fix the issue.

Anyway, thanks for the great free game, even if it cause BSODs, which is pretty much the most egregious offense possible.

129,000 hits on google for that particular card

https://www.google.co.uk/search?q=Creative+X-Fi+Titanium+BSOD

It's something that creative excel at is getting BSOD's

"

lagwin1980 wrote:

129,000 hits on google for that particular card

https://www.google.co.uk/search?q=Creative+X-Fi+Titanium+BSOD

It's something that creative excel at is getting BSOD's

Your post serves no purpose and you already posted that previously. Please stop being a blind apologist for this issue. The bottom line is ONLY POE gives me BSODs. I literally have 300 other Steam games and none BSOD. Please think about this logically.

By the way, posting Google results means nothing. Search "Path of Exile BSOD". 40,000 results.

Anyway, there is no reason to blindly defend GGG on this point. I promise you other players will HATE POE for causing a BSOD. It is in everyone's interest for GGG to fix this problem, even if the problem originates with bad drivers. Wise developers work around bad drivers, as evidently all other developers have done with the X-Fi...

"

Brumbek wrote:

"

lagwin1980 wrote:

129,000 hits on google for that particular card

https://www.google.co.uk/search?q=Creative+X-Fi+Titanium+BSOD

It's something that creative excel at is getting BSOD's

Your post serves no purpose and you already posted that previously. Please stop being a blind apologist for this issue. The bottom line is ONLY POE gives me BSODs. I literally have 300 other Steam games and none BSOD. Please think about this logically.

By the way, posting Google results means nothing. Search "Path of Exile BSOD". 40,000 results.

Anyway, there is no reason to blindly defend GGG on this point. I promise you other players will HATE POE for causing a BSOD. It is in everyone's interest for GGG to fix this problem, even if the problem originates with bad drivers. Wise developers work around bad drivers, as evidently all other developers have done with the X-Fi...

And yours adds nothing either, it's not a problem with the game its a problem with
Creative...they have added a workaround and that was -swa.
So please don't prattle on about how blind i am...i've got eyes and sense enough to see where the problem lies when a quick google search shows you what it does...in almost all the cases people need to wait until creative fix it with a new driver update.

Hmm...I have hundreds of games that work fine with my X-Fi. Only POE causes BSODs. Others are reporting the same thing on this thread. All my other games work fine. All of them. Only POE causes BSODs.

These are the facts. Period.

For now I will use "--softwareaudio" launch option and hope this works.

Let me say one final time, despite over-enthusiastic forum fanboys, it is crazy that I have to resort to software audio to avoid BSODs.

Did I mention literally every other PC game I've played in the last 5 years with my X-Fi has worked and never resulted in a BSOD?

Lastly, @lagwin1980, no need to respond. Let the facts speak for themselves.

Got 2 BSOD with PoE today also.

Was my first blue screen after several years. I dont even remember the last one.

And may it be because of the drivers of my creative sound card, since i only get a blue screen with PoE, it's up to GGG to fix it.

Anyway, will use the --swa switch, but GGG needs to get this fixed.

@lagwin1980 it's something GGG needs to fix, not someone else. If i have this problem ONLY with PoE, then the solution needs to be delivered by GGG, and not Creative. Cant be that hard, or otherwise i (and others) would have this problem with other games also. Thats not the case. I know, you like this game but you should stop to defend it like it's your mother or something else :)

I have to disagree on this topic. Surely, I don't like having BSOD either - but it's not JUST problem of GGG.

The Creative is doing a lame job with drivers for years, and neglecting whole generations of customers - audigy 1, 2 and 4, X, etc.

They basically made cards working with XP only, which was the only OS at the time, and never bother to make even vista/win7 versions right. I had problems with drivers since switching from XP, and (due to not so small ego and consequently, stubbornness, when comes to fixing such issues, did... well, say everything - yes, kxdrivers, yes, other-drivers, goes on and on and on about specific card functions not wanting to bother people with)

Anyhow, OS and software *should* use hardware through driver, and driver in question produce lags or BSOD even when playing music (solved later) and numerous other occasions.

That is the reason I would recommend everyone to go to Creative site, and complain THERE. Far from truth is that PoE is *only* software having trouble with their drivers - I've paid my card 85eur, and expect support for it at least for next revision of OS

For rather overpriced product of obviously too rich and arrogant hardware company, I expect support from THEM, not a small, self-supporting company, having just made their first launch.

Audigy problem, on the other hand, exist for years.

[all of this I said there already]

I'm having this issue as well. PCIe Titanium Fatality Pro card on Windows 8.1.

And while I understand that it isn't GGG's fault, it's still an issue with their product for many users. I will play with the -swa switch in the mean time, but it really would be nice of them to get this licked. So yet another vote from a user for them to keep putting time into this issue.

Thanks.

Well I had this issue with my Creative sound card, and I just disable my audio device and when I play POE only use USB Headset. Cheers! I hope this helps others.

"

sabin1001 wrote:

I'm having this issue as well. PCIe Titanium Fatality Pro card on Windows 8.1.

And while I understand that it isn't GGG's fault, it's still an issue with their product for many users. I will play with the -swa switch in the mean time, but it really would be nice of them to get this licked. So yet another vote from a user for them to keep putting time into this issue.

Thanks.

Yep - me too. In fact I reported this issue back in early 2012 or late 2011 during the beta. Obviously no solution yet given it's still BSOD after >18 months and 1.0 launch.