WinEQ2 and WC3 Frozen Throne Issue

WinEQ 2.0 Pro discussion and support

Moderators: Lavish Software Team, Moderators

Post Reply
Arghificious
GamingTools Subscriber
Posts: 10
Joined: Sat Jul 17, 2004 11:50 pm

WinEQ2 and WC3 Frozen Throne Issue

Post by Arghificious » Wed Mar 16, 2005 3:43 pm

Just purchased it, and when I try to run Warcraft III FT on it, it gives me the following error:

This application has encountered a critical error:

FATAL ERROR!

Program: i:\games\warcraft III official\war3.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:0979DC60

The instruction at '0x0979DC60' referenced memory at '0x0979DC60'.
The memory could not be 'read'.

Press OK to terminate the application.

I hit OK, and it says the CD isn't in the drive (when it is).

I can run WC3 just fine from that directory as long as I'm not trying to run it through WinEQ2.

Any suggestions?

Arghificious
GamingTools Subscriber
Posts: 10
Joined: Sat Jul 17, 2004 11:50 pm

Post by Arghificious » Wed Mar 16, 2005 3:47 pm

Sorry, sysinfo.txt here:

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP//2600.xpclnt_qfe.021108-2107
System Physical RAM: 1102/1535MB
Page File: 4164/4425MB
Virtual Memory: 2012/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) XP 3000+ @ 2091MHz
Video 1: \\.\DISPLAY1/RADEON 9500 @ 9700 (http://softmod.techpowerup.com)
Video 2: \\.\DISPLAY2/RADEON 9500 @ 9700 (http://softmod.techpowerup.com) - Secondary
Video 3: \\.\DISPLAYV1/NetMeeting driver
Video 4: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1280,1024) (1280x1024) PRIMARY
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2600.0000
WinEQ: 2.07

Loaded Modules:
-----------------------------------
Module 0: i:\games\warcraft iii official\war3.exe
Module 1: C:\WINDOWS\System32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: C:\WINDOWS\system32\user32.dll
Module 4: C:\WINDOWS\system32\GDI32.dll
Module 5: C:\WINDOWS\system32\ADVAPI32.dll
Module 6: C:\WINDOWS\system32\RPCRT4.dll
Module 7: C:\WINDOWS\system32\comdlg32.dll
Module 8: C:\WINDOWS\system32\SHLWAPI.dll
Module 9: C:\WINDOWS\system32\msvcrt.dll
Module 10: C:\WINDOWS\system32\COMCTL32.dll
Module 11: C:\WINDOWS\system32\SHELL32.dll
Module 12: C:\WINDOWS\System32\winmm.dll
Module 13: i:\games\warcraft iii official\storm.dll
Module 14: C:\WINDOWS\system32\VERSION.dll
Module 15: i:\games\warcraft iii official\mss32.dll
Module 16: C:\WINDOWS\System32\wsock32.dll
Module 17: C:\WINDOWS\System32\WS2_32.dll
Module 18: C:\WINDOWS\System32\WS2HELP.dll
Module 19: C:\WINDOWS\System32\imm32.dll
Module 20: C:\WINDOWS\system32\wininet.dll
Module 21: C:\WINDOWS\system32\CRYPT32.dll
Module 22: C:\WINDOWS\system32\MSASN1.dll
Module 23: C:\WINDOWS\system32\OLEAUT32.dll
Module 24: C:\WINDOWS\system32\OLE32.DLL
Module 25: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a\comctl32.dll
Module 26: C:\Program Files\WinEQ2\WinEQ2.dll
Module 27: C:\WINDOWS\Lavish.dll
Module 28: C:\WINDOWS\System32\PSAPI.DLL
Module 29: C:\Program Files\WinEQ2\WinEQ2-WC3.dll
Module 30: C:\WINDOWS\System32\MSIMG32.dll
Module 31: C:\Program Files\WinEQ2\WinEQ2-Win32I.dll
Module 32: C:\Program Files\WinEQ2\WinEQ2-D3D8.dll
Module 33: C:\Program Files\Google\Google Desktop Search\GoogleDesktopNetwork1.dll
Module 34: C:\WINDOWS\System32\Secur32.dll
Module 35: C:\WINDOWS\system32\mswsock.dll
Module 36: C:\WINDOWS\System32\wshtcpip.dll
Module 37: C:\WINDOWS\System32\DNSAPI.dll
Module 38: C:\WINDOWS\System32\winrnr.dll
Module 39: C:\WINDOWS\system32\WLDAP32.dll
Module 40: C:\WINDOWS\System32\rasadhlp.dll
Module 41: C:\WINDOWS\system32\uxtheme.dll
Module 42: C:\Program Files\WinEQ2\EQPlayNice.dll
Module 43: C:\Program Files\mq2\MQ2Main.dll
Module 44: C:\WINDOWS\System32\MSCTF.dll
Module 45: C:\Program Files\WinPortrait\WinpHook.dll

Win32 Input:
-----------------------------------

Direct3D8:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: (not currently available)
Warcraft III:
-----------------------------------
Profile 1: War3 DOTA
WC3Path: I:\games\Warcraft III Official
Video Adapter: Application Controlled

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

Post by Lax » Wed Mar 16, 2005 4:01 pm

I'll do some testing on this right now

Arghificious
GamingTools Subscriber
Posts: 10
Joined: Sat Jul 17, 2004 11:50 pm

Post by Arghificious » Wed Mar 16, 2005 4:05 pm

Sweet, thanks :)

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

Post by Lax » Sat Mar 19, 2005 8:27 pm

Sorry for the late response.

I'm having successful tests with retail version 1.18, and successful tests with 1.17 before patching it to the latest -- with and without Frozen Throne enabled in the profile.

Is this a clean retail install (aside from maps)? You havent applied any patches such as nocd cracks, etc? Is this updated to the latest, or an older version?

You can also try through Inner Space. Install it, then go into the Games window and expand Warcraft III. Go to Profiles->Warcraft III Default Profile. If you want WC3 to run in windowed mode (like WinEQ does), enable "Force Window" in the General category for the profile. In the Launch category, change the path to the right location for your copy of WC3. It might be automatically detected. IS runs war3.exe directly, so it will use the last expansion settings you had (if you last ran without TFT, it will run without TFT. If you last ran with TFT, it will run with TFT). Then just run WC3 through IS and it should feel just like using WinEQ.

Arghificious
GamingTools Subscriber
Posts: 10
Joined: Sat Jul 17, 2004 11:50 pm

Post by Arghificious » Sun Mar 20, 2005 9:54 am

OK, I'll try it with IS.

It is a clean retail install, I just installed it two weeks ago, actually.

Only patch that I've applied to it is the latest one from b.net.

Arghificious
GamingTools Subscriber
Posts: 10
Joined: Sat Jul 17, 2004 11:50 pm

Post by Arghificious » Sun Mar 20, 2005 9:57 am

It gives me the exact same error with IS as it does with WinEQ2.

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

Post by Lax » Sun Mar 20, 2005 1:32 pm

Okay. Next order of business :)

1. Giving softmod the benefit of the doubt, my assumption is that some software installed on your system must be interfering, or is simply not updated (see #2). Try closing everything else down besides WinEQ or Inner Space, whichever you want to try with (including but not limited to the ones that show up in your modules list -- google desktop search, WinPortrait?, MQ2, though EQPlayNice is fine since its built into WinEQ 2), and see if it happens again.

2. Your windows version is Pre-SP1... is there a reason for that? If it's because of horror stories about SP2 from when it first came out, then your worries are unfounded. Millions of people, including me and my family, run SP2 without any problems. In fact MS is going to stop supporting anyone that wont update their XP to SP2, to my knowledge. That and I've seen people have problems with WinEQ 2 before on XP before SP2 and they seemed to stop after updating.

3. Scan for spyware, etc. MS AntiSpyware is great at this http://www.microsoft.com/downloads/deta ... laylang=en
WinEQ and Inner Space are more vulnerable problems caused by spyware/viruses/etc than other software because they work inside host processes such as EQ and Warcraft 3.

I would be surprised if the above dont solve your problem. I can guarantee that WinEQ and IS work great on a fresh install of Windows XP with SP2, latest drivers, etc. In fact I'll throw an old hard drive in one of my machines here and test XP with no service packs and see what happens

Let me know if you solve the problem or find a software package that causes WinEQ and IS to not work

Arghificious
GamingTools Subscriber
Posts: 10
Joined: Sat Jul 17, 2004 11:50 pm

Post by Arghificious » Sun Mar 20, 2005 2:13 pm

I scan for spyware / viruses every weekend, have none.

I've tried closing everything down except WinEQ and it still gives me the same problem.

My windows version is PreSP1 because it's not an officially licenced copy, and I was under the assumption you have to actually be registered to upgrade to SP1/SP2, and had heard the horror stories about them as well. If this is not the case, I'll try to get a copy and upgrade, and see if that fixes it.

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

Post by Lax » Sun Mar 20, 2005 2:20 pm

With SP1 they had protection against unlicensed copies, but hackers worked around that anyway. While I don't condone piracy, I will tell you that SP2 does not have such a requirement -- there was a lot in the news about that, and the consensus was that there's a LOT of pirated copies of XP, and allowing them to be updated to SP2 for protection against viruses and such is better than not. http://www.pcsympathy.com/article619.html

I highly recommend updating to SP2. On another note, I just completed installing XP Pro retail with no SP on a spare hard drive, and I'll be seeing what happens with WinEQ and IS.

Arghificious
GamingTools Subscriber
Posts: 10
Joined: Sat Jul 17, 2004 11:50 pm

Post by Arghificious » Sun Mar 20, 2005 2:26 pm

OK, thanks a bunch for everything. I'll obtain SP2 and install it and hope that works.

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

Post by Lax » Sun Mar 20, 2005 4:42 pm

With a fresh install where the only things updated are DirectX and NVIDIA drivers (no other driver updates, no windows updates at all, etc), I do get this crash. I'm positive SP2 will fix it, but I'm going to set up a test environment and see if I can fix the problem for non-SP2

Arghificious
GamingTools Subscriber
Posts: 10
Joined: Sat Jul 17, 2004 11:50 pm

Post by Arghificious » Sun Mar 20, 2005 5:16 pm

Ah, OK neat. Isolated what it was at least :) Thanks so much for your continued work on these kickass programs and this specific problem.

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

Post by Lax » Tue Mar 22, 2005 5:21 pm

Unfortunately I am unable to solve this issue for WC3 in particular. It is not friendly to attaching a debugger and there's no other way for me to track down the bug.

Installing SP2 did in fact solve the issue on the test system, and that is the only possible fix for Windows XP at this time.. Grab SP2 and you should be fine.

Post Reply