Everquest crash on secondary monitor

[cbdougla]

I've recently installed a secondary monitor and have been trying to two box one EQ account in a window on the primary screen and another EQ account in emulated full screen on the secondary monitor.

What I am experiencing is frequent crashes on the second account that is being boxed on the second monitor. It doesn't matter much whether it's full screen (emulated) or windowed, it still crashes.

One thing I have noticed is that it seems to crash only when I use ALT-TAB to switch to that EQ session. This doesn't ALWAYS trigger it but it seems to be the deciding factor as to whether it's going to crash.

I do not have this problem with crashes if I run both accounts on the same screen.

Here's a snip from the dbg.txt file in the Everquest directory. It contains an interesting error similar to one I see listed in another thread:

2004-12-08 20:31:05 fatal error in main thread Code = c0000005 ADDR=0x00f8ee00
2004-12-08 20:31:05
2004-12-08 20:31:05 EAX=00000000 EBX=00ff8510 ECX=01290001 EDX=00000000
2004-12-08 20:31:05
2004-12-08 20:31:05 ESI=00ff89b4 EDI=24c71594 EBP=0012dbd0 ESP=0012db64
2004-12-08 20:31:05
2004-12-08 20:31:05 Process was trying to READ invalid data.
2004-12-08 20:31:05
2004-12-08 20:31:06 Invalid access occurred at virtual address 0x01290001.
2004-12-08 20:31:06
2004-12-08 20:31:06 Fatal error occurred in mainthread! (Release Client #630)
2004-12-08 20:31:06
2004-12-08 20:31:06 Client Version: Oct 11 2004 15:21:50
2004-12-08 20:31:06 Skin Directory: UIFiles\Default\
2004-12-08 20:31:06
2004-12-08 20:31:06 Graphics DLL Loaded: Graphics DLL Version 2.00.0149
2004-12-08 20:31:06 Graphics Build Date: Oct 13 2004 13:23:10
2004-12-08 20:31:06 Video Card: RADEON 9700 PRO - Secondary, 6.14.10.6490
2004-12-08 20:31:06 Crash (char = Xxxxxxx, zone = ecommons)
2004-12-08 20:31:06
2004-12-08 20:31:06 Local Player's World location at time of crash: -1565.905762, 771.817017, 7.062698.
2004-12-08 20:31:06
2004-12-08 20:31:06 Gamestate at crash = 5
2004-12-08 20:31:06
2004-12-08 20:31:07 Processor: 1 of type 586
2004-12-08 20:31:07 Physical memory: 768 Megs
2004-12-08 20:31:07 CPU: AMD Athlon(tm) XP 1600+ 1421951

If you would like, I can provide this dbg.txt file in whole. I just didn't want to cut and paste it into this thread because it is rather large.

Ok. Here's the sysinfo stuff pasted in below.

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_rtm.040803-2158
System Physical RAM: 102/767MB
Page File: 1829/2722MB
Virtual Memory: 1280/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) XP 1600+ @ 1400MHz
Video 1: \\.\DISPLAY1/RADEON 9700 PRO
Video 2: \\.\DISPLAY2/RADEON 9700 PRO - Secondary
Video 3: \\.\DISPLAYV1/NetMeeting driver
Video 4: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1280,1024) (1280x1024) PRIMARY
Monitor 2: \\.\DISPLAY2 (1280,160,2304,928) (1024x768)
Sound: SB Audigy Audio [E800]
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.05

Loaded Modules:
-----------------------------------
Module 0: c:\programs\everquest2\eqgame.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: c:\programs\everquest2\mss32.dll
Module 4: C:\WINDOWS\system32\USER32.dll
Module 5: C:\WINDOWS\system32\GDI32.dll
Module 6: C:\WINDOWS\system32\WINMM.dll
Module 7: C:\WINDOWS\system32\ADVAPI32.dll
Module 8: C:\WINDOWS\system32\RPCRT4.dll
Module 9: C:\WINDOWS\system32\WSOCK32.dll
Module 10: C:\WINDOWS\system32\WS2_32.dll
Module 11: C:\WINDOWS\system32\msvcrt.dll
Module 12: C:\WINDOWS\system32\WS2HELP.dll
Module 13: C:\WINDOWS\system32\DINPUT8.dll
Module 14: C:\WINDOWS\system32\IMM32.dll
Module 15: C:\WINDOWS\system32\SHELL32.dll
Module 16: C:\WINDOWS\system32\SHLWAPI.dll
Module 17: C:\WINDOWS\system32\ole32.dll
Module 18: C:\WINDOWS\system32\serwvdrv.dll
Module 19: C:\WINDOWS\system32\umdmxfrm.dll
Module 20: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
Module 21: C:\WINDOWS\system32\comctl32.dll
Module 22: C:\Program Files\WinEQ2\WinEQ2.dll
Module 23: C:\WINDOWS\Lavish.dll
Module 24: C:\WINDOWS\system32\PSAPI.DLL
Module 25: C:\Program Files\WinEQ2\WinEQ2-EQ.dll
Module 26: C:\WINDOWS\system32\MSIMG32.dll
Module 27: C:\Program Files\WinEQ2\WinEQ2-D3D9.dll
Module 28: C:\Program Files\WinEQ2\WinEQ2-D3D8.dll
Module 29: C:\Program Files\WinEQ2\WinEQ2-DI8.dll
Module 30: C:\WINDOWS\system32\xfire_lsp_8742.dll
Module 31: C:\WINDOWS\system32\Secur32.dll
Module 32: C:\WINDOWS\system32\mswsock.dll
Module 33: C:\WINDOWS\system32\hnetcfg.dll
Module 34: C:\WINDOWS\System32\wshtcpip.dll
Module 35: C:\WINDOWS\system32\DNSAPI.dll
Module 36: C:\WINDOWS\System32\winrnr.dll
Module 37: C:\WINDOWS\system32\WLDAP32.dll
Module 38: C:\WINDOWS\system32\rasadhlp.dll
Module 39: C:\WINDOWS\system32\uxtheme.dll
Module 40: C:\WINDOWS\system32\NTMARTA.DLL
Module 41: C:\WINDOWS\system32\SAMLIB.dll
Module 42: c:\programs\everquest2\EQGraphicsDX9.DLL
Module 43: C:\WINDOWS\system32\d3d9.dll
Module 44: C:\WINDOWS\system32\d3d8thk.dll
Module 45: C:\WINDOWS\system32\VERSION.dll
Module 46: c:\programs\everquest2\dpvs.dll
Module 47: C:\WINDOWS\system32\HID.DLL
Module 48: C:\WINDOWS\system32\SETUPAPI.DLL
Module 49: C:\WINDOWS\system32\WINTRUST.dll
Module 50: C:\WINDOWS\system32\CRYPT32.dll
Module 51: C:\WINDOWS\system32\MSASN1.dll
Module 52: C:\WINDOWS\system32\IMAGEHLP.dll
Module 53: C:\WINDOWS\system32\usp10.dll

Direct3D9:
-----------------------------------
Driver: RADEON 9700 PRO - Secondary/ati2dvag.dll/6/14/10/6490
Adapter Display Mode: 1024x768 D3DFMT_X8R8G8B8
Game Display Mode: 1024x768 D3DFMT_UNKNOWN
Current Adapter: 1

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

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

EverQuest:
-----------------------------------
Profile 2: EQ2
EQ Path: c:\programs\everquest2
EQClient.ini: .\eqclient.ini
Patch: OFF Test Server: OFF Locale: us
Video Adapter: Secondary
Luclin models: 9 (+45 min RAM)
Texture Compression: ON (+0 min RAM)
Texture Quality: MEDIUM (+30 min RAM)
Calculated minimum RAM: 358MB (BASE+75MB)
Level of Detail: 1
MaxFPS: 100
Additional setting: VertexShaders=TRUE
Additional setting: 20PixelShaders=1
Additional setting: 1xPixelShaders=1

[Lax]

The crash is likely due to XFire. If you don't use XFire or have no idea what it is, get the program here that can remove its LSP http://www.cexx.org/lspfix.htm (you basically just run the program and hit the remove button). I can only assume that you dont use it, since the dll loaded on your system appears to be an old one. If you do use it, I would suggest the possibility of updating it.

Let me know if this helps

[cbdougla]

I will give that a shot and let you know how it works out. I've also had some really funky issues with my system in the past few days that I really can't explain (nothing to do with winEQ). Mouse pointer corruption, texture issues in game etc. I run a pretty tight ship so I am 99.9% sure I have no viruses or spyware. I just got everything working the way I like it too. Sigh.

Anyway, a friend of mine is on the Xfire team. I will contact and let him know they are breaking stuff. : )

[Lax]

What you should really tell them is to get rid of the LSP crap It's not necessarily that theyre breaking stuff, but that I didn't anticipate other programs making their own DirectInput objects inside games when creating WinEQ. I can work around it by checking if XFire is loaded and then just not do anything with DirectInput, but the code I have in it right now looks for a specific name DLL. The problem is they appear to change the numbers attached to the name of the DLL with every build

[cbdougla]

I am pretty sure they are creating their direct input objects to facilitate their in game chat system.

Seeing as I am not really a programmer (my C skills extend somewhat beyond hello-world.c but not much), I can't say for sure.

I didn't get a chance to get online last night but I should have time tonight after work. I will make sure to let them know about the conflict. They have generally been pretty good about trying to fix things they interfere with so one can only be optimistic that they will be cooperative in this case too.

[Lax]

Yes thats why they create their direct input objects BUT it can be done without it (Inner Space for example adds a console window to the games and does not create its own DirectInput interfaces).. It's fine that they do it, I just didn't anticipate it. I would really be happiest if they could just pick one filename for each of their DLLs

[cbdougla]

Just an update. I ran the secondary screen yesterday as I described when I was having problems and experienced no issues. We were in a 5 hour Xegony raid in PoA so I consider this a pretty good test.

I will let you know how things work from here.