Community Crashing Troubleshooting Guide

---

@kwerbias wrote:

Reading these most recent posts about voltage is what fixed it for me. I too am overclocking an i7 8086k from 4.0 to 5.0ghz set to all cores. I had kept my voltage lower at 1.198 for a while since it was stable in every app/ stress test before playing apex. however, apex uses avx2 instructions which need an offset in the bios when they are in use as they address significantly more power to your cores. so either vcore needs to go way higher or you tell your cores to run on a -2 or -4 offset (effectively -200 or -400mhz) whatever runs best. 

I remember touching these AVX offset settings a long time ago. turns out they were okay, set to -2, so I went with upping my voltage a bit. I went up slowly, experiencing the same crashes to desktop every game or every other game until settling on 1.225 which now for 10 games has been stable. I'll update as well after 20 or 30 to see if it remains the same.

I guess this is the first AVX2 instructions use game i've played because nothing ever gave me any sweat at the lower, cooler voltage. Increasing it did see my load temps hitting 55C vs. 48C from before. I just like to run my hardware as cold as possible at all times. Anyway, thanks to whoever noticed this first and started trying to troubleshoot it in relation to the types of errors being shown in event viewer. 

I can actually start playing the game now! :D

some more info:

 

I run the game 1920x1080, with gsync on in nvidia control panel, vsync disabled in-game. FPS capped to 238fps using RTSS. Video settings set to low for everything. Texture streaming set to 2GB. Model quality set to High. Framerate is about 125-150 when flying and once landed caps to 238fps.

 

Operating System

Windows 10 Pro 64-bit Version 1803 (OS Build 17134.590)

CPU

Intel 8086k Core i7 @ 5.00GHz at 1.225v 55 °C

Coffee Lake 14nm Technology

RAM

32.0GB Dual-Channel Corsair Dominator Platinum PC3200 @ 1600MHz (14-14-14-34)

Motherboard

ASUSTeK COMPUTER INC. ROG MAXIMUS XI HERO (WI-FI) (LGA1151)

Graphics

ROG PG258Q (1920x1080@240Hz)

ROG PG278Q (2560x1440@144Hz)

NVIDIA GeForce RTX 2080 Ti XC Hybrid (EVGA) @ 2040mhz boost clock 38 °C

GeForce Drivers 419.35 WHQL

Storage

1863GB Samsung SSD 860 EVO 2TB (SATA (SSD))

1907GB Micron\_1100\_MTFDDAK2T0TBN (SATA (SSD))

931GB Samsung SSD 960 EVO 1TB (m.2 PCI-E x4 (SSD))

Power Supply

Seasonic PRIME SSR-1000PD 80+ Platinum 1000W

Optical Drives

No optical disk drives detected

Audio

Sound BlasterX AE-5

Mouse

Logitech G305 Wireless

Keyboard

Corsair K65 RGB

AIO Cooler

Corsair H110i GTX

Printer

Brother HL-L2360D series laser

Network/Wireless devices

Intel Ethernet Connection I219-V

Intel(R) Wireless-AC 9560 (disabled)

Bluetooth enabled (onboard)

 

Notable software running in the taskbar: Corsair iCue, Greenshot, 1Password, Samsung Magician, Sound Blaster Connect 2, NVIDIA Control Panel, Color Sustainer (icc color profile keeper software), Display Fusion Pro, Logitech Gaming Software, Discord, Riva Tuner Statistics Server, EVGA Precision X1 - all up to date versions.

---

UPDATE!!! :

After about 12 hours of playing I can say I fixed it for good. The game doesn't crash when I'm on 4.6 Ghz (stock OC). Thank you for sharing the AVX info, I didn't know that. The upcoming days I will test with a avx offset to see if I can manage to hit higher frequencies.
This is a game engine specific, which needs to be fixed, unfortunately.
I can now say 100% that this kind of crash is a CPU related issue. Took me a month to figure it out...