Bluescreen on zoning
|
Thanks a lot!
Yea,... the onboard sound is really crappy... and since I'm also listening a lot of music on my computer, it's also not really an option :\ Then I can just as well take a restart every now and then, instead of crawling on the floor plugging the headphones into different jacks... :D |
|
|
Did the opensource drivers help?
|
|
|
I tried these drivers as well about a week ago.
I almost cried "WHAT HAVE I DONE!?"... I had no idea how these things work, suddenly I had about 7 playback devices, only one of them was my Headphones/Loudspeakers. Since my headset needs a certain amount of bass boost, I tried to figure out how to do that with these drivers... but I just stumbled upon a DSP editor, which was way too complex for me. I changed back to the creative drivers... maybe these alternative drivers work without bluescreen, but I have no idea how I can use them properly... :( |
|
|
By the way, it seems to get worse... is it possible that these crashes are damaging the OS or even the hardware permanently?
When I go from the Forest Encampment to the Dark Forest by foot, it crashes almost every time after I have been in the dark forest for a time span between a few seconds and a few minutes. Please guys, try to fix this until open beta... the game is getting almost unplayable :\ As I mentioned before, these crashes do never happen with any other games, so there must be a workaround or fix for this. |
|
|
My opinion, your confusing 3 different issues and assuming they are the same issue.
Issues: 1) Creative HARDWARE (not just Sound) 2) Crash into town in Act 2 - was Very common - with no time denominator. 3) E_outofmemry - appears after 1hour on most systems, more ram, longer, no sound, longer, less tasks, longer... 1) --nosound works but then you still get #2 and #3 2) Delete or Rename the Content.ggpk file and redownload )approx. 30-45minutes) Corrects corruption not found by the PACKCHECK 3) More Ram, more time for GGG to find and fix the issue. Now, this is just a personal thought as well. Defrag the system using a GOOD DEFRAGGER (check out iobit / Easeus / pirioform) Turn off the Paging File, Defrag the system, Turn on the Paging File 2048 min and max, clean the Registry. Never rule out an infected system or bad hardware either. OS: WinXP SP2 32bit
CPU: Athlon 64 X2 3800+ Ram : 4GB Kingston PC2-6400 5-5-5-18 Mobo: Abit KN9-Sli (NF570-Sli chipset with Realtek Audio) GPU: ATI HD4670 1GB HD: Maxtor 20GB - OS - Seagate 500GB - Games / Storage / PageFile Network / ISP: Wired / Cox Cable |
|
|
And I'm thinking you are wrong. No offense.
When I use --nosound, the game isn't crashing at all. I never got an e_outofmemore Error whatsoever. It doesn't even crash in Act 2 when I go back to the Encampment. So --nosound really solves the crashes, but... obviously... I don't have any sound. Which is okay for the moment, but it should really be fixed until open beta. |
|
|
So, then I have to ask....did you try the CREATIVE BETA DRIVERS from CREATIVE? This has fixed a few players issues.
Did you read the THREAD about Creative Sound and XRAM and the CREATIVE REGISTRY fix? OS: WinXP SP2 32bit CPU: Athlon 64 X2 3800+ Ram : 4GB Kingston PC2-6400 5-5-5-18 Mobo: Abit KN9-Sli (NF570-Sli chipset with Realtek Audio) GPU: ATI HD4670 1GB HD: Maxtor 20GB - OS - Seagate 500GB - Games / Storage / PageFile Network / ISP: Wired / Cox Cable Last edited by Greybear1andonly#1583 on Aug 18, 2012, 5:47:12 PM
|
|
|
I will refer first to your second question...
I have an Audigy 2 ZS, NOT a X-Fi or Titanium. The Audigy 2 ZS does not have XRAM, therefore the Registry fix is useless, since it can't be applied here. I even tried looking in the registry if there is a similar entry, but there isn't. To the first question: The beta drivers are from 1st October 2009, the normal drivers however are from 9th April 2010. But - I will test them also... just to make sure... I think I even tested them before, but I'm not sure anymore. ... but seriously... what's your deal? Do you want to help or do you want to chase ghosts? At some point you need to accept that there is something wrong - the mistake may not be on the the GGG developters side - but there is certainly a way how they can avoid this. Because it doesn't happen on other games and it is partly recreatable. And --nosound is avoiding it, which narrows it down. |
|
|
KX project
Spoiler
" It is obvious that I am pissing you off so Ill end with this. What I was getting at is that the issue is the same as those with the X-FI cards. If the REGISTRY has the same entries, great. - This is a fix that goes back to 2008 according to one poster. The BETA drivers also helped other that obviously were using the latest drivers, so that shows it is most likely a DRIVER issue with the latest, so if the BETA is older maybe it was working then. So, if nothing else is working, the only resource to use presently is the --nosound. Lets hope that Creative or GGG figures out the final piece of the puzzle. OS: WinXP SP2 32bit
CPU: Athlon 64 X2 3800+ Ram : 4GB Kingston PC2-6400 5-5-5-18 Mobo: Abit KN9-Sli (NF570-Sli chipset with Realtek Audio) GPU: ATI HD4670 1GB HD: Maxtor 20GB - OS - Seagate 500GB - Games / Storage / PageFile Network / ISP: Wired / Cox Cable |
|
" I just read quite often that beta drivers did not help, but maybe I was mistaken, I'll try that later this day. I already downloaded them. You are not pissing me off, I really appreciate the help. But with a little background myself, I don't cope well with replies that suggest that my carefully manifested opinions are wrong ;) Oh shit, now I really sound arrogant... |
|
