Everquest 1.0~~
I am bout to wipe. and im 3 boxin~ So i try and log the clr and Bam Blue screen of death >< Wth i dont understand~ tired of random BSOD"s am afraid to box sometimes cause i might bsod ><
Need this resolved
Olsolm
WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.050301-1519
System Physical RAM: 614/1279MB
Page File: 2123/3017MB
Virtual Memory: 1924/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) XP 2200+ @ 1799MHz
CPU Affinity Mask: 1
Video 1: \\.\DISPLAY1/NVIDIA GeForce FX 5200
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1024,768) (1024x768) PRIMARY
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.13
Loaded Modules:
-----------------------------------
Module 0: C:\Program Files\Sony\EverQuest\eqgame.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: C:\Program Files\Sony\EverQuest\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:\Program Files\Sony\EverQuest\DSETUP.dll
Module 16: C:\WINDOWS\system32\VERSION.dll
Module 17: C:\WINDOWS\system32\ole32.dll
Module 18: C:\WINDOWS\system32\SHELL32.dll
Module 19: C:\WINDOWS\system32\SHLWAPI.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\mswsock.dll
Module 31: C:\WINDOWS\system32\hnetcfg.dll
Module 32: C:\WINDOWS\System32\wshtcpip.dll
Module 33: C:\WINDOWS\system32\DNSAPI.dll
Module 34: C:\WINDOWS\System32\winrnr.dll
Module 35: C:\WINDOWS\system32\WLDAP32.dll
Module 36: C:\WINDOWS\system32\rasadhlp.dll
Module 37: C:\WINDOWS\system32\uxtheme.dll
Module 38: C:\Program Files\WinEQ2\EQPlayNice.dll
Module 39: C:\WINDOWS\system32\NTMARTA.DLL
Module 40: C:\WINDOWS\system32\SAMLIB.dll
Module 41: C:\Program Files\Sony\EverQuest\EQGraphicsDX9.DLL
Module 42: C:\WINDOWS\system32\d3d9.dll
Module 43: C:\WINDOWS\system32\d3d8thk.dll
Module 44: C:\Program Files\Sony\EverQuest\dpvs.dll
Module 45: C:\WINDOWS\system32\HID.DLL
Module 46: C:\WINDOWS\system32\SETUPAPI.DLL
Module 47: C:\WINDOWS\system32\WINTRUST.dll
Module 48: C:\WINDOWS\system32\CRYPT32.dll
Module 49: C:\WINDOWS\system32\MSASN1.dll
Module 50: C:\WINDOWS\system32\IMAGEHLP.dll
Module 51: C:\Program Files\Sony\EverQuest\mssmp3.asi
Module 52: C:\Program Files\Sony\EverQuest\mssvoice.asi
Module 53: C:\Program Files\Sony\EverQuest\mssa3d.m3d
Module 54: C:\Program Files\Sony\EverQuest\mssds3d.m3d
Module 55: C:\Program Files\Sony\EverQuest\mssdx7.m3d
Module 56: C:\Program Files\Sony\EverQuest\msseax.m3d
Module 57: C:\Program Files\Sony\EverQuest\mssrsx.m3d
Module 58: C:\WINDOWS\system32\MSACM32.dll
Module 59: C:\Program Files\Sony\EverQuest\msssoft.m3d
Module 60: C:\Program Files\Sony\EverQuest\mssdsp.flt
Module 61: C:\WINDOWS\system32\wdmaud.drv
Module 62: C:\WINDOWS\system32\msacm32.drv
Module 63: C:\WINDOWS\system32\midimap.dll
Module 64: C:\WINDOWS\system32\DSOUND.DLL
Module 65: C:\WINDOWS\system32\KsUser.dll
Direct3D9:
-----------------------------------
Driver: NVIDIA GeForce FX 5200/nv4_disp.dll/6/14/10/8185
Adapter Display Mode: 1024x768 D3DFMT_X8R8G8B8
Game Display Mode: 1024x768 D3DFMT_X8R8G8B8 (Windowed)
Current Adapter: 0
Available Texture Memory: 422MB
Direct3D8:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: (not currently available)
DirectInput8:
-----------------------------------
EverQuest:
-----------------------------------
Profile 1: WinEQ 2.0 Default Profile
EQ Path: C:\Program Files\Sony\EverQuest
EQClient.ini: .\eqclient.ini
Patch: OFF Test Server: OFF Locale: us
Video Adapter: Application Controlled
Luclin models: 0 (+0 min RAM)
Sound: ON (+22 min RAM)
Texture Quality: INVALID VALUE 3
Calculated minimum RAM: 305MB (BASE+22MB)
Level of Detail: 1
MaxFPS: 100
Additional setting: HardwareTnL=TRUE
Additional setting: VertexShaders=1
Additional setting: 20PixelShaders=0
Additional setting: 1xPixelShaders=1
EQPlayNice:
-----------------------------------
EQ Version: eqgame.exe Oct 31 2005 10:33:37
Foreground
Mode: FPS Limiter
Max FPS: 50
Rendering: 1/1
Background
Mode: CPU Limiter
Max FPS: 50
Rendering: 1/50
Seems wineq2.0 is crashin more
Moderators: Lavish Software Team, Moderators
Well, uhhh... WinEQ 2 runs in user mode. To the best of my knowledge, the only things that can BSOD are drivers and other kernel mode programs (and anything that accesses the video memory directly). Bad hardware can cause the problem to happen as well, since that causes drivers to not work properly.
The only BSOD that I am aware of with multiboxing EQ1 is the old EQ1+Multiboxing+NVIDIA+Vertex Shaders off. Your vertex shaders at least in this sysinfo.txt appear to be on, so if you dont have other EQ directories or eqclient.ini files, I dont think that would be the problem.
My only remaining guess, if that's not the case, really is bad hardware.
The only BSOD that I am aware of with multiboxing EQ1 is the old EQ1+Multiboxing+NVIDIA+Vertex Shaders off. Your vertex shaders at least in this sysinfo.txt appear to be on, so if you dont have other EQ directories or eqclient.ini files, I dont think that would be the problem.
My only remaining guess, if that's not the case, really is bad hardware.
-
- Non-Subscriber
- Posts: 16
- Joined: Wed Jan 12, 2005 6:36 pm