so is 1.2.6 broken? C++ runtime error

[RagnarDa]

it points back to the user.

Well actually it can be anything. A crash like this just means the error wasn't handled by DCS own error catching. Possible culprits (that I can think of) are:

- Any combination of software and hardware

- Any combination of modules

- Any combination of mods

- Any combination of settings in DCS and Windows or any other software or hardware

- Any combination of the above but at a small rate that over time acumulates to a real detectable error or vice versa.

 

This unfortunstely leaves out a pretty large area to seearch for why some have this issue and others don't.

 

I didn't have the crash yesterday night (nothing changed on my comp) but to help to nail it down I can say I have all the modules plus the F-16 EFM and was running among other things TS3 on Windows 8 with UAC enabled.

[silentbob11]

Well actually it can be anything. A crash like this just means the error wasn't handled by DCS own error catching. Possible culprits (that I can think of) are:

- Any combination of software and hardware

- Any combination of modules

- Any combination of mods

- Any combination of settings in DCS and Windows or any other software or hardware

- Any combination of the above but at a small rate that over time acumulates to a real detectable error or vice versa.

 

This unfortunstely leaves out a pretty large area to seearch for why some have this issue and others don't.

 

I didn't have the crash yesterday night (nothing changed on my comp) but to help to nail it down I can say I have all the modules plus the F-16 EFM and was running among other things TS3 on Windows 8 with UAC enabled.

 

Well, for most people who have this error (like me) 1.2.5 was stable and worked fine. I would start there, and look for a change that was made and might cause an error.

 

SB11

[RagnarDa]

Well, for most people who have this error (like me) 1.2.5 was stable and worked fine. I would start there, and look for a change that was made and might cause an error.

 

SB11

 

Yes but you are missing my point. The difference between 1.2.5 and 1.2.6 represent not only what three months work on EDs part, but also one completely new module (Mi-8) and updated mods if you are using that in addition to any updates to drivers or the operating system.

[silentbob11]

Yes but you are missing my point. The difference between 1.2.5 and 1.2.6 represent not only what three months work on EDs part, but also one completely new module (Mi-8) and updated mods if you are using that in addition to any updates to drivers or the operating system.

 

That's all very impressive, but what good is it if so many people can't use it due to instability issues?

 

SB11

[Devrim]

I don't know if I get Runtime Error in single player; Last 4 days I constantly get error in Multiplayer arena.

 

First! I got Runtime error window. When clicked OK, APPCrash window comes (below). Later second APPCrash window appears, this time Module name: A10C_cockpit.dll or someting...

 

WTF! I'm tired to fight with errors and bugs. I quit to play DCS. Enough!

 

Bye...

 

(Edit: By the way, this is my 1000th message on forum.)

 

Sorunlu Olay Adı:	APPCRASH
 Uygulama Adı:	DCS.exe
 Uygulama Sürümü:	1.2.6.17746
 Uygulama Zaman Damgası:	5225b96f
 Hata Modülü Adı:	uh1_protect.dll
 Hata Modülü Sürümü:	5.70.46.4
 Hata Modülü Zaman Damgası:	5225bcb4
 Özel Durum Kodu:	40000015
 Özel Durum Uzaklığı:	000000000002e2ee
 OS Sürümü:	6.1.7601.2.1.0.768.3
 Yerel Kimlik:	1055
 Ek Bilgiler 1:	ac3c
 Ek Bilgiler 2:	ac3c736c072fb320659f14fb2b4a17f5
 Ek Bilgiler 3:	dfea
 Ek Bilgiler 4:	dfea8026abd8aa4425112550c2f539aa

Çevrimiçi gizlilik bildirimimizi okuyun:
 http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x041f

[Mattressi]

Sorunlu Olay Adı:	APPCRASH

Uygulama Adı: DCS.exe

Uygulama Sürümü: 1.2.6.17746

Uygulama Zaman Damgası: 5225b96f

Hata Modülü Adı: [b]uh1_protect.dll[/b]

 

Again, the uh1_protect.dll. I'm seeing this every time I crash and many others seem to be seeing it too. I wonder how many people who own the Huey [i]don't[/i] get this crash. I think it might be the Huey DRM which is causing this. Which, as I've said before, would further ingrain my hatred for the DRM used on DCS (the DRM is the sole reason I held off buying DCS products for so long).

[NineLine]

Again, the uh1_protect.dll. I'm seeing this every time I crash and many others seem to be seeing it too. I wonder how many people who own the Huey don't get this crash. I think it might be the Huey DRM which is causing this. Which, as I've said before, would further ingrain my hatred for the DRM used on DCS (the DRM is the sole reason I held off buying DCS products for so long).

 

 

Are you getting this while flying the Huey or not?

[Mattressi]

Are you getting this while flying the Huey or not?

 

I'm usually flying my Su-25, but I get this error when flying everything, not just the Su-25. I've got the Huey module installed and have it activated.

[71st_Mastiff]

I'm usually flying my Su-25, but I get this error when flying everything, not just the Su-25. I've got the Huey module installed and have it activated.

 

there's a number of threads about this same issue. So its obvious that the Team is not working together to report this on there whiteboard.:thumbup:

 

http://forums.eagle.ru/showthread.php?t=114527

 

http://forums.eagle.ru/showthread.php?t=113264

Edited September 29, 2013 by Mastiff

[71st_Mastiff]

another crash

 

another crash windows has report; log files do not.

 

Fault bucket , type 0

Event Name: AppHangTransient

Response: Not available

Cab Id: 0

Problem signature:

P1: DCS.exe

P2: 1.2.6.17746

P3: 5225b96f

P4: unknown

P5: unknown

P6: unknown

P7: unknown

P8:

P9:

P10:

Attached files:

These files may be available here:

Analysis symbol:

Rechecking for solution: 0

Report Id: fb7e0018-28ed-11e3-b33c-c86000287612

Report Status: 1

Edited September 30, 2013 by Mastiff

[RagnarDa]

so is 1.2.6 broken? C++ runtime error

 

That's all very impressive, but what good is it if so many people can't use it due to instability issues?

 

SB11

 

Do you want to see the bug fixed or do you just want to whine about DCS not being 100% stable on 100% of the different PCs out there?

 

Edit: I see now that there might have been a slight misunderstanding on my part. Sorry about that.

Edited September 29, 2013 by RagnarDa

[Antorian]

Errors can't be fixed without good data on what is causing them. Yes, I've had more stability issues with this last patch but ED is aware of the issues. To find solutions error reporting is the most constructive thing us users can do.

[NineLine]

I'm usually flying my Su-25, but I get this error when flying everything, not just the Su-25. I've got the Huey module installed and have it activated.

 

Interesting, Can you try unisntalling the Huey and playing without it? I have the Huey and I have never gotten this error, maybe you have somethng corrupt there....

[Antorian]

I was able to reproduce the C++ error. I read up on how communication requests to ATC are causing crashes when repeating and responding before the AI has a chance to respond for ATC. Add AWACS to the list. I was requesting picture repeatedly and I guess I requested at the wrong time and it crashed. I'm sure this is what is causing my crashes.

[RagnarDa]

To me it sounds like there is at least two different bugs, one related to comms and one related to the Huey or something else.

[RagnarDa]

You that experience these random crashes, do you have a overclocked CPU?

[Antorian]

Nope. System is normal temps and stable and not overclocked. But to be fair I think I nailed down the cause for my crashes.

Edited September 30, 2013 by Antorian

[Gate-5]

Interesting, Can you try unisntalling the Huey and playing without it? I have the Huey and I have never gotten this error, maybe you have somethng corrupt there....

 

It happens when flying something else than Huey too. I didnt try uninstalling the Huey-Module only, but it definitely still crashes after a complete redownload / reinstallation of all modules: http://forums.eagle.ru/showpost.php?p=1873538&postcount=28

 

For me it definitely seems coms related, but in kind of a random way. I was not able to nail it down so far, but as soon as I use coms (without requesting stuff twice or similar) its a matter of time until the game closes. It also crashes without using coms at all, but this might be becuase of the automatic reply of the ATC when starting up and taxi. Unfortunatley the error message often pops up "behind" the DCS screen and I cannot see the error.

 

Since MP s really messed up, I played some SP recently and had no problems with runtime errors at all.

Edited September 30, 2013 by Gate-5

[NineLine]

It happens when flying something else than Huey too. I didnt try uninstalling the Huey-Module only, but it definitely still crashes after a complete redownload / reinstallation of all modules: http://forums.eagle.ru/showpost.php?p=1873538&postcount=28

 

For me it definitely seems coms related, but in kind of a random way. I was not able to nail it down so far, but as soon as I use coms (without requesting stuff twice or similar) its a matter of time until the game closes. It also crashes without using coms at all, but this might be becuase of the automatic reply of the ATC when starting up and taxi. Unfortunatley the error message often pops up "behind" the DCS screen and I cannot see the error.

 

Since MP s really messed up, I played some SP recently and had no problems with runtime errors at all.

 

 

I have not seen this crash, of course the comms one I can reproduce, and ED is working on the fix, but I think that people seeing reference to the Huey may just be an irrelevant part of the crash message, but I dont know enough about it to say for sure.

[Gate-5]

Just had another crash, but in single player now.

 

I wanted to fly this A-10C mission: http://forums.eagle.ru/showpost.php?p=1813679&postcount=6 . Once in the game, I was only able two switch on battery and inverter and it crashed about 10 seconds into the mission. After the crash the game returned to the main DCS menu.

 

I just started the mission again and no crash so far... I'll report if it was fine.

EDIT: Mission didnt crash the second time, but no radio coms. Second mission I get this kind of problem... this is all messed up, Ill wait for 1.2.7 :(.

 

me.log and dcs.log are in the attachment.

 

Problemsignatur:

Problemereignisname: APPCRASH

Anwendungsname: dcs.exe

Anwendungsversion: 1.2.6.17746

Anwendungszeitstempel: 5225b96f

Fehlermodulname: uh1_protect.dll

Fehlermodulversion: 5.70.46.4

Fehlermodulzeitstempel: 5225bcb4

Ausnahmecode: 40000015

Ausnahmeoffset: 000000000002e2ee

Betriebsystemversion: 6.1.7601.2.1.0.768.3

Gebietsschema-ID: 2055

Zusatzinformation 1: da30

Zusatzinformation 2: da302a0eb92a1fc1b46caeddf6ee8cd3

Zusatzinformation 3: 4fd5

Zusatzinformation 4: 4fd53f28e4b6e176db2c27cd17a583be

Logs.zip

Edited October 1, 2013 by Gate-5

[idenwen]

Just another crash while flying the KA-50 first quick action mission "attack insurgents"

 

Windows error reporting:

 

Name der fehlerhaften Anwendung: dcs.exe, Version: 1.2.6.17746, Zeitstempel: 0x5225b96f

Name des fehlerhaften Moduls: MSVCR100.dll, Version: 10.0.40219.325, Zeitstempel: 0x4df2bcac

Ausnahmecode: 0xc0000005

Fehleroffset: 0x000000000003c02a

ID des fehlerhaften Prozesses: 0x250c

Startzeit der fehlerhaften Anwendung: 0x01cebee1bcd15afb

Pfad der fehlerhaften Anwendung: S:\Programme\Eagle Dynamics\DCS World\bin\dcs.exe

Pfad des fehlerhaften Moduls: C:\Windows\system32\MSVCR100.dll

Berichtskennung: 6082b157-2ad6-11e3-b6f1-e0cb4e97775b

 

 

Crashlog from DCS:

 

# -------------- 20131001-201637 --------------

C:\Windows\system32\MSVCR100.dll

# C0000005 ACCESS_VIOLATION at 6891C02A 01:0003B02A

00000000 00000000 0000:00000000

6891C02A 0019F0B0 0001:0003B02A C:\Windows\system32\MSVCR100.dll memcpy()+CA

F38E6475 0019F140 0000:00000000 ??0EffectHolderImpl@PSEffects@@QEAA@XZ()+1E5

F38F0075 0019F180 0000:00000000 ?getCurrentEffect@PSEffects@@YA?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@ed@@@std@@XZ()+325

F8EF86A1 0019F210 0000:00000000

F8EF8B5B 0019F260 0000:00000000

3F368099 0019F2F0 0000:00000000

3F36AACD 0019F350 0000:00000000

3F380A14 0019F380 0000:00000000

3F3808EB 0019F3B0 0000:00000000

3F414B38 0019F420 0000:00000000

3F416139 0019FA20 0000:00000000

3F418DAB 0019FAD0 0000:00000000

7793652D 0019FB00 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D

77B6C541 0019FB50 0001:0002B541 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

 

 

No commucations from my side involved in the whole mission.

Yesterday I flew some rounds with the F-15C and there was not a single crash - maybe its a help...

 

In dcs.log the last entry was

00109.312 ERROR SOUND: source_is_playing(-1): invalid source

 

Maybe its just a missing sound file?

Edited October 1, 2013 by idenwen
DCS.log entry

[Jara4]

Just had another crash, but in single player now.

 

I wanted to fly this A-10C mission: http://forums.eagle.ru/showpost.php?p=1813679&postcount=6 . Once in the game, I was only able two switch on battery and inverter and it crashed about 10 seconds into the mission. After the crash the game returned to the main DCS menu.

 

I just started the mission again and no crash so far... I'll report if it was fine.

EDIT: Mission didnt crash the second time, but no radio coms. Second mission I get this kind of problem... this is all messed up, Ill wait for 1.2.7 :(.

 

me.log and dcs.log are in the attachment.

 

I experienced the same error message where failed module was "uh1_protect.dll" too while flying Su-25 SP. Maybe some clue/pointing to uh1 Huey module? I have UH1 Huey installed and registered either.

[NineLine]

Have you installed the update yet to see if that makes a difference?

[Jara4]

Updated, tested ca for 2 hours in singleplayer (Su-25, UH-1, A-10C) and no crash. I will continue my testing tomorrow. BTW, before game update also deleted and reinstalled Microsoft Visual C++ 2010 library.

[NineLine]

Glad to hear it, let us know how it goes....