Jump to content

Some tests about crash on exit mission.


Fra298

Recommended Posts

Been using BN's autoconfig too.... I keep coming back to the dx11backend.  Just gave that dll full access on all system/users/etc.  still crashing.  The darn thing is that sometime sit doesn't!

 

More stuff I've looked at:

dxdiag.txt

 

Fault bucket 1632219489306657687, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: DCS.exe
P2: 2.7.1.6709
P3: 60adebf9
P4: dxgi.dll
P5: 4.9.1.1003
P6: 5ffa0e92
P7: c0000005
P8: 0000000000036c83
P9: 
P10: 

 

Crash report:

 

C:\WINDOWS\SYSTEM32\d3d11.dll
# C0000005 ACCESS_VIOLATION at B8606BAE 00:00000000
SymInit: Symbol-SearchPath: '.;d:\Program Files\Eagle Dynamics\DCS World;d:\Program Files\Eagle Dynamics\DCS World\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'Daddy'
OS-Version: 10.0.19042 () 0x100-0x1

 

which this is interesting rabbit hole C:\websymbols*https://msdl.microsoft.com/download/symbols;

 

Microsoft Internet Symbol Server


The data you requested cannot be retrieved.

You have reached this page because either you or an application that you are running has tried to retrieve debugging data from Microsoft. The requested data is either not available or needs to be retrieved by using the latest Microsoft Symbol Server technology.

The data at this site is not accessed from a web browser. Instead, it is accessed by the symbol server technology that ships as part of the Debugging Tools for Windows and Visual Studio. For more information, see Symbols for Windows debugging (WinDbg, KD, CDB, NTSD) and Specify symbol (.pdb) and source files in the Visual Studio debugger.

 


Edited by Ddaddy

R5 2600 @4.2 GHZ, 16GB ram @ 3133, 1060 6GB at 2100 and 4400 970 Evo, TM16000M FCS Flight Pack and old eyes. Just an old Hillbilly that does what he wants when he wants...if I can get out of bed!

Link to comment
Share on other sites

Just did 3 back to back 3 dif maps, no crash... I turned Win Def Private network off.  Turned Win Def Private network back on,,, no crash...

Def seems to be access issue sometimes! with that backend file... taking a break, gl and will check back later

 

R5 2600 @4.2 GHZ, 16GB ram @ 3133, 1060 6GB at 2100 and 4400 970 Evo, TM16000M FCS Flight Pack and old eyes. Just an old Hillbilly that does what he wants when he wants...if I can get out of bed!

Link to comment
Share on other sites

So 4 times good... then crashes again on exit...

R5 2600 @4.2 GHZ, 16GB ram @ 3133, 1060 6GB at 2100 and 4400 970 Evo, TM16000M FCS Flight Pack and old eyes. Just an old Hillbilly that does what he wants when he wants...if I can get out of bed!

Link to comment
Share on other sites

@Fra298In the bin folder, what's the date/properties of dxbackens_mem.dll and D3DCompiler_47.dll?

R5 2600 @4.2 GHZ, 16GB ram @ 3133, 1060 6GB at 2100 and 4400 970 Evo, TM16000M FCS Flight Pack and old eyes. Just an old Hillbilly that does what he wants when he wants...if I can get out of bed!

Link to comment
Share on other sites

Ty.  Ah, can I presume you did a clean install on the 18th?  Anyway this is why I asked since I have a few files from previous install and wondering if that was an issue. 

dcs crash.png

R5 2600 @4.2 GHZ, 16GB ram @ 3133, 1060 6GB at 2100 and 4400 970 Evo, TM16000M FCS Flight Pack and old eyes. Just an old Hillbilly that does what he wants when he wants...if I can get out of bed!

Link to comment
Share on other sites

    Can't remember why but I think i removed the bin folder and made a repair.

If you're investigating this way, looking at modified files, you can check autoupdate_log.txt in root folder, you'll get here all modified files.

Link to comment
Share on other sites

Yea, I got here from that and got interested in the file dates i.e. what 2.7 changed in bin.  Just rabbit hole...but one is bound to have a rabbit in it! On another note, I tried to re-register the dx11backend.dll file in win but it fails.... rabbit hole in rabbit hole... likely.  

 

edit.  and btw, did 3 missions tonight... no crashes on exit...


Edited by Ddaddy
content

R5 2600 @4.2 GHZ, 16GB ram @ 3133, 1060 6GB at 2100 and 4400 970 Evo, TM16000M FCS Flight Pack and old eyes. Just an old Hillbilly that does what he wants when he wants...if I can get out of bed!

Link to comment
Share on other sites

     Well, I can run several missions in a row too. this is why I thought maybe graphic settings were the cause. I tried to find a pattern... it worked during a time... I was able to get crash with exact same settings, but not during a long time... so must be a dead end 😞

 

If I get time I'll try to recheck a few cases tonight.

 

I did not check yet, but maybe problem is gone as the crash section of the forum was so quiet this morning 😉


Edited by Fra298
Link to comment
Share on other sites

Yea, did the graphics... do have one thing funky there... aspect ratio I can't change.  at 1.333 and needs to be 4:3 (4646x1080).  However displays correctly.  I contribute this to 2.7 and it messing up my multidisplay setting.  A rebuild fixed the weird Rmfd bloom I was getting in when displayed in either aux display but not in main...

 

MSD Broke.png

Might do a bac of it, uninstall, reg clean and reinstall... even install non beta....  IF/WHEN it starts crashing again.

 

Since 2018 updates have never been an issue except reshade 1 time.  

R5 2600 @4.2 GHZ, 16GB ram @ 3133, 1060 6GB at 2100 and 4400 970 Evo, TM16000M FCS Flight Pack and old eyes. Just an old Hillbilly that does what he wants when he wants...if I can get out of bed!

Link to comment
Share on other sites

    I think the 1.333 ration is when by default. I saw it when starting tests. It was working ok with this one, but real one for me must be 16:9 (1920*1080).

I do make a backup of my DCS folder after each update too. And i figured out that I still had some reshade files inside...

Link to comment
Share on other sites

yea, I also updated resahade too and had to manually/remove/insure uninstall of it as their uninstaller missed a couple files.  On a slight dif note, you  fly f18?  Is your map in amp displayed in all range settings still?  Mine seems to only work at short range now, not 160 or 80.

R5 2600 @4.2 GHZ, 16GB ram @ 3133, 1060 6GB at 2100 and 4400 970 Evo, TM16000M FCS Flight Pack and old eyes. Just an old Hillbilly that does what he wants when he wants...if I can get out of bed!

Link to comment
Share on other sites

Did a few more tests. So far, running DCS in Windows 8 compatibility mode has been the only way I've been able to avoid any crashing. The instability might have something to do with the recent Windows 10 update.

F/A-18C; A-10C; F-14B; Mirage 2000C; A-4E; F-16C; Flaming Cliffs 3

Link to comment
Share on other sites

Yes, I agree CarbonFox, yet another rabbit hole to look in.  I am pretty convinced, right or wrong, it's some kind of authorization issue with that 1 file, whether it's the file or windows (because of a coup[le error discriptions).  I might just give that win 8 compat a try, ty and watch your 6!

R5 2600 @4.2 GHZ, 16GB ram @ 3133, 1060 6GB at 2100 and 4400 970 Evo, TM16000M FCS Flight Pack and old eyes. Just an old Hillbilly that does what he wants when he wants...if I can get out of bed!

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...