Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
n0sferatu said:There is no hotfix for Windows XP Professional x64 Edition, correct? I used the boot.ini switch and it fixed my problem but I'm still curious as if there is a hotfix for x64. Thanks.
marley1 said:help me out here guys.
ive been having a different crashing problem with CS:S not related to benny hill. their was an update this week that caused me to get a crash every 15 min or so, many reports of it on teh forum.
im trying to trouble shoot so i set the affinity to a core.
here is what i did
C:\Program Files\Steam\SteamApps\marley0ne\counter-strike source>imagecfg -a 0x1
hl2.exe
hl2.exe contains the following configuration information:
hl2.exe contains a Subsystem Version of 4.0
hl2.exe updated with the following configuration information:
Process Affinity Mask: 00000001
Now when i loaded up hl2 in control process i see CPU 0 and CPU 1 set in teh Task Manager, what did i do wrong?
If you load the AMD driver for x64 - it will add the uptimer switch in boot.ini (which seems to be the main thing the amd "fix" does)kirbyrj said:AFAIK, there is no hotfix for x64 WinXP. The reason is I think they incorporated the fix already, but I'm not sure if where I read that was a reputable source or not.
seanmcd said:Join the club. I struggle constantly with DOD:Source. I simply manually set the affinity to steam.exe when I start it up. It in turn starts Hl2.exe and it's affinity will be set the same way. So perhaps try only setting the affinity on steam.exe. (PS I get two different crashes with source - one will be a looping sound freeze and I may or may not make it back to the desktop. The other is a crash to desktop with a datacache.dll error.)
seanmcd said:Join the club. I struggle constantly with DOD:Source. I simply manually set the affinity to steam.exe when I start it up. It in turn starts Hl2.exe and it's affinity will be set the same way. So perhaps try only setting the affinity on steam.exe. (PS I get two different crashes with source - one will be a looping sound freeze and I may or may not make it back to the desktop. The other is a crash to desktop with a datacache.dll error.)
If you have no problems gaming, what are you doing in this thread?!C-Otto said:I think you should alter the subject line to include something "Windows". I have no problems gaming, so this is no CPU problem...
C-Otto said:I think you should alter the subject line to include something "Windows". I have no problems gaming, so this is no CPU problem...
marley1 said:yeah alot of users are having this problem.
http://forums.steampowered.com/forums/showthread.php?s=&postid=4166179#post4166179
thatst he forum.
we get a datacache.dll crash and sound looping.
i have manually set the affinitive by using task manager, or using XP Loader, and it works fine.
shit use to crash after 10-15min, been playing for at max an hour all good.
kirbyrj said:Read through some of the posts there. I wouldn't use imageCFG only because it might be construed as cheating by VAC (even though it's not). It might just be something steam has to work out. Probably XP Loader is the best fix for now.
seanmcd said:If you have no problems gaming, what are you doing in this thread?!
kirbyrj said:...forgive me your worshipful Linuxness. How dare we clutter up your thread space with our lowly Windows XP problems
. Oh wait. We wanted to get the best possible gaming performance without having to emulate Windows on a separate OS...what was I thinking?
C-Otto said:Well, you are exaggerating, but I indeed think you should not write about pure Windows problems in such a general thread. It is confusing, after all. The problem is not Dual Core itself, but Windows' scheduler or something.
PS: There are games that do not need Windows emulation (and that is enough for me).
kirbyrj said:You would have to agree that 99%+ of the gaming done with AMD dual core processors is done on Windows based systems. Sometimes it is easier to make that assumption and allow the sub-1% of those who game on other OS's to just ignore the Windows community.
I'm not bashing Linux. I use Linux in a secondary box, but your original post seemed to be along the lines of those who proclaim Linux the answer to all computer questions. I apologize for being overly sarcastic.
kirbyrj said:I'd install the hotfix and see if that fixes any of your issues. That's generally the one I recommend first.
Visable-assassin said:ya think the hot fix would possibly fix that "vibrating" windows thing?
well..i can always disable it so ill try it when i get back home and see whats what
if i can get rid the that vibing windows thing and maybe the lag in game menus id be happy as hell!
sad part is im willing to bet if i went the XP64 id have not on issue other than my soundcard LOL
kirbyrj said:I'm betting Vista will fix these problems (and likely introduce a bunch more).
Ingonuts13 said:Does WindowsXP 64 have these issues also?
kirbyrj said:I don't use WinXP64, but if I were to guess from what I've read, I think the hotfix is incorporated into XP64, but you can still add the /usepmtimer if you need it.
Ingonuts13 said:Ahh that is great news then since I am about to upgrade to XP64 and I have a bunch of games with the stuttering problem right now.
kirbyrj said:Did you install the hotfix? I don't have many stuttering issues with that installed.
Visable-assassin said:i did the hot fix from the first link you listed dude. and it didnt change anything that i can see.
hund_ said:so amd didnt have this problem in testing?i am guessing they did and still released it.amd[not ms] needs to release a driver for this and not this bandaid crap.this is why intel still leads---compatibility.
kirbyrj said:Try the AMD driver or /usepmtimer in your boot.ini. One of those two usually solves the problems![]()
hund_ said:so amd didnt have this problem in testing?i am guessing they did and still released it.amd[not ms] needs to release a driver for this and not this bandaid crap.this is why intel still leads---compatibility.
kirbyrj said:The issue really isn't the hardware. It's a Windows problem with power states. But if you want to blame AMD for a Microsoft problem I can't stop you.
Visable-assassin said:isnt there a rule about trolling?
its not an AMD problem its a windows problem. please come back when you can read up on the problem.
hund_ said:its not like the hardware was out first and the os didnt support it.its the other way around.again this didnt come up in testing???