| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
R4d1o4ct1v3
MySQL Real Escape String
   |
Posted - 2009.03.27 18:46:00 -
[1]
If the EVE client itself were to blame for such crashes, it would affect everybody, which would pretty much flood these forums with whining. (Justified whining is still whining  )
Frequent crashes are usually caused by faulty drivers.
And note that any driver can cause this, not just the video/audio drivers.
Updating ALL drivers is a good first step. (Although, up-to-date driers can still be faulty)
Full on system lockups are very unlikely to be caused by the EVE client. The OS can usually handle a single program that is not working properly. For the OS itself to get completely locked up, there is usually some problem with the OS itself.
This is most likely, again, caused by faulty drivers or broken hardware.
HDD problems and corrupt files can also make the OS very unstable.
To sum up... it's probably a faulty driver, broken hardware or file-system corruption.
Update, upgrade, reformat, reinstall, or get Linux!
O, and also keep an eye on hardware heat levels.
Better graphics => more stress on the hardware => more heat generated => BIOS shuts your OS down to prevent heat damage.
----
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
|
R4d1o4ct1v3
MySQL Real Escape String
|
Posted - 2009.03.27 18:52:00 -
[2]
 Originally by: Innara Tal
...Don't suggest it's a system problem, CCP...
So, they should lie to you? 
99.9% of these sort of problems are system problems.
The other 0.01% are usually caused by the "new" WoW shadow engine
----
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
|
R4d1o4ct1v3
MySQL Real Escape String
|
Posted - 2009.03.27 19:49:00 -
[3]
Originally by: Zeba
Originally by: R4d1o4ct1v3
If the EVE client itself were to blame for such crashes, it would affect everybody, which would pretty much flood these forums with whining. (Justified whining is still whining )
Actually thats not quite true. It could be many many factors like certain hardware combinations that ccp never had a chance to test the code out on that are triggering random crashing. [...]
Even if that were the case, the problem would not be with the EVE client itself, but rather with the drivers for that specific hardware-combo.
Software developers can never be expected to test their software out on more than a fraction of available hardware.
If a specific hardware fails to run code built on standard libraries, like DirectX, which I assume EVE is built on, it can't be blamed on the code itself.
If there were problems with the code itself, any hardware that executes standard code correctly would be affected.
Seeing as most hardware runs it without problems, I would assume the code is fine, but that the hardware (driver) failing to execute it is defective.
----
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
|
R4d1o4ct1v3
MySQL Real Escape String
|
Posted - 2009.03.27 20:08:00 -
[4]
Originally by: Zeba
Originally by: R4d1o4ct1v3
Seeing as most hardware runs it without problems, I would assume the code is fine, but that the hardware (driver) failing to execute it is defective.
Or it could be a combination of both. Hardware makers tend to have close ties to game developers and will work with them to add fixes to drivers or help the devs to iron out some issues in thier own code. This is why you get driver updates from the card makers so often. Case in point was supreme commander due to the way ati cards handled shaders and the games own grahics code. A new buggy(yay ati!) driver release triggered the faulty code and then both companys plugged it up. Result was an even prettier and better performing supreme commander than before the bug manifested itself.
It could be, but it would be pure guesswork on our part.
At least for the purpose of debugging, it is better to assume it is something you can fix, and try to fix it, before you blame it on the software, which you can do nothing about.
----
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
|
R4d1o4ct1v3
MySQL Real Escape String
|
Posted - 2009.03.27 20:43:00 -
[5]
Edited by: R4d1o4ct1v3 on 27/03/2009 20:46:35
Originally by: Khlitouris RegusII
No it could be a problem with the client and the hardware nothing to do with drivers at all.
It could be sonic vibrations emanating from the roof of your house, which is being hit by the radiation from solar-flairs!
... Simply saying it doesn't really mean anything unless you can at least logically explain it.
Like I explained before, most actual client problems would have a global effect.
Actual hardware defects are rare (relatively) and usually have less than subtle side-affects. (Boot-failures and such)
Driver problems are very common and can be very elusive.
The simplest explanation is usually the right one.
Edit:
Not that I am excluding client or hardware problems...
But when you hear hoof beats, think horses, not zebras (in most parts, anyways)
----
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
|
R4d1o4ct1v3
MySQL Real Escape String
|
Posted - 2009.03.27 20:50:00 -
[6]
Originally by: Khlitouris RegusII
Originally by: R4d1o4ct1v3
Originally by: Khlitouris RegusII
No it could be a problem with the client and the hardware nothing to do with drivers at all.
It could be sonic vibrations emanating from the roof of your house, which is being hit by the radiation from solar-flairs!
... Simply saying it doesn't really mean anything unless you can at least logically explain it.
Like I explained before, most actual client problems would have a global effect.
Actual hardware defects are rare (relatively) and usually have less than subtle side-affects. (Boot-failures and such)
Driver problems are very common and can be very elusive.
The simplest explanation is usually the right one.
the huge list of python25.dll errors in my event viewer is the simplest explanation i need.
Well if you found the error the whole debugging process if over. No guesswork required.
By the way, what do the errors say, exactly?
----
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
|
R4d1o4ct1v3
MySQL Real Escape String
|
Posted - 2009.03.27 21:01:00 -
[7]
Originally by: Khlitouris RegusII
Faulting module python25.dll lol
Ok.
To be honest, that sounds like a file-system error to me... a corrupt DLL.
I would try re-installing EVE. See if that helps.
Or even re-install it into a second, temporary, location and copy the "python25.dll" from the new one to the old one.
----
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
|
R4d1o4ct1v3
MySQL Real Escape String
|
Posted - 2009.03.27 21:34:00 -
[8]
Originally by: Khlitouris RegusII
Yeah tried that million and one times. it started the patch b4 the first apocrypha patch.
Hmmm... Do you have Python installed separately? Could it be interfering somehow?
There are to many possible reasons why this may be affecting yo so much, really.
I would probably re-format my HDD and go from there. But that's just me 
Windows can get really buggy, really fast. I prefer not to use the same installation for more than a couple of months if I can help it.
Come to think of it... EVE has crashed on me a couple of times since Apocrypha. Maybe it's time to wipe it clean 
----
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
|
R4d1o4ct1v3
MySQL Real Escape String
|
Posted - 2009.03.29 04:39:00 -
[9]
Originally by: Beth Korai
Originally by: Sagitaruis
Since the latest patch my vista PC has been crahing on multiple occasions BSOD, hang ups. So i swapped to a friends other PC Xp service pack 2 running on low settings and its also BSOD random hangs.
Both were running sweet before patch.
Don't tell radioactive, he'll tell you your drivers are screwed up. Just ignore the fact that your drivers were working perfectly BEFORE a code update on the client. That's irrelevent. Completely. Cuz if code works on one machine it'll work on EVERY SINGLE MACHINE it runs on. Just ask radioactive. 
Yes, that's exactly what I said
... no.
BSoD is actually Windows trying to prevent damage to your computer.
There are sooo many reasons why this can happen, that without the actual error message, there is no way to know what caused it.
But, the usual suspects are:
- Faulty drivers (often trying to use reserved memory or failed to clean up after themselves)
- Software memory leaks (which triggers errors when other programs try to use the locked memory)
- Hard-Drive errors (corrupt files, damaged sectors, etc...)
- Defective hardware
With #1 being the problem in something like 99% of the cases (in my experience, at least).
So you see why I tend to lean in that general direction 
And keep in mind that even tho your drivers may have been working perfectly before the patch, any minor change could trigger a dormant defect.
This is especially true for video and audio drivers, as they tend to be rather complex.
Try to catch the error the BSoD is showing. It usually points to what is causing the problem.
----
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
|
| |
|