Crashing while two-boxing

DarkSir · Post by **DarkSir** » Thu Nov 25, 2004 2:06 pm

Since 2.04, I've been crashing a lot while two boxing. If I try to run on separate monitors, I''m crashing as the second instance gets logged into game from character select (first instance crashes).

If I try to run on the same monitor, I can sometimes play for as many as 5 minutes before one instance crashes. Included is my info:

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 1/2600.xpsp2.030422-1633
System Physical RAM: 662/1023MB
Page File: 1611/2078MB
Virtual Memory: 1425/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) XP 1800+ @ 1532MHz
Video 1: \\.\DISPLAY1/NVIDIA GeForce4 Ti 4200
Video 2: \\.\DISPLAY2/NVIDIA GeForce4 Ti 4200
Video 3: \\.\DISPLAYV1/NetMeeting driver
Video 4: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1280,1024) (1280x1024) PRIMARY
Monitor 2: \\.\DISPLAY2 (1280,0,2560,1024) (1280x1024)
Sound: SB Live! Audio [E800]
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2800.1106
WinEQ: 2.05

Loaded Modules:
-----------------------------------
Module 0: e:\program files\everquest\eqgame.exe
Module 1: E:\WINDOWS\System32\ntdll.dll
Module 2: E:\WINDOWS\system32\kernel32.dll
Module 3: e:\program files\everquest\mss32.dll
Module 4: E:\WINDOWS\system32\USER32.dll
Module 5: E:\WINDOWS\system32\GDI32.dll
Module 6: E:\WINDOWS\system32\ADVAPI32.dll
Module 7: E:\WINDOWS\system32\RPCRT4.dll
Module 8: E:\WINDOWS\System32\WINMM.dll
Module 9: E:\WINDOWS\System32\WSOCK32.dll
Module 10: E:\WINDOWS\System32\WS2_32.dll
Module 11: E:\WINDOWS\system32\msvcrt.dll
Module 12: E:\WINDOWS\System32\WS2HELP.dll
Module 13: E:\WINDOWS\System32\DINPUT8.dll
Module 14: E:\WINDOWS\System32\IMM32.dll
Module 15: E:\WINDOWS\system32\SHELL32.dll
Module 16: E:\WINDOWS\system32\SHLWAPI.dll
Module 17: E:\WINDOWS\system32\ole32.dll
Module 18: E:\WINDOWS\System32\ShimEng.dll
Module 19: E:\WINDOWS\AppPatch\AcGenral.DLL
Module 20: E:\WINDOWS\System32\MSACM32.dll
Module 21: E:\WINDOWS\system32\VERSION.dll
Module 22: E:\WINDOWS\system32\USERENV.dll
Module 23: E:\WINDOWS\System32\UxTheme.dll
Module 24: E:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.1331_x-ww_7abf6d02\comctl32.dll
Module 25: E:\WINDOWS\system32\comctl32.dll
Module 26: E:\WINDOWS\System32\MSCTF.dll
Module 27: E:\WINDOWS\System32\ctagent.dll
Module 28: C:\EQPlayNice\WinEQ2\WinEQ2.dll
Module 29: E:\WINDOWS\Lavish.dll
Module 30: E:\WINDOWS\System32\PSAPI.DLL
Module 31: C:\EQPlayNice\WinEQ2\WinEQ2-EQ.dll
Module 32: E:\WINDOWS\System32\MSIMG32.dll
Module 33: C:\EQPlayNice\WinEQ2\WinEQ2-D3D9.dll
Module 34: C:\EQPlayNice\WinEQ2\WinEQ2-D3D8.dll
Module 35: C:\EQPlayNice\WinEQ2\WinEQ2-DI8.dll
Module 36: E:\WINDOWS\system32\mswsock.dll
Module 37: E:\WINDOWS\System32\wshtcpip.dll
Module 38: E:\WINDOWS\System32\DNSAPI.dll
Module 39: E:\WINDOWS\System32\winrnr.dll
Module 40: E:\WINDOWS\system32\WLDAP32.dll
Module 41: E:\WINDOWS\System32\rasadhlp.dll
Module 42: C:\EQPlayNice\WinEQ2\EQPlayNice.dll
Module 43: C:\EQPlayNice\stuff\MQ2Main.dll
Module 44: E:\Program Files\Messenger Plus! 2\MsgPlusH.dll
Module 45: E:\WINDOWS\system32\comdlg32.dll
Module 46: E:\WINDOWS\system32\OLEAUT32.dll
Module 47: E:\Program Files\VCOM\PowerDesk\pddlghlp.dll
Module 48: E:\WINDOWS\System32\MSVCP60.dll
Module 49: E:\WINDOWS\System32\NTMARTA.DLL
Module 50: E:\WINDOWS\System32\SAMLIB.dll
Module 51: e:\program files\everquest\EQGraphicsDX9.DLL
Module 52: E:\WINDOWS\System32\d3d9.dll
Module 53: E:\WINDOWS\System32\d3d8thk.dll
Module 54: e:\program files\everquest\dpvs.dll
Module 55: C:\EQPlayNice\stuff\mq2labels.dll
Module 56: C:\EQPlayNice\stuff\mq2itemdisplay.dll
Module 57: C:\EQPlayNice\stuff\mq2custombinds.dll
Module 58: C:\EQPlayNice\stuff\mq2hud.dll
Module 59: C:\EQPlayNice\stuff\mq2map.dll
Module 60: C:\EQPlayNice\stuff\mq2bzsrch.dll
Module 61: C:\EQPlayNice\stuff\mq2chatwnd.dll
Module 62: C:\EQPlayNice\stuff\mq2eqbugfix.dll
Module 63: E:\WINDOWS\System32\HID.DLL
Module 64: E:\WINDOWS\System32\SETUPAPI.DLL
Module 65: E:\WINDOWS\System32\usp10.dll
Module 66: E:\WINDOWS\System32\mslbui.dll

Direct3D9:
-----------------------------------
Driver: NVIDIA GeForce4 Ti 4200/nv4_disp.dll/6/14/10/6177
Adapter Display Mode: 1280x1024 D3DFMT_X8R8G8B8
Game Display Mode: 1280x1024 D3DFMT_UNKNOWN
Current Adapter: 0

Direct3D8:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0

DirectInput8:
-----------------------------------

EverQuest:
-----------------------------------
Profile 4: PiP LowRez
EQ Path: e:\program files\everquest
EQClient.ini: .\lowrez.ini
Patch: OFF Test Server: OFF Locale: us
Video Adapter: Primary
Luclin models: 3 (+15 min RAM)
Texture Compression: ON (+0 min RAM)
Dynamic Lighting: ON (+4 min RAM)
Texture Caching: ON (+0 min RAM)
Texture Quality: MEDIUM (+30 min RAM)
Calculated minimum RAM: 332MB (BASE+49MB)
Level of Detail: 0
MaxFPS: 100
Additional setting: VertexShaders=TRUE
Additional setting: 20PixelShaders=TRUE
Additional setting: 1xPixelShaders=TRUE

EQPlayNice:
-----------------------------------
EQ Version: eqgame.exe Oct 11 2004 15:21:50
Foreground
Mode: FPS Limiter
Max FPS: 40
Rendering: 1/1
Background
Mode: CPU Limiter
Max FPS: 30
Rendering: 1/30

Post by **Lax** » Thu Nov 25, 2004 2:26 pm

Have you tried running without MQ2 to make sure thats not related?

DarkSir · Post by **DarkSir** » Thu Nov 25, 2004 3:28 pm

I have, same error

Post by **Lax** » Thu Nov 25, 2004 10:20 pm

I've reproduced a crash and I'll be working on this

Post by **Lax** » Thu Nov 25, 2004 10:34 pm

I take it back, I went through the pain in the ass of removing the Xfire LSP (which is not removed when you uninstall xfire, and stays active...) - i had installed Xfire to work on a completely different problem -.. and I cant seem to get it to crash now. I'll keep trying.

DarkSir · Post by **DarkSir** » Thu Nov 25, 2004 10:49 pm

I thought it might be the new memory I installed, but undoing that hasn't fixed it. I've tried it with and without MQ, with and without PinP, on one monitor, on two monitors... I seem to be fine til I load a second instance, then it gets boggy, and crashes. Then, shortly after that, whichever instance that's remaining crashes too.

Blah :/

Thankfully, I have faith in you.

Post by **Lax** » Thu Nov 25, 2004 11:30 pm

Gets boggy? Can you give more information on that specifically?
Do you see the memory indicator in the upper left at the EULA? (You cant miss it if you havent disabled the option)

DarkSir · Post by **DarkSir** » Thu Nov 25, 2004 11:53 pm

Yeah, I can see the memory indicator. Usually the first instance drops me down to about 30% remaining memory, the second drops me down to nothing or next to nothing.

By boggy, I should clarify: It takes a while to load. That I'm used to. But once it's loaded, both instances work fine for a short bit (provided one didn't crash as the second was loading), then switching windows gets problematic, taking a while, or black-screening, then finally crash.

DarkSir · Post by **DarkSir** » Thu Nov 25, 2004 11:55 pm

And the first instance seems to be using up more memory than it used to. I used to have no trouble at all two-boxing with 768. But since 2.04, it drops down really fast, and the second instance usually eats the rest.

Post by **Lax** » Fri Nov 26, 2004 12:38 am

Frankly, 2.04 didn't change anything relevant. 2.03 may have... however.. this issue could be related to a problem in EQ itself. If you have access to the test server, you can try running with the current test server client and you may have better luck. They supposedly have a fix in testing for the huge memory leaks previously seen, and say it's more stable after fixing that. So with specific regards to their fix, it might be worth seeing if you still crash while playing on the test server. (my info from: http://eqforums.station.sony.com/eq/boa ... ge.id=4852 )

Let me know