Anyone running GW on Vista?
momo2oo2
Hi!
Seems I'm playing again after 4 months, a lot of issues got me away from GW.
But now I'm using a Vista Beta (exactly 5472 build). The game starts, runs pretty well on windowed and full screen mode, but after some minutes it totally hangs the computer.
I guess you'll think it doesn't make many sense asking for such help, but what I want to know is if someone with this build (or 5536) runs the game without hangs, to leave Vista out of the scenario.
Thanks a lot!
Seems I'm playing again after 4 months, a lot of issues got me away from GW.
But now I'm using a Vista Beta (exactly 5472 build). The game starts, runs pretty well on windowed and full screen mode, but after some minutes it totally hangs the computer.
I guess you'll think it doesn't make many sense asking for such help, but what I want to know is if someone with this build (or 5536) runs the game without hangs, to leave Vista out of the scenario.
Thanks a lot!
Alias_X
I'm not, but I know for sure that some people here are. Could it be that running Vista is too much of a drain on your computer, and Guild Wars on top of that is enough to make it crash?
scotty4168
GW runs perfectly on my labtop running Vista 5472. It must be something with your hardware configuration.
momo2oo2
Quote:
Originally Posted by Alias_X
I'm not, but I know for sure that some people here are. Could it be that running Vista is too much of a drain on your computer, and Guild Wars on top of that is enough to make it crash?
|
But I get random BSODs so I think I'll have to wait for another beta, or go back to XP.
levortex
i really think its just vista or that GW isn't ready for vista. What about the Vista RC1 isn't that a newer version
levortex
Microsoft Windows Vista Build 5552 RC1 32Bit newest version that i know
Omega X
Vista Beta 2 Ran GW perfectly. Any problems can be the result of one's hardware.
Dark Exige
I've been running Vista Beta 2 for some time with guild wars some times crashes when traveling via map or porting. But then in the last few days it has started to crash Vista completly just during normal play.
Will either revert to XP or upgrade to RC1 soon
Will either revert to XP or upgrade to RC1 soon
momo2oo2
Well the pre-RC1 5536 doesn't work, I tried to upgrade and fresh install but neither work.
I'll try to get the 5552 RC1 and see. Maybe I install it in my raid as primary OS.
Thanks everyone
I'll try to get the 5552 RC1 and see. Maybe I install it in my raid as primary OS.
Thanks everyone
Numa Pompilius
Quote:
Originally Posted by Dark Exige
But then in the last few days it has started to crash Vista completly just during normal play.
|
If you've not changed drivers in the last few days, it'll be overheating. Check if the heatsinks on your CPU or graphics card or chipset have become clogged with dust, or if any fans have stopped working.
It'd make me sad if it's the drivers, as I had hoped Microsoft with Vista had reversed the silly decision they made with XP to run drivers at ring zero (and thereby able to crash the system).
Ghozer
wow.. 1gb [email protected] 2-2-2-5
I wouldnt even run memory that SAID it was CL2 at that, and @ 250Mhz, is that final? (125Mhz x2) or is that 250Mhz x2? = 500Mhz... in EITHER case, Try Relaxing your memory timings to 2.5-2-2-6, and maybe run the ram @ what It should be @ (200Mhz x2 - 400Mhz) (Unless its an AM2 chipset that uses DDR2, but that should be CL3)
also, drop your CPU to factory settings also..
and an X1900XTX @ 700/850.. that should be ATLEAST 700/1500 (again, unless your only working on 1/2 the ram clock)
Put ALL your things to bios defaults, set them all to auto etc, and then try it, random BSOD's as you call them are often caused by over clocked components, or components running at settings/timings they shouldnt be at...
I wouldnt even run memory that SAID it was CL2 at that, and @ 250Mhz, is that final? (125Mhz x2) or is that 250Mhz x2? = 500Mhz... in EITHER case, Try Relaxing your memory timings to 2.5-2-2-6, and maybe run the ram @ what It should be @ (200Mhz x2 - 400Mhz) (Unless its an AM2 chipset that uses DDR2, but that should be CL3)
also, drop your CPU to factory settings also..
and an X1900XTX @ 700/850.. that should be ATLEAST 700/1500 (again, unless your only working on 1/2 the ram clock)
Put ALL your things to bios defaults, set them all to auto etc, and then try it, random BSOD's as you call them are often caused by over clocked components, or components running at settings/timings they shouldnt be at...
Nexium
Keep your Xp ore win 2003 Vista is crap really sure it gott some nice eye candy but it's not worth it...
Kaguya
Quote:
Originally Posted by Nexium
Keep your Xp ore win 2003 Vista is crap really sure it gott some nice eye candy but it's not worth it...
|
GW works just great on Vista Beta build 5381 atleast, haven't upgraded it much since that, mwe.
Omega X
Quote:
Originally Posted by Numa Pompilius
It'd make me sad if it's the drivers, as I had hoped Microsoft with Vista had reversed the silly decision they made with XP to run drivers at ring zero (and thereby able to crash the system).
|
Atleast that's what the tech sites report.
Numa Pompilius
What? Win2K didn't run drivers at ring zero, but XP does. Or are you saying that Vista doesn't?
I wouldn't know. I tried to get in on the Vista beta programme, but never got the authorization mail from MS even though they promised to send it. So I said "F it" and stayed with XP pro until Vista is released.
If they've done the right thing and moved the drivers out of ring zero, buggy drivers can't crash the system any more. If buggy drivers can't crash the system anymore, then neither can applications or games. If games can't crash the system, then any system crashes are due to hardware errors or critical flaws in the OS (and I'd not expect to see any in a release candidate, not when running well-behaved software like GW).
And if it's a hardware issue, we're talking overheating, weak PSU, memory errors - the usual suspects basically.
I wouldn't know. I tried to get in on the Vista beta programme, but never got the authorization mail from MS even though they promised to send it. So I said "F it" and stayed with XP pro until Vista is released.
If they've done the right thing and moved the drivers out of ring zero, buggy drivers can't crash the system any more. If buggy drivers can't crash the system anymore, then neither can applications or games. If games can't crash the system, then any system crashes are due to hardware errors or critical flaws in the OS (and I'd not expect to see any in a release candidate, not when running well-behaved software like GW).
And if it's a hardware issue, we're talking overheating, weak PSU, memory errors - the usual suspects basically.
Big_Iron
I was using Beta 2 for a while and GW was running fine...sort of. Well, the performance sucked, but that wasn't because of GW. Vista was such a pig I eventually blew it away and rebuilt with XP. It's back to purring like a kitten.
TreeDude
I think Ghozer is right. Those are really low timings for OCed RAM. The extra strain from Vista might be causing your RAM to give out. I had my RAM timings pretty low at one point. Everything ran fine except BF2, bumped a few timings up and I was fine. So even though your stable for other things doesn't mean your OK for everything.
gabrial heart
5536 works fine on my pc. Basically i have, and still have to some extent, issues with my sound driver and the driver for a tv pvr video board. Both can cause it to hang or BSoD randomly. GW runs well though and it's hung a few times with eax on, cranked to maximum. Other then that it's been pretty stable. Haven't seen a 5551 yet...
an interesting blog article http://www.mstechtoday.com/2006/08/1...ows-vista-rc1/
an interesting blog article http://www.mstechtoday.com/2006/08/1...ows-vista-rc1/
Numa Pompilius
I just checked, and drivers are NOT out of ring zero.
Now, "user mode" drivers do not have root access - but that'd be, like, the kind of lightweight crud drivers things like Quicktime or Flash installs.
However, any driver which wants to run as root and which is installed with an MS-approved app and/or the expressed consent of a user with admin access, will run at ring zero.
And you can bet your camels that not only antivirus drivers but pretty much every driver under the sun will demand to run at ring zero, *especially* DRM drivers, infamously buggy as they all are.
This means that yes, Creative Labs eternally sucky drivers will continue to crash the system and yes, DRM filth like Starforce will too.
Well, keeping shitty drivers out of ring zero was the single best design decision Microsoft could have made for Vista. That they didn't have the balls means that Vista can never be bulletproof like, say, MacOS and Linux.
Too bad. Too fricking bad.
Now, "user mode" drivers do not have root access - but that'd be, like, the kind of lightweight crud drivers things like Quicktime or Flash installs.
However, any driver which wants to run as root and which is installed with an MS-approved app and/or the expressed consent of a user with admin access, will run at ring zero.
And you can bet your camels that not only antivirus drivers but pretty much every driver under the sun will demand to run at ring zero, *especially* DRM drivers, infamously buggy as they all are.
This means that yes, Creative Labs eternally sucky drivers will continue to crash the system and yes, DRM filth like Starforce will too.
Well, keeping shitty drivers out of ring zero was the single best design decision Microsoft could have made for Vista. That they didn't have the balls means that Vista can never be bulletproof like, say, MacOS and Linux.
Too bad. Too fricking bad.
Dark Exige
Its defently not heat my system run very cool (and its still winter until tomorrow).
Its will probably be video drivers. The Vista team has said there have been significant improvments in the video drivers from beta 2 to RC1. So heres hoping RC1 will fix it.
Its will probably be video drivers. The Vista team has said there have been significant improvments in the video drivers from beta 2 to RC1. So heres hoping RC1 will fix it.
jimmy_logic
@Numa
I hear you brother... I hear you. Guess they need scapegoats to blame if their OS crashes.
I hear you brother... I hear you. Guess they need scapegoats to blame if their OS crashes.
Mushroom
That is always the problem when you work with a Beta version of software.
And not only is the OS in beta, but so are the drivers. And bad drivers are the cause of more crashes and lockups then anything else. Just ask anybody with an NVidia card that has installed some of the bad drivers they have had this year.
And you can't blame the OS if it is a driver issue. MicroSoft (or Apple, or Red Hat, etc) has no control on the drivers that are released for their OS.
And not only is the OS in beta, but so are the drivers. And bad drivers are the cause of more crashes and lockups then anything else. Just ask anybody with an NVidia card that has installed some of the bad drivers they have had this year.
And you can't blame the OS if it is a driver issue. MicroSoft (or Apple, or Red Hat, etc) has no control on the drivers that are released for their OS.
Numa Pompilius
Quote:
Originally Posted by Mushroom
And you can't blame the OS if it is a driver issue.
|
In Windows XP drivers (but not programs) have unlimited access to the system, so buggy drivers (but not buggy programs) can and do crash XP.
I was simply hoping that Vista used the Linux architecture for drivers, but it appears Microsoft has chosen to use a hybrid, something that is more secure than XP, but not as secure as Linux.
Well, the proof is in the pudding. Maybe Microsoft intends to be extremely restrictive with approving drivers for ring zero, or even only allow MS drivers and viruskillers to run there... but I doubt it.