Crash reporter ineffective

[discwalker]

because many times windows take over the remainig control with a force to close DCS window.

At this time crash reporter asking for user input create or not dxdiag.

Error reporter should create A zip with dump and log and trk files before asking user input,

failsafe report file this way createable.

 

DCS 2.5.5.32533

mission: https://forums.eagle.ru/attachment.php?attachmentid=212109&d=1560741361

(Russian Insurgents 1.miz)

logs: pan and zoom out with 16GB RAM this caucasus mission

Logs.man.zip

[discwalker]

I moved pagefile to SSD

 

crash is the same:

edit: now i'm running windows with system32/WerFault.exe disabled, that is the small foreign window over DCS ;-) And now I can use DCS crash reporter with limits -> no dump file created in this case, dump file created in other cases.

Edited June 24, 2019 by discwalker
werfault.exe

[discwalker]

Help!

 

(((this))) zip with the same "Russian Insurgents 1.miz" mission.

 

I reverted back twice. And cleared my game install folder, temp folder.

All 3 versions of 2.5.5 crashing with this mission and derivatives during simulation start too.

Two of my buddies run this mission without any flaw.

edit: my only one simulated derivative was the bare coalitions only mission without any units

edit: with new saved games :-(

Edited February 4, 2020 by discwalker
deprecated crash file removed

[BIGNEWY]

Hi discwalker,

 

I have run the mission, it does not produce a crash for me.

 

Have you insured windows and all drivers are up to date?

 

If you are still having issues you could contact support directly

 

https://www.digitalcombatsimulator.com/en/support/

 

please provide as much information as possible for them

 

https://www.digitalcombatsimulator.com/en/support/faq/710/

[discwalker]

Question on thread title

 

Is the crash reporter working in the same "ineffective" way as in 2019?

Because 4 of 5 times the OS (Win 8.1) intercepted the crash reporter with

system32/WerFault.exe

modal window,

it renders unusable for crash .zip creation and/or automatic upload with a comment.

Impossible to answer the dxdiag creation question under a modal window. :(

Do I still needed to run a modified (system32/WerFault.exe renamed) Win 8.1 to able to catch possible crashes? Is this the case for only Win 8.1?

Is storage read error still displayed as IN_PAGE_ERROR in crash?

[BIGNEWY]

I will ask the team,

 

I run windows 10 so can not test this.