WinEQ Crashing While Team Viewer Open (Everquest)

[elsawdelabone00]

Ive already posted this on the Lavish Software Forums, but I figured it doesnt hurt to post it here to. My issue itself, has nothing to do with MQ2, but I know there are a lot of people here that are much better with computers than I. And im sure quite a bit of you are Familiar with these 2 programs.

"As a background, I have used this combination before, and never had an issue with it. Last time I used both programs was back in 2012.

About 3 months ago I reinstalled my OS - Windows 7 Ultimate.
I began playing Everquest again, and using WinEQ Lite 2.15, and have had no issues whatsoever. I regularly box between 3 and 8 windows, and dont see any issues.

I recently installed TeamViewer and suddenly I began getting this message...

"eqgame.exe has stopped working"

Now the strange part is that I can open the program, log into my account, all the way to the server select menu. But when I try and log into a specific server (doesnt matter which one) this message comes up. If I turn off TeamViewer, it works just fine. If I log in through the regular launcher, it works just fine. But when I log in with WinEQ while TeamViewer is on, it crashes.

I apologize if you need more information, ill post anything you need...

This is the info from my SysInfo File

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Windows 7 Ultimate//7601.win7sp1_gdr.150525-0603
System Physical RAM: 5991/8183MB
Page File: 13020/16364MB
Virtual Memory: 1762/2047MB (Extended: 0MB)
CPU 1: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz @ 2676MHz
CPU 2: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz @ 2676MHz
CPU 3: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz @ 2676MHz
CPU 4: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz @ 2676MHz
CPU Affinity Mask: 8
Video 1: \\.\DISPLAY1/AMD Radeon HD 7900 Series
Video 2: \\.\DISPLAY2/AMD Radeon HD 7900 Series
Video 3: \\.\DISPLAY3/AMD Radeon HD 7900 Series
Video 4: \\.\DISPLAY4/AMD Radeon HD 7900 Series
Video 5: \\.\DISPLAY5/AMD Radeon HD 7900 Series
Video 6: \\.\DISPLAY6/AMD Radeon HD 7900 Series
Video 7: \\.\DISPLAYV1/RDPDD Chained DD
Video 8: \\.\DISPLAYV2/RDP Encoder Mirror Driver
Video 9: \\.\DISPLAYV3/RDP Reflector Display Driver
Monitor 1: \\.\DISPLAY1 (1920,84,3360,984) (1440x900)
Monitor 2: \\.\DISPLAY2 (0,0,1920,1080) (1920x1080) PRIMARY
Sound: ¨

DirectX: 4.09.00.0904
Internet Explorer: 9.11.9600.17914
WinEQ: 2.15

Loaded Modules:
-----------------------------------
Module 0: D:\Everquest\eqgame.exe
Module 1: C:\Windows\SysWOW64\ntdll.dll
Module 2: C:\Windows\syswow64\kernel32.dll
Module 3: C:\Windows\syswow64\KERNELBASE.dll
Module 4: D:\Everquest\mss32.dll
Module 5: C:\Windows\syswow64\USER32.dll
Module 6: C:\Windows\syswow64\GDI32.dll
Module 7: C:\Windows\syswow64\LPK.dll
Module 8: C:\Windows\syswow64\USP10.dll
Module 9: C:\Windows\syswow64\msvcrt.dll
Module 10: C:\Windows\syswow64\ADVAPI32.dll
Module 11: C:\Windows\SysWOW64\sechost.dll
Module 12: C:\Windows\syswow64\RPCRT4.dll
Module 13: C:\Windows\syswow64\SspiCli.dll
Module 14: C:\Windows\syswow64\CRYPTBASE.dll
Module 15: C:\Windows\system32\WINMM.dll
Module 16: C:\Windows\system32\WSOCK32.dll
Module 17: C:\Windows\syswow64\WS2_32.dll
Module 18: C:\Windows\syswow64\NSI.dll
Module 19: C:\Windows\system32\DINPUT8.dll
Module 20: C:\Windows\system32\d3dx9_30.dll
Module 21: C:\Windows\syswow64\WININET.dll
Module 22: C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
Module 23: C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
Module 24: C:\Windows\syswow64\shlwapi.DLL
Module 25: C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
Module 26: C:\Windows\system32\version.DLL
Module 27: C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
Module 28: C:\Windows\syswow64\normaliz.DLL
Module 29: C:\Windows\syswow64\iertutil.dll
Module 30: C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
Module 31: C:\Windows\syswow64\USERENV.dll
Module 32: C:\Windows\syswow64\profapi.dll
Module 33: D:\Everquest\xul.dll
Module 34: D:\Everquest\js3250.dll
Module 35: D:\Everquest\nspr4.dll
Module 36: D:\Everquest\MSVCR71.dll
Module 37: D:\Everquest\plc4.dll
Module 38: D:\Everquest\plds4.dll
Module 39: C:\Windows\syswow64\SHELL32.dll
Module 40: C:\Windows\syswow64\ole32.dll
Module 41: C:\Windows\system32\WINSPOOL.DRV
Module 42: C:\Windows\syswow64\comdlg32.dll
Module 43: C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18837_none_ec86b8d6858ec0bc\COMCTL32.dll
Module 44: D:\Everquest\steam_api.dll
Module 45: C:\Windows\syswow64\IMM32.dll
Module 46: C:\Windows\syswow64\MSCTF.dll
Module 47: C:\Windows\system32\mswsock.dll
Module 48: C:\Windows\System32\wship6.dll
Module 49: D:\WinEQ2\EQPlayNice.dll
Module 50: D:\WinEQ2\Lavish.dll
Module 51: C:\Windows\system32\IPHLPAPI.DLL
Module 52: C:\Windows\system32\WINNSI.DLL
Module 53: C:\Program Files (x86)\TeamViewer\Version8\tv_w32.dll
Module 54: C:\Windows\system32\CRTDLL.dll
Module 55: D:\WinEQ2\WinEQ2.dll
Module 56: C:\Windows\syswow64\PSAPI.DLL
Module 57: C:\Windows\System32\wshtcpip.dll
Module 58: C:\Windows\system32\NLAapi.dll
Module 59: C:\Windows\system32\napinsp.dll
Module 60: C:\Windows\system32\pnrpnsp.dll
Module 61: C:\Windows\system32\DNSAPI.dll
Module 62: C:\Windows\System32\winrnr.dll
Module 63: C:\Windows\System32\fwpuclnt.dll
Module 64: C:\Windows\system32\rasadhlp.dll
Module 65: D:\WinEQ2\WinEQ2-EQ.DLL
Module 66: C:\Windows\system32\MSIMG32.dll
Module 67: D:\WinEQ2\WinEQ2-D3D9.dll
Module 68: C:\Windows\system32\d3d9.dll
Module 69: C:\Windows\system32\d3d8thk.dll
Module 70: C:\Windows\system32\dwmapi.dll
Module 71: D:\WinEQ2\WinEQ2-D3D8.dll
Module 72: D:\WinEQ2\WinEQ2-DI8.dll
Module 73: C:\Users\Nick\Downloads\MQ2-MMOBugs-2015-05-19\MQ2Main.dll
Module 74: D:\Everquest\EQGraphicsDX9.DLL
Module 75: D:\Everquest\dpvs.dll
Module 76: C:\Windows\system32\uxtheme.dll
Module 77: D:\Everquest\eqmain.dll
Module 78: C:\Windows\system32\aticfx32.dll
Module 79: C:\Windows\system32\atiu9pag.dll
Module 80: C:\Windows\system32\atiumdag.dll
Module 81: C:\Windows\system32\atiumdva.dll
Module 82: C:\Windows\system32\POWRPROF.dll
Module 83: C:\Windows\syswow64\SETUPAPI.dll
Module 84: C:\Windows\syswow64\CFGMGR32.dll
Module 85: C:\Windows\syswow64\OLEAUT32.dll
Module 86: C:\Windows\syswow64\DEVOBJ.dll
Module 87: C:\Windows\system32\HID.DLL
Module 88: C:\Windows\syswow64\WINTRUST.dll
Module 89: C:\Windows\syswow64\CRYPT32.dll
Module 90: C:\Windows\syswow64\MSASN1.dll

Direct3D9:
-----------------------------------
Driver: AMD Radeon HD 7900 Series/aticfx32.dll/8/17/10/1333
Adapter Display Mode: 1920x1080 D3DFMT_X8R8G8B8
Game Display Mode: 1366x768 D3DFMT_X8R8G8B8 (Windowed)
Current Adapter: 0
Available Texture Memory: 2776MB
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 7: Chanter
EQ Path: D:\Everquest
EQClient.ini: .\eqclient.ini
Patch: OFF Server Type: Normal Locale: us
Video Adapter: Application Controlled
Luclin models: 29 (+145 min RAM)
Dynamic Lighting: ON (+4 min RAM)
Texture Quality: 1. HIGH (+32 min RAM)
Calculated minimum RAM: 464MB (BASE+181MB)
Level of Detail: 1
MaxFPS: 150
Additional setting: VertexShaders=TRUE
Additional setting: 20PixelShaders=TRUE
Additional setting: 1xPixelShaders=TRUE

EQPlayNice:
-----------------------------------
EQPlayNice version: 1.22
EQ Version: eqgame.exe Jul 23 2015 21:51:18
Foreground
Mode: FPS Limiter
Max FPS: 40
Rendering: 1/1
Background
Mode: CPU Limiter
Max FPS: 30
Rendering: 1/30"

 

[Blitzkrieg]

I've had issues with crashing on char select loading if I am clicking around on the focused window. You may try to edit the FPS limitations on WinEQ or wait to load TeamViewer until you are in game.

I had this issue heaps of times when loading up teams with a low delay on autologin and then tabbing through them accidentally.

 

[elsawdelabone00]

I guess I would only wonder why the program works perfectly fine when TeamViewer isnt running. I can close TV and run as many windows of EQ as I want, but if TV is active when I logon, I crash.

 

[Blitzkrieg]

Try focusing on and off EQ while it is loading character select. You'll have it crash. That is essentially what TeamViewer is doing. Could try adjusting the modes on TV or not press anything while it loads. I just know it is ultra sensitive and I had problems with eqgame.exe crashing all of the time when I would mess around actively focused on a window that was loading after server select.

 

[Fry]

I wasted a good 2 hours on this problem awhile ago.

I was headed out of town, so setup teamviewer so I could watch my bots while out of town. I could not launch EQ sessions. I thought it was MQ2 related, but like you said, ended up being WINEQ2 problem. I ended up ditching wineq2 because of it while out of town.

The problem has been reported on lavishsoft forums for awhile now, but doesn't look like Lax considers it a priority. I'm not sure there is anything we can really do.

 

[elsawdelabone00]

Yea, I saw a few threads reporting a similar problem even dating back to 2013. It's just weird that I've never had this experience before. I played on Fippy for a couple years and used both WinEQ and TV and never had an issue.

My friend recently installed his OS onto a new SDD and began having the same problem, but after upgrading to Windows 10 it stopped. It's a very strange issue.

 

[htw]

That's interesting, I've always used Teamviewer, and although most of the time I just run EQ from a eqgame shortcut for testing, I do use Inner Space and WinEQ2 also, to test.

I just checked again to be sure, and ya, it's working fine for me.

Load order I use (if it even matters), is teamviewer is set to autostart, so it is launched and in tray and ready for connections soon as I log in. Then I start MMOLoader and let it log in, then WinEQ2. Tested by using the WinEQ2 tray icon and running a profile (which is set to patch=no). EQPN is turned on (don't really need it, I use MQ2FPS in game).

Only thing I can think of you having issue, is if it is somehow video related? I really got no clue, tell ya the truth. Have you tried completely fresh wineq2 installation? I.e., uninstall, remove all files in \Program Files (x86)\WinEQ2 dir, reinstall)?

BTW, this is on 2 systems I use (and checked), laptop with win 8.1 pro, and desktop with win 7 ultimate - both with TV.

Sorry I don't have more to offer at the moment, but if I think of anything else, can throw it in here. Good luck!

htw

 

[htw]

That does make me think though...

Have you tried it without MQ2? Just TV & WinEQ2? Does it do the same thing in that case? Asking because wondering if it could be plugin related in any way.

htw

 

[elsawdelabone00]

That does make me think though...

Have you tried it without MQ2? Just TV & WinEQ2? Does it do the same thing in that case? Asking because wondering if it could be plugin related in any way.

htw

I have tried it with no MQ2 and nothing changes. Coincidentally I use the exact same startup order.

The REALLY weird thing, is that when i bypass WinEQ and JUST use the launcher. It logs in perfectly fine. No crashes, no issues. So its obviously an issue with WinEQ, I just dont understand what.

Ive reinstalled WinEQ, I just recently deleted all my EQ files and reinstalled those, and nothing has changed. Im almost considering upgrading to windows 10, since so far thats the only solution ive seen work.

 

[Fry]

The issue only started happened to me when I setup auto-launch teamviewer on startup. So when I restart computer, connect, load up wineq2, launch eq session, crash every time.

 

[elsawdelabone00]

Yea, it's one of the strangest bugs I've come across. Lax from lavish is asking for some data from the Windows event log to try and figure it out.

In the mean time, are there any other programs that function similar to WinEQ. It's really the only one I've ever used.

 

[elsawdelabone00]

The issue only started happened to me when I setup auto-launch teamviewer on startup. So when I restart computer, connect, load up wineq2, launch eq session, crash every time.

So, I had a friend look at this, he did some things...the exact texts were

"Tldr being I cleaned your registry properly, Uninstalled your graphics card properly, then set in fresh drivers directly from amd"

"Ntdll.dll was throwing a 0x0000005 error. Usually contributed by registry errors, video driver issues, memory going bad, or virus. Other things can cause it too but pretty rare"

Everything works just fine now, so I'm not sure exactly what fixed it because he did a bunch of things at once.

 

[linken]

This happened to me and after about 8 hours of digging around I found the issue that solved it for me.

Disable 'Quick Launch Button' on Teamviewer in the Settings.