Launcher.exe problem

[nivenj]

Hi,

 

I'm bought and am running DCS:BS 1.0.1c and have the following problem. After I complete the first mission of the first campaign (familiarisation mission), I land, press esc to end mission and quit. The program then crashes to desktop and I get an error saying "Launcher.exe" has stopped working and I cannot restart the game.

 

If I uninstall and re-install the game fails to load with the same error.

 

I uninstalled and installed into a seperate directory as suggested in other threads and hey presto it worked. Completed first mission again and on quit it crashed again and the same problem exists.

 

The only things I have done is to assign some joystick control commands, other than that its a vrigin install and 1.0.1c patch applied.

 

In Event viewer I get the following:-

Log Name: Application

Source: Application Error

Date: 16/12/2009 15:27:35

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: jim-PC

Description:

Faulting application name: Launcher.exe_unknown, version: 0.0.0.0, time stamp: 0x4a817b84

Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdadb

Exception code: 0xc0000005

Fault offset: 0x00052bfe

Faulting process id: 0xa38

Faulting application start time: 0x01ca7e64499ee168

Faulting application path: C:\Program Files\Bs\Ka-50\bin\stable\Launcher.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 88b10dfe-ea57-11de-bfbc-0010c69d4cd1

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Application Error" />

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2009-12-16T15:27:35.000000000Z" />

<EventRecordID>1283</EventRecordID>

<Channel>Application</Channel>

<Computer>jim-PC</Computer>

<Security />

</System>

<EventData>

<Data>Launcher.exe_unknown</Data>

<Data>0.0.0.0</Data>

<Data>4a817b84</Data>

<Data>ntdll.dll</Data>

<Data>6.1.7600.16385</Data>

<Data>4a5bdadb</Data>

<Data>c0000005</Data>

<Data>00052bfe</Data>

<Data>a38</Data>

<Data>01ca7e64499ee168</Data>

<Data>C:\Program Files\Bs\Ka-50\bin\stable\Launcher.exe</Data>

<Data>C:\Windows\SYSTEM32\ntdll.dll</Data>

<Data>88b10dfe-ea57-11de-bfbc-0010c69d4cd1</Data>

</EventData>

</Event>

 

I also attach my latest dxdiag.

 

The system was fine whilst doing all the training scenario's and some missions, I only get this issue when starting the campaign.

 

Any ideas?

DxDiag.txt

[EtherealN]

Hm. My initial reaction is on the fact that you have a GeForce Go 6800, but if that would create issues (old OpenGL version - afaik the 6800 only supports OpenGL 2.1) I feel it should take effect before flying - not after.

 

Exception code 5 with ntdll.dll indicates some kind of memory issue. I'll see if I can find something that fits with the other information there.

 

Does multiplayer work even after that problem occurs? (Multiplayer goes directly into dcs.exe without use of launcher.exe. Would help diagnosis.)

[Panzertard]

Hi nivenj, thanks for the detailed explanation there :)

 

Looked at your DxDiag - looks very good, I cant really see any immediate problems.

ntdll.dll was involved in the crash - this may indicate maaany things, but lets see what we can figure out here.

The file is taking part of many requests going to the OS itself. I'm not sure if it's involved in filetransactions - but, maybe it's during the "end" of a mission where MIZ.TRK files are being written it crashes.

 

- If so, then we might look at the disk/interfaces on your computer. Maybe find newer drivers.

 

Also you Nvidia driver is the "default" Windows 7 driver, is it? It look like that by the DxDiag.

Driver File Version: 7.15.0011.7967 (English)
    Driver Version: 7.15.11.7967
       DDI Version: 9Ex
      Driver Model: WDDM 1.0
 Driver Attributes: Final Retail
  Driver Date/Size: 3/6/2009 11:52:00, 5976064 bytes

I dont think it's cause for the crash - but why not try to update it as well?

 

- Update the Nvidia Driver.

 

Then lastly;

- make sure you run DCS:BS with no mods while you test now.

- you can also try to install in a different directory (permission problems here), like for example D:\Games\DCS

- install / launch the game with administrative permissions. "Run as Administrator" when starting it.

 

And clean out your \Eagle Dynamics\Ka-50\Temp folder between each test, then you can look for interesting LOG/Error files from the crash - or maybe we can figure out of the *.MIZ.TRK files are missing.

 

EDIT: /me slaps himself with a big spoon for writing a novel and letting Ethereal answer first ...

[EtherealN]

Hah! I win this time! :P

 

Though you made some good points there that I didn't think of.

Do we have a way to disable the recording of tracks to prevent it from trying to save those files and thereby pinpoint it as the cause?

[Panzertard]

Hah! I win this time! :P

 

Though you made some good points there that I didn't think of.

Do we have a way to disable the recording of tracks to prevent it from trying to save those files and thereby pinpoint it as the cause?

*Shh*, I've told you; - never ask questions I can't answer right away ... you make me look bad :(

j/k :D

 

Good point, let's dig into the options/lua and see what we can find ....

 

EDIT: For future ref, I didnt find any such options.

Edited December 16, 2009 by Panzertard

[nivenj]

Thanks guys

 

Multiplayer does work (although it looks like a very low resolution and no option to change it, is that correct?)

 

I did a quick search for .trk files in install directory and can only find files in the /mission/Training directory. Where should I check for campaign .trk files?

 

I have been keeping an eye on the ka-50\Temp directory but its empty, no error or crash files are created.

 

I did update my video driver, the standard one from windows 7 was a standard VGA...searched for new driver using windows update and it brought this current one in. Had no issues and it does play DCS:BS beautifully @ 1900x1200 and medium to high settings on everything so would be surprised if it was a video issue.

 

No mods installed.

 

Installing in a different directory does solve the issue, but only temporarily until I complete the first mission then I am back at square 1. (any idea why installing in a different directory works? what permissions problems could be causing the issue?)

[Panzertard]

I have been keeping an eye on the ka-50\Temp directory but its empty, no error or crash files are created.

This may very well be an indication that you have a permission problem if no files are found there.

And thats where the temporary *:MIZ.TRK file should have ended up.

And lots of more log files.

 

Several options for the permission problem though;

- "Run as Administrator" may fix it.

- Change permissions on the Eagle Dynamics\Ka-50 folder (including subfolders) to say "Interactive" (users) = Full Control. This way "anyone who physically logged on to the computer" will have permissions to change the content of the folders.

- Reinstall on another location outside the "C:\Program Files". The default Program Files *do* have restrictions, you as a "user" may not have full controll, or allowed to change the files "while you run a program".

Reinstall to D:\Myfolder may fix that issue, if the permission on D:\ is correct.

 

Btw, if you reinstall on the same computer - the same os, you wont have to reactivate - it will "reuse" the same activation.

[nivenj]

Ok, will give that a go.

 

One small thing came to mind seeing you talk about options lua. When I remapped my joystick and saved the profile. I think I used BlackShark.lua, its just dawned on me that I didnt create this, it was already there..could this be the issue. Indeed, the more I think about it, the more I'm convinced this happend both times not long after changing the joystick mappings. :-S

[Panzertard]

Ok, will give that a go.

 

One small thing came to mind seeing you talk about options lua. When I remapped my joystick and saved the profile. I think I used BlackShark.lua, its just dawned on me that I didnt create this, it was already there..could this be the issue. Indeed, the more I think about it, the more I'm convinced this happend both times not long after changing the joystick mappings. :-S

Yes, if you overwrite Blackshark.lua that may cause a myriad of issues! It contains quite a bit of code.

Good thing you remembered to mention this ;)

Try to reapply the patch - I think it's included there - then you might fix the problems. If not, a reinstall will fix it.

[EtherealN]

Also, note that if you need to edit files, do not use the standard windows notepad - get Notepad++ for this task instead. This is because standard notepad might cause syntax issues since it is not intended to handle code (whereas Notepad++ is).

[nivenj]

Yes, if you overwrite Blackshark.lua that may cause a myriad of issues! It contains quite a bit of code.

Good thing you remembered to mention this ;)

Try to reapply the patch - I think it's included there - then you might fix the problems. If not, a reinstall will fix it.

 

Re-installed patch, same issue.

 

Will go ahead an re-install in c:\games I am sure that will work, will complete first mission and see what happens.

[EtherealN]

Do see if there is any difference without the patch (that is, vanilla 1.0.0). Would be interesting to know if this issue is version-dependant, just in case.

[nivenj]

ok will do.

[nivenj]

Have just reinstalled 1.0.0 have started and exited (not completed) the first mission and everything was ok. Have to pop out for a few hours, will complete the mission when I return and let you know. If that works I will install 1.0.1c and restart the campaign and see if there is any difference. If that also works will change my joystick settings and see if that causes an issue (these are the only 3 things I've done before it crashes).

 

thanks for the input so far.

[nivenj]

Everything seems to be ok, it must have been my stupidity in using the BlackShark.lua to save the profile. My profile name for freetrack is Blackshark, hence the confusion. Thanks for all your help.

[Panzertard]

Everything seems to be ok, it must have been my stupidity in using the BlackShark.lua to save the profile. My profile name for freetrack is Blackshark, hence the confusion. Thanks for all your help.

 

Good to hear you solved it and can enjoy the sim :)

[EtherealN]

No stupidity involved, nivenj, everyone makes mistakes and it's only when we don't learn from them that stupidity arises. Great to hear you've got it running nicely again and see you in the skies. :)

[Chris CDN]

Is there anyway someone can post a copy of the blackshark.lua file? I'd hate to reinstall the entire game just to fix this issue.