| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
RoundupGang
   |
Posted - 2007.01.11 16:37:00 -
[1]
Edited by: RoundupGang on 11/01/2007 16:48:27
I am running 2 clients on the same computer. They run fine when one is sitting the station. However, when I run them both out to do some mining, my computer always locks and crashes to blue screen of death with in 1 minute of opening a jettison can to fill from my cargo hold. I have tried running 2 clients from 1 installation of EVE and running 2 clients from 2 different installations of EVE and the result is the same. The way the game locks up then blue screens gives me a memory leak feel but I don't have any proof to back this up. Wanted to see if anybody has encountered this and has fix.
EDIT: I tried again just with the 2nd account (ie. just 1 instance of EVE running) and it crashes when I mine. This is on the 2nd installation of EVE (but I had this same blue screen of death when I was running it off just 1 EVE installation; although I didn't test it then for just this 2nd account mining by itself.) I am just running a navitas with 2 mining 1 lasers, WCS, and a plate. Can anybody help me.
my setup is:
AMD Athlon X2 4200+ dual core
2GB of RAM
cable ISP
NVIDIA 7800 GT 256MB
|
Wulfe Stillborne
Caldari
|
Posted - 2007.01.11 21:11:00 -
[2]
You didn't mention your sound setup. You might want to turn off audio on both clients to see if it resolves the issue.
Besides, you can check your memory with Memtest to see whether it has anything to do with CTD (are you using quality RAM?).
|
RoundupGang
|
Posted - 2007.01.12 16:16:00 -
[3]
my sound car is Soundblaster Audigy Gamer. After testing it further it seems to be fine with just 1 client running. Doesn't matter which one (whether the first installed one or the second).
I think it is a memory error, like the memory footprint cache for both exceeds my 2GB of RAM. The reason I think this is that the last 2 times it crashed I had opened up things that would cause more stuff to be cached like Corp/Alliance mail and corporation window looking at alliance members.
I have disabled the auto reboot on crash in XP and was able to see what was on the blue screens of death.
1st one blue screen:
DRIVER_IRQL_NOT_LESS_OR EQUAL
***(bunch of standard warning crap here)
Tech Info:
STOP Ox00000001 (0x00000005,0x00000002,0x00000000,0xBF2F40A2)
tcip.sys - Address 0xBF2F40A2 at BF72ED00
2nd blue screen
Tech Info:
STOP 0x0000008E (0XC0000005,0XB961034D,0XB48D2850,0x00000000)
ha10kx2k.sys - Address 0XB961034D base at B95B5000
|
amagonsan
|
Posted - 2007.01.14 07:30:00 -
[4]
The DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen is usualy an indication of a broken driver or a defective memory. 1) install new sound and video drivers 2)use memtest86 (freeware) to test your memory.
It can be caused by a program trying to access a driver in a way that it wasn't intended, but a good driver is protected from this.
In any case, it can never harm to test your pc's memory :)
|
Biosman
GALAXIAN
Rule of Three
|
Posted - 2007.01.14 11:16:00 -
[5]
I get exactly the same thing which I resolve by having
sound disabled on my second client.Def an Audigy thing.
|
RoundupGang
|
Posted - 2007.01.16 07:01:00 -
[6]
Thanks, I will try disabling the sound on the second client.
|
RoundupGang
|
Posted - 2007.01.20 04:07:00 -
[7]
Just wanted to follow up on suggestion to turn the sound off on the 2nd client. It worked. Hopefully if someone else is getting this problem they can use this solution.
|
Bryante
Minmatar
Free Mercenaries Union
The Hired
|
Posted - 2007.01.20 18:19:00 -
[8]
I run two clients on a lower spec machine than yours mentioned. 512mb ram and a geforce 6600 card, I turned sound off on both accounts and would recommend this!
|
Broc Vallion
United Outworlders Corporation
|
Posted - 2007.01.20 22:40:00 -
[9]
Don't install Eve twice... install it once and copy the Eve folder, and make a new shortcut to the copied eve client etc...
|
Andraea Sarstae
|
Posted - 2007.07.14 22:01:00 -
[10]
Ok, so making two clients and disabling the sound (iva the prefs.ini file) worked for me up until the latest changed where the prefs file got moved and is now apparently shared.
Now, I'm back to getting BSOD's if I try to multi-client.
Anyone have any ideas on how we can get around this given the new limitations?
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |