Apex Legends Crash no error - PC (apex_crash.txt)

[JBM_NY]

new patch 1.1.3 is fixed the intel cpu game crash issue but problem is ( video settings sometime reset to default automatic ) if you use custom high or low settings anyway no more crash for me now

[_S7ORM-BRINGR]

@OrioStorm , hello, just crashed, my first time after the patch. You will find the log attached.

[OrioStorm]

@_S7ORM-BRINGR, the address of the next instruction to execute is in RIP. The address that gave the execute violation is in the crash report.

00007FF635AC5B39 -- RIP address

00007FF600005B39 -- execute violation address

Notice that the only difference is that some of the address bits have been zero'd out in the execute violation address. These addresses should always be the same if the CPU was working right. Were you overclocking when this happened?

We saw this sort of crash a lot before I "jiggled the handle" in patch 1.1.3. This is the first time I've seen this category of crash since then.

[_S7ORM-BRINGR]

---

@OrioStorm wrote:

@_S7ORM-BRINGR, the address of the next instruction to execute is in RIP. The address that gave the execute violation is in the crash report.

00007FF635AC5B39 -- RIP address

00007FF600005B39 -- execute violation address

Notice that the only difference is that some of the address bits have been zero'd out in the execute violation address. These addresses should always be the same if the CPU was working right. Were you overclocking when this happened?

We saw this sort of crash a lot before I "jiggled the handle" in patch 1.1.3. This is the first time I've seen this category of crash since then.

---

Yes, it is overclocked - 5.0 GHZ at the moment. My first crash after the patch.

[_S7ORM-BRINGR]

---

@_S7ORM-BRINGR wrote:

---

@OrioStorm wrote:

@_S7ORM-BRINGR, the address of the next instruction to execute is in RIP. The address that gave the execute violation is in the crash report.

00007FF635AC5B39 -- RIP address

00007FF600005B39 -- execute violation address

Notice that the only difference is that some of the address bits have been zero'd out in the execute violation address. These addresses should always be the same if the CPU was working right. Were you overclocking when this happened?

We saw this sort of crash a lot before I "jiggled the handle" in patch 1.1.3. This is the first time I've seen this category of crash since then.

---

Yes, it is overclocked - 5.0 GHZ at the moment. My first crash after the patch.

---

An just got another one..

[SeTiNg_Flash]

Apex crash after i change video settings to Low Preset

[OrioStorm]

@SeTiNg_Flash, the log shows that this is a crash inside your nVidia driver, since the crashing module is "nvwgf2umx". I'd recommend updating your driver, and then reporting the issue to nVidia if it still crashes in there (or if you were already up-to-date).

[SeTiNg_Flash]

@OrioStormthis strange, becouse game stopped crashing after I changed the graphics settings to Medium graphics settings

[asetepa]

i have this crash message  

crash:
{
module@00007FFB4FA20000: 000000000007276D
EXCEPTION_ACCESS_VIOLATION(write): 0000000000000188
}
cpu: "AMD Ryzen 5 2400G with Radeon Vega Graphics "
ram: 16 // GB
callstack:
{
KERNELBASE: 00000000000EBDC0
ntdll: 00000000001088A2
ntdll: 00000000000A1D4D
ntdll: 000000000008B5E6
ntdll: 000000000009A59E
ntdll: 000000000009F7DD
ntdll: 000000000000D856
ntdll: 000000000009E70E
module@00007FFB4FA20000: 000000000007276D
module@00007FFB4FA20000: 0000000000072A1D
module@00007FFB4FA20000: 00000000000183B0
module@00007FFB511C0000: 000000000000D3BE
d3d11: 00000000000658DA
GDI32: 00000000000045A1
ntdll: 000000000004A49C
ntdll: 000000000004A176
ntdll: 000000000004A010
ntdll: 000000000002C814
ntdll: 00000000000265D9
KERNEL32: 0000000000014034
ntdll: 0000000000073691
}
registers:
{
rax = 0
rbx = 1
rcx = 0x0000025266CF6D18
rdx = 262144 // 0x00040000
rsp = 0x000000A904CDF450
rbp = 2
rsi = 3
rdi = 0
r8 = 0
r9 = 2
r10 = 0x00007FFB577D4A04
r11 = 582 // 0x00000246
r12 = 1
r13 = 0x0000025294F500B8
r14 = 0
r15 = 0x0000025266CF6B20
rip = 0x00007FFB4FA9276D
xmm0 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm1 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm2 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm3 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm4 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm7 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm8 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm9 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm12 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm13 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm14 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm15 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
}

[AbideDudeAbide]

Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number GeForce GTX 970M
Enter RAM memory size in GB 16
What is your gamertag/PSN ID/EA Account name? AbideDudeAbide
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible.
Which Legend were you playing (if applicable)? Any
Which Legends were your squad mates using (if applicable)?
Where did the issue occur? In a match
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. runoff
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. looting
Did your squad mates also experience the issue? No
How many matches had you played in a row before the issue occurred? 0
When did this happen? (dd.mm.yy hh:mm) 01.06.19 10:24 EDT
How often does the bug occur? Often (50% - 99%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? The sound begins to decline, then the game freezes, then briefly unfreezes, then disconnects from the server
What should be happening instead? The game should be running
Steps: How can we find the bug ourselves? I'm not sure

‌

crash:
{
msvcrt: 000000000002A9E6
EXCEPTION_ACCESS_VIOLATION(write): 0000000000000000
}
cpu: "Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz"
ram: 16 // GB
callstack:
{
KERNELBASE: 000000000008667C
ntdll: 00000000000A81CB
ntdll: 000000000008FD56
ntdll: 00000000000A477F
ntdll: 0000000000004BEF
ntdll: 00000000000A34EE
msvcrt: 000000000002A9E6
sapi_onecore: 000000000011CA8F
sapi_onecore: 000000000011CAC9
sapi_onecore: 000000000003F4D1
sapi_onecore: 000000000015E8C7
sapi_onecore: 0000000000026C30
sapi_onecore: 0000000000026BE4
sapi_onecore: 0000000000026B7B
module@00007FFACF2C0000: 000000000009759D
module@00007FFACF2C0000: 00000000000978CF
module@00007FFACF2C0000: 0000000000097C5C
ntdll: 0000000000048F07
ntdll: 00000000000435BC
ntdll: 0000000000066DCD
KERNEL32: 000000000001D62A
R5Apex: 0000000001245764
R5Apex: 0000000001245700
R5Apex: 00000000004B0BE2
R5Apex: 0000000001206836
Activation64: 0000000000011050
Activation64: 0000000000008F82
KERNEL32: 0000000000017974
ntdll: 000000000006A271
}
registers:
{
rax = 0
rbx = 0x000000FE241AED80
rcx = 0x2C6D57A9F9280000
rdx = 0
rsp = 0x000000FE241AED10
rbp = 0x000002D06B05C370
rsi = -1 // 0xFFFFFFFF
rdi = 0x000002D06B049BD0
r8 = 0
r9 = 0x000000FE241AE320
r10 = 0x00007FFB24171E94
r11 = 0x000000FE241AE750
r12 = 0x000002D06B05C370
r13 = 0
r14 = 0x000000FE241AED78
r15 = 0x00007FFAF3BF4070
rip = 0x00007FFB220FA9E6
xmm0 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm1 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm2 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm3 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm4 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm7 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm8 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm9 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm12 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm13 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm14 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm15 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
}
build_id: 1557879477