Command & Conquer

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="CNC4.game" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="dbghelp.dll" SIZE="1030144" CHECKSUM="0xC9CCA318" BIN_FILE_VERSION="6.6.7.5" BIN_PRODUCT_VERSION="6.6.7.5" PRODUCT_VERSION="6.6.0007.5" FILE_DESCRIPTION="Windows Image Helper" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Debugging Tools for Windows(R)" FILE_VERSION="6.6.0007.5 (debuggers(dbg).051021-1446)" ORIGINAL_FILENAME="DBGHELP.DLL" INTERNAL_NAME="DBGHELP.DLL" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFF021" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.6.7.5" UPTO_BIN_PRODUCT_VERSION="6.6.7.5" LINK_DATE="07/08/2006 20:11:32" UPTO_LINK_DATE="07/08/2006 20:11:32" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="libsndfile-1.dll" SIZE="325120" CHECKSUM="0x3F42E87C" MODULE_TYPE="WIN32" PE_CHECKSUM="0x57DF6" LINKER_VERSION="0x10000" LINK_DATE="08/31/2006 11:35:29" UPTO_LINK_DATE="08/31/2006 11:35:29" />
<MATCHING_FILE NAME="ortp.dll" SIZE="290816" CHECKSUM="0xE18F63E0" MODULE_TYPE="WIN32" PE_CHECKSUM="0x4A47E" LINKER_VERSION="0x0" LINK_DATE="09/04/2009 14:25:09" UPTO_LINK_DATE="09/04/2009 14:25:09" />
<MATCHING_FILE NAME="vivoxoal.dll" SIZE="339968" CHECKSUM="0x10D6E28B" MODULE_TYPE="WIN32" PE_CHECKSUM="0x54A07" LINKER_VERSION="0x10008" LINK_DATE="09/04/2009 14:27:54" UPTO_LINK_DATE="09/04/2009 14:27:54" />
<MATCHING_FILE NAME="vivoxplatform.dll" SIZE="1400832" CHECKSUM="0x20CD328F" MODULE_TYPE="WIN32" PE_CHECKSUM="0x159DB0" LINKER_VERSION="0x0" LINK_DATE="09/04/2009 14:36:05" UPTO_LINK_DATE="09/04/2009 14:36:05" />
<MATCHING_FILE NAME="vivoxsdk.dll" SIZE="7401472" CHECKSUM="0xFAB5783D" BIN_FILE_VERSION="3.0.6.7278" BIN_PRODUCT_VERSION="3.0.6.7278" PRODUCT_VERSION="3, 0, 0006, 7278" FILE_DESCRIPTION="Vivox Communications API" COMPANY_NAME="Vivox Inc." PRODUCT_NAME="Vivox SDK 3.0" FILE_VERSION="3, 0, 0006, 7278" ORIGINAL_FILENAME="vivoxsdk.dll" INTERNAL_NAME="sdk" LEGAL_COPYRIGHT="Copyright (C) ..." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x71C9D0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="3.0.6.7278" UPTO_BIN_PRODUCT_VERSION="3.0.6.7278" LINK_DATE="09/04/2009 14:35:57" UPTO_LINK_DATE="09/04/2009 14:35:57" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="xinput1_3.dll" SIZE="81768" CHECKSUM="0xFBA3232C" BIN_FILE_VERSION="9.18.944.0" BIN_PRODUCT_VERSION="9.18.944.0" PRODUCT_VERSION="9.18.944.0000" FILE_DESCRIPTION="Microsoft Common Controller API" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® DirectX for Windows®" FILE_VERSION="9.18.944.0000" ORIGINAL_FILENAME="XInput1_3.dll" INTERNAL_NAME="XInput" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1A809" LINKER_VERSION="0x50002" UPTO_BIN_FILE_VERSION="9.18.944.0" UPTO_BIN_PRODUCT_VERSION="9.18.944.0" LINK_DATE="04/05/2007 01:39:01" UPTO_LINK_DATE="04/05/2007 01:39:01" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="zlib1.dll" SIZE="59904" CHECKSUM="0x7697A3DC" BIN_FILE_VERSION="1.2.3.0" BIN_PRODUCT_VERSION="1.2.3.0" PRODUCT_VERSION="1.2.3" FILE_DESCRIPTION="zlib data compression library" PRODUCT_NAME="zlib" FILE_VERSION="1.2.3" ORIGINAL_FILENAME="zlib1.dll" INTERNAL_NAME="zlib1.dll" LEGAL_COPYRIGHT="(C) 1995-2004 Jean-loup Gailly &amp; Mark Adler" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF587" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2.3.0" UPTO_BIN_PRODUCT_VERSION="1.2.3.0" LINK_DATE="07/20/2005 09:48:10" UPTO_LINK_DATE="07/20/2005 09:48:10" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="989696" CHECKSUM="0x2D998938" BIN_FILE_VERSION="5.1.2600.5781" BIN_PRODUCT_VERSION="5.1.2600.5781" PRODUCT_VERSION="5.1.2600.5781" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.5781 (xpsp_sp3_gdr.090321-1317)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFE572" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5781" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5781" LINK_DATE="03/21/2009 14:06:58" UPTO_LINK_DATE="03/21/2009 14:06:58" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>


Now it crashed right after loading the autosave.

Try lowering the Graphics detail if you have it on Ultra, as it is very different in terms of resources it usess than RA3, knock it down to medium and see if it helps.

Thanks for the response. I've tried it already and it didn't help. I saved the game just before the crash and now I can reproduce it quickly anytime. I'm now trying to install Win 7 on a separate hard-drive. When it crashes the cnc4.game process does have only 1 GB of memory allocated and I have 2 GB of ram so it shouldn't be a problem. I'll try it in win7 and then again in win xp with the lowest settings (resolution and detail) and I hope it will work. I can only hope.

Does it happen in that one specific mission? Or any old skirmish or online game will crash too?

I've played only some online co-op, that was ok. I've experienced it in solo, because I play solo mostly, so I can't confirm if it crashes also in online match. I was now able to complete this mission on Win 7. I've installed Windows 7 32bit, the latest nvidia drivers, sb-audigy drivers, CnC4 and completed the mission. So it was probably something in Win XP, some cpmponent, driver or codec I don't know.

And I can play on full resolution ultra-high details - antialiasing level 3. I'm glad it works under Win 7 and I can just play.

It sounds like a video driver having an issue with one of the shaders used.

But good to see you got things sorted, even though it took a lot.

i´m just wondering HOW you updated your graphic-drivers.
did you uninstall the old ones first, BEFORE you installed the new drivers?

there is no need to. The new driver software removes the old driver version when you reboot your pc. the new drivers then kick in when windows restarts

Yeah that is correct. I have Nvidia GPU graphics driver and when I want to check for updates I use this link. There I click on option 2 automatic which in a few seconds checks to see if I have the latest driver on my computer, and if not then a downloader and installer appears where it's an easy process to update if needed, then after an install you must do a restart.
http://www.nvidia.com/Download/index.aspx

that´s not correct.
if you want to update your drivers, you have to do it on the right way.
if you just download and install the new drivers without uninstalling the old ones, then the registry-keys of the new and the old drivers will overmatch, even if the new drivers remove the files of the old drivers after rebooting the PC, the registry-keys of the old drivers will stay in the regsitry.
that could cause a bluescreen (not always) or graphic-issues in games.
i know that link of nVidia and of course it´s easier just to press the "check for updates"-button but i can´t recommend this for a complete driverupdate.
believe me guys, i know about this. i "work" since 2 years in this business and i have a lot of experience with driverupdates.
i had this problem with overmatched drivers 1 year ago, and i got a bluescreen in my games.

the correct way for a driverupdate is:
1. download the new drivers. (don´t install it!)
2. uninstall the old drivers in ----Control Panel-----SOFTWARE
3. clean the registry with a cleaner (Ccleaner or Window Registry Reair 2.0)
4.defrag the Systempartition (Auslogics Disk Defrag is much more thorough than the programm of windows)
5. install the new drivers
6. reboot the PC

Apt I can't recommend uninstalling old drivers unless they were the original drivers that came with the motherboard, or are a good few years old.

and why?

People asking for help are often unsure of what they are doing, and driver updates are built to replace the previous one already.