December 2015
Holly *! It worked. You sir are a saint!
December 2015
@MrKrustenkaese Ah, nice! This had already been suggested, but it's nice to see it confirmed, with a specific link, even
December 2015
December 2015 - last edited December 2015
@GrimWrapper wrote:@MrKrustenkaeseWhat kind of computer do you have? I have a lenovo Yoga 2 pro, so lenovo has its own drivers available for download. I'm not sure if downloading an older driver from intel would damage my machine since lenovo do their own versions. Can someone help me out? If the old drivers would be fine I would download in a heartbeat!
Hi,
i have a Lenovo G50 with Intel Core i3-4030U CPU (1.9 GHz) and 4 GB Ram.
My graphic chip is an Intel HD 4400. Not the best hardware for Kanes Wrath (hard lags when you build more than 100 units) but
for online gaming it works well.
And there are no problems with the old driver...
February 2016
Hi,
I have a lenovo G40 and with the exact same damn error.
I have installed the AMD graphic driver. then after installation, I right-clicked the desktop --> configure switchable graphics --> assigned the 'High Performance' to the CNC KR .exe file and no more errors.
Hope this helps.
Laith
April 2016
same problem help!
May 2016 - last edited May 2016
Thanks for the suggestion lihar1. I had the same issue with an NVIDIA Quadro graphics card on Windows 10. For some reason, per default C&C3KW chooses the Intel HD graphics card an it will crash before running the game. Doing as you suggest (choosing to use the NVIDIA graphics card per default in the NVIDIA Control Panel) solves the problem :-)
June 2016
I'm also having this problem and tried several solutions, with nothing working. I have uninstalled both game and origin, gotten the updates (though I do not know how to update the drivers) and still getting the same error. I have an HP Pavilion 15 Notebook PC with Intel Core i7.
June 2016
Um. Only updating your drivers will solve this issue.
If you don't know how to do that... either get professionals to help you with it, or just google around a bit.
June 2016
I've updated my drivers, gotten the Directx update as well, and I'm still receiving the same error unfortunately.