Crashing with EQ1 2 boxing continued...

WinEQ 2.0 Pro discussion and support

Moderators: Lavish Software Team, Moderators

Post Reply
Maliki2
GamingTools Subscriber
Posts: 43
Joined: Tue Jul 13, 2004 12:18 am

Crashing with EQ1 2 boxing continued...

Post by Maliki2 » Thu Nov 25, 2004 5:34 am

Since going to WinEQ 2.0+, when two boxing I crash when I camp one of my characters out. Instead of going to the character selection screen I get the little blue box about eqgame crashing and then it drops to desktop. I don't get this with 1.38. Any ideas?

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Thu Nov 25, 2004 11:37 am

Please post SysInfo.txt

Maliki2
GamingTools Subscriber
Posts: 43
Joined: Tue Jul 13, 2004 12:18 am

Post by Maliki2 » Sun Nov 28, 2004 1:56 am

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 1/2600.xpsp1.020828-1920
System Physical RAM: 555/1023MB
Page File: 2082/2462MB
Virtual Memory: 1389/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) XP 2400+ @ 2008MHz
Video 1: \\.\DISPLAY1/RADEON 8500 SERIES
Video 2: \\.\DISPLAY2/RADEON 8500 SERIES
Video 3: \\.\DISPLAYV1/NetMeeting driver
Video 4: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1024,768) (1024x768) PRIMARY
Sound: SB Live! Audio [D800]
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2800.1106
WinEQ: 2.05

Loaded Modules:
-----------------------------------
Module 0: C:\Program Files\Sony\EverQuest Trilogy\eqgame.exe
Module 1: C:\WINDOWS\System32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: C:\Program Files\Sony\EverQuest Trilogy\mss32.dll
Module 4: C:\WINDOWS\system32\USER32.dll
Module 5: C:\WINDOWS\system32\GDI32.dll
Module 6: C:\WINDOWS\system32\ADVAPI32.dll
Module 7: C:\WINDOWS\system32\RPCRT4.dll
Module 8: C:\WINDOWS\System32\WINMM.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.10.0_x-ww_f7fb5805\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\mswsock.dll
Module 31: C:\WINDOWS\System32\wshtcpip.dll
Module 32: C:\WINDOWS\System32\DNSAPI.dll
Module 33: C:\WINDOWS\System32\winrnr.dll
Module 34: C:\WINDOWS\system32\WLDAP32.dll
Module 35: C:\WINDOWS\System32\rasadhlp.dll
Module 36: C:\WINDOWS\System32\uxtheme.dll
Module 37: C:\Program Files\WinEQ2\EQPlayNice.dll
Module 38: C:\WINDOWS\System32\NTMARTA.DLL
Module 39: C:\WINDOWS\System32\SAMLIB.dll
Module 40: C:\Program Files\Sony\EverQuest Trilogy\EQGraphicsDX9.DLL
Module 41: C:\WINDOWS\System32\d3d9.dll
Module 42: C:\WINDOWS\System32\d3d8thk.dll
Module 43: C:\WINDOWS\system32\VERSION.dll
Module 44: C:\Program Files\Sony\EverQuest Trilogy\dpvs.dll
Module 45: C:\WINDOWS\System32\ctagent.dll
Module 46: C:\WINDOWS\System32\DSOUND.dll
Module 47: C:\WINDOWS\System32\HID.DLL
Module 48: C:\WINDOWS\System32\SETUPAPI.DLL
Module 49: C:\WINDOWS\System32\MSACM32.dll
Module 50: C:\WINDOWS\System32\wdmaud.drv
Module 51: C:\WINDOWS\System32\msacm32.drv
Module 52: C:\WINDOWS\System32\midimap.dll
Module 53: C:\WINDOWS\System32\KsUser.dll
Module 54: C:\WINDOWS\System32\usp10.dll
Module 55: C:\Program Files\Sony\EverQuest Trilogy\eqmain.dll

Direct3D9:
-----------------------------------
Driver: RADEON 8500 SERIES /ati2dvag.dll/6/14/10/6490
Adapter Display Mode: 1024x768 D3DFMT_X8R8G8B8
Game Display Mode: 1024x768 D3DFMT_UNKNOWN
Current Adapter: 0

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

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

EverQuest:
-----------------------------------
Profile 1: WinEQ 2.0 Default Profile
EQ Path: C:\Program Files\Sony\EverQuest Trilogy
EQClient.ini: .\eqclient.ini
Patch: OFF Test Server: OFF Locale: us
Video Adapter: Application Controlled
Luclin models: 3 (+15 min RAM)
MipMapping: ON (+4 min RAM)
Sound: ON (+22 min RAM)
Dynamic Lighting: ON (+4 min RAM)
Texture Caching: ON (+0 min RAM)
Texture Quality: LOW (+0 min RAM)
Calculated minimum RAM: 328MB (BASE+45MB)
Level of Detail: 1
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

Maliki2
GamingTools Subscriber
Posts: 43
Joined: Tue Jul 13, 2004 12:18 am

Post by Maliki2 » Mon Nov 29, 2004 6:10 am

While playing with the split screen I just had both instances crash, after I went to the character select screen and logged out. Trying to go back to the id and pw screen in EQ1.

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Mon Nov 29, 2004 11:03 am

If you're speaking of going from character select to server select, this is an EQ bug not a WinEQ bug (happens without WinEQ), and happens if you do it more than once. You shouldn't do so anyway, because even if it didn't crash there's a massive memory leak when you go from character select to server select. They said this should be fixed in the next patch, so you might want to try on the test server to see if that's true

Maliki2
GamingTools Subscriber
Posts: 43
Joined: Tue Jul 13, 2004 12:18 am

Post by Maliki2 » Mon Nov 29, 2004 1:01 pm

Lax wrote:If you're speaking of going from character select to server select, this is an EQ bug not a WinEQ bug (happens without WinEQ), and happens if you do it more than once. You shouldn't do so anyway, because even if it didn't crash there's a massive memory leak when you go from character select to server select. They said this should be fixed in the next patch, so you might want to try on the test server to see if that's true
Thanks Lax that is exactly what I was talking about.

Post Reply