Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
2005 (x86, x64), 2008 (x86, x64), 2010 (x86, x64), 2012 (x86, x64) and finally 2013 (x86 and x64). Or did I miss anything?
Please include a description of your problem, a DxDiag.txt. and a link to this thread within the mail.
To create the DxDiag.txt, please do the following:
Click "Start" button and choose "Run". Or alternatively, press (Windows-Button)+R.
Then type "dxdiag" (without quotation marks) and click Ok.
You will find all relevant information in the following window.
Click the "Save all Information" button, located at the bottom of the program window.
Save the file as "dxdiag.txt".
Attach the file "dxdiag.txt" with your E-mail reply.
Thank you very much for your assistance.
> 'cmd' > 'sfc /scannow' couldn't find anything.
> Windows repair installation by booting from the DVD didn't find anything either.
> Deinstalling various Windows Updates wouldn't help either.
> 'Dependency Walker''s results were inconclusive.
So, here's the solution, but let me explain. While playing with 'Dependency Walker' I found that *all* Software, running or not, had at least some minor issues, like this:
--
Started "TROPICO4.EXE" (process 0x1BB0) at address 0x0000000000400000. Cannot hook module.
Loaded "NTDLL.DLL" at address 0x0000000077B00000. Cannot hook module.
Loaded "NTDLL32.DLL" at address 0x0000000077CE0000. Cannot hook module.
Loaded "WOW64.DLL" at address 0x0000000075680000. Cannot hook module.
Loaded "WOW64WIN.DLL" at address 0x0000000075620000. Cannot hook module.
Loaded "WOW64CPU.DLL" at address 0x0000000075610000. Cannot hook module.
Entrypoint reached. All implicit modules have been loaded.
Loaded "WOW64_IMAGE_SECTION" at address 0x00000000779E0000. Cannot hook module.
Unloaded "WOW64_IMAGE_SECTION" at address 0x00000000779E0000.
Loaded "WOW64_IMAGE_SECTION" at address 0x0000000076F50000. Cannot hook module.
Unloaded "WOW64_IMAGE_SECTION" at address 0x0000000076F50000.
Loaded "NOT_AN_IMAGE" at address 0x00000000779E0000. Cannot hook module.
Unloaded "NOT_AN_IMAGE" at address 0x00000000779E0000.
Loaded "NOT_AN_IMAGE" at address 0x00000000778E0000. Cannot hook module.
Unloaded "NOT_AN_IMAGE" at address 0x00000000778E0000.
Error reading KERNEL32.DLL's export table. Function call tracking may not work properly.
Loaded "KERNEL32.DLL" at address 0x0000000076F50000. Cannot hook module.
Loaded "KERNELBASE.DLL" at address 0x0000000076D90000. Cannot hook module.
Exited "TROPICO4.EXE" (process 0x1BB0) with code -2147483645 (0x80000003).
--
What's important is this: This is fine. The error was caused by a faulty DirectX file inside Windows\SysWOW64. Despite re-installing DirectX a few times, the setup would not (as I noticed) change any files inside that directory. Additionally there is no possibility in Windows 7 to 'repair' an installation of DirectX. The only thing one can do is install it again and again, maybe from different sources.
So I got brave - and deleted every d3d9_xx.dll and d3d10_xx.dll as well as xinput1_x.dll and the d3dcompiler_42.dll inside the Windows\SysWOW64 directory, for they were outdated either way and I got nothing to lose. Without rebooting (!) I then ran the well-known dxwebsetup.exe. The setup then proceeded to install DirectX as if it has never been installed before - et voilà! Tropico now runs like a charm again.
What's weird is that other games which also need DirectX did not complain about anything. But... Oh, well. It works. Phew. And I really do hope that some of my 'proposed solutions' will help other people fix the 0xc000007b error. May this be the 'wisdom of the ancients'. (see http://xkcd.com/979/)