Athlon X2 and Lineage 2

[compnurd9]

I am actually back to the original windows based drivers for the cpu and i had to manually remove the flag because the driver rollback didnt remove it. no problems so far but we shall see. i have tried rope and several other programs to no avail. all of those programs crash the game at load up to a blue screen. without using them i get an error when the game tried to load.

 

[evilharp]

Originally posted by: Ronin

Originally posted by: evilharp

Originally posted by: Ronin
Uh, no, Intel doesn't have this problem because they don't scare cache between CPUs, where AMD does (although you'll find that nowhere in the documentation).

Thanks for providing misinformation, though.

Really? Well your post is the first I have read that implies that a "shared" cache is the root cause of issues with games. Can you refer me to a site that explains this in detail, I am curious to learn more.

As for "misinformation", I am afraid that I don't totally follow your meaning. Intel did have a problem with Hyperthreading, and does have better driver support courtesy of a larger install base and "Intel" compilers being the norm. Working as a Systems Analyst, I had nothing but trouble with certain in-house applications when HT systems first arrived. We used /pmtimer to resolve these problems until new drivers arrived.

Originally posted by: Markfw900
Did you read his reply ? The X2 drivers FIXED the problem ! He didn't even need that pmtimer flag, in fact it messed it up !

Yes, I read his reply. However, the /pmtimer flag has resolved numerous problems for other games, so I wouldn't say that the "problem is fixed". Considering that the X2 drivers add the /pmtimer flag to the boot.ini, the drivers didn't completely fix the problem either. Also, if you read my post you'll notice I try to explain why Intel DC chips are not having these problems. Ronin was kind enough to add some more information that I was unaware of.

All I tried to do was add some input, and suggest some fixes that have worked for other X2 owners (including myself).

This information is based on extensive internal research at my office, in an attempt to figure out what was causing the problem, so I'm afraid I can't provide you a link.

Can you provide some information in the form of a forum post - or - are you bound by a confidentiality clause? Is the shared cache issue a "global" problem, or is it application specific?

I hope I'm not bugging you, but you are literally the only voice claiming that a shared cache is causing problems for X2 processors. If what you say is true, on a global scale (i.e. all apps), then the implications for DC-Opteron/X2 installs is quite ominous. As it is, everyone seems to be giddy about the X2/DC-Opteron.

 

[Ronin]

Since the issue with the X2s seem to be specific to gaming (as far as I know, anyway), I'm guessing there's something specific there (since it doesn't seem to pose a problem with other applications, but most other applications aren't using components as a whole like a game would, and those that do, already tend to be multithreaded).

 

[Markbnj]

The current XP drivers for the X2 on the AMD site are dated at May, 2005. I installed these and occasional lockup problems I had with BF2 were cured. Nothing else has caused problems. You might want to try these as they are apparently six months or so newer than the ones you have.

 

[evilharp]

Originally posted by: Ronin
Since the issue with the X2s seem to be specific to gaming (as far as I know, anyway), I'm guessing there's something specific there (since it doesn't seem to pose a problem with other applications, but most other applications aren't using components as a whole like a game would, and those that do, already tend to be multithreaded).

This would make for an interesting article for Anandtech to explore. You're right that games tend to max the total system more than any other application, but some game companies (I could name names, but I'll be nice today) are notorious for:

B) sloppy code
F) rushed products
2) memory leaks

Personally, I haven't experienced Delta Time errors (unique to Unreal engine games) but that doesn't mean that the problem isn't there all the time.

 

[I am not an addict]

yeah, I am having the same problem with Lineage2. I have an epox EP-9NPA+ Ultra mb, 3800+ X2 dual core, and an XFX 7800 GTX gcard. I've tried practically everything.. ROPE, RunFirst, and THG Task Assignment Manager, and setting affinity manually.... all this on the L2.exe process. All my drivers/bios (everything) is up to date. When I run any of these utilities, it ends with a blue screen, then a reboot.

I usually end up spawning more processes, then kicking of L2. Eventually, the game comes up, and runs incredibly good... just a pain to get it going. Seems like all my other games run great.

I went through ncsoft support, but eventually they came back and said dual core processors are not officially supported.... and for me to work with AMD on the issue instead.

Anyone have any better luck than I. Anyone working with AMD on this issue?.. specifically with Lineage2?

 

[Markfw]

Note the other thread where the Microsoft patch along with the X2 driver fixes the problem with Lineage 2.

The op posted in this thread that the MS patch fixed his problems

 

[EightySix Four]

MS has a patch out for dual core users... but you have to actually call MS to get ahold of it?

 

[Duvie]

Originally posted by: Markfw900
Note the other thread where the Microsoft patch along with the X2 driver fixes the problem with Lineage 2.

The op posted in this thread that the MS patch fixed his problems

Plain and simple it is an OS and software issue....I think this just about confirms it as every case has been solved with software drivers or reg hacks.....M$ sucks and as soon as we come to grips with that we will all live less stressful lives...