I crashed when I jumped at a Zipline.
EA Staff (Retired)Thanks for these logs. I'm the engineer who implemented the crash log system. I'm also the one who used the logs when we first implemented the voluntary crash reporting system to find and fix the bug causing the vast majority of the crashes we were seeing. After that fix, we saw the rates of players vanishing from servers plummet.
I just found this thread and am now looking into each of these logs. I see four different crash reports in this thread.
One of them is the one I just commented on, in msvcrt.dll when quitting. As I said, I don't think we can do anything about that one, since it's Microsoft's code that is crashing, but at least it only seems to happen when you already wanted to exit anyway.
The other three are in r5apex at three different offsets: 00000000002F2DCA, 00000000002F2E2A, 00000000002F2E9E. I'll comment on these in reverse order.
The last one (00000000002F2E9E) happened once for TlElTlRlIlS and is the most confusing. That's executing code in the middle of an instruction. That shouldn't be possible.
The middle one (00000000002F2E2A) happened for two people, kaolinAngel_TTV (original poster) and umarusann. This looks like it might be a legitimate stack corruption bug, but it might also be an overclocking / overheating bug. I'm in the process of analyzing the code to figure out how this might be possible. This is hard, and may take some time. I can't just analyze the human-readable code we actually wrote; I also have to analyze the machine-readable code the compiler generated from what we wrote.
The first one (00000000002F2DCA) happened for 12 people in this thread, making it the most common. This one is also bizarre. It's executing an instruction that just asks if a CPU register is zero. (In very basic terms, a register is a place inside the CPU that holds a number that's being used in its computations. In one sense, it's like a super tiny cache of super fast memory. If that doesn't make sense, don't worry about it!) That instruction is causing either a CPU breakpoint to be hit (10x), or causing a write access violation (2x). This instruction should not be able to do either of these things. It's not a breakpoint, it's a bit test. It doesn't write memory, it reads a register.
Interestingly, all three of these crashes are in the same function. This is also the function that sometimes reports an execution access violation on a memory location that isn't the current or next instruction, which should also be impossible for a properly functioning CPU. When that crash happens, I made the latest patch of Apex tell you that the crash is probably due to overclocking or overheating.
So, the most likely explanation I can come up with for these other crashes is that your CPU is overheating, possibly due to overclocking. xjungleWarrior even helpfully mentioned that he had a 3.7 GHz CPU overclocked to 4.9 GHz. Thanks for that extra tidbit!
I have worked as a software engineer in the games industry for nearly 20 years, but before that I earned a Master's in electrical engineering from Stanford, with a specialization in microprocessor design. So, while not an expert on overclocking/overheating behavior of modern Intel CPUs, I do have a lot of relevant experience and background. I'm a very logical and scientific guy. So, I don't suggest overclocking/overheating lightly. I suggest it because it's the most logical explanation.
Overclocking / overheating can cause very rare CPU faults. These can even show up only when you execute a particular sequence of instructions, so you can think that your computer is perfectly stable when it's overclocked, and then one day you install a new program and it crashes a lot. It's only natural to think that it's the program's fault, since everything else worked fine for so long. But CPU clock speeds are set to make sure that the CPU *always* finishes every possible instruction sequence in time for the next instruction to start. If you increase the clock speed, you give it less time to finish instructions. That will usually work, since there will usually be some "buffer" time at the end of each instruction. But in very rare cases, it needed the whole clock cycle to finish this particular instruction with that particular data, and something else need the results right away, and then your CPU will crash.
Overclocking can also lead to overheating, but overheating can happen even without overclocking, such as in a hot room. These can have similar effects as overclocking, but overheating can be even worse. It can lead to more thermal noise inside the CPU, especially when the CPU is working hard, which can cause bits to flip inside the CPU when they shouldn't. If that happens, your CPU is likely to crash.
All that to say, the most likely explanation for the vast majority of these crashes is overheating and/or overclocking.
If you're experiencing these issues, please try these things and reply to this thread. I really want Apex to be stable for all our players, which is why I implemented the crash log in the first place!
Thanks again for all these logs, and hopefully together we'll be able to figure out how to keep you all in the arena!
Hi,
Thanks for feedback. I've reverted my 8700k to 4.7Ghz with temps not exceeding 85C also run default RAM settings. Still same result and crash every other game.
It's not temperature or OC related as I've been running OC settings for the past months without any single crash.
There is something wrong with the code after last update, please sort it out.
@Benef1cient wrote:Hi,
Thanks for feedback. I've reverted my 8700k to 4.7Ghz with temps not exceeding 85C also run default RAM settings. Still same result and crash every other game.
It's not temperature or OC related as I've been running OC settings for the past months without any single crash.
There is something wrong with the code after last update, please sort it out.
85C is very hot for a cpu and will definitely shorten the life span. Invest in a new cooler preferably an AIO cooler.
Considerably new PC (3 months old) with quite decent setup. Tried so many different things that I can't even list them all anymore.
The game keeps crashing, sometimes generating DMP file, sometimes not. Installed fresh OS yesterday due to new SSD NVME Raid0 setup. Nothing else installed, just standard, out of the box OS, drivers, Origin and Apex and guess what ... crash after crash.
Just played the most bizarre ranked game and crashed 3 times in a single game.
Majority of these DMP files are similar to this (right now I have 48 of DMP files in my game folder):
EXCEPTION_RECORD: (.exr -1)ExceptionAddress: 00007ff6f6bf6367 (r5apex+0x0000000000236367) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000008 Parameter[1]: 00007ff6f0bf6367 Attempt to execute non-executable address 00007ff6f0bf6367 PROCESS_NAME: r5apex.exe EXECUTE_ADDRESS: 7ff6f0bf6367 FAILED_INSTRUCTION_ADDRESS: r5apex+236367 00007ff6`f6bf6367 f30f597f0c mulss xmm7,dword ptr [rdi+0Ch] ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja w 0x%p odwo a a si do pami ci pod adresem 0x%p. Pami nie mo e by %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000008 EXCEPTION_PARAMETER2: 00007ff6f0bf6367 STACK_TEXT: 00000099`d0451e20 00007ff6`f6da2356 : 000001f5`9e4b7c80 00007ff6`ff74ac40 ffcdffff`fffffffb 00007ff6`00000001 : r5apex+0x236367 00000099`d045b580 00007ff6`f6da2747 : 00007ff6`f69c0000 00000000`00000007 00007ff6`ff7a06c8 00000000`00000000 : r5apex!LauncherMain+0x10af6 00000099`d045b5b0 00007ff6`f6bf6142 : 00000000`00000006 00007ff6`f6c36d2d ffffffff`ffffffff 00000000`00000000 : r5apex!LauncherMain+0x10ee7 00000099`d045b650 00007ff6`f6da2356 : 000001f5`9e4afc30 00007ff6`ff74b340 ffdfffff`ffffffff 00007ff6`00000001 : r5apex+0x236142 00000099`d045fce0 00007ff6`f6da2747 : 00007ff6`f69c0000 00000000`00000007 00007ff6`ff7a06c8 00000000`00000000 : r5apex!LauncherMain+0x10af6 00000099`d045fd10 00007ff6`f6da0f95 : 00000000`00000000 00007ff6`f726ce40 ffffffff`ffffffff 00000000`00000000 : r5apex!LauncherMain+0x10ee7 00000099`d045fdb0 00007ff6`f6da2bc2 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : r5apex!LauncherMain+0xf735 00000099`d045fea0 00007ff9`a5407bd4 : 00000000`00000000 00000000`00000000 00000000`00000000 00007ff6`f6da2b40 : r5apex!LauncherMain+0x11362 00000099`d045fee0 00007ff9`a630ce51 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14 00000099`d045ff10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21 SYMBOL_NAME: r5apex+236367 MODULE_NAME: r5apex IMAGE_NAME: r5apex.exe STACK_COMMAND: ~15s ; .ecxr ; kb FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_c0000005_r5apex.exe!Unknown OS_VERSION: 10.0.18362.1 BUILDLAB_STR: 19h1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {97ecc5bf-25a5-a91f-408d-00e3953f49af}
My CPU is Intel i7-9700KF with turbo enabled (up to 5.2GHz) but it never goes above 75°C, yes I did made sure to have proper cooling in place for this when assembling it. None of my PC components is overheating but also no other game is crashing like Apex so maybe game code seriously needs some quality review.
Please check the code for some sort of "CPU Parity error" corruption, if that is possible.
I do know that one reason for these crashes, which I have managed to log myself, is a "correctable" (meaning: not blue screen) WHEA error, called "CPU Internal Parity Error". This seems to happen randomly and happens usually on overclocked systems but if it is happening at STOCK (that same R5Apex: 00000000002F2DCA) error, then it means there is something seriously wrong. Intel designs their CPU's to run at stock up to 100C (at the highest official turbo frequency). This is absolutely *NOT* an overheating bug at all. These errors can happen even as low as 45-50C. In most people's cases, reverting to pure stock settings will prevent this.
I do know that this "Parity error" was first reported after some old microcode updates (originally for Haswell processors) for Spectre/Meltdown mitigation, although the OS had to be aware for these protections to actually work. What I believe is that these crashes are caused purely by AVX code doing some..."strange" things that I've never seen before.
In my case, I know that programs that use AVX and hit the L2 cache heavily, like Realbench 2.56 and Cinebench R20 (new version) start going pear-shaped in an overclocked system at about 94 degrees celsius. However the errors generated here are (CPU Cache L0 errors) (correctable WHEA Errors), and if it is not correctable, a System service exception, Kmode exception not handled, or IRQL Not Less or Equal BSOD will be generated. (funny enough it's never Clock Watchdog Timeout (stop 0x101--frozen cores) or WHEA uncorrectable error (stop 0x124--usually a cache error). A CPU Cache L0 error isn't even a cache error relating to normal CPU caches--it's some sort of instruction register (CPU's don't have a L0 cache). There have been some comments that this is an "Operand Cache" or Register file, or access to the stack.
These L0 errors are the "overheating" errors you are referring to. You only get these errors when you are overclocked and your CPU exceeds a certain temperature in a stress test or full usage application.
Apex isn't generating these errors. It's generating "Internal Parity Errors". These are most likely causing the game to crash. But these errors are happening at VERY Low temps.
This could also be some sort of Intel Microcode bug as well. But I have no way at all to check on such a thing. That being said, the newest 9900K microcode you can download and patch (in windows, without bios flashing) yourself is ucode AE, which doesn't do anything helpful for this.
Please check on this however. This "CPU Internal Parity Error".
But for those who are getting these crashes at *STOCK* speeds, this is not an overheating issue and should not be happening. There may be a bug with the AVX code or something Apex legends is doing.
I am also seeing this crash at both stock and overclocked settings.: R5Apex: 00000000002F2E2A
I have been a PC building hobbyist for the last 20 years and I also work as a software engineer. I have also been overclocking pcs for the last ~15 years. I've run extensive tests under both stock and overclocked settings to determine component stability. HWINFO, Event Viewer, and all benching software /stability software are showing no errors, crashes or any indication of hardware failure.
I am 100% confident temperatures are not an issue under either clock speed as the cpu and gpu are both being cooled under water (I have HWINFO logs to show temps are fine even for extended heavy stress testing (24 hr stress tests)). Additionally, I have a wireless probe within the case to provide temperature readings.
I am currently allowing GSync to cap my frames with VSync disabled both in game and via nvidia control panel. I could switch over to using command line args if that helps you rule out some interaction with GSync.
I have recently wiped my computer, updated bios, upgraded firmware on everything that was out of date, and installed up to date drivers.
I honestly think you have something wrong in your stack, compiler, or some interaction with the micro processor code. If you want me to provide any further information let me know, happy to help.
Here are some more crash logs:
Brand new PC. I have never had issues in any other games and even this game rarely crashed until the most recent update. Today alone it crashed 5 times in an hour and a half. I am also seeing a crash were the game freezes completely no sound and crashes to desktop without a crash log that is new.
Here is one more crash log:
ctd randomly in games.
crash:
{
R5Apex: 00000000002F2DCA
EXCEPTION_ACCESS_VIOLATION(write): 0000000000000001
}
cpu: "Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz"
ram: 8 // 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: 0000000000017974
ntdll: 000000000006A271
}
registers:
{
rax = 1
rbx = 0x0000005942B56FA0
rcx = 0
rdx = 1
rsp = 0x000000594C76F780
rbp = 1530 // 0x000005FA
rsi = 0x000001779731A040
rdi = 1278 // 0x000004FE
r8 = 0
r9 = 27905 // 0x00006D01
r10 = 447828 // 0x0006D554
r11 = 447828 // 0x0006D554
r12 = 448215 // 0x0006D6D7
r13 = 448215 // 0x0006D6D7
r14 = 1
r15 = 0x0000017552F5ABF0
rip = 0x00007FF61F542DCA
xmm0 = [ [33068080, 0, 0, 0], [0x4BFC4A18, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [1.5746706e+08, 0, 0, 0], [0x4D162C1B, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [5.3491611, 0, 0, 0], [0x40AB2C54, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [1.768865e+08, 0, 0, 0], [0x4D28B12E, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [13648643, 0, 0, 0], [0x4B504303, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [0, 0, 11882.521, 26989.451], [0x00000000, 0x00000000, 0x4639AA15, 0x46D2DAE7] ]
xmm6 = [ [13648643, 0, 0, 0], [0x4B504303, 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 = [ [1, 0, 0, 0], [0x3F800000, 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
Another one
crash:
{
R5Apex: 00000000002F2DCA
EXCEPTION_BREAKPOINT: 80000003
}
cpu: "Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz"
ram: 8 // 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: 0000000000017974
ntdll: 000000000006A271
}
registers:
{
rax = 1
rbx = 0x0000006DD45BBB80
rcx = 0
rdx = 32
rsp = 0x0000006DD516F890
rbp = 298 // 0x0000012A
rsi = 0x000001DDD88336C0
rdi = 1914 // 0x0000077A
r8 = 0
r9 = 22965 // 0x000059B5
r10 = 447828 // 0x0006D554
r11 = 447828 // 0x0006D554
r12 = 448215 // 0x0006D6D7
r13 = 448215 // 0x0006D6D7
r14 = 1
r15 = 0x000001DB57632410
rip = 0x00007FF61F542DCA
xmm0 = [ [4.0952231e+14, 0, 0, 0], [0x57BA3AAC, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [1.9501056e+15, 0, 0, 0], [0x58DDB38B, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [5.7619019, 0, 0, 0], [0x40B86180, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [2.3596274e+15, 0, 0, 0], [0x59062119, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [4.2811824e+08, 0, 0, 0], [0x4DCC2487, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [4.2811824e+08, 0, 0, 0], [0x4DCC2487, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [4284900, 11902500, 23328900, 57608100], [0x4A82C3C8, 0x4B359E24, 0x4BB1FC42, 0x4C5BC1E9] ]
xmm9 = [ [4.2848998e+08, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x4DCC51E8, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm12 = [ [1, 0, 0, 0], [0x3F800000, 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
Here is one more crash report...
I know you're a busy guy, any help on the cause or source of this crash would be extremely helpful
Thank,
Vantyrr
crash:
{
module@00007FFCEB370000: 0000000000628608
EXCEPTION_ACCESS_VIOLATION(read): 0000000000000808
}
cpu: "AMD Ryzen 5 2600X Six-Core Processor "
ram: 16 // GB
callstack:
{
KERNELBASE: 000000000008669C
ntdll: 00000000000A80CB
ntdll: 000000000008FD36
ntdll: 00000000000A468F
ntdll: 0000000000004BEF
ntdll: 00000000000A33FE
module@00007FFCEB370000: 0000000000628608
module@00007FFCEB370000: 000000000063B8C1
module@00007FFCEB370000: 0000000000636E4E
module@00007FFCEB370000: 0000000000637237
module@00007FFCEB370000: 000000000053A553
module@00007FFCEB370000: 000000000053A5DF
module@00007FFCEB370000: 000000000046F9F1
module@00007FFCEB370000: 00000000003BFCCA
module@00007FFCEB370000: 00000000001C2F3A
module@00007FFCEB370000: 0000000000E2A4B2
module@00007FFCEB370000: 0000000000DA705B
module@00007FFCEB370000: 000000000037A529
module@00007FFCEB370000: 000000000019A8F6
module@00007FFCEB370000: 0000000000451D25
module@00007FFCEB370000: 00000000004EE5B7
module@00007FFCEB370000: 00000000012A066C
KERNEL32: 00000000000181F4
ntdll: 000000000006A251
}
registers:
{
rax = 4
rbx = 2048 // 0x00000800
rcx = 2382 // 0x0000094E
rdx = 14
rsp = 0x00000056F4BED300
rbp = 0x00000056F4BED400
rsi = 0
rdi = 81
r8 = 77
r9 = 0xFFFFFFFF
r10 = 1
r11 = 0x000001FFB1638AB0
r12 = 0x000001FFB1555078
r13 = 81
r14 = 0
r15 = 0x000001FFB1639448
rip = 0x00007FFCEB998608
xmm0 = [ [17.25, 0, 0, 0], [0x418A0000, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [57.142857, 0, 0, 0], [0x42649249, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [57.142857, 0, 0, 0], [0x42649249, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [57.142857, 0, 0, 0], [0x42649249, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [0.5, 0, 0, 0], [0x3F000000, 0x00000000, 0x00000000, 0x00000000] ]
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
Hi there, my rig is Ryzen 5 2600x, 16gb Gskill 3000Mhz ram and an RTX 2060. I haven't overclocked any of the components it runs on the base clock speeds and i still get this error message when opening the game. tried capping the fps, disabling in-game origin and every possible way there is on the internet.
EA Staff (Retired)@iceplague007, it looks like our call to D3DReflect failed. This is a Direct3D call to get information about a shader.
We've never seen this fail in any of our dev builds, where we detect this and report an error. Our shipping builds assume this will work if it always worked in dev, so it doesn't do any error checking. Instead, it crashes the first time it tries to use the results of the D3DReflect call.
The most likely reason for this function to fail is corrupt data. Did you try repairing or reinstalling Apex? I'm not sure what options Origin gives you here.
@OrioStorm, yes I've tried repairing the game through origin and the easy anti-cheat service but it doesn't work. Reinstalled it quite a few times but that doesn't work either.
Once i'm in game, i can't last more than 30 second and it crashed.
crash:
{
d3d11: 000000000008AD10
EXCEPTION_ACCESS_VIOLATION(read): FFFFFFFFFFFFFFFF
}
cpu: "Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz"
ram: 24 // GB
callstack:
{
KERNELBASE: 0000000000086B2C
ntdll: 00000000000A81CB
ntdll: 000000000008FD56
ntdll: 00000000000A477F
ntdll: 0000000000004BEF
ntdll: 00000000000A34EE
d3d11: 000000000008AD10
d3d11: 0000000000051C0D
R5Apex: 00000000003EB11B
R5Apex: 00000000004016CB
R5Apex: 0000000000452F4A
R5Apex: 0000000000453113
R5Apex: 00000000001E416A
R5Apex: 00000000001E7803
R5Apex: 00000000001E5E76
R5Apex: 00000000001E47DD
R5Apex: 000000000043A163
R5Apex: 000000000043A43F
R5Apex: 0000000000456C7D
R5Apex: 0000000000456666
R5Apex: 0000000000456A57
R5Apex: 00000000004552E7
R5Apex: 0000000000457012
KERNEL32: 0000000000017974
ntdll: 000000000006A271
}
registers:
{
rax = 0xCD8B48D78BC38B44
rbx = 0x00000284EA8FFAF0
rcx = 0x00000284EA8FFB18
rdx = 0
rsp = 0x000000EB1F85F4B8
rbp = 0x0000028463E288A0
rsi = 0
rdi = 128
r8 = 1
r9 = 0xFFFFFFFF00000000
r10 = 0x00007FF6A3E17C60
r11 = 0x000002846409A180
r12 = 2
r13 = 0x0000028463C50F30
r14 = 0
r15 = 80
rip = 0x00007FFC1EA6AD10
xmm0 = [ [1.6784498e-31, 9.0383751e-43, 0, 0], [0x0C59E010, 0x00000285, 0x00000000, 0x00000000] ]
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: 1562876448
@OrioStorm Hey i've been having a similar problem im not sure if this is one of the codes thats been reported i was just sending in just in case but i havent been able to start apex and when i do it says
---------------------------
Apex Crash Message
---------------------------
Apex crashed in ntdll.
More technical information should be available in "apex_crash.txt" in your Documents folder.
Ctrl+C in this window will copy this message so you can paste it as text.
---------------------------
OK
---------------------------
in a little pop up message and when i go to my documents folder this is what it says crash:
{
ntdll: 000000000003AA0F
EXCEPTION_ACCESS_VIOLATION(read): FFFFFFFFFFFFFFFF
}
cpu: "Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz"
ram: 16 // GB
callstack:
{
KERNELBASE: 00000000000FF67A
ntdll: 00000000000A4AF2
ntdll: 000000000008C6E6
ntdll: 00000000000A120F
ntdll: 000000000006A299
ntdll: 000000000009FE7E
ntdll: 000000000003AA0F
AUDIOSES: 00000000000500BF
AUDIOSES: 000000000002E297
wdmaud: 0000000000017246
wdmaud: 0000000000006B26
wdmaud: 00000000000058B0
wdmaud: 00000000000055E4
KERNEL32: 0000000000017BD4
ntdll: 000000000006CEE1
}
registers:
{
rax = 1
rbx = 0x000002A2767FC620
rcx = 0x07D0000000000000
rdx = 0x00007FFB2AF0A658
rsp = 0x000000BD3AFEF250
rbp = 0x000000BD3AFEF3D0
rsi = 0x000002A2396F8A80
rdi = 0
r8 = 0x000002A2767FC698
r9 = 0x000002A2390F0070
r10 = 0x00007FFB2AF0A658
r11 = 0x000002A239554960
r12 = 0x00007FFB19FE1E80
r13 = 0
r14 = 0x000002A2398AA6F0
r15 = 0
rip = 0x00007FFB37C3AA0F
xmm0 = [ [9.1836897e-41, 3.0898631e-41, 6.1797262e-41, 1.4693707e-39], [0x00010001, 0x00005622, 0x0000AC44, 0x00100002] ]
xmm1 = [ [4.4530225e+13, -2.7853275e-12, 1.8367099e-40, 2.2420775e-44], [0x56220001, 0xAC440000, 0x00020000, 0x00000010] ]
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: 1569284646 im hoping you can help me out with this problem i really want to play apex with my friend
Community Manager
