Jump to content

Consistent crash due to ACCESS_VIOLATION in Persian Gulf with Harrier


Recommended Posts

Posted

I have a very consistent crash in a test mission in persian gulf flying the harrier.

It is over a small town on the east coast (Shiran?). I fire two AGM-65Ds at two WW2 tanks. Both hit. When I try to slew the next missile onto a target the game crashes, every time.

I am in active pause the enitre time (still learning!)

Log files attached, thanks for any advice :-)

dcs.log-20180524-205157.zip

Posted

Thanks - I've updated my graphics drivers and still have the same issue.

 

 

The crash also happens in a mission another person created.

 

 

 

Same symptoms: Harrier on PG map, fired two mavericks. crash when I start to try slewing the third one on.

Posted

I think I've confirmed this is a harrier bug: on the caucasus map, if I fire two agm 65d's, then try to slew a agm-65g, the moment I try to slew it it crashes.

  • ED Team
Posted (edited)

Thanks for the info, I will try and reproduce

 

edit

 

I was unable to reproduce on my machine.

 

if you have a fresh set of dcs.logs with the track I will take a look again.

 

thanks

Edited by BIGNEWY

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, PIMAX Crystal

  • ED Team
Posted

Thanks

 

2018-05-27 08:14:32.036 INFO EDCORE: try to write dump information

2018-05-27 08:14:32.061 INFO EDCORE: # -------------- 20180527-081432 --------------

2018-05-27 08:14:32.061 INFO EDCORE: C:\Windows\system32\nvwgf2umx.dll

2018-05-27 08:14:32.062 INFO EDCORE: # C0000005 ACCESS_VIOLATION at F612E67B 00:00000000

2018-05-27 08:14:32.245 INFO EDCORE: 00000000 00000000 0000:00000000

2018-05-27 08:14:32.322 INFO EDCORE: F612E67B 2683F130 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+12A2B

2018-05-27 08:14:32.323 INFO EDCORE: F6147323 2683F1F0 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+2B6D3

2018-05-27 08:14:32.324 INFO EDCORE: F61435C0 2683F410 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+27970

2018-05-27 08:14:32.325 INFO EDCORE: F6139805 2683F490 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+1DBB5

2018-05-27 08:14:32.341 INFO EDCORE: F6139B1C 2683F660 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+1DECC

2018-05-27 08:14:32.342 INFO EDCORE: F613AD1A 2683F6E0 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+1F0CA

2018-05-27 08:14:32.343 INFO EDCORE: F62FCC3D 2683F710 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+1E0FED

2018-05-27 08:14:32.344 INFO EDCORE: F62F99AB 2683F920 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+1DDD5B

2018-05-27 08:14:32.345 INFO EDCORE: F5985F32 2683FBF0 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+1B4E2

2018-05-27 08:14:32.346 INFO EDCORE: F5AE430F 2683FC90 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+1798BF

2018-05-27 08:14:32.347 INFO EDCORE: F5AD8140 2683FCC0 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+16D6F0

2018-05-27 08:14:32.348 INFO EDCORE: F5ADFFFF 2683FCF0 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+1755AF

2018-05-27 08:14:32.348 INFO EDCORE: F5ADFEA6 2683FD40 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+175456

2018-05-27 08:14:32.349 INFO EDCORE: F5AD7EAD 2683FD70 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+16D45D

2018-05-27 08:14:32.350 INFO EDCORE: F61C844A 2683FDA0 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+AC7FA

2018-05-27 08:14:32.355 INFO EDCORE: F65C9EA0 2683FDD0 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+4AE250

2018-05-27 08:14:32.358 INFO EDCORE: 77B559CD 2683FE00 0000:00000000 C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D

2018-05-27 08:14:32.359 INFO EDCORE: 77CB383D 2683FE50 0000:00000000 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+1D

2018-05-27 08:14:40.725 INFO EDCORE: Minidump created.

2018-05-27 08:14:40.906 INFO DCS: try to write track file

2018-05-27 08:14:43.194 INFO DCS: 'C:\Users\Finn\Saved Games\DCS.openbeta\Logs\dcs.20180527-081432.crash' deleted successfully

2018-05-27 08:14:43.386 INFO DCS: 'C:\Users\Finn\Saved Games\DCS.openbeta\Logs\dcs.20180527-081432.dmp' deleted successfully

=== Log closed.

 

I am still unable to reproduce sadly. The crash looks like a nvidia driver crash here

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, PIMAX Crystal

Posted

Had the exact same type of errors and crashes until I disabled the XMP profile assigned to my RAM

Are you using XMP to boost your RAM ?

Win10 x64, Intel core I9 9900k@5ghz, 32GB DDR4, RTX2080 ti, MSI Z370 Tomahawk mobo, M.2 SSD, Warthog HOTAS, home made trackIr, Pimax 8K

Posted
Thanks

 

 

 

I am still unable to reproduce sadly. The crash looks like a nvidia driver crash here

 

 

 

Nvidia driver is fully uptodate.

Apart from having set FXAA in Nvidia control panel instead of using ingame MSAA, everything else is set to default.

 

 

Maybe DCS is doing something that the Nvidia drivers doesn´t like cry.gif

| i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD |  1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |

Posted

And here are my settings:

 

 

DCS_Settings.thumb.jpg.89418f08e0316db9810879c79a2a2f42.jpg

 

 

Only addition is FXAA set to On in the Nvidia Control Panel.

| i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD |  1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |

Posted

Gulf map + Harrier = hundreds of EDTERRAINGRAPHICS41 errors and crash

PC: i7-13700K - Gigabyte RTX 5080 GAMING OC - 64GB DDR5 6400 - VPC MongoosT-50CM3 - VKB GF pro - MFG Crosswind - Msi MPG321UR-QD + LG OLED 32GS95UE - TrackIR5 - Quest 3

  • Recently Browsing   0 members

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