The Launcher Issue Thread
 

Hello every one.

There has been alot of problems with this game in terms of the launcher.exe stopping when the game is launched. Some of this has gone unresolved for some, and some has been solved by simple fixes.

Ive been suffering from this ever since I bought and downloaded the game. Even with the patch installed the game still doesnt launch up.

Ive:

Uninstalled the game,

reinstalled several times

Verified Cahce several times

reinstalled the redist programs

uninstalled old graphics drivers and installed the 270. beta drivers

installed a UBI Game launcher utility which didn't work

uninstalled and reinstalled DirectX

Moved the CONF files into the 1CSoft folder and didn't solve the problem.

Ive tried near enough every thing. Can any one suggest any other solutions for me please?

And every one please SHARE your solutions here! We need to compile this info into one if possible.

With out further due, My system specs:

Default BIOS
Intel Core 2 Duo E6750 Processor @ 2.66GHz x2 ~ 2.7GHz
3072MB RAM
Windows 7 Home Premium 64bit
MSI N460GTX 1GB Cyclone ed. OC'd @ 270. Beta Drivers

Exactly the same on my PC with a GTX 470. I can access the menu screens if I exit the launcher error message, but cannot change any settings. Starting a mission revives the launcher error message. My old PC with a GTX 275 runs the game OK! Very annoying.

Ok, one thing to do is run the Windows Event Viewer and locate your Launcher.exe crash. And log its report in this thread:

Faulting application name: Launcher.exe_Launcher, version: 1.0.0.0, time stamp: 0x4d6e3d08
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf
Exception code: 0xc06d007e
Fault offset: 0x0000b727
Faulting process id: 0x23a8
Faulting application start time: 0x01cbf076271eadf8
Faulting application path: c:\program files (x86)\steam\steamapps\common\il-2 sturmovik cliffs of dover\Launcher.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 7e2fb55b-5c69-11e0-8a81-0019665bc20a

So my fault is with the KERNELBASE.dll, I guess?

Nice initiative. I'm absolutely clueless around the Event Viewer though, could you give me any directions on where I'm most likely to find the Launcher crash?

Launcher only crashes whenever I change Video settings requiring a restart. The only other problem I had was after installing the beta patch when it would crash before the menu even came up.

Crashes like this are sometimes attributable to overall system stability. A CPU or GPU overclock can seem like it's running stable and not crash until something specific stresses one of them. For me I have an i5-750 2.66ghz overclocked to 3.8ghz and it runs quite stable in demanding games but crashes during an ffmpeg decode so I have to reboot at stock to get it to work, (at least until I find the appropriate voltage or memory timings).

It's definitely hard to sacrifice a good overclock for a game that shouldn't need it as much as CoD does but at least it can help you eliminate the o/c as a culprit. Even stock speeds on some systems can be unstable depending on other bios settings so an underclock can help diagnose whether that's the issue.

Of course the instabilities really need to be addressed on the developer's end.

.net


Application: Launcher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at XLAND.W_LinearObjectManager..ctor(Int32)
at vGtSsMOhuSY3FEB7oGM.ODo1i7O0lnkdDVLJJvc.Te7LZF1ip( EYTQ29yiVTsZdDOgFMx.uMda2qyLbjb0GsKMGvu, Int32[])
at qjp7jtFx7FSx9oCCMJT.8qG05pFGNbgFyKaRVAE.FU2RAjaDNp 7MPa4Kojui(System.Object, System.Object)
at qjp7jtFx7FSx9oCCMJT.8qG05pFGNbgFyKaRVAE.createStep (5FxXUsIC1GM5vyvExl)
at qjp7jtFx7FSx9oCCMJT.8qG05pFGNbgFyKaRVAE+o5qrQZFL7q arLXvw9fU.kd3DavaDd8LsJL17IERO(System.Object, 5FxXUsIC1GM5vyvExl)
at qjp7jtFx7FSx9oCCMJT.8qG05pFGNbgFyKaRVAE+o5qrQZFL7q arLXvw9fU.vhg4FiZqhB(CA38LNo90lC3KnsOQAK.NN1luLoFc GvncfEdYwF)
at U2halPsiTkXERr5pFMn.11EpI9sLBepUZHZtJxj.cPMPKbw0K( EYTQ29yiVTsZdDOgFMx.uMda2qyLbjb0GsKMGvu)
at U2halPsiTkXERr5pFMn.11EpI9sLBepUZHZtJxj.S5BP2xEJ18 NUMJJncbc(System.Object)
at U2halPsiTkXERr5pFMn.11EpI9sLBepUZHZtJxj.BWVOOM6uZ( EYTQ29yiVTsZdDOgFMx.uMda2qyLbjb0GsKMGvu)
at U2halPsiTkXERr5pFMn.11EpI9sLBepUZHZtJxj.TXbpUTTJ5( EYTQ29yiVTsZdDOgFMx.uMda2qyLbjb0GsKMGvu)
at U2halPsiTkXERr5pFMn.11EpI9sLBepUZHZtJxj.huIZBtfKiW PUmLbsvnC(System.Object)
at U2halPsiTkXERr5pFMn.11EpI9sLBepUZHZtJxj.Ev7eqColN( System.String)
at 3j4uLN4HQG4t0yHxjwp.WTFjvZ4MKNNhCZmqZCx.a1detCviAY CN6gXXeksj(System.Object)
at 3j4uLN4HQG4t0yHxjwp.WTFjvZ4MKNNhCZmqZCx.MissionLoa d(System.String)
at moI6xodR5RLIqMOVNeD.1mea88dgIVnoinHMbYV.jJWkE548os 45tV1OTCFo(System.Object, System.Object)
at moI6xodR5RLIqMOVNeD.1mea88dgIVnoinHMbYV.mxDl13myH( )
at System.Threading.ThreadHelper.ThreadStart_Context( System.Object)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()


application

Faulting application name: Launcher.exe_Launcher, version: 1.0.0.0, time stamp: 0x4d6e3d08
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0b115cb8
Faulting process id: 0xb54
Faulting application start time: 0x01cbf7fecaa3b69e
Faulting application path: f:\program files (x86)\steam\steamapps\common\il-2 sturmovik cliffs of dover\Launcher.exe
Faulting module path: unknown
Report Id: 60c538ef-63f2-11e0-a4cd-001b2152d602




Faulting application name: Launcher.exe_Launcher, version: 1.0.0.0, time stamp: 0x4d6e3d08
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0c22f7a0
Faulting process id: 0xfe4
Faulting application start time: 0x01cbf7ff29a8561b
Faulting application path: f:\program files (x86)\steam\steamapps\common\il-2 sturmovik cliffs of dover\Launcher.exe
Faulting module path: unknown
Report Id: 8e3662a2-63f2-11e0-a4cd-001b2152d602





Faulting application name: Launcher.exe_Launcher, version: 1.0.0.0, time stamp: 0x4d6e3d08
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0ea12368
Faulting process id: 0xc38
Faulting application start time: 0x01cbf7ff63f71e3f
Faulting application path: f:\program files (x86)\steam\steamapps\common\il-2 sturmovik cliffs of dover\Launcher.exe
Faulting module path: unknown
Report Id: d0d639dd-63f2-11e0-a4cd-001b2152d602






do users really need the DotNetFX40 Full ie the full redist package? (I'm not saying go out and get it... I'm only asking a question)

because the only version I have on my machine is the Client version which came with the COD install disc

Gents, Its coming to conclusion some of the Launcher problems relate to whether your PC is fully up to date. I have a Windows 7 SP1 to install but I am un able due to a deep down virus on my system.

If your desperate, look to see if you have any updates, update as nessary or reinstall your OS. I need to due to I get alot of BSOD for no reason. I even get it when I try to install DCS: BS too :(

So im gunna try that and see the Result Thursday / Firday

Hi

I have the same problem.
I bought the game (DVD version). Even with the patch installed the game still doesnt launch up.
The game crashe at the beginning without error message.
Help !!!

My computer :
Notebook Asus G73Jh
Intel Core i7 CPU - Q720 @1.60GHz
8 Go RAM
Win 7 SP1 64 Bits
ATI HD 5870 1 Go
DirectX 11

fully updated here, including the security update for the .Net 4 Client

I updated my system to SP1 on Win 7, game runs now. Got FPS trouble but I expected that.

Finally sorted for me :grin:

Go to 1C SoftClub/il-2 sturmovik cliffs of dover, delete everything except the cache folder, go to cache folder, delete everything except shaders folder, go to shaders folder, delete all contents.

Open steam, et voila, CoD runs!

Congrats unreasonable, enjoy the game :)

My fix
 

I was also getting the "KERNELBASE.dll" message.

In my case the problem was with the Microsoft .NET Framework 4 Client Profile. Windows 7.

I went for an uninstall of Microsoft .NET Framework 4 Client Profile. It gave me the option to repair and so I did, all this in the control panel "programs" part.
It took a while but finally gave the repaired finished message.

I went to "windows update" and found a security update of about 23 MB for
the Microsoft .NET Framework 4 Client Profile, went through it and finally the game is running.

Salutes Majo

I have the launcher issue and none of the solutions posted so far have resolved my problem.

any more ideas ?

This thread has 5 pages of sarcastic dwelling on many solutions and issues, maybe one of them might do the trick for you: http://forum.1cpublishing.eu/showthread.php?t=21055

Good luck!

I'm getting kernelbase as the reason too, but I am running win7 service pack 1...

Any suggestions?

Source: .NET runtime
Application: Launcher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at <Module>.corelib.Context.renderFlushQueue(corelib. Context*, Int32, Boolean)
at lhn6Z3r6bTVp1wDRHcs.C8KS81rtyRdCJK5lJoo.6So6Q8vO4S J(Int32, Boolean)
at yjxHH3O14TjhRyJQQuo.7QqrWQOyxEXSLfcxZmC.a7nqKSvVos i(Int32, Int32)
at BJWoN6iOBbkOnMUnKIh.au1jyXiSFtOAu3u3jVG.gv3SLaH3nY 9()
at RWrdMU2MqfMQKiR2uTN.wiKvIj2curlbSCX5BIA.sWE6FkxjPs b(System.Object)
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCat chWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.Invok eImpl()
at System.Windows.Threading.DispatcherOperation.Invok eInSecurityContext(System.Object)
at System.Threading.ExecutionContext.runTryCode(Syste m.Object)
at System.Runtime.CompilerServices.RuntimeHelpers.Exe cuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
at System.Threading.ExecutionContext.RunInternal(Syst em.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invok e()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(In tPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation( System.Object)
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCat chWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.InvokeImpl(Sys tem.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(Syste m.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl( System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(Syst em.Windows.Threading.DispatcherFrame)
at Rt2Lf1r9U07syGJqRKT.1HVM7ErHQXdXEWPIFQ4.wJuScuNOQa y()
at vXR6sJr8KA6LTfXUb4F.UmcZj0raFEpLPQWuaFm.WSlhEBNWOH IAM9o3j45L(System.Object)
at vXR6sJr8KA6LTfXUb4F.UmcZj0raFEpLPQWuaFm.gea6wGYRwT A(vXR6sJr8KA6LTfXUb4F.UmcZj0raFEpLPQWuaFm, System.String[], System.String, System.String)
at BBVXsTwl82sEsIrEYng.WUxOYgwQhJ6EXHNlnaP.VigqEKxcy5 V(System.String[])
at maddox.Launch.Program(System.String[])
at Launcher.Program.Main(System.String[])


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Faulting application launcher.exe, version 1.0.0.0, stamp 4d6e3d08, faulting module msvcr100.dll, version 10.0.30319.1, stamp 4ba1dbbe, debug? 0, fault address 0x00001fc8.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Application: Launcher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception
Stack:
at System.Diagnostics.Process.StartWithShellExecuteEx (System.Diagnostics.ProcessStartInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(System.Diagnostic s.ProcessStartInfo)
at vXR6sJr8KA6LTfXUb4F.UmcZj0raFEpLPQWuaFm.fA1y2SNW24 Ja1UFarPvZ(System.Object, System.Object)
at vXR6sJr8KA6LTfXUb4F.UmcZj0raFEpLPQWuaFm.gea6wGYRwT A(vXR6sJr8KA6LTfXUb4F.UmcZj0raFEpLPQWuaFm, System.String[], System.String, System.String)
at BBVXsTwl82sEsIrEYng.WUxOYgwQhJ6EXHNlnaP.VigqEKxcy5 V(System.String[])
at maddox.Launch.Program(System.String[])
at Launcher.Program.Main(System.String[])


EventType clr20r3, P1 launcher.exe, P2 1.0.0.0, P3 4d6e3d08, P4 system, P5 4.0.0.0, P6 4ba1dff4, P7 2fd6, P8 2a9, P9 system.componentmodel.win32, P10 NIL.


pplication: Launcher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException
Stack:
at System.RuntimeMethodHandle._InvokeMethodFast(Syste m.IRuntimeMethodInfo, System.Object, System.Object[], System.SignatureStruct ByRef, System.Reflection.MethodAttributes, System.RuntimeType)
at System.RuntimeMethodHandle.InvokeMethodFast(System .IRuntimeMethodInfo, System.Object, System.Object[], System.Signature, System.Reflection.MethodAttributes, System.RuntimeType)
at System.Reflection.RuntimeMethodInfo.Invoke(System. Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo, Boolean)
at System.Delegate.DynamicInvokeImpl(System.Object[])
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCat chWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.Invok eImpl()
at System.Windows.Threading.DispatcherOperation.Invok eInSecurityContext(System.Object)
at System.Threading.ExecutionContext.runTryCode(Syste m.Object)
at System.Runtime.CompilerServices.RuntimeHelpers.Exe cuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
at System.Threading.ExecutionContext.RunInternal(Syst em.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invok e()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(In tPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation( System.Object)
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCat chWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.InvokeImpl(Sys tem.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(Syste m.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl( System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(Syst em.Windows.Threading.DispatcherFrame)
at Rt2Lf1r9U07syGJqRKT.1HVM7ErHQXdXEWPIFQ4.wJuScuNOQa y()
at vXR6sJr8KA6LTfXUb4F.UmcZj0raFEpLPQWuaFm.WSlhEBNWOH IAM9o3j45L(System.Object)
at vXR6sJr8KA6LTfXUb4F.UmcZj0raFEpLPQWuaFm.gea6wGYRwT A(vXR6sJr8KA6LTfXUb4F.UmcZj0raFEpLPQWuaFm, System.String[], System.String, System.String)
at BBVXsTwl82sEsIrEYng.WUxOYgwQhJ6EXHNlnaP.VigqEKxcy5 V(System.String[])
at maddox.Launch.Program(System.String[])
at Launcher.Program.Main(System.String[])

EventType clr20r3, P1 launcher.exe, P2 1.0.0.0, P3 4d6e3d08, P4 core, P5 1.0.0.0, P6 4dac2346, P7 b6f, P8 6, P9 system.accessviolationexception, P10 NIL.

Faulting application launcher.exe, version 1.0.0.0, faulting module msvcr100.dll, version 10.0.30319.1, fault address 0x0008d635.

I am having a different issue I can the play the game fine for an hour or so then I get a launcher error.

Faulting application name: Launcher.exe_Launcher, version: 1.0.0.0, time stamp: 0x4d6e3d08
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7bafa
Exception code: 0xe0434352
Fault offset: 0x0000b727
Faulting process id: 0x370
Faulting application start time: 0x01cc01ec7570692f
Faulting application path: c:\program files (x86)\steam\steamapps\common\il-2 sturmovik cliffs of dover\Launcher.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 1b2fd84c-6de3-11e0-969f-00248c270258

Same problem here

Thanks for that!

It solved my Launch problems:)

That worked for me too before installing the last patch.

Apparantly from this point on the installer automatically purges the cache folder so it shouldn't be a problem anymore.

okay... a new Launcher crash when turning Shadows off in game Options/ Video


"ERROR C++ Runtime
R6025 - Pure function call" message baox appeared after the alert to restart COD appeared to accept the change (Shadows off) and then the Launcher crash message when the error box was closed:

Problem Event Name: APPCRASH
Application Name: Launcher.exe_Launcher
Application Version: 1.0.0.0
Application Timestamp: 4d6e3d08
Fault Module Name: MSVCR100.dll
Fault Module Version: 10.0.30319.415
Fault Module Timestamp: 4d26c6a1
Exception Code: 40000015
Exception Offset: 0008cb95
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: aa75
Additional Information 2: aa75936dc530b2d4d9dbf0da90fd1456
Additional Information 3: 90e8
Additional Information 4: 90e8b9873cb327bd08b567c6b04a9abc


nVidia 275.33 WHQL driver release

Well it has happened to me twice now, but for some reason there is nothing in the 'Event Viewer' that tells me what caused it to happen?

I just got the Launcher.exe has stopped working message.

Now both times this has happened (it must be coincidence) I noted that the Right wheel of the undercarriage of the aircraft I was attacking had dropped down. This happened just before both Launcher crashes?

I have cleared the cache, have cloud enabled and done all the other 'tricks', but currently I can't play this game as it's just too frustrating.

I'll sit and wait for another patch....again! :(

MP

The launcher will not work for me. :( I can't find 1C SoftClub? Is it in CoD or stream?


http://www.degnans.com/markd/Launcher.jpg

I can't read much, so, it is a problem for me. :confused:

"The launcher will not work for me. :( I can't find 1C SoftClub? Is it in CoD or stream?"

Its not in either, its in user's documents.


G.C.

1CSoftClub is located in your documents folder.

Thanks you for the post. :)


It is in /C/Users/name/my documents?

Hi,
I solved launcher crash with a ram timmings change. +80 hours fliying without errors confirm it me.
It´s a personal solution only because no work for a friend with the same issue, but it can help to anybody I hope.
I change timmings from 7-7-7-20 to 9-9-9-25.

oh my god i love you soooooooooo much

I went thru many of the same problems/fixes, and slowly got the sim to function, at least for part of a mission. At the time, my system was a Core 2 Quad Q9550 2.83GHz, with 4GB DDR2 RAM, and an NVidia 9500GT video card w/1GB, operating Windows Vista w/SP 2.

So, I upgraded my system some... I changed to a stronger power supply (850W), changed to an NVidia GTX 580 w/1.5GB, and doubled my RAM to 8GB.

Now, I can fly two complete missions, but start to see some stuttering as I land at the end of the 2nd mission, and when I'm done, and hit ESC, the sim drops me back to my desktop. If I hit ESC again, I'm back in the cockpit. Hit ESC a 3rd time, and I'm back to my desktop, and the sim fails to respond, and I have to use Task Manager to end the program.

There's not much more that I can do to my system, that I know of. I'm new to the world of "overclocking" stuff (i.e. I don't know squat about overclocking... LOL).

Anyone have any thoughts on how to make this sim work a bit longer, without the freeze-up after two missions?

Thanks,

Ed

Got it working this morning by uninstalling .NET framework 4 and reinstalling it using the redist folder. At least now it runs but crashes again if I do a mission with a lot of aircraft and objects within it.

Looking at the Event Viewer in windows, it does seem to be something to do with the KERNALBASE.dll file. This is causing the launcher to crash.

Read this thread and I have this problem.

The only thing that changed is I bought and installed RoF which was a large install itself. I think I recall it installed DX9. Just throwing out things that happened between then and now and where it started. Not saying it is related but that is the only thing that has changed.

Installed .Net 4 and deleted all the old as suggested in the post from unreasonable. I haven't had it crash yet. But it is very random. Give me another evening to play and see if we've made it through the forest.

Thats were softclub folder should be.



G.C.

For some reason I only get a freeze up when I start to play the 'Campaign' and this has only occured during Mission 11,I'm on the grass runway,get the engine started up,always using CEM and before I can get airborne 'FREEZE'.

I then have to get it back to Windows before I can close COD down properly,:rolleyes:it's very annoying and I don't get this with any other game,again maybe the next patch will sort this.