Jump to content

DCS crash total game freeze


GazAce

Recommended Posts

Hornet Syria map, DCS crash in same user created mission twice in 10 mins. Tried repair after first crash. Flew same mission yesterday & many times prior with no issues. No mods used. Game crashes at about the same place, either just after launching off boat or soon after. Left with in-game image screen freeze & no ability to alt tab or ctrl alt delete. Only option avail is to manually & totally shut down pc which I hate doing. Files attached 

dcs.20210106-143602.crash dcs.20210106-143602.dmp dcs.20210106-142002.crash dcs.20210106-142002.dmp


Edited by GazAce
Added more details
  • Like 1

:: 13th Gen Intel Core i9-13900K :: Asus ROG Strix Z790-A mobo :: Asus Tuff Gaming GeForce RTX 3080 Ti :: NZXT Kraken Elite 280 RGB AIO white cooler :: G Skill Trident Z Royals DDR4 4x16GB = 64GB :: WD Black SN 850X NVMe SSD 2TB M.2 (C Drive) :: Samsung 860 Pro 2TB SATA (D Drive) :: Corsair Crystal 680X White Case :: Asus XG349C 34" Curve G-Sync 180Hz 3440x1440 Mon :: Corsair 850W PSU :: Virpil Constellation Alpha-R Stick with VPC WarBRD Base :: Virpil MongoosT-50CM3 Throttle :: 3 x CubeSim ext mini screens with TM Cougar MFD Bezels :: Asus ROG Pugio 503 Gaming Mouse & Razer BlackWidow mech kb :: TrackIR 5 Pro & Cap Clip :: Win 11 64 Bit 😉

Link to comment
Share on other sites

Hi. Please attach your dcs.log file (from the same Logs folder) to get a broader view. For now, it looks like a graphics driver crash:

 

# -------------- 20210106-143602 --------------
DCS/2.5.6.59625 (x86_64; Windows NT 10.0.19042)
C:\WINDOWS\SYSTEM32\d3d11.dll
# C0000005 ACCESS_VIOLATION at 4B8998A0 00:00000000
SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'gazzy'
OS-Version: 10.0.19042 () 0x300-0x1
0x00000000001298A0 (d3d11): CreateDirect3D11SurfaceFromDXGISurface + 0x10420
0x0000000000044048 (dx11backend): createRenderer + 0x2B0B8
0x0000000000004006 (GraphicsVista): Graphics::CustomMaterial_Impl::GetMaterialCaps + 0x816
0x0000000000031131 (GraphicsVista): Graphics::RenderObject::render + 0x21
0x00000000002BD2D1 (CockpitBase): cockpit::ceSimpleLineObject::self_render + 0xA1
0x00000000002C5892 (CockpitBase): cockpit::ceSimple::draw + 0xE2
0x00000000002B2830 (CockpitBase): cockpit::ccIndicatorPage::draw + 0x60
0x00000000002AB7D5 (CockpitBase): cockpit::ccIndicator::draw + 0x75
0x00000000002ABB8E (CockpitBase): cockpit::ccIndicator::draw_to_viewport + 0xDE
0x00000000002B1A1D (CockpitBase): cockpit::ccIndicatorBake::addSource + 0x2ED
0x00000000002B15E6 (CockpitBase): cockpit::ccIndicatorBake::OnBeginFrame + 0xB6
0x000000000004AA2E (GraphicsCore): Graphics::fireRendererCallbacks + 0x15E
0x000000000015A094 (Visualizer): smSceneManager::CreateSceneManager + 0x5684
0x00000000007B02A7 (DCS): CoreUtils::TempFilesManager::operator= + 0x3BE537
0x00000000007C3AB3 (DCS): CoreUtils::TempFilesManager::operator= + 0x3D1D43
0x0000000000794834 (DCS): CoreUtils::TempFilesManager::operator= + 0x3A2AC4
0x0000000000794BF9 (DCS): CoreUtils::TempFilesManager::operator= + 0x3A2E89
0x00000000018572FC (DCS): AmdPowerXpressRequestHighPerformance + 0xBEA2F8
0x000000000098462E (DCS): CoreUtils::TempFilesManager::operator= + 0x5928BE
0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14
0x000000000004D0D1 (ntdll): RtlUserThreadStart + 0x21

 

Are you using an overclocked GPU?

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

Oh ok so I fly this mission nearly 20 x without DCS crashing.. same settings, same software/hardware no mods & then immediately after the latest Update my DCS crashes twice within the same mission virtually at the same point & your saying it's my doing? Err I think not, files attached   

dcs.log.old

  • Thanks 1

:: 13th Gen Intel Core i9-13900K :: Asus ROG Strix Z790-A mobo :: Asus Tuff Gaming GeForce RTX 3080 Ti :: NZXT Kraken Elite 280 RGB AIO white cooler :: G Skill Trident Z Royals DDR4 4x16GB = 64GB :: WD Black SN 850X NVMe SSD 2TB M.2 (C Drive) :: Samsung 860 Pro 2TB SATA (D Drive) :: Corsair Crystal 680X White Case :: Asus XG349C 34" Curve G-Sync 180Hz 3440x1440 Mon :: Corsair 850W PSU :: Virpil Constellation Alpha-R Stick with VPC WarBRD Base :: Virpil MongoosT-50CM3 Throttle :: 3 x CubeSim ext mini screens with TM Cougar MFD Bezels :: Asus ROG Pugio 503 Gaming Mouse & Razer BlackWidow mech kb :: TrackIR 5 Pro & Cap Clip :: Win 11 64 Bit 😉

Link to comment
Share on other sites

Hi Gaz. 

Since the first December 2020 update my DCS is crashing on GBU12 release and also randomly on carrier cat launch. 

Prior to that in had 11 crashless months and I played DCS every single day in 2020! 

Could be nvidia drivers, could be DCS but it is nothing to do with overclock. 

 

Intel i7-13700KF :: ROG STRIX Z790-A GAMING WIFI D4 :: Corsair Vengeance LPX 64GB ::  MSI RTX 4080  Gaming X Trio  :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta

Link to comment
Share on other sites

@GazAceThe full log speaks for itself. I let you Google "DXGI_ERROR_DEVICE_REMOVED" (which is a DirectX error, not a DCS one).

 

2021-01-06 14:34:01.659 WARNING FLIGHT: crew 2 wCarrierCrew::reset_LA()
2021-01-06 14:35:14.222 INFO    DCS: wcTanker::onEvent:0
2021-01-06 14:36:00.627 ERROR   DX11BACKEND: DX device removed. Reason: 0x887A0007
2021-01-06 14:36:00.848 WARNING LOG: 26 duplicate message(s) skipped.
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create structed buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.848 WARNING LOG: 1 duplicate message(s) skipped.
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:379
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.848 WARNING LOG: 1 duplicate message(s) skipped.
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:379
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: CreateShaderResourceView FAILED. Reason: E_INVALIDARG
2021-01-06 14:36:00.848 WARNING LOG: 1 duplicate message(s) skipped.
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:379
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create structed buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: CreateShaderResourceView FAILED. Reason: E_INVALIDARG
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create structed buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: CreateShaderResourceView FAILED. Reason: E_INVALIDARG
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:379
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.853 ERROR   DX11BACKEND: DX device removed. Reason: 0x887A0007
2021-01-06 14:36:00.848 WARNING LOG: 1 duplicate message(s) skipped.
2021-01-06 14:36:00.848 ERROR   DX11BACKEND: failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:00.866 ERROR   DX11BACKEND: DX device removed. Reason: 0x887A0007
2021-01-06 14:36:01.568 WARNING LOG: 62 duplicate message(s) skipped.
2021-01-06 14:36:01.568 ERROR   DX11BACKEND: failed to create structed buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:01.568 ERROR   DX11BACKEND: CreateShaderResourceView FAILED. Reason: E_INVALIDARG
2021-01-06 14:36:01.569 ERROR   DX11BACKEND: failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:01.569 ERROR   DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:01.569 WARNING LOG: 1 duplicate message(s) skipped.
2021-01-06 14:36:01.569 ERROR   DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:379
2021-01-06 14:36:01.569 WARNING LOG: 1 duplicate message(s) skipped.
2021-01-06 14:36:01.569 ERROR   DX11BACKEND: failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:01.572 WARNING LOG: 1 duplicate message(s) skipped.
2021-01-06 14:36:01.572 ERROR   DX11BACKEND: DX device removed. Reason: 0x887A0007
2021-01-06 14:36:02.078 WARNING LOG: 66 duplicate message(s) skipped.
2021-01-06 14:36:02.078 ERROR   DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2021-01-06 14:36:02.078 ERROR   DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:379
2021-01-06 14:36:02.079 INFO    EDCORE: try to write dump information
2021-01-06 14:36:02.084 INFO    EDCORE: # -------------- 20210106-143602 --------------
2021-01-06 14:36:02.087 INFO    EDCORE: DCS/2.5.6.59625 (x86_64; Windows NT 10.0.19042)
2021-01-06 14:36:02.090 INFO    EDCORE: C:\WINDOWS\SYSTEM32\d3d11.dll
2021-01-06 14:36:02.093 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at 4B8998A0 00:00000000
2021-01-06 14:36:02.097 INFO    EDCORE: SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'gazzy'
2021-01-06 14:36:02.100 INFO    EDCORE: OS-Version: 10.0.19042 () 0x300-0x1
2021-01-06 14:36:02.826 INFO    EDCORE: 0x00000000001298A0 (d3d11): CreateDirect3D11SurfaceFromDXGISurface + 0x10420
2021-01-06 14:36:02.826 INFO    EDCORE: 0x0000000000044048 (dx11backend): createRenderer + 0x2B0B8
2021-01-06 14:36:02.827 INFO    EDCORE: 0x0000000000004006 (GraphicsVista): Graphics::CustomMaterial_Impl::GetMaterialCaps + 0x816
2021-01-06 14:36:02.827 INFO    EDCORE: 0x0000000000031131 (GraphicsVista): Graphics::RenderObject::render + 0x21
2021-01-06 14:36:02.827 INFO    EDCORE: 0x00000000002BD2D1 (CockpitBase): cockpit::ceSimpleLineObject::self_render + 0xA1
2021-01-06 14:36:02.827 INFO    EDCORE: 0x00000000002C5892 (CockpitBase): cockpit::ceSimple::draw + 0xE2
2021-01-06 14:36:02.827 INFO    EDCORE: 0x00000000002B2830 (CockpitBase): cockpit::ccIndicatorPage::draw + 0x60
2021-01-06 14:36:02.828 INFO    EDCORE: 0x00000000002AB7D5 (CockpitBase): cockpit::ccIndicator::draw + 0x75
2021-01-06 14:36:02.828 INFO    EDCORE: 0x00000000002ABB8E (CockpitBase): cockpit::ccIndicator::draw_to_viewport + 0xDE
2021-01-06 14:36:02.828 INFO    EDCORE: 0x00000000002B1A1D (CockpitBase): cockpit::ccIndicatorBake::addSource + 0x2ED
2021-01-06 14:36:02.828 INFO    EDCORE: 0x00000000002B15E6 (CockpitBase): cockpit::ccIndicatorBake::OnBeginFrame + 0xB6
2021-01-06 14:36:02.829 INFO    EDCORE: 0x000000000004AA2E (GraphicsCore): Graphics::fireRendererCallbacks + 0x15E
2021-01-06 14:36:02.829 INFO    EDCORE: 0x000000000015A094 (Visualizer): smSceneManager::CreateSceneManager + 0x5684
2021-01-06 14:36:02.829 INFO    EDCORE: 0x00000000007B02A7 (DCS): CoreUtils::TempFilesManager::operator= + 0x3BE537
2021-01-06 14:36:02.829 INFO    EDCORE: 0x00000000007C3AB3 (DCS): CoreUtils::TempFilesManager::operator= + 0x3D1D43
2021-01-06 14:36:02.829 INFO    EDCORE: 0x0000000000794834 (DCS): CoreUtils::TempFilesManager::operator= + 0x3A2AC4
2021-01-06 14:36:02.830 INFO    EDCORE: 0x0000000000794BF9 (DCS): CoreUtils::TempFilesManager::operator= + 0x3A2E89
2021-01-06 14:36:02.830 INFO    EDCORE: 0x00000000018572FC (DCS): AmdPowerXpressRequestHighPerformance + 0xBEA2F8
2021-01-06 14:36:02.830 INFO    EDCORE: 0x000000000098462E (DCS): CoreUtils::TempFilesManager::operator= + 0x5928BE
2021-01-06 14:36:02.830 INFO    EDCORE: 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14
2021-01-06 14:36:02.830 INFO    EDCORE: 0x000000000004D0D1 (ntdll): RtlUserThreadStart + 0x21
2021-01-06 14:36:03.131 INFO    EDCORE: Minidump created.

 

 

Here are four threads dealing with the same kind of crashlog ("DXGI_ERROR_DEVICE_REMOVED"). The OPs all had their issue fixed, according to them. Feel free to read them and try what they have tried:

  1. Cause: faulty PSU
  2. Cause: SSLR enabled
  3. Cause: overclocked GPU
  4. Cause: RAM overclocked

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

@Flappie

Your answer is inconsistent. 

First, you say, it is DirectX and not DSC, then in possible causes you mention DCS option in point 2. 

But important thing is that the log on DCS is not logging the cause but the effect. 

That DirectX error is the outcome of DCS code issue. I have been long enough with DCS to see that.

 

No other games crash, and my entire system is a high end gaming gear, typically factory overclocked. 

 

If it was the hardware, nothing would have worked, not only DCS and certainly not only specific portions of it (like Supercarrier launch or GBU12 release).

 

But, we can't do much to be honest. DCS code is bug free, while fat digit $$$ gaming hardware is culprit here. No. I will wait for further updates instead. Even better, wait for DCS 3.0

Intel i7-13700KF :: ROG STRIX Z790-A GAMING WIFI D4 :: Corsair Vengeance LPX 64GB ::  MSI RTX 4080  Gaming X Trio  :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta

Link to comment
Share on other sites

16 minutes ago, Flappie said:

@GierasimovWell, it seems you are quite the expert. I let you guys solve your issues. Bye.

Oh so your solution for DCS constantly crashing after recent update is to blame our hardware? Are you serious? This is where we are now? "Solve our own issues" That's pathetic... are you even a dedicated support person?


Edited by GazAce

:: 13th Gen Intel Core i9-13900K :: Asus ROG Strix Z790-A mobo :: Asus Tuff Gaming GeForce RTX 3080 Ti :: NZXT Kraken Elite 280 RGB AIO white cooler :: G Skill Trident Z Royals DDR4 4x16GB = 64GB :: WD Black SN 850X NVMe SSD 2TB M.2 (C Drive) :: Samsung 860 Pro 2TB SATA (D Drive) :: Corsair Crystal 680X White Case :: Asus XG349C 34" Curve G-Sync 180Hz 3440x1440 Mon :: Corsair 850W PSU :: Virpil Constellation Alpha-R Stick with VPC WarBRD Base :: Virpil MongoosT-50CM3 Throttle :: 3 x CubeSim ext mini screens with TM Cougar MFD Bezels :: Asus ROG Pugio 503 Gaming Mouse & Razer BlackWidow mech kb :: TrackIR 5 Pro & Cap Clip :: Win 11 64 Bit 😉

Link to comment
Share on other sites

27 minutes ago, Flappie said:

@GierasimovWell, it seems you are quite the expert. I let you guys solve your issues. Bye.

Look mate, these are not OUR issues, these are the software issues. Here is the LOG file that DCS was creating when we (GazAce and I) play the same mission -- 

 

I took the liberty to include only ERRORS as the file is rather long due to a 2,5 hours mission. 

 

In this mission, I took of the boat, performed AAR, killed two F-16, landed to take weapons and fuel, killed HAWK SAM, and then when I tried to drop GBU-12, DCS froze.

 

There is no track, obviously, but that is not a problem, even if DCS saved that track it would not have played back correctly anyway, coz tracks are bugged as well. 

 

Now, in my LOG, which exact line points out to my factory overclocked GPU, boost mode CPU, XMP memory issue or my faulty PSU? To me they all relate to code of the software rather than anything else. 

 

One more thing. It was working fine in September when I build this PC - till the first DCS update in December, and it was working fine on previous PC I had, which was the same GPU that GazAce has got right now. 

 

 

dcs - Copy.log

Intel i7-13700KF :: ROG STRIX Z790-A GAMING WIFI D4 :: Corsair Vengeance LPX 64GB ::  MSI RTX 4080  Gaming X Trio  :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta

Link to comment
Share on other sites

22 minutes ago, GazAce said:

Oh so your solution for DCS constantly crashing after recent update is to blame our hardware? Are you serious? This is where we are now? "Solve our own issues" That's pathetic... are you even a dedicated support person?

 

If you're implying I'm working at ED, I'm not: I'm a customer who likes to help people. I was trying to help you, but you guys were hostile to me from the very begining. I'm not masochistic, so I'm out of here. Period.

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

8 hours ago, GazAce said:

Oh so your solution for DCS constantly crashing after recent update is to blame our hardware? Are you serious? This is where we are now? "Solve our own issues" That's pathetic... are you even a dedicated support person?

 

 

He's not dedicated support person.  He's a user who helps others a lot.  It sounds like you guys are not even open to idea of your system being the issue but certain that it is DCS issue so there's nothing else to suggest but wait for ED to fix it.  But I doubt they'll find anything useful out of this thread.


Edited by Taz1004
Link to comment
Share on other sites

8 hours ago, Flappie said:

If you're implying I'm working at ED, I'm not: I'm a customer who likes to help people. I was trying to help you, but you guys were hostile to me from the very begining. I'm not masochistic, so I'm out of here. Period.

I've thought about my reply & I was out of line man, so I apologise to you Flappy for being so abrasive & snappy. I was frustrated & pissed off & I won't be coming in Forum anymore to report bugs or problems, I'll just suck it up. It's too unnerving & upsetting & I'm too old for it. Again.. sorry, peace out 

:: 13th Gen Intel Core i9-13900K :: Asus ROG Strix Z790-A mobo :: Asus Tuff Gaming GeForce RTX 3080 Ti :: NZXT Kraken Elite 280 RGB AIO white cooler :: G Skill Trident Z Royals DDR4 4x16GB = 64GB :: WD Black SN 850X NVMe SSD 2TB M.2 (C Drive) :: Samsung 860 Pro 2TB SATA (D Drive) :: Corsair Crystal 680X White Case :: Asus XG349C 34" Curve G-Sync 180Hz 3440x1440 Mon :: Corsair 850W PSU :: Virpil Constellation Alpha-R Stick with VPC WarBRD Base :: Virpil MongoosT-50CM3 Throttle :: 3 x CubeSim ext mini screens with TM Cougar MFD Bezels :: Asus ROG Pugio 503 Gaming Mouse & Razer BlackWidow mech kb :: TrackIR 5 Pro & Cap Clip :: Win 11 64 Bit 😉

Link to comment
Share on other sites

They reckon it's says a lot about someone who can make a meaningful apology..  also says a lot a about someone who can accept one...  I'm not holding my breath 

  • Like 1

:: 13th Gen Intel Core i9-13900K :: Asus ROG Strix Z790-A mobo :: Asus Tuff Gaming GeForce RTX 3080 Ti :: NZXT Kraken Elite 280 RGB AIO white cooler :: G Skill Trident Z Royals DDR4 4x16GB = 64GB :: WD Black SN 850X NVMe SSD 2TB M.2 (C Drive) :: Samsung 860 Pro 2TB SATA (D Drive) :: Corsair Crystal 680X White Case :: Asus XG349C 34" Curve G-Sync 180Hz 3440x1440 Mon :: Corsair 850W PSU :: Virpil Constellation Alpha-R Stick with VPC WarBRD Base :: Virpil MongoosT-50CM3 Throttle :: 3 x CubeSim ext mini screens with TM Cougar MFD Bezels :: Asus ROG Pugio 503 Gaming Mouse & Razer BlackWidow mech kb :: TrackIR 5 Pro & Cap Clip :: Win 11 64 Bit 😉

Link to comment
Share on other sites

1 hour ago, GazAce said:

..  also says a lot a about someone who can accept one...  I'm not holding my breath 


Maybe he has not seen your apology, I rarely return to a toxic thread .. you could had at least mentioned @Flappie so that he would have received a notification 🙂

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

  • ED Team

Guys Flappie is trying to help, dont give him a hard time. 

 

The crash is a display driver crash, most likely driver issue or a hardware issue. 

 

Remove all unofficial mods, run a full cleanup and repair. Update windows and your display driver. 

If you are over clocking remove the over clocks. 

 

If you are getting the crash still attach fresh logs, if the crash zip folder is generated attach it, the track replay may help us try to reproduce the issue. 

But I can tell you now nine times out of ten with display driver crashes its not DCS. 

 

Please keep the thread for crash report data. 

 

thanks

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

@Rudel_chwThanks for notifying me.

 

@GazAceApology accepted. User silentbob11 had the exact same crashlog ("GetMaterialCaps") with the same NVIDIA driver version (v460.89) in the same week. This is what he did to successfully stop DCS from crashing:

 

1/ He reverted  to a previous NVIDIA driver (460.79) -> He then had another kind of crashlog

2/ He emptied these folders:

  • C:\ProgramData\NVIDIA Corporation\NV_Cache (you will probably get a message saying Windows can't remove some files: that's OK, just hit "Ignore")
  • C:\Users\your-name\AppData\Local\Temp\DCS.openbeta

3/ Then he dusted off his CPU.

 

Please try steps 1 and 2.

Step 3 at your own discretion.

  • Like 1

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

I appreciate your advice, cheers  

4 hours ago, Rudel_chw said:


Maybe he has not seen your apology, I rarely return to a toxic thread .. you could had at least mentioned @Flappie so that he would have received a notification 🙂

I've thought about my reply & I was out of line man, so I apologise to you Flappy for being so abrasive & snappy. I was frustrated & pissed off & I won't be coming in Forum anymore to report bugs or problems, I'll just suck it up. It's too unnerving & upsetting & I'm too old for it. Again.. sorry, peace out 

2 hours ago, Flappie said:

@Rudel_chwThanks for notifying me.

 

@GazAceApology accepted. User silentbob11 had the exact same crashlog ("GetMaterialCaps") with the same NVIDIA driver version (v460.89) in the same week. This is what he did to successfully stop DCS from crashing:

 

1/ He reverted  to a previous NVIDIA driver (460.79) -> He then had another kind of crashlog

2/ He emptied these folders:

  • C:\ProgramData\NVIDIA Corporation\NV_Cache (you will probably get a message saying Windows can't remove some files: that's OK, just hit "Ignore")
  • C:\Users\your-name\AppData\Local\Temp\DCS.openbeta

3/ Then he dusted off his CPU.

 

Please try steps 1 and 2.

Step 3 at your own discretion.

Thank you, appreciate your tips & advice. GA out 

4 hours ago, BIGNEWY said:

Guys Flappie is trying to help, dont give him a hard time. 

 

The crash is a display driver crash, most likely driver issue or a hardware issue. 

 

Remove all unofficial mods, run a full cleanup and repair. Update windows and your display driver. 

If you are over clocking remove the over clocks. 

 

If you are getting the crash still attach fresh logs, if the crash zip folder is generated attach it, the track replay may help us try to reproduce the issue. 

But I can tell you now nine times out of ten with display driver crashes its not DCS. 

 

Please keep the thread for crash report data. 

 

thanks

Thanks BN, appreciate that mate 👍

  • Like 1

:: 13th Gen Intel Core i9-13900K :: Asus ROG Strix Z790-A mobo :: Asus Tuff Gaming GeForce RTX 3080 Ti :: NZXT Kraken Elite 280 RGB AIO white cooler :: G Skill Trident Z Royals DDR4 4x16GB = 64GB :: WD Black SN 850X NVMe SSD 2TB M.2 (C Drive) :: Samsung 860 Pro 2TB SATA (D Drive) :: Corsair Crystal 680X White Case :: Asus XG349C 34" Curve G-Sync 180Hz 3440x1440 Mon :: Corsair 850W PSU :: Virpil Constellation Alpha-R Stick with VPC WarBRD Base :: Virpil MongoosT-50CM3 Throttle :: 3 x CubeSim ext mini screens with TM Cougar MFD Bezels :: Asus ROG Pugio 503 Gaming Mouse & Razer BlackWidow mech kb :: TrackIR 5 Pro & Cap Clip :: Win 11 64 Bit 😉

Link to comment
Share on other sites

I had simular problems. DCS VR would crash on Syria map as soon as I shifted the IPD slider on my Reverb G2. I noticed a massive frame drop on the few times it didn't crash. Also using FPSVR on Syria map was impossible. Game would freeze or fps would dive below 10.

I rolled back to Nvidia driver 446.14 and all problems were gone.


Edited by motjoo
Link to comment
Share on other sites

  • 3 weeks later...
  • Recently Browsing   0 members

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