I can remember when I first downloaded the mod I ended up having all sorts of DLL errors, I went to microsoft and downloaded the C++ redistributable package. That fixed my issues.
Might be worth a try
You need to be a member in order to leave a comment
Already have an account? Sign in here.
Sign In NowSign up for a new account in our community. It's easy!
Register a new accountThere are 36 replies in this Thread. The last Post () by Martind Forlon.
I can remember when I first downloaded the mod I ended up having all sorts of DLL errors, I went to microsoft and downloaded the C++ redistributable package. That fixed my issues.
Might be worth a try
yeah, you shouldnt expect a microsoft game run on a microsoft OS
Same problem
Clear crossfire 2.0
23:18:32.863 --> [i]:Prepare Crossfire Start
23:18:33.525 --> [i]:Starting Crossfire
23:18:34.546 --> [i]:Crossfire is running
23:21:34.088 --> [x]:Crossfire Exit - CODE0
23:21:34.401 --> [i]:Crossfire was closed
Update
23:21:38.267 --> [i]:Starting Update...
23:23:41.687 --> [i]:Prepare Crossfire Start
23:23:42.398 --> [i]:Starting Crossfire
23:23:42.909 --> [i]:Crossfire is running
23:23:44.399 --> [x]:Crossfire Crash Exit - CODE ffffffffc06d007e [E000000D3]
23:23:46.030 --> [i]:Crossfire was closed
23:23:55.281 --> [i]:Starting Update...
23:24:03.574 --> [i]:Prepare Crossfire Start
23:24:04.247 --> [i]:Starting Crossfire
23:24:04.725 --> [i]:Crossfire is running
23:24:06.089 --> [x]:Crossfire Crash Exit - CODE ffffffffc06d007e [E000000D3]
23:24:06.329 --> [i]:Crossfire was closed
probably even the same solution
Remove d3d11.dll from folder EXE after update and run without updating
in that case you can also switch to the vanilla FL shader
because removing that file will disable the other shaders
Switching to vanila FL sharders doens't help. Only deleteing.
Hello Everyone,
i think, i have found the solution for the Crossfire Crash Exit - CODE ffffffffc06d007e [E000000D3]:
The reason ist the Windows 10 Fall-Update to 1809 Version. I've reinstalled Windows 10 on my PC and I'd use a 1809-Iso for that. After installation of CF the Loader crashed with this fault message. On my "old" Windows-Version 1803 it was running fine on my pc, but stillI've tried out everything, whats suggested here with no access, but the suggestion of SWAT_OP-R8R brought me on the right way, I've reinstalled Windows 10, but Version 1803 this time and CF worked right away.
Now I've found the post of foma with the "kernelbase.dll" and i checked the Version numbers, - the working one is the one of 1803!!
The bad thing of this is the force of MS to update Win10. I guess, you can stop it for only 4 weeks then probably the new "kernelbase.dll" will be back on your pc and the loader crash again...
you will find the working kernelbase-File in the attachment, i hope it helps KernelBase.zip
the latest windows updates pretty much all have errors... up to the point where windows deletes personal files
it is strange that such huge mistakes happen... especially with such a wide spread beta test
its not a good idea to exchange the kernelbase.dll file. Its is integral part of windows and only changing of this dll might bring other problems.
... but if it helps to fun CF you can ignore all the problems and side effects (just saying - you have to set priorities)
Yeah, at least temporarily until microsoft penguins find the fixes
Can confirm the issue for me is Windows 1809 update. CF was working perfectly 2 days ago, only change since then was the update and now if fails with
ffffffffc06d007e.
Reinstalled on 1803 and CF works perfectly. Thanks Windows...
Got the same issue.
Yes, window updates like to mess things up, see posts above.
I have the same problem, so what is the most practical solution that doesn't compromise my Windows OS?
Thanks.
Crossfire + Windows 10 build 1809
please read through thread how to "force" launcher update and chose vanila shader in launcher options.