Spt Posted October 18, 2014 Share Posted October 18, 2014 My config : Motherboard MSI Z87-G43 Gaming Graphics Gtx770 4Gb Last driver Nvidia 344.11 RAM 16Gb 1866Mhz Windows Seven 64Bits My several and random crash logs : thanks for your future help ;) :helpsmilie: # -------------- 20141018-135405 -------------- # C0000005 ACCESS_VIOLATION at E35C4DB5 00:00000000 00000000 00000000 0000:00000000 E35C4DB5 1256E760 0000:00000000 E37AB735 1256E7A0 0000:00000000 QueryOglResource()+31FF5 E376B938 1256ED20 0000:00000000 E3771F89 1256ED50 0000:00000000 E36DC969 1256FB20 0000:00000000 E36D91ED 1256FB50 0000:00000000 E36F9E03 1256FB80 0000:00000000 E39B4C07 1256FBB0 0000:00000000 QueryOglResource()+23B4C7 E39B4E52 1256FBE0 0000:00000000 QueryOglResource()+23B712 779559ED 1256FC10 0001:000149ED C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 77B8C541 1256FC60 0001:0002B541 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 # -------------- 20141018-130252 -------------- # C0000005 ACCESS_VIOLATION at ECE2959F 00:00000000 00000000 00000000 0000:00000000 ECE2959F 002DE8F0 0000:00000000 luaF_newproto()+176F ECE29487 002DE920 0000:00000000 luaF_newproto()+1657 ECE288B8 002DE950 0000:00000000 luaF_newproto()+A88 ECE21583 002DE980 0000:00000000 lua_gc()+73 ECE130E3 002DE9B0 0000:00000000 E586BD6B 002DE9F0 0000:00000000 ?update@Application@gui@@UEAAXXZ()+AB ECE117BD 002DEA20 0000:00000000 ECE26AA4 002DEA60 0000:00000000 luaD_growstack()+3C4 ECE3444D 002DEC20 0000:00000000 luaS_newlstr()+40ED ECE26568 002DEC50 0000:00000000 lua_setlocal()+C58 ECE26BCF 002DEDD0 0000:00000000 luaD_growstack()+4EF ECE2674E 002DEE10 0000:00000000 luaD_growstack()+6E ECE21C90 002DEE60 0000:00000000 lua_pcall()+60 3FFAC407 002DEEB0 0000:00000000 3FFA543D 002DFB20 0000:00000000 3FFACECB 002DFB50 0000:00000000 775B59ED 002DFB80 0001:000149ED C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 776EC541 002DFBD0 0001:0002B541 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 # -------------- 20141018-125943 -------------- # C0000005 ACCESS_VIOLATION at E5B168F9 00:00000000 00000000 00000000 0000:00000000 E5B168F9 001EDA50 0000:00000000 E5B1D2E8 001EDAA0 0000:00000000 E5B16A88 001EDB00 0000:00000000 E5B165D8 001EDB30 0000:00000000 E5B27B8B 001EDB80 0000:00000000 E5B34862 001EDBB0 0000:00000000 E5B3436E 001EDBE0 0000:00000000 E5B903B5 001EDE00 0000:00000000 E5BA16DE 001EDE40 0000:00000000 E5BA39E9 001EE160 0000:00000000 E5BAA2AC 001EE1A0 0000:00000000 ED036AA4 001EE1E0 0000:00000000 luaD_growstack()+3C4 ED04444D 001EE3A0 0000:00000000 luaS_newlstr()+40ED ED036568 001EE3D0 0000:00000000 lua_setlocal()+C58 ED036BCF 001EE550 0000:00000000 luaD_growstack()+4EF ED03674E 001EE590 0000:00000000 luaD_growstack()+6E ED031C90 001EE5E0 0000:00000000 lua_pcall()+60 E6529CE7 001EE630 0000:00000000 luaopen_dxgui()+1417 E652A046 001EE680 0000:00000000 luaopen_dxgui()+1776 E6511710 001EE6C0 0000:00000000 E75B2A55 001EE6F0 0000:00000000 ?onMouseUp@ButtonBase@gui@@UEAAXAEBV?$Vector2@H@2@W4MouseButton@2@@Z()+65 E75C3C45 001EE720 0000:00000000 ?getTooltipText@WindowsManager@gui@@QEBA?AV?$basic_string@_WU?$char_traits@_W@std@@V?$allocator@_W@ed@@@std@@XZ()+6A5 E75BCB8C 001EE770 0000:00000000 ?processMessages@GUI@gui@@QEAAXXZ()+5C E75BBCF2 001EE7B0 0000:00000000 ?update@Application@gui@@UEAAXXZ()+32 F85517BD 001EE7E0 0000:00000000 ED036AA4 001EE820 0000:00000000 luaD_growstack()+3C4 ED04444D 001EE9E0 0000:00000000 luaS_newlstr()+40ED ED036568 001EEA10 0000:00000000 lua_setlocal()+C58 ED036BCF 001EEB90 0000:00000000 luaD_growstack()+4EF ED03674E 001EEBD0 0000:00000000 luaD_growstack()+6E ED031C90 001EEC20 0000:00000000 lua_pcall()+60 3F0EC407 001EEC70 0000:00000000 3F0E543D 001EF8E0 0000:00000000 3F0ECECB 001EF910 0000:00000000 775B59ED 001EF940 0001:000149ED C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 776EC541 001EF990 0001:0002B541 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Flagrum Posted October 18, 2014 Share Posted October 18, 2014 Did you try to run a "Repair DCS"? And also, are your DirectX drivers and your GPU drivers all up to date? Link to comment Share on other sites More sharing options...
Spt Posted October 18, 2014 Author Share Posted October 18, 2014 Yes for repair DCS two Times without any success Graphics driver is up to date but I don't know for directX [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Corrigan Posted October 18, 2014 Share Posted October 18, 2014 Are you overclocked? Too aggressive OC on the CPU caused me crashes a few years ago. Win10 x64 | SSDs | i5 2500K @ 4.4 GHz | 16 GB RAM | GTX 970 | TM Warthog HOTAS | Saitek pedals | TIR5 Link to comment Share on other sites More sharing options...
Wrecking Crew Posted October 18, 2014 Share Posted October 18, 2014 Are you overclocked? Too aggressive OC on the CPU caused me crashes a few years ago. I had similar problems and my CPU temp was unstable. Reseated the CPU cooler and replaced the fans -- on v1.2.10 now and DCS is quite stable. WC Visit the Hollo Pointe DCS World server -- an open server with a variety of COOP & H2H missions including Combined Arms. All released missions are available for free download, modification and public hosting, from my Wrecking Crew Projects site. Link to comment Share on other sites More sharing options...
Spt Posted October 18, 2014 Author Share Posted October 18, 2014 Cpu I7 4790K non-overclocked Just the RAM 1333 to 1866 [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Corrigan Posted October 18, 2014 Share Posted October 18, 2014 Well, undo that and check. Win10 x64 | SSDs | i5 2500K @ 4.4 GHz | 16 GB RAM | GTX 970 | TM Warthog HOTAS | Saitek pedals | TIR5 Link to comment Share on other sites More sharing options...
Spt Posted October 18, 2014 Author Share Posted October 18, 2014 Ok I will check ;) 1 [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Spt Posted October 19, 2014 Author Share Posted October 19, 2014 Ok seems to be the RAM frequency Now on automatic position (1333 instead of 1866) ans no more crash for the moment ;) Thanks But my RAM is expecting to work at 1866 ( corsair vengeance PC3-14900 ) so I don't understand! [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
NeilWillis Posted October 19, 2014 Share Posted October 19, 2014 You're saying the ram was rated to work at 1866? If so, and if it is still in warranty, I'd be taking it back to the suppliers. Link to comment Share on other sites More sharing options...
Rhinox Posted October 19, 2014 Share Posted October 19, 2014 ...But my RAM is expecting to work at 1866 ( corsair vengeance PC3-14900 ) so I don't understand! Check SPD/XMP of your memory-modules. Sometimes it *can* run on higher frequency, but it also needs higher voltage... Link to comment Share on other sites More sharing options...
Spt Posted October 19, 2014 Author Share Posted October 19, 2014 Now this one on standard RAM frequency :( # -------------- 20141019-134834 -------------- # C0000005 ACCESS_VIOLATION at E6EF94FC 00:00000000 00000000 00000000 0000:00000000 E6EF94FC 002CD4B0 0000:00000000 D3DXCreateEffectEx()+1C608 E8026246 002CD5A0 0000:00000000 ??4FileFilter@io@@QEAAAEAV01@AEBV01@@Z()+363F6 E80397E4 002CD810 0000:00000000 ??4FileFilter@io@@QEAAAEAV01@AEBV01@@Z()+49994 E8039332 002CD840 0000:00000000 ??4FileFilter@io@@QEAAAEAV01@AEBV01@@Z()+494E2 E7FECBB2 002CD9B0 0000:00000000 ?RenderSurface@edtg@@YAXPEAUhandle_renderitem@1@AEBVVec3f@osg@@AEBVMatrixf@4@2AEBUGlobalLights@1@AEBVFog@edcg@@PEAXPEAUSurfaceRenderData@1@@Z()+502 E7FDF61C 002CE190 0000:00000000 ?RenderSmallShit@edtg@@YAXPEAUhandle_renderitem@1@0@Z()+15AC E7FDE051 002CE1D0 0000:00000000 ?ParseSmallShit@edtg@@YAXPEAUhandle_renderitem@1@AEBVVec3f@osg@@1AEBUTerrainOptions@1@PEAX@Z()+51 E5AD3C1E 002CE9E0 0000:00000000 ?RenderSurface@SceneManager_Implement@@AEAAXPEAVsmCamera_Implement@@W4eDrawRoutines@edtg@@PEAUhandle_renderitem@4@AEBUTerrainOptions@4@@Z()+C1E E5AD2BB5 002CECD0 0000:00000000 ?RenderScene@SceneManager_Implement@@QEAAXPEAVsmCamera@@_N@Z()+2F5 E5AD1824 002CEFF0 0000:00000000 ?RenderMain@SceneManager_Implement@@UEAAXAEBVdPosition@@MW4vCameraType_e@@AEBUsmViewport@@PEAVContext@Graphics@@@Z()+454 E5AD041E 002CF1D0 0000:00000000 ?Render@SceneManager_Implement@@UEAAXXZ()+73E 3F441F0F 002CF260 0000:00000000 3F44420D 002CF2C0 0000:00000000 3F45AEE4 002CF2F0 0000:00000000 3F45B10B 002CF320 0000:00000000 3F4FE9DB 002CF390 0000:00000000 3F4FF236 002CF9B0 0000:00000000 3F502290 002CF9F0 0000:00000000 76E759ED 002CFA20 0001:000149ED C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 770AC541 002CFA70 0001:0002B541 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Spt Posted October 19, 2014 Author Share Posted October 19, 2014 I have this lines in DCS log : 00015.221 UNKNOWN WinMain: 00015.846 ERROR GRAPHICSXP: ModelManager: can't find Cockpit_MiG-29G 00015.888 ERROR GRAPHICSXP: ModelManager: can't find Kabina-Mig-29A-Glass 00015.889 ERROR GRAPHICSXP: ModelManager: can't find Cockpit_MiG-29G 00015.904 ERROR GRAPHICSXP: ModelManager: can't find Kabina-Mig-29G-Glass [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
AtaliaA1 Posted October 19, 2014 Share Posted October 19, 2014 Ok seems to be the RAM frequency Now on automatic position (1333 instead of 1866) ans no more crash for the moment ;) Thanks But my RAM is expecting to work at 1866 ( corsair vengeance PC3-14900 ) so I don't understand! The gains between those ram timings are minimal and in some software non existent. This was a Boutique Builder iBuypower rig. Until I got the tinker bug again i7 920 @3.6Mhz 12Gig Corsair XMS3 ram 1600 Nvidia 760 SLi w/4Gig DDR5 Ram Intel 310 SSD HDD 160 Gb + Western Digital 4Terabyte HDD Creative SB X-Fi HD Audio Logitech X-530 5.1 Surround Speaker System Dual Acer 32"Monitors. PSU 1200 w Thermaltake Win10 64Bit. Link to comment Share on other sites More sharing options...
Recommended Posts