April 2019 - last edited April 2019
UPDATE BELOW
I usually dont * and try to provide a solution for complaints I make... but this is absolutely crazy. Prior to the most recent patch I had crashes and dropped games MAYBE 1-2 times a week. Understandable... new game... got it coach. After this most recent patch I get them HOURLY! Yes... hourly. Here are the proof and logs just from TONIGHT! TONIGHT!!!! This has been going on since the most recent patch.
Get a legendary peacekeeper and gold chest piece
*APEX* nah fam crash to desktop with no error
Just get done wiping a squad and up 4 or 5 kills
*APEX* LOLOLOLOL bye Felicia
Whats crazy is no matter if its C2DT with or without an error, I can still load into the game and be back in the group I was with already. But I lose experience and all the data from the game I was playing. I have tried all the youtube/reddit fix solutions but to no avail
Attached is a word document detailing the time and date of crashes just today. PC is not even 3 months old. Specs below.
Please fix your game.
-the_k1g
PC SPECS:
8700K OC'd to 4.8ghz
windows 10
32gb ram
2070
nothing CPU or GPU intensive running while gaming
UPDATE 1:
Contrary to being told to bump down your overclock to fix the crashes; I went ahead and bumped it up. Mom didnt raise no quitters here. It was only a very slight bump. I went from 4.8ghz (4.77 core clock according to CPU monitoring stuffs) and 1.285v across all core to 4.9ghz and 1.36v. I tried 5 but didnt want to bump voltage to 1.4.
The goal here is to work down to see if there is an OC voltage that it doesnt respond to and/or a frequency that it doesnt like either. I only played 2 hours at 4.9 but that doesnt mean it wont crash again. Here is the current crash logs for today. You will notice that I get two crashes regardless of what my in game settings were. Then I redid the OC and its been okay. Statistically speaking the game crumbles every hour or so so this has been a win so far. Here is the log. Take what you will but frequency and voltage changes (up or down) to find a sweet spot may be the solution. More testing soon.
4/9/19 Started playing at 7:43pm (turned ALL graphic settings to medium/low)
4/9/19 @ 8:21PM CST C2DT w/error
crash:
{
R5Apex: 00000000002F2E2A
EXCEPTION_ACCESS_VIOLATION(write): 00000000000004B0
}
cpu: "Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz"
ram: 32 // GB
callstack:
{
KERNELBASE: 000000000008669C
ntdll: 00000000000A80CB
ntdll: 000000000008FD36
ntdll: 00000000000A468F
ntdll: 0000000000004BEF
ntdll: 00000000000A33FE
R5Apex: 00000000002F2E2A
R5Apex: 00000000004C0B56
R5Apex: 00000000004C0F47
R5Apex: 00000000004BF767
R5Apex: 00000000004C1502
KERNEL32: 00000000000181F4
ntdll: 000000000006A251
}
registers:
{
rax = 128596 // 0x0001F654
rbx = 0x000000A02DBBC200
rcx = 0
rdx = 1
rsp = 0x000000A02D60F7B0
rbp = 1844 // 0x00000734
rsi = 0x000001C4D03B68E0
rdi = 1197 // 0x000004AD
r8 = 0
r9 = 64326 // 0x0000FB46
r10 = 447828 // 0x0006D554
r11 = 447828 // 0x0006D554
r12 = 448215 // 0x0006D6D7
r13 = 448215 // 0x0006D6D7
r14 = 1
r15 = 0x000001C2D2374CD0
rip = 0x00007FF61C792E2A
xmm0 = [ [899829, 0, 0, 0], [0x495BAF50, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [4284900, 0, 0, 0], [0x4A82C3C8, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [1.2223067, 0, 0, 0], [0x3F9C748C, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [1099867, 0, 0, 0], [0x498642D8, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [4084862, 0, 0, 0], [0x4A7951F8, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [2756.2605, 0, 0, 0], [0x452C442B, 0x00000000, 0x00000000, 0x00000000] ]
xmm6 = [ [4084862, 0, 0, 0], [0x4A7951F8, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [3.4028235e+38, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm9 = [ [3.4028235e+38, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm12 = [ [0.60000002, 0, 0, 0], [0x3F19999A, 0x00000000, 0x00000000, 0x00000000] ]
xmm13 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm14 = [ [13.8, 0, 0, 0], [0x415CCCCD, 0x00000000, 0x00000000, 0x00000000] ]
xmm15 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
}
build_id: 1553899726
4/9 @ 9:30 PM CST C2DT w/error (setting reverted to high)
crash:
{
R5Apex: 00000000002F2DCA
EXCEPTION_BREAKPOINT: 80000003
}
cpu: "Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz"
ram: 32 // GB
callstack:
{
KERNELBASE: 000000000008669C
ntdll: 00000000000A80CB
ntdll: 000000000008FD36
ntdll: 00000000000A468F
ntdll: 0000000000004BEF
ntdll: 00000000000A33FE
R5Apex: 00000000002F2DCA
R5Apex: 00000000004C0B56
R5Apex: 00000000004C0F47
R5Apex: 00000000004BF767
R5Apex: 00000000004C1502
KERNEL32: 00000000000181F4
ntdll: 000000000006A251
}
registers:
{
rax = 1
rbx = 0x000000B73B3BBB20
rcx = 0
rdx = 16
rsp = 0x000000B73AE0F580
rbp = 725 // 0x000002D5
rsi = 0x000002924A9E9320
rdi = 1913 // 0x00000779
r8 = 0
r9 = 23704 // 0x00005C98
r10 = 447828 // 0x0006D554
r11 = 447828 // 0x0006D554
r12 = 448215 // 0x0006D6D7
r13 = 448215 // 0x0006D6D7
r14 = 1
r15 = 0x0000028F870E31F0
rip = 0x00007FF61C792DCA
xmm0 = [ [2.1000008e+11, 0, 0, 0], [0x524393EC, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [1e+12, 0, 0, 0], [0x5368D4A5, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [5.7588711, 0, 0, 0], [0x40B848AC, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [1.2093635e+12, 0, 0, 0], [0x538CC9D7, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [6.3664032e+08, 0, 0, 0], [0x4E17C971, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [-6.0122151, -6.0122151, 49.445347, -6.0122151], [0xC0C06411, 0xC0C06411, 0x4245C809, 0xC0C06411] ]
xmm6 = [ [6.3664032e+08, 0, 0, 0], [0x4E17C971, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [1542564.3, 2742336.5, 4284901, 8398405], [0x49BC4D22, 0x4A276102, 0x4A82C3CA, 0x4B002645] ]
xmm9 = [ [68558416, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x4C82C3CA, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm12 = [ [0.60000002, 0, 0, 0], [0x3F19999A, 0x00000000, 0x00000000, 0x00000000] ]
xmm13 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm14 = [ [13.8, 0, 0, 0], [0x415CCCCD, 0x00000000, 0x00000000, 0x00000000] ]
xmm15 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
}
build_id: 1553899726
4/9 @ 10 PM CST – changed overclock settings to 4.9ghz + 1.36 CPU voltage (from 4.8ghz + 1.285v)
April 2019
April 2019
April 2019
Interesting.
This all kind of goes against conventional widsom wisdom of what OC’ing actually does. Why would a game crash and not throttle because of an overclock? If it’s more demanding then turning down all the settings would work right (I’m at max everything besides the usual texture streaming budgets and whatnot).
If the game is now more demanding and the game wont throttle then turning down settings should alleviate the crashes. If not then it has nothing to do with the overclock as the overclock is not having great demand out on it and therefore not being heavily drawn from.
In going to do three tests. I’m going to reduce the settings to nothing and play the game as is currently. Then I’m going to test different OC frequencies and voltages to see if the game responds to a clock frequency better than what I have now. Lastly, I will try reverting.
I just dont see how reverting back to stock is going to fix anything. If the game is demanding as stated then it will still crash at a lower frequency.
Weird. But whatever I’ll try figuring this out. WISH THE DEVELOPERS WOULD ENLIGHTEN US A BIT *footstomp wink wink*
April 2019
@the_k1g wrote:Interesting.
This all kind of goes against conventional widsom wisdom of what OC’ing actually does. Why would a game crash and not throttle because of an overclock? If it’s more demanding then turning down all the settings would work right (I’m at max everything besides the usual texture streaming budgets and whatnot).
If the game is now more demanding and the game wont throttle then turning down settings should alleviate the crashes. If not then it has nothing to do with the overclock as the overclock is not having great demand out on it and therefore not being heavily drawn from.
In going to do three tests. I’m going to reduce the settings to nothing and play the game as is currently. Then I’m going to test different OC frequencies and voltages to see if the game responds to a clock frequency better than what I have now. Lastly, I will try reverting.
I just dont see how reverting back to stock is going to fix anything. If the game is demanding as stated then it will still crash at a lower frequency.
Weird. But whatever I’ll try figuring this out. WISH THE DEVELOPERS WOULD ENLIGHTEN US A BIT *footstomp wink wink*
Let us know what worked for you, but I suspect that increasing the voltage to your CPU might help.
April 2019
@VarcanG wrote:
@the_k1g wrote:Interesting.
This all kind of goes against conventional widsom wisdom of what OC’ing actually does. Why would a game crash and not throttle because of an overclock? If it’s more demanding then turning down all the settings would work right (I’m at max everything besides the usual texture streaming budgets and whatnot).
If the game is now more demanding and the game wont throttle then turning down settings should alleviate the crashes. If not then it has nothing to do with the overclock as the overclock is not having great demand out on it and therefore not being heavily drawn from.
In going to do three tests. I’m going to reduce the settings to nothing and play the game as is currently. Then I’m going to test different OC frequencies and voltages to see if the game responds to a clock frequency better than what I have now. Lastly, I will try reverting.
I just dont see how reverting back to stock is going to fix anything. If the game is demanding as stated then it will still crash at a lower frequency.
Weird. But whatever I’ll try figuring this out. WISH THE DEVELOPERS WOULD ENLIGHTEN US A BIT *footstomp wink wink*
Let us know what worked for you, but I suspect that increasing the voltage to your CPU might help.
Will do. I suspect the same or at least a small frequency change “could” help balance the game. I’ve been wanting to press 5.0 for a while now just to see if the silicone lottery is in my favor. But I’m not opposed to going down either.
April 2019 - last edited April 2019
UPDATE:
EDIT: also i turned all my setting to medium or low if no medium is available
started playing at 7:41PM today and I just C2DT w/error. Here is the code:
crash:
{
R5Apex: 00000000002F2E2A
EXCEPTION_ACCESS_VIOLATION(write): 00000000000004B0
}
cpu: "Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz"
ram: 32 // GB
callstack:
{
KERNELBASE: 000000000008669C
ntdll: 00000000000A80CB
ntdll: 000000000008FD36
ntdll: 00000000000A468F
ntdll: 0000000000004BEF
ntdll: 00000000000A33FE
R5Apex: 00000000002F2E2A
R5Apex: 00000000004C0B56
R5Apex: 00000000004C0F47
R5Apex: 00000000004BF767
R5Apex: 00000000004C1502
KERNEL32: 00000000000181F4
ntdll: 000000000006A251
}
registers:
{
rax = 128596 // 0x0001F654
rbx = 0x000000A02DBBC200
rcx = 0
rdx = 1
rsp = 0x000000A02D60F7B0
rbp = 1844 // 0x00000734
rsi = 0x000001C4D03B68E0
rdi = 1197 // 0x000004AD
r8 = 0
r9 = 64326 // 0x0000FB46
r10 = 447828 // 0x0006D554
r11 = 447828 // 0x0006D554
r12 = 448215 // 0x0006D6D7
r13 = 448215 // 0x0006D6D7
r14 = 1
r15 = 0x000001C2D2374CD0
rip = 0x00007FF61C792E2A
xmm0 = [ [899829, 0, 0, 0], [0x495BAF50, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [4284900, 0, 0, 0], [0x4A82C3C8, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [1.2223067, 0, 0, 0], [0x3F9C748C, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [1099867, 0, 0, 0], [0x498642D8, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [4084862, 0, 0, 0], [0x4A7951F8, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [2756.2605, 0, 0, 0], [0x452C442B, 0x00000000, 0x00000000, 0x00000000] ]
xmm6 = [ [4084862, 0, 0, 0], [0x4A7951F8, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [3.4028235e+38, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm9 = [ [3.4028235e+38, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm12 = [ [0.60000002, 0, 0, 0], [0x3F19999A, 0x00000000, 0x00000000, 0x00000000] ]
xmm13 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm14 = [ [13.8, 0, 0, 0], [0x415CCCCD, 0x00000000, 0x00000000, 0x00000000] ]
xmm15 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
}
build_id: 1553899726
What does exception access violation (write) mean? And how would this pertain to an overclock? If overclocking is related to crashing why are my errors fluctuating and not consistently one or two things?
April 2019
crash:
{
R5Apex: 00000000002F2DCA
EXCEPTION_ACCESS_VIOLATION(write): FFFFFFFFFFFFFF8B
}
cpu: "Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz"
ram: 16 // GB
callstack:
{
KERNELBASE: 000000000008667C
ntdll: 00000000000A810B
ntdll: 000000000008FD56
ntdll: 00000000000A46AF
ntdll: 0000000000004BEF
ntdll: 00000000000A341E
R5Apex: 00000000002F2DCA
R5Apex: 00000000004C0B56
R5Apex: 00000000004C0F47
R5Apex: 00000000004BF767
R5Apex: 00000000004C1502
KERNEL32: 00000000000181F4
ntdll: 000000000006A271
}
registers:
{
rax = 0
rbx = 0x0000007AB93BBB00
rcx = 1
rdx = 2
rsp = 0x0000007AB900F3F0
rbp = 741 // 0x000002E5
rsi = 0x000001AC2D762540
rdi = 1101 // 0x0000044D
r8 = 0
r9 = 55593 // 0x0000D929
r10 = 447828 // 0x0006D554
r11 = 447828 // 0x0006D554
r12 = 448215 // 0x0006D6D7
r13 = 448215 // 0x0006D6D7
r14 = 1
r15 = 0x000001AB23C4E2F0
rip = 0x00007FF707272DCA
xmm0 = [ [548017.75, 0, 0, 0], [0x4905CB1C, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [2609608, 0, 0, 0], [0x4A1F4720, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [0.12471768, 0, 0, 0], [0x3DFF6BFB, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [68347.5, 0, 0, 0], [0x47857DC0, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [3089278.3, 0, 0, 0], [0x4A3C8DF9, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [374.48026, 374.48026, 374.48026, 305.25116], [0x43BB3D79, 0x43BB3D79, 0x43BB3D79, 0x4398A026] ]
xmm6 = [ [3089278.3, 0, 0, 0], [0x4A3C8DF9, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [0.12471768, 0, 0, 0], [0x3DFF6BFB, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [144020.25, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x480CA510, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm9 = [ [3.4028235e+38, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm12 = [ [0.5, 0, 0, 0], [0x3F000000, 0x00000000, 0x00000000, 0x00000000] ]
xmm13 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm14 = [ [13.8, 0, 0, 0], [0x415CCCCD, 0x00000000, 0x00000000, 0x00000000] ]
xmm15 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
}
build_id: 1553899726
April 2019
April 2019
I'm in the same boat as the OP - constant crashes - tried everything software related (even as far as formatting) and still get crashes.
I've tried low AF settings - I've tried resetting BIOS to defaults - i've tried a different HDD - i've tried different ram - nothing seems to make any difference - and it is JUST APEX.