WinEQ Crashing While Team Viewer Open (Everquest)

WinEQ 2.0 Lite discussion

Moderators: Lavish Software Team, Moderators

Post Reply
elsawdelabone
Non-Subscriber
Posts: 3
Joined: Fri Feb 03, 2012 9:27 pm

WinEQ Crashing While Team Viewer Open (Everquest)

Post by elsawdelabone » Fri Jul 31, 2015 10:18 pm

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

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

Post by Lax » Sat Aug 01, 2015 11:51 am

Unfortunately I don't have a different solution for you at this time.

TeamViewer 8 has been known to cause issues like this for some people, and the recommended solution has been to close it.

When you select a server, the game is resetting the game window, and that is apparently what is causing the issue here for you when TeamViewer is active.

It's possible that the Windows Event Viewer might have some more technical details about the error. Here's a paste of instructions that might get us somewhere further. (No promises on that, but with some luck...)
I would probably check the Windows Event Log and see if there's an application error listed for eqgame. Microsoft's instructions for opening the Event Viewer are "Open Event Viewer by clicking the Start button, clicking Control Panel, clicking System and Security, clicking Administrative Tools, and then double-clicking Event Viewer.‌ Administrator permission required If you're prompted for an administrator password or confirmation, type the password or provide confirmation.". (You may be able to Win+R and type in "eventvwr")

After opening event viewer, expand "Windows Logs" (not "Applications and Services Logs") and click "Application". This should list recent application crashes and other things at the top of the middle area. If there is an entry for eqgame (should say that under Source) from the date/time of the crash, select it grab me the XML View under the Details tab at the bottom.

elsawdelabone
Non-Subscriber
Posts: 3
Joined: Fri Feb 03, 2012 9:27 pm

Post by elsawdelabone » Sat Aug 01, 2015 1:47 pm

Lax wrote:Unfortunately I don't have a different solution for you at this time.

TeamViewer 8 has been known to cause issues like this for some people, and the recommended solution has been to close it.

When you select a server, the game is resetting the game window, and that is apparently what is causing the issue here for you when TeamViewer is active.

It's possible that the Windows Event Viewer might have some more technical details about the error. Here's a paste of instructions that might get us somewhere further. (No promises on that, but with some luck...)
I would probably check the Windows Event Log and see if there's an application error listed for eqgame. Microsoft's instructions for opening the Event Viewer are "Open Event Viewer by clicking the Start button, clicking Control Panel, clicking System and Security, clicking Administrative Tools, and then double-clicking Event Viewer.‌ Administrator permission required If you're prompted for an administrator password or confirmation, type the password or provide confirmation.". (You may be able to Win+R and type in "eventvwr")

After opening event viewer, expand "Windows Logs" (not "Applications and Services Logs") and click "Application". This should list recent application crashes and other things at the top of the middle area. If there is an entry for eqgame (should say that under Source) from the date/time of the crash, select it grab me the XML View under the Details tab at the bottom.
Thanks at least for the start, Im at work unfortunately so I cannot do this now, but ill give it a try and see what happens.

To clarify, ive tried with TV10 and TV9 also. I read a few of the posts that had a similar issue a few years ago. The strange thing is, ive used this combo before and never had issues. Its a strange bug to say the least.

elsawdelabone
Non-Subscriber
Posts: 3
Joined: Fri Feb 03, 2012 9:27 pm

Post by elsawdelabone » Sat Aug 01, 2015 5:17 pm

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-08-01T22:05:30.000000000Z" />
<EventRecordID>12203</EventRecordID>
<Channel>Application</Channel>
<Computer>Nick-PC</Computer>
<Security />
</System>
- <EventData>
<Data>eqgame.exe</Data>
<Data>0.0.0.0</Data>
<Data>55b161d6</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.18869</Data>
<Data>55636317</Data>
<Data>c0000005</Data>
<Data>0002225b</Data>
<Data>5a8</Data>
<Data>01d0cca6224a15c7</Data>
<Data>D:\Everquest\eqgame.exe</Data>
<Data>C:\Windows\SysWOW64\ntdll.dll</Data>
<Data>6b99d520-3899-11e5-ad76-20cf30e68ab3</Data>
</EventData>
</Event>

That should be all the needed information. If you require anything else, please let me know!

I also wanted to note that a friend recently reinstalled his Teamviewer on a clean OS install of Windows 8.1. He hadn't updated his Teamviewer in months, but went from 10 to 10. Upon the clean install, he had the exact same issue. Logs are not available, as he says his update to Windows 10 2 days ago fixed the problem.

Post Reply