PoE 1 PC servers are restarting in: .
They should be back up in approximately .PoE 1 Xbox servers are restarting in: .
They should be back up in approximately .PoE 1 Sony servers are restarting in: .
They should be back up in approximately .Blue Screen of Death with some sound cards
|
Yesterday 1st Bsod.Today another one.Unfortunately is 1st game in many years who do this.
Spec: Windows 7 64bit,CPU Core2 E6850,4gb ram,soundcard Audigy 4,video card 9600GT.Drivers are updated. LE: i'll put that switch "--softwareaudio" and see what happend. Last edited by santer#2232 on Jan 30, 2013, 9:34:31 AM
|
|
|
Tried the fix. Didnt work. Still getting BSoD.
Creative sound card. |
|
|
Hi everybody,
after successfully resolving a problem for my hardware, I wanted to let you know. I also experienced BSODs while playing PoE and have also observed buggy behavior of the windows sound mixer after a reboot. I couldn't believe that PoE would be responsible for the BSOD since an application should only be able to crash itself in a decent operating system. But you never know with MS. My first guess was a hardware problem with my sound card, an Auzentech X-Fi Forte 7.1, which is based on a chip from Creative Labs btw. After switching to onboard sound, the problems disappeared. Searching for a cause, I stumbled over the following driver update from my sound card vendor Auzentech, which is supposed to resolve the following issue: "Driver fix for BSOD encountered with 64-bit O/Ses when playing OpenAL games". see http://www.auzentech.com/site/download/updates.php#xfiforte After installing the new driver, I have played several hours without any problems now. Many thanks to GGG for building such a great game. You are doing an awesome job here. |
|
|
I use creative sound card and have no problem
|
|
|
I'm using a Creative X-fi platinum and been having random BSODs with this game for awhile, tried --softwareaudio and was able to go yesterday without one but had one today when I reached the dark pyramid end and got the BSOD the moment I used the Apex item.
Going to just try playing with the Realtek onboard sound for this game I suppose. |
|
|
Only been playing a couple of days and didn't have any BSOD until this afternoon after the latest patch. I'm only in Act 1. For the record, this is the first time in a few years that I've experienced a BSOD. Playing anything from Alpha Protocol, COD series, BF series, Fallout, Skyrim, X-COM, Dragon's Age, ME series, Civ, TL, The Witcher 1 & 2, Diablo, Sup Com, Borderlands, Farcry; hell..you name it, almost 500 games via Steam alone. I'll give the tag a shot, but here's hoping it'll be fixed by release.
Few quick specs: Win7 x64 Ultimate X-FI xtrememusic Asus M3N-HT Deluxe Phenom II X4 965 BE 8GB 1066 Geil DDR2 EVGA gtx570 SC Last edited by Circlestrafe#0494 on Jan 30, 2013, 5:37:34 PM
|
|
" so x-fi users could potentialy than have a fix from moded auzentech drivers(which are far better than creative ones anyway as they solve plethora of problems with hissing and crackling that ocurs on x-fi with creative drivers) unfortunately that doesnt solve the problems for audigy users Last edited by grimyhr#0988 on Jan 31, 2013, 6:12:02 AM
|
|
|
Used --softwareaudio and haven't had another BSOD...yet. Keeping fingers crossed, really don't want to enable onboard audio for just one single solitary game!
Last edited by Circlestrafe#0494 on Jan 31, 2013, 4:25:17 PM
|
|
|
Hey guys
i figure out how to stop blue Screens permanently! i read about it here: AllAround.cc PoE blueScreen WorkAround 1st: get new Drivers form January 2013 you see it cause they have a A on end of filename! 2nd: get Alchemy 2rd: install both and restart your System. 4th: Use Alchemy to get Path of Exile running with OpenAL! enjoy the game with out any BSOD! with best +DS_DV+ PS: for detailed instruction look at my Forum at: AllAround.cc |
|
|
BSOD on my X-Fi Titanium as well. I could disable it, but why should I? Either it gets fixed or lose potential patrons for your game. Either way, I already uninstalled it and might check up on it later, or maybe not. It's been an issue since last year, so there should be no reason for you to not fix this major bug.
|
|
