[Bug 20326] New: Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

Summary: Crash caused by Call of Duty 4 installer (Exception
                    EExternalException in module ntdll.dll)
           Product: Wine
           Version: 1.1.31
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: trivial
          Priority: P3
         Component: ntdll
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Created an attachment (id=24037)
 --> (http://bugs.winehq.org/attachment.cgi?id=24037)
Install log of Call of Duty 4: Modern warfare

Hi, Call of Duty 4: Modern Warfare's installer crashes at the very end. It
means i go through steps:

* Entering key code
 * Accepting the agreement
 * Install punkbuster -> No
 * Choose install type -> Typical
 * Create shortcut on desktop -> No
 * Registration -> No
 * Install DirectX9 -> No
 * Setup has finished, click Finish

and when i click Finish attached crash happens. CoD4 is installed in clean wine
environment and 100% reproducible. Following windows message box is displayed:

"Exception EExternalException in module ntdll.dll at 0002c358. External
exception C0000025."

Wine .31, .30, .29, .28, .26 have same problem (.27 not tested). Wine .25 and
older have other issues and end up with another error a bit sooner.

Even the crash, the game is installed OK, hence low severity/priority.

Unfortunately CoD4 demo does not crash and installs fine.

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

Nikolay Sivov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|ntdll                       |-unknown

--- Comment #1 from Nikolay Sivov   2009-10-11 14:36:42 ---
Your game tries to create ADODB.Command object and fails obviously, try to
install mdac with 'winetricks mdac25'.

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

--- Comment #2 from Wylda   2009-10-11 15:17:49 ---
Created an attachment (id=24039)
 --> (http://bugs.winehq.org/attachment.cgi?id=24039)
Install log of CoD4 with winetricks mdac25

Nikolay, thank you for really quick replay (wow). So in clean wine environment
i run 'winetricks mdac25' and than began to install CoD4. Still crashes, but
that trace is different this time.

Also windows message box says something different:

"Exception EAccessViolation in module ~gs6379.tmp at 00025C70. Access violation
at address 003C5C70in module '~gs6379.tmp'. Read of address 7C730061".

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

Louis Lenders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from Louis Lenders   2009-11-03 17:11:11 ---
(In reply to comment #2)
> Created an attachment (id=24039)

--> (http://bugs.winehq.org/attachment.cgi?id=24039) [details]
> Install log of CoD4 with winetricks mdac25
>
> Nikolay, thank you for really quick replay (wow). So in clean wine environment
> i run 'winetricks mdac25' and than began to install CoD4. Still crashes, but
> that trace is different this time.
>
> Also windows message box says something different:
>
> "Exception EAccessViolation in module ~gs6379.tmp at 00025C70. Access violation
> at address 003C5C70in module '~gs6379.tmp'. Read of address 7C730061".

This might be a duplicate of another bug

Could you try this:

rm -rf ~/.wine/drive_c/windows/system32/user32.dll
rm -rf ~/.wine/drive_c/windows/system32/kernel32.dll

Then see if the app starts up?

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

--- Comment #4 from Wylda   2009-11-03 17:26:52 ---
(In reply to comment #3)
> Could you try this:
>
> rm -rf ~/.wine/drive_c/windows/system32/user32.dll
> rm -rf ~/.wine/drive_c/windows/system32/kernel32.dll
>
> Then see if the app starts up?

Hi Louis, this bug report is not about problem with starting CoD4. In fact it
runs very well _after_instalation_. The reported problem is about last step in
installation -> when you click finish, this crash occur.

Installation was performed in clean wine environment, ie. removed .wine, than
run winecfg. So i do not know, if i catched your idea. Shoud i remove those two
files _after_ winecfg and _before_ wine setup.exe? Thank you for advise.

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

--- Comment #5 from Louis Lenders   2009-11-03 17:28:40 ---
> Shoud i remove those two
> files _after_ winecfg and _before_ wine setup.exe? Thank you for advise.

yes please, to see if this bug is a duplicate of bug #15437

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

--- Comment #6 from Wylda   2009-11-08 11:29:02 ---
Created an attachment (id=24595)
 --> (http://bugs.winehq.org/attachment.cgi?id=24595)
Crash log of CoD4 after clicking FINISH.

(In reply to comment #5)
> yes please, to see if this bug is a duplicate of bug #15437

So i did under current git (wine-1.1.32-402-gde00535):

* rm -rf ~/.wine
 * winecfg
 * rm -rf ~/.wine/drive_c/windows/system32/kernel32.dll
 * rm -rf ~/.wine/drive_c/windows/system32/user32.dll
 * cd /media/COD4MW ; wine setup.exe &> ~/cod4_console_log.txt

Crashed like in comment #0. None winetricks were used.

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

--- Comment #7 from Louis Lenders   2009-11-08 12:27:28 ---
(In reply to comment #6)
> Created an attachment (id=24595)

--> (http://bugs.winehq.org/attachment.cgi?id=24595) [details]
> Crash log of CoD4 after clicking FINISH.
>
> (In reply to comment #5)
> > yes please, to see if this bug is a duplicate of bug #15437
>
> So i did under current git (wine-1.1.32-402-gde00535):
> - rm -rf ~/.wine
> - winecfg
> - rm -rf ~/.wine/drive_c/windows/system32/kernel32.dll
> - rm -rf ~/.wine/drive_c/windows/system32/user32.dll
> - cd /media/COD4MW ; wine setup.exe &> ~/cod4_console_log.txt
>
> Crashed like in comment #0. None winetricks were used.

I meant do it like this:

* rm -rf ~/.wine
 * winetricks mdac28 jet40
 * rm -rf ~/.wine/drive_c/windows/system32/kernel32.dll
 * rm -rf ~/.wine/drive_c/windows/system32/user32.dll

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

Wylda  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #24595|0                           |1
        is obsolete|                            |

--- Comment #8 from Wylda   2009-11-08 15:36:44 ---
Created an attachment (id=24603)
 --> (http://bugs.winehq.org/attachment.cgi?id=24603)
Crash log of CoD4 after clicking FINISH with winetricks mdac28 jet40

(In reply to comment #7)
> I meant do it like this:
> - rm -rf ~/.wine
> - winetricks mdac28 jet40
> - rm -rf ~/.wine/drive_c/windows/system32/kernel32.dll
> - rm -rf ~/.wine/drive_c/windows/system32/user32.dll

Done, but crashes anyway. But i noticed a difference. This time windows error
message pop ups and says "Can't load DLL". Maybe in Windows environment, when
one click Finish, game is run automatically and this for unknown reason (to me)
does not work under wine. New relevant console log attached.

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

--- Comment #9 from Wylda   2009-12-20 10:23:55 ---

Still happens in wine-1.1.35.

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

--- Comment #10 from Wylda   2010-06-19 16:41:08 ---

Still present in wine-1.2-rc4.

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

starslights  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #11 from starslights   2010-06-24 08:43:09 ---
Hello,

I just want to confirm that bug, i run Kubuntu Lucid 10.04 LTS on x86 64,
(Linux xxxxxxxxxxx 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC
2010 x86_64 GNU/Linux
)

using wineHQ 1.2rc4 and i get same error at end of the installation.

By chance it's not a bad bug while it can terminate correctly the install and
the game work really good.

Thanks for all your good work , best regards

Stars

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

Xavier Vachon  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #12 from Xavier Vachon  2010-11-22 19:31:10 CST ---
This is still an issue in git (1.3.7). The messages I get are :

err:ole:dispatch_rpc no apartment found for ipid
{ffffffff-ffff-ffff-1f00-000008000000}
err:rpc:I_RpcReceive we got fault packet with status 0x80010108
err:ole:dispatch_rpc no apartment found for ipid
{ffffffff-ffff-ffff-1f00-000008000000}
err:rpc:I_RpcReceive we got fault packet with status 0x80010108
err:ole:dispatch_rpc no apartment found for ipid
{ffffffff-ffff-ffff-1f00-000008000000}
err:rpc:I_RpcReceive we got fault packet with status 0x80010108
err:ole:dispatch_rpc no apartment found for ipid
{ffffffff-ffff-ffff-1f00-000008000000}
err:rpc:I_RpcReceive we got fault packet with status 0x80010108
err:ole:dispatch_rpc no apartment found for ipid
{ffffffff-ffff-ffff-1f00-000008000000}
err:rpc:I_RpcReceive we got fault packet with status 0x80010108
err:ole:CoGetClassObject class {00000507-0000-0010-8000-00aa006d2ea4} not
registered
err:ole:create_server class {00000507-0000-0010-8000-00aa006d2ea4} not
registered
err:ole:CoGetClassObject no class object {00000507-0000-0010-8000-00aa006d2ea4}
could be created for context 0x5
wine: Unhandled exception 0x0eedfade at address 0x0000:0x7edaa9c2 (thread
0034), starting debugger...

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

Wylda  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #13 from Wylda  2011-06-25 05:33:28 CDT ---
*** Bug 26394 has been marked as a duplicate of this bug. ***

[Bug 20326] Crash caused by Call of Duty 4 installer (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

Wylda  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #14 from Wylda  2011-06-28 04:14:13 CDT ---
*** Bug 27626 has been marked as a duplicate of this bug. ***

[Bug 20326] Call of Duty 4: Installer crashes at the end (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

Wylda  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Crash caused by Call of     |Call of Duty 4: Installer
                   |Duty 4 installer (Exception |crashes at the end
                   |EExternalException in       |(Exception
                   |module ntdll.dll)           |EExternalException in
                   |                            |module ntdll.dll)

[Bug 20326] Call of Duty 4: Installer crashes at the end (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

--- Comment #15 from Diego Viola  2011-06-28 16:35:20 CDT ---
I have the same error with Wine 1.3.23, Linux 2.6.39, Arch Linux x86-64, nvidia
drivers 275.09.07-1.

The game runs great but when install is done, it gives me the same error the
original reporter mentioned. I also noticed the same "ISBEW64.exe" error when
trying to uninstall the game with 'wine uninstaller'.

[Bug 20326] Call of Duty 4: Installer crashes at the end (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

--- Comment #16 from Wylda  2012-05-05 02:14:42 CDT ---

Still present in wine-1.5.3-164-gdec3d50.

[Bug 20326] Call of Duty 4: Installer crashes at the end (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

Brandon Corujo  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 20326] Call of Duty 4: Installer crashes at the end (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[e-mail]
         Resolution|                            |DUPLICATE
           Severity|trivial                     |minor

--- Comment #17 from Anastasius Focht  2013-05-03 15:33:42 CDT ---
Hello folks,

fortunately there is still a "backup" available from some "online archive" so I
looked into the installer...

The first thing has already been mentioned: Microsoft Data Access Components
(MDAC)

You need 'winetricks -q mdac28' in clean WINEPREFIX.

The installer spawns the following process as part of post-installation:

--- snip ---
...
0028:trace:process:create_process_impl starting L"E:\setup\rsrc\cod4.exe" as
Win32 binary (0x400000-0xa12000)
0047:trace:loaddll:load_builtin_dll Loaded L"KERNEL32.dll" at 0x7b810000:
builtin
0047:trace:process:init_current_directory starting in L"E:\setup\rsrc\"
(nil)
0047:trace:process:__wine_kernel_init starting process
name=L"E:\setup\rsrc\cod4.exe" argv[0]=L"E:\setup\rsrc\cod4.exe"
0047:trace:loaddll:load_native_dll Loaded L"E:\setup\rsrc\cod4.exe" at
0x400000: native
0028:trace:process:create_process_impl started process pid 0046 tid 0047 
...
0047:err:ole:CoGetClassObject class {00000507-0000-0010-8000-00aa006d2ea4} not
registered
0047:err:ole:create_server class {00000507-0000-0010-8000-00aa006d2ea4} not
registered
0047:err:ole:CoGetClassObject no class object
{00000507-0000-0010-8000-00aa006d2ea4} could be created for context 0x5
0047:trace:seh:raise_exception code=eedfade flags=1 addr=0x7b83aad3 ip=7b83aad3
tid=0047
0047:trace:seh:raise_exception  info[0]=0057de3f
0047:trace:seh:raise_exception  info[1]=00b40d2c
0047:trace:seh:raise_exception  info[2]=006eb394
0047:trace:seh:raise_exception  info[3]=0033f8f4
0047:trace:seh:raise_exception  info[4]=00000000
0047:trace:seh:raise_exception  info[5]=0033f8c8
0047:trace:seh:raise_exception  info[6]=0033f8bc
0047:trace:seh:raise_exception  eax=7b826891 ebx=7b8b96b0 ecx=0033f8bc
edx=0033f850 esi=0033f8f4 edi=00000000 
--- snip ---

GUID "{00000507-0000-0010-8000-00aa006d2ea4}" followed by Delphi external
exception code "0xeedfade" is something not to be ignored -> MDAC.

Anyway ... the next crashes are related to madCodeHook Delphi library -> bug
15437
Louis was right on track.

The executable is wrapped with UPX and there are typical madCodeHook Delphi
library sequences present after unpacking.

Additional proof via trace log:

--- snip ---
...
0024:Call KERNEL32.CreateFileW(0018f640
L"C:\windows\system32\KERNEL32.dll",80000000,00000001,00000000,00000003,00000000,00000000)
ret=0315fa8a
0024:Ret  KERNEL32.CreateFileW() retval=000000e8 ret=0315fa8a 
...
0024:Call
KERNEL32.CreateFileMappingW(000000e8,00000000,00000002,00000000,00000000,00000000)
ret=0315fae6
0024:Ret  KERNEL32.CreateFileMappingW() retval=000000ec ret=0315fae6
0024:Call KERNEL32.MapViewOfFile(000000ec,00000004,00000000,00000000,00000000)
ret=0315fb0e
0024:Ret  KERNEL32.MapViewOfFile() retval=03280000 ret=0315fb0e
0024:Call KERNEL32.CloseHandle(000000ec) ret=0315fb16
0024:Ret  KERNEL32.CloseHandle() retval=00000001 ret=0315fb16
0024:Call KERNEL32.CloseHandle(000000e8) ret=0315fb1c
0024:Ret  KERNEL32.CloseHandle() retval=00000001 ret=0315fb1c 
...
0024:trace:seh:raise_exception code=c0000005 flags=0 addr=0x315fc5a ip=0315fc5a
tid=0024
0024:trace:seh:raise_exception  info[0]=00000000
0024:trace:seh:raise_exception  info[1]=03329994
0024:trace:seh:raise_exception  eax=03329978 ebx=7b810000 ecx=00000001
edx=000a9978 esi=7b810040 edi=03280000
0024:trace:seh:raise_exception  ebp=03329978 esp=0032f490 cs=0023 ds=002b
es=002b fs=0063 gs=006b flags=00010206
0024:trace:seh:call_stack_handlers calling handler at 0x316b605 code=c0000005
flags=0
0024:trace:seh:call_stack_handlers handler at 0x316b605 returned 1
0024:trace:seh:call_stack_handlers calling handler at 0x3143db8 code=c0000005
flags=0
0024:Call KERNEL32.UnhandledExceptionFilter(0032ef70) ret=03143ddc 
...
--- snip ---

Removing Wine's "kernel32.dll" placeholder:

--- snip ---
0024:Call KERNEL32.CreateFileW(0018f640
L"C:\windows\system32\KERNEL32.dll",80000000,00000001,00000000,00000003,00000000,00000000)
ret=0315fa8a
0024:Ret  KERNEL32.CreateFileW() retval=ffffffff ret=0315fa8a 
...
0024:Call KERNEL32.OpenFileMappingW(000f001f,00000000,03180d98
L"Global\NamedBuffer, mix, Process $00000023, API $7b810000") ret=031657c1
0024:Ret  KERNEL32.OpenFileMappingW() retval=00000000 ret=031657c1
0024:Call KERNEL32.OpenFileMappingW(000f001f,00000000,03180e5c L"NamedBuffer,
mix, Process $00000023, API $7b810000") ret=031657ea
0024:Ret  KERNEL32.OpenFileMappingW() retval=00000000 ret=031657ea 
...
0024:Call KERNEL32.OpenFileMappingW(00000004,00000000,03180d98
L"Global\NamedBuffer, mAH, Process $00000023, API $7b810000") ret=031657c1
0024:Ret  KERNEL32.OpenFileMappingW() retval=00000000 ret=031657c1
0024:Call KERNEL32.OpenFileMappingW(00000004,00000000,03180e5c L"NamedBuffer,
mAH, Process $00000023, API $7b810000") ret=031657ea
0024:Ret  KERNEL32.OpenFileMappingW() retval=00000000 ret=031657ea 
...
0024:Call KERNEL32.CreateFileW(0018f640
L"C:\windows\system32\user32.dll",80000000,00000001,00000000,00000003,00000000,00000000)
ret=0063cbae
0024:Ret  KERNEL32.CreateFileW() retval=000000f4 ret=0063cbae 
...
0024:Call
KERNEL32.CreateFileMappingW(000000f4,00000000,00000002,00000000,00000000,00000000)
ret=0063cc0a
0024:Ret  KERNEL32.CreateFileMappingW() retval=000000f8 ret=0063cc0a
0024:Call KERNEL32.MapViewOfFile(000000f8,00000004,00000000,00000000,00000000)
ret=0063cc32
0024:Ret  KERNEL32.MapViewOfFile() retval=03280000 ret=0063cc32
0024:Call KERNEL32.CloseHandle(000000f8) ret=0063cc3a
0024:Ret  KERNEL32.CloseHandle() retval=00000001 ret=0063cc3a
0024:Call KERNEL32.CloseHandle(000000f4) ret=0063cc40
0024:Ret  KERNEL32.CloseHandle() retval=00000001 ret=0063cc40 
...
0024:trace:seh:raise_exception code=c0000005 flags=0 addr=0x63cd7e ip=0063cd7e
tid=0024
0024:trace:seh:raise_exception  info[0]=00000000
0024:trace:seh:raise_exception  info[1]=033709f4
0024:trace:seh:raise_exception  eax=033709d8 ebx=7eab0000 ecx=00000001
edx=000f09d8 esi=7eab0040 edi=03280000
0024:trace:seh:raise_exception  ebp=033709d8 esp=0032f8c4 cs=0023 ds=002b
es=002b fs=0063 gs=006b flags=00210206
0024:trace:seh:call_stack_handlers calling handler at 0x648729 code=c0000005
flags=0 
--- snip ---

Again - even if this has already been said multiple times in this bug (it seems
people still messed this up):

1) clean (new) 32-bit WINEPREFIX
2) 'bash winetricks -q mdac28'
3) rm -f $WINEPREFIX/drive_c/windows/system32/kernel32.dll
4) rm -f $WINEPREFIX/drive_c/windows/system32/user32.dll

$WINEPREFIX -> ~/.wine if default is used, otherwise make sure you delete it
from the right one where the game is installed!

If you are installing in 64-bit WINEPREFIX make sure you remove the _right_
placeholders!
32-bit kernel/user placefolder dlls live in "syswow64", "system32" is for
64-bit.

With that steps I got successfully into main menu right after installation.
There is nothing to fix here and it's really a dupe of bug 15437

Regards

*** This bug has been marked as a duplicate of bug 15437 ***

[Bug 20326] Call of Duty 4: Installer crashes at the end (Exception EExternalException in module ntdll.dll)

http://bugs.winehq.org/show_bug.cgi?id=20326

Bruno Jesus  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #18 from Bruno Jesus  2013-05-06 09:10:17 CDT ---
Closing duplicate.