Restart Problems (exclusive to GW)

12 pages Page 2
Virtuoso
Virtuoso
Krytan Explorer
#21
The BSOD they are getting is in no way related to the installation of Guild Wars. I would not recommend reinstalling Guild Wars as I highly doubt that will fix the issue. Have either of you tried defragging yet?

-Virt
e
explode9339
Ascalonian Squire
#22
kmixer is a .sys file used by windows, its a system audio driver kernel, but I dont know if its corrputed or it isnt meshing with the game somehow

and i deff have nforce2 chipset which i just updated the chipset drivers from files on nvidia (but without removing the old drivers first, i just wrote over them... i dont know how to find and remove all of the old drivers.........)

I am going to take your advice and defrag right now

Ill keep ya updated...

-Ex
R
Rememdium
Ascalonian Squire
#23
I turned off the auto reboot, but the crash still reboots the comp automatically... I've yet to actually see a BSOD.

I don't think my mobo is a Nforce config, as my case is a Shuttle (and they use their own proprietary mobos)... but you guys can probably tell better than I could at this point.

Edit: Yeah, I defragged right after uninstalling/reinstalling my ATI drivers.
A
Apocalypz
Pre-Searing Cadet
#24
There seems to be a problem with the nv4_disp.dll file (nvidia driver). Log files show this is the file causing this problem for me. Have run out of memory (running 1 gig DDR)
I run EQ2 with no crashes or errors at all. I am also running a 256MB Asus v9570
video card. I am going to try the omega drivers mentioned in another thread, and I will let you know if they work
e
explode9339
Ascalonian Squire
#25
Can somebody tell me how to completely remove all of the old drivers (nforce chipset and/or audio only and/or video only).

Thanks...

Ex
c
cleric
Frost Gate Guardian
#26
ok i was just seeing if it was bsod- that is not happening i guess

if you need to see what mobo you have and what chipset get cpu-z it can tell you
Nall
Nall
Ascalonian Squire
#27
The problem exists for me and I don't have an Nforce chipset (MoBo is P4C800-E w/ Intel chipset). Turning off the sound also does nothing.


-Nall
R
Rememdium
Ascalonian Squire
#28
So I've tried everything in the thread so far, to no avail. New drivers, defragged HD, reinstalled GW, no OCd processor... I'm convinced it's gotta be something with the client, because (like the OP) only GW gives me this problem. Which is a shame, because I want to play so bad!

and a bump.
Discord
Discord
Ascalonian Squire
#29
There is a little known proggy that you might use to check driver probs. I used to get the kmixer.sys error.

If you go into Start> Run and type in verifier.exe it will give you options to check non-WHQL drivers. Rather than try to explain the whole process, the info is here:

http://support.microsoft.com/kb/q244617/

It's a bit technical. Maybe others on the board could simplify it a bit.
E
Emperor Mordred
Ascalonian Squire
#30
What motherboard do you guys use?
i had major problems during the E3 for everyone weekend last year

my pc started to turn off during playing GW.
windows was corrupt and my pc turned off after 5-15 minutes during everything i did, not only playing games.

i never thought GW had something to do with it, and i still think that.

i don't remember the exact name of my motherboard but it was an ASUS.

it stopped after i changed the power supply and motherboard, got a Gigabyte now, after 4 months of troubles (and a bad pc shop...).

never had problems again.
ph0ck
ph0ck
Ascalonian Squire
#31
Until yesterday GuildWars NEVER crashed. Then it started... getting different BSODs after 5-45 minutes playing. I first thought it was my gfx card (i was so sure of it i went and bought a new one), but the problem is still there. I'm pretty pissed now
E
Emperor Mordred
Ascalonian Squire
#32
how many Watt is your power supply?
i have 550 now since i had my problems
A
Apocalypz
Pre-Searing Cadet
#33
I have done everything i know to do, and am convinced it is a problem with the client, not my system. I ran this game in beta with no problems at all. Now at release is unplayable. If they don't fix this soon, I'll be taking my copy back.
B
Balthasar
Ascalonian Squire
#34
Kmixer.sys
PAGE_FAULT_IN_NONPAGED_AREA
***STOP:0x00000050 (0xE4EA000, 0X00000000, 0XF00E0ECF, 0X00EDEECF)
***MKINXER.SYS - ADDRESS F00EDECF base at F000F000, Datestamp 41107d32
Begining dump of physical memory
Physical dump complete

i have got the retail version and it comes up with this on the loading screen
V
VikingBlade
Pre-Searing Cadet
#35
Guys, make sure you use the support system, so they actually know about it. It seems the unstability has something to do with the client. Another machine was running fine on all the BWE until the last one, and now carried over into retail.
ph0ck
ph0ck
Ascalonian Squire
#36
I just reeinstalled windows. The System is now completely clean but for the Windows XP SP2 with all the newest drivers and Guild Wars. Hasn't helped though
Ender
Ender
Ascalonian Squire
#37
Are you using onboard sound or do you have a Sound Card? If so, what kind?
ph0ck
ph0ck
Ascalonian Squire
#38
I've got an Audigy Soundcard. I removed it before i re-installed windows and used onboard sound with the new installation... but that didn't help.

as for graphic cards i have tried a geforce TI 4400 and a 6600 GT, both with the same results.
R
Rememdium
Ascalonian Squire
#39
I'm using onboard sound, but the problem is definitely the client. I didn't get it in the first BWE that I was in, but in the last one and retail I crash all the time.
Nall
Nall
Ascalonian Squire
#40
Quote:
Originally Posted by VikingBlade
Guys, make sure you use the support system, so they actually know about it. It seems the unstability has something to do with the client. Another machine was running fine on all the BWE until the last one, and now carried over into retail.
I'm conversing back and forth using the support system now. So far they just keep telling me to recheck installations and reinstall drivers. I've yet to get another reply.

This is way frustrating to pay $50 for a game and get excited to play it only to be completely unable to for seeminly no reason. If its indeed a problem with the client, I sure hope they fix it soon.


-Nall