When running WinEQ2 and Everquest 1, my computer randomly locks up, total lockup, no mouse, no ctrl alt del, no nothing. My computer ONLY does this when using wineq2, and doesn't do this even if running EQ by itself. Also, this started happening when I put in brand new motherboard / pentium d processor / ddr 5400 ram / nvidia 7800 gtx video card. Thanks in advance for your assistance! Also, I should note that this is on US english server, and the freeze happens roughly every 3-4 hours, and almost always happens twice in a row, the second freeze up is exactly as the second character gets fully logged into the game.
Sysinfo is as follows:
WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.050301-1519
System Physical RAM: 1512/2047MB
Page File: 3513/3940MB
Virtual Memory: 1921/2047MB (Extended: 0MB)
CPU 1: Intel(R) Pentium(R) D CPU 3.00GHz @ 3150MHz
CPU Affinity Mask: 1
Video 1: \\.\DISPLAY1/NVIDIA GeForce 7800 GTX
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1600,1200) (1600x1200) PRIMARY
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.12
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\nvappfilter.dll
Module 31: C:\WINDOWS\system32\OLEAUT32.dll
Module 32: C:\WINDOWS\system32\mswsock.dll
Module 33: C:\WINDOWS\system32\hnetcfg.dll
Module 34: C:\WINDOWS\system32\rsvpsp.dll
Module 35: C:\WINDOWS\System32\wshtcpip.dll
Module 36: C:\WINDOWS\system32\DNSAPI.dll
Module 37: C:\WINDOWS\System32\winrnr.dll
Module 38: C:\WINDOWS\system32\WLDAP32.dll
Module 39: C:\WINDOWS\system32\rasadhlp.dll
Module 40: C:\WINDOWS\system32\uxtheme.dll
Module 41: C:\WINDOWS\system32\MSCTF.dll
Module 42: C:\Program Files\Logitech\SetPoint\lgscroll.dll
Module 43: C:\WINDOWS\system32\MSVCR71.dll
Module 44: C:\WINDOWS\system32\MSVCP71.dll
Module 45: C:\WINDOWS\system32\CLBCATQ.DLL
Module 46: C:\WINDOWS\system32\COMRes.dll
Module 47: C:\WINDOWS\system32\xpsp2res.dll
Module 48: C:\WINDOWS\system32\SXS.DLL
Module 49: C:\WINDOWS\system32\NTMARTA.DLL
Module 50: C:\WINDOWS\system32\SAMLIB.dll
Module 51: C:\Program Files\Sony\EverQuest\EQGraphicsDX9.DLL
Module 52: C:\WINDOWS\system32\d3d9.dll
Module 53: C:\WINDOWS\system32\d3d8thk.dll
Module 54: C:\Program Files\Sony\EverQuest\dpvs.dll
Module 55: C:\WINDOWS\system32\mslbui.dll
Module 56: C:\WINDOWS\system32\usp10.dll
Module 57: C:\WINDOWS\system32\HID.DLL
Module 58: C:\WINDOWS\system32\SETUPAPI.DLL
Module 59: C:\WINDOWS\system32\WINTRUST.dll
Module 60: C:\WINDOWS\system32\CRYPT32.dll
Module 61: C:\WINDOWS\system32\MSASN1.dll
Module 62: C:\WINDOWS\system32\IMAGEHLP.dll
Direct3D9:
-----------------------------------
Driver: NVIDIA GeForce 7800 GTX/nv4_disp.dll/6/14/10/7801
Adapter Display Mode: 1600x1200 D3DFMT_X8R8G8B8
Game Display Mode: 1600x1200 D3DFMT_X8R8G8B8
Current Adapter: 0
Available Texture Memory: 452MB
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 2: Snarkle
EQ Path: C:\Program Files\Sony\EverQuest
EQClient.ini: .\eqclient.ini
Patch: OFF Test Server: OFF Locale: us
Video Adapter: Application Controlled
Luclin models: 29 (+145 min RAM)
Texture Compression: ON (+0 min RAM)
MipMapping: ON (+4 min RAM)
Dynamic Lighting: ON (+4 min RAM)
Texture Caching: ON (+0 min RAM)
Texture Quality: MEDIUM (+30 min RAM)
Sky: COMPLEX (+10 min RAM)
Calculated minimum RAM: 476MB (BASE+193MB)
Level of Detail: 1
MaxFPS: 100
Additional setting: HardwareTnL=TRUE
Additional setting: VertexShaders=TRUE
Additional setting: 20PixelShaders=TRUE
Additional setting: 1xPixelShaders=TRUE
Computer lockup issue
Moderators: Lavish Software Team, Moderators
Well, here's my guess.When running WinEQ2 and Everquest 1, my computer randomly locks up, total lockup, no mouse, no ctrl alt del, no nothing. My computer ONLY does this when using wineq2, and doesn't do this even if running EQ by itself.
The only difference you should be experiencing with WinEQ vs normal EQ in this respect is that WinEQ is setting your processor affinity to a single CPU (virtual CPU for your hyperthreading P4D) for each session, whereas otherwise it is defaulting to using both. Unless, of course, you are manually setting the CPU affinity when you run normal EQ, but I will assume you're not.
What happens with this set is that each session is individually going to be running with higher performance, because of not having to wait for the other CPU under some situations, and such (EQ1 is not optimized for dual CPU systems). Less waiting on the other CPU means more time spent executing instructions, which in turn means more heat generated.
Assuming you're not running MacroQuest 2 with MQ2FPS (if you are, then my entire hypothesis is probably wrong, so let me know), and with EQPlayNice disabled, your processors are getting very little time to rest, if any. My guess is that the heat from full CPU loads over that amount of time is just becoming too much for the processor, and it's locking up on you. The ambient heat (room temperature, etc) also contributes, since a little fan on the CPU isnt going to do much good if the room temperature is too hot as it is.
My suggestion is going to be to simply turn on EQPlayNice. If you disabled it to stop the "flashing" effect in the background sessions, just disable Rendering Limiting instead.
I am not setting the processor affinity. I can say that it's possible that I have not played eq without wineq2 long enough to duplicate the issue. I can say that this problem occurs with and without mq2 running. I am not running standard fans, and cpu very rarely gets over 145 degrees. Do you think that the cause is still the same, or do you think that is still the issue? One other thing I forgot to mention earlier is that this mostly happens when zoning or switching windows quickly.
But didnt mention whether or not you use MQ2FPSI can say that this problem occurs with and without mq2 running.
Hmmm well it's easier to think of CPU temperature in degrees Celius instead of Fahrenheit. 62.8 C is kind of hot, I wouldn't let my CPU get that hot. It's probably not hot enough to do any physical damage, but could contribute to the problem. I have had systems lock up or reboot at 125 F / 51.7 C before, but if I remember correctly, it was actually the video card overheating from the fan dying, and I didnt check that temp before replacing it.I am not running standard fans, and cpu very rarely gets over 145 degrees.
I would definitely make sure it's not your new video card, or the motherboard chipset (north bridge or whatever it is that usually has a heatsink and fan nowadays) overheating though.
Past that, the next thing that comes to mind is motherboard drivers, particularly IDE/SATA. If those are old versions, you might get freeze or BSOD during any disk access randomly. When I first got started with SATA drives, the driver on the install CD had a bug that caused problems like that, and updating it solved the problem. So make sure that's not the case as well.
Yesterday I loaded the lastest SATA drivers and restarted, changed wineq2 to use eq playnice, put up my trader, and left it there, and computer froze. When I went away on biz for 2 days my computer ran the whole time with no everquest or wineq2 running. With the game only having 1 toon in trader mode, this shouldn't have caused the computer to overheat I don't think, right? I did have the hide traders feature on also.
I still dont have information on whether or not you were using MQ2FPS at the time. If not, and your FPS setting in EQ is set at 100 (as is shown by sysinfo.txt), then it's entirely possible it was overheating. I'm going to assume that you havent been using MQ2FPS at least since the expansion came out since MQ2 wasnt updated until today and still has huge problems.
There's a big difference between the computer idling while you are away for 2 days and under full load with EQ running. Regardless of whether you had hide traders on, trader mode on, whatever else, the game was still processing information and rendering the game display. I'm still going to highly recommend the use of EQPlayNice or MQ2FPS to avoid this type of problem.
Another thing you can try is to disable sound in the Windows device manager, to see if the sound driver is the actual problem.
The long and the short of it is basically that either overheating or some driver on your system is causing this problem. WinEQ could slow down your system, but not really freeze it.
There's a big difference between the computer idling while you are away for 2 days and under full load with EQ running. Regardless of whether you had hide traders on, trader mode on, whatever else, the game was still processing information and rendering the game display. I'm still going to highly recommend the use of EQPlayNice or MQ2FPS to avoid this type of problem.
Another thing you can try is to disable sound in the Windows device manager, to see if the sound driver is the actual problem.
The long and the short of it is basically that either overheating or some driver on your system is causing this problem. WinEQ could slow down your system, but not really freeze it.