| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
OneSock
   |
Posted - 2006.10.10 16:46:00 -
[1]
/signed.
Intel Core2 Duo E6600
Asus P5N32-SLI Delux
2GB RAM (2x1GB PC5400)
Nvidia 7900GTX
(using built in Realtek AC97 audio)
Western Digital Raptor 74GB 10k RPM SATA150 HD
600watt PSU
etc.
Already ruled out the Audio, cleared cache, etc. usual stuff, still CTD on Undock and Jump only since last client side patch.
|
OneSock
|
Posted - 2006.10.11 11:00:00 -
[2]
Edited by: OneSock on 11/10/2006 11:00:28
 Originally by: Charok
These 2 things got his system stable and he was able to run EVE and even boosted his FPS in other games.
Its not the eve client, its your system.
This is frankly nonsense. We are not talking about random crashes and lockups which you would expect in all games not just Eve. We are talking about specific repeatable problem on Jumping and Undocking.
1. My system is completely stable in all other games and software.
2. My system is not hot.
3. I am using all the latest drivers.
4. I have proven it is not the "disable audio" excuse.
5. I have ruled out power saving options.
and last but not least.
6. THIS PROBLEM ONLY STARTED AFTER THE LAST CLIENT PATCH.
|
OneSock
|
Posted - 2006.10.16 14:32:00 -
[3]
Interesting:
My Core2 Duo system uses NVIDIA« nForce4 SLI Intel« Edition
I wonder if it's SLI boards with nForce4 chipset ?
Does l3VGV have an SLI board ?
|
OneSock
|
Posted - 2006.10.16 14:37:00 -
[4]
Originally by: FurbySlayer
while not everyone using these chipsets are all experiencing the same problem until someone with data on these crashes can compile and research this data and find the trends that lead to this issue, we may never know what is the cause. since ccp undoubtedly recieves the most information on the crashes of its own game using its own logging tools and the games crash file we kinda have to rely upon them to sort it out.
it may very well turn out to be a driver issue, hardware incompatability, or software issue. but until someone figures this out..............
QFT as they say. CCP are best placed to collate and analyse the info on this problem. At the least they could collect the info and say "There is no apparent pattern".
|
OneSock
|
Posted - 2006.10.16 19:23:00 -
[5]
Originally by: l3VGV
Edited by: l3VGV on 16/10/2006 15:12:58
no my board is not SLI. if there msi neo have troubles i dont kno what to think 
in my corp not only me using x2, and there all fine 
Can you be specific about your board type. Msi K8N Neo is an nForce 3 not Nforce 4. K8n Neo4 is nforce 4 SLI. So maybe your board is nforce 3 and the culprit is the nforce4 chipset ?
|
OneSock
|
Posted - 2006.10.17 10:10:00 -
[6]
Originally by: FurbySlayer
one question i would ask of those using the Nforce 4 boards is which nic are you using.. my boards have the nvidia nic, and marvell nic. i find that using the marvell has helped some with this problem. since network cards have become integral parts of motherboards they often can get overlooked as a problem source.
my onboard NICs are disabled. I use a belkin 54g wireless PCI card.
|
OneSock
|
Posted - 2006.10.25 10:32:00 -
[7]
Originally by: Karash Amerius
As a side note...a Corp member of mine just bought a new computer. It is a dual core Intel based box. Latest drivers on everything and only has EVE installed. CTDs on session change pretty frequently. He is pretty upset by this.
Thinking maybe graphics card now. He has a 7900GT.
My problem exactly. Core2Duo, ASUS P5N32-SLI, 2GB, 7900GTX. It's almost as if the machine is too fast for Eve. I get 100+FPS and CPUs never hit 100%, it's not even stressing my PC.
Tell him to get a copy of Company of Heros and ditch Eve until Kali comes along.
|
OneSock
|
Posted - 2006.10.27 11:58:00 -
[8]
I had another crash this morning on Jumping into erme system in Sinq. This time however, I had an interesting message when I tried to reconnect. It could possibly support my theory that my system is simply "too fast" for Eve.
OK, so I jump into Erme and CTD. So I immediatly relauch eve and get the following message : "Cluster has reached max user limit you are #64 in queue". Now at the time I figure, ok bit odd. So I shut down the client again and relog. This time it starts fine.
After talking to my mate at work (who also plays Eve) he mentioned that this was quite common for a node death (he plays down in catch region and they have plenty of node deaths due to fleet wars etc). So here's my theory.
My client connection to the Eve Proxy is fine, but when I undock or move to another system, the proxy has to change my connection to a different node. My client requests the node very quickly before the proxy has connected to the node, proxy says "sorry node not available", so the client thinks ok it's dead, i'll shutdown.
Is there someing in this or am I talking nonsense ?
|
OneSock
|
Posted - 2006.11.03 11:03:00 -
[9]
Originally by: Bombcrater
I posted a possible fix for dual-core issues on the second page of this thread. Can people please try it and report back? No guarantees, but this trick is known to fix CTDs at least on some machines.
To recap:
Quote:
Add the line advancedDevice=1 to the prefs.ini file and then load Eve and in the graphics section of the preferences window change the 'present interval' setting to interval one. Also try this in window mode as well as full screen.
Bomb, you know I think you might have hit the jackpot !
I have not had a CTD on jumping or undocking since making these changes a few days ago. So far so good. I am not sure what the advancedDevice=1 function does but certainly the "interval one" setting is basically enabling v-synch. My FPS is pegged to max 60fps, which is no great problem.
I will continue to monitor for a couple of weeks and report back.
|
OneSock
|
Posted - 2006.11.09 16:45:00 -
[10]
Seeing as this thread had dropped to page 4 I can only assume people are not seeing the CTDs any more ?
I had my first CTD for over a week just last night. which is way better than the numberous CTDs before. So either CCP fixed something or the changes suggested earlier in the thread have worked around the problem.
|
| |
|