Re: Crashing with new gpu

by EA_Darko
Reply

Original Post

Accepted Solution

Crashing with new gpu

★★★ Novice

SO I was having issues where after I did a GPU upgrade specifically a  RX 580 to a GTX 1070 I the game would freeze and I would have to force close it via task manager. So I decided to update the drivers. After I did it still crashed but with a error message this time. (Previously I would get not error message. The only error I would get was in event viewer.) Here is the text document I got. The file itself is here too if needed.

 

crash:
{
!!!unknown-module!!!: 00007FFE468C72A0
EXCEPTION_ACCESS_VIOLATION(execute): 00007FFE468C72A0
}
cpu: "AMD Ryzen 5 1600 Six-Core Processor "
ram: 32 // GB
callstack:
{
KERNELBASE: 0000000000086B2C
ntdll: 00000000000A81CB
ntdll: 000000000008FD56
ntdll: 00000000000A477F
ntdll: 0000000000004BEF
ntdll: 00000000000A34EE
!!!unknown-module!!!: 00007FFE468C72A0
}
registers:
{
rax = 0
rbx = 0x00007FF60B729B10
rcx = 0x000000C4126EFB80
rdx = 0
rsp = 0x000000C4126EFB18
rbp = 0x000000C4126EFD39
rsi = 2
rdi = 0x00007FF632655440
r8 = 0x000000C4126EFA38
r9 = 1
r10 = 0x00007FFE406B10C4
r11 = 582 // 0x00000246
r12 = 1
r13 = 0x00007FF60B70E4D0
r14 = 0
r15 = 0
rip = 0x00007FFE468C72A0
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: 1561694190
modules:
{
R5Apex: [00007FF60B350000, 00007FF634AE2000]
ntdll: [00007FFE44590000, 00007FFE4477D000]
KERNEL32: [00007FFE42320000, 00007FFE423D3000]
KERNELBASE: [00007FFE41420000, 00007FFE416B3000]
Activation64: [00007FFDF6D50000, 00007FFDF7051000]
GDI32: [00007FFE41F60000, 00007FFE41F89000]
gdi32full: [00007FFE406D0000, 00007FFE40869000]
msvcp_win: [00007FFE410C0000, 00007FFE41160000]
ucrtbase: [00007FFE40FC0000, 00007FFE410BA000]
USER32: [00007FFE41D60000, 00007FFE41EF7000]
win32u: [00007FFE406B0000, 00007FFE406D0000]
CRYPT32: [00007FFE41160000, 00007FFE4133B000]
MSASN1: [00007FFE405E0000, 00007FFE405F2000]
SHLWAPI: [00007FFE42240000, 00007FFE42292000]
msvcrt: [00007FFE41CC0000, 00007FFE41D5E000]
combase: [00007FFE44080000, 00007FFE443AC000]
RPCRT4: [00007FFE43D50000, 00007FFE43E72000]
bcryptPrimitives: [00007FFE416E0000, 00007FFE4175E000]
WINTRUST: [00007FFE41760000, 00007FFE417B9000]
MSVCP140: [00007FFE15090000, 00007FFE15136000]
gdiplus: [00007FFE33D70000, 00007FFE33F15000]
ole32: [00007FFE418E0000, 00007FFE41A35000]
VCRUNTIME140: [00007FFE3CE60000, 00007FFE3CE76000]
advapi32: [00007FFE41F90000, 00007FFE42033000]
sechost: [00007FFE41820000, 00007FFE418BE000]
OLEAUT32: [00007FFE42040000, 00007FFE42104000]
SHELL32: [00007FFE423E0000, 00007FFE438D0000]
cfgmgr32: [00007FFE40660000, 00007FFE406AA000]
shcore: [00007FFE43FB0000, 00007FFE44058000]
windows.storage: [00007FFE40870000, 00007FFE40FBA000]
profapi: [00007FFE405B0000, 00007FFE405D4000]
powrprof: [00007FFE40600000, 00007FFE4065D000]
kernel.appcore: [00007FFE40590000, 00007FFE405A1000]
cryptsp: [00007FFE416C0000, 00007FFE416D7000]
WINHTTP: [00007FFE3B590000, 00007FFE3B682000]
IMM32: [00007FFE43F80000, 00007FFE43FAE000]
ntmarta: [00007FFE3F640000, 00007FFE3F671000]
uxtheme: [00007FFE3EBC0000, 00007FFE3EC5C000]
SS3DevProps: [00007FFE11AA0000, 00007FFE11B1F000]
WS2_32: [00007FFE43E80000, 00007FFE43EED000]
clbcatq: [00007FFE41A40000, 00007FFE41AE2000]
bcrypt: [00000263858C0000, 00000263858E6000]
webio: [00007FFE345A0000, 00007FFE34637000]
mswsock: [00007FFE3FDA0000, 00007FFE3FE07000]
IPHLPAPI: [00007FFE3FB00000, 00007FFE3FB3D000]
WINNSI: [00007FFE3BAA0000, 00007FFE3BAAB000]
NSI: [00007FFE418D0000, 00007FFE418D8000]
SspiCli: [00007FFE40490000, 00007FFE404BF000]
DNSAPI: [00007FFE3FB40000, 00007FFE3FC06000]
rasadhlp: [00007FFE392C0000, 00007FFE392CA000]
fwpuclnt: [00007FFE39920000, 00007FFE39999000]
schannel: [00007FFE3F890000, 00007FFE3F915000]
mskeyprotect: [00007FFE31160000, 00007FFE31175000]
ncrypt: [00007FFE40070000, 00007FFE40096000]
NTASN1: [00007FFE40030000, 00007FFE4006C000]
ncryptsslp: [00007FFE31690000, 00007FFE316B4000]
DPAPI: [00007FFE3F9A0000, 00007FFE3F9AA000]
rsaenh: [00007FFE3F960000, 00007FFE3F993000]
CRYPTBASE: [00007FFE3FF70000, 00007FFE3FF7C000]
imagehlp: [00007FFE44060000, 00007FFE4407D000]
gpapi: [00007FFE3F280000, 00007FFE3F2A2000]
cryptnet: [00007FFE39F60000, 00007FFE39F8F000]
AVIFIL32: [00007FFE39EC0000, 00007FFE39EE0000]
MSACM32: [00007FFE28180000, 00007FFE2819C000]
MSVFW32: [00007FFE39CB0000, 00007FFE39CD9000]
WINMM: [00007FFE3E680000, 00007FFE3E6A4000]
winmmbase: [00007FFE3E1F0000, 00007FFE3E21D000]
COMCTL32: [00007FFE33CC0000, 00007FFE33D69000]
d3d11: [00007FFE3D7E0000, 00007FFE3DA5E000]
dxgi: [00007FFE3F300000, 00007FFE3F3C2000]
D3DCOMPILER_43: [00007FFDF6AE0000, 00007FFDF6D4F000]
mileswin64: [00007FFE13C40000, 00007FFE13CED000]
AVRT: [00007FFE3CB90000, 00007FFE3CB9A000]
binkawin64: [00007FFE39C70000, 00007FFE39CA6000]
WLDAP32: [00007FFE417C0000, 00007FFE41820000]
Normaliz: [00007FFE418C0000, 00007FFE418C8000]
bink2w64: [00007FFE14EF0000, 00007FFE14F62000]
SETUPAPI: [00007FFE438D0000, 00007FFE43D46000]
HID: [00007FFE3F270000, 00007FFE3F27E000]
MMDevApi: [00007FFE39890000, 00007FFE39900000]
DEVOBJ: [00007FFE40340000, 00007FFE40369000]
PROPSYS: [00007FFE3CFC0000, 00007FFE3D168000]
AUDIOSES: [00007FFE359A0000, 00007FFE35AE8000]
wintypes: [00007FFE3BFB0000, 00007FFE3C103000]
IGO64: [00007FFDF6870000, 00007FFDF6ADE000]
nvldumdx: [00007FFE39070000, 00007FFE3915E000]
VERSION: [00007FFE3BA30000, 00007FFE3BA3A000]
nvwgf2umx: [00007FFDF92D0000, 00007FFDFB883000]
XInput1_3: [0000000000400000, 000000000041E000]
EasyAntiCheat_x64: [00000263CD100000, 00000263CD1C9000]
MSCTF: [00000263CD1E0000, 00000263CD34B000]
dwmapi: [00007FFE3EFD0000, 00007FFE3EFFE000]
TextInputFramework: [00007FFE34B00000, 00007FFE34B95000]
CoreUIComponents: [00007FFE3C510000, 00007FFE3C832000]
CoreMessaging: [00000263CD450000, 00000263CD532000]
dcomp: [00000263CFE40000, 00000263D0003000]
dsound: [00007FFE0DA10000, 00007FFE0DAA6000]
wdmaud: [00007FFDFFF30000, 00007FFDFFF74000]
ksuser: [00007FFE0DAB0000, 00007FFE0DAB9000]
msacm32: [00007FFE32FC0000, 00007FFE32FCD000]
midimap: [00000263BBB60000, 00000263BBB6A000]
Windows.UI: [00007FFE33280000, 00007FFE333BA000]
InputHost: [00007FFE34720000, 00007FFE347EC000]
twinapi.appcore: [00007FFE3EC90000, 00007FFE3EE9D000]
d2d1: [00007FFE3DA60000, 00007FFE3E01E000]
RMCLIENT: [00000263EA140000, 00000263EA168000]
XAudio2_6: [00000000703C0000, 000000007044D000]
uiComputer: [00007FFDF64C0000, 00007FFDF66B9000]
napinsp: [00000263EABC0000, 00000263EABD6000]
pnrpnsp: [00007FFE391B0000, 00007FFE391CA000]
winrnr: [00007FFE3CE40000, 00007FFE3CE4E000]
NLAapi: [00000263EABF0000, 00000263EAC0B000]
wshbth: [00007FFE2EA90000, 00007FFE2EAA5000]
dhcpcsvc: [00007FFE3B2A0000, 00007FFE3B2BC000]
resourcepolicyclient: [00007FFE3EED0000, 00007FFE3EEE4000]
secur32: [00007FFE25100000, 00007FFE2510C000]
}

Message 1 of 13 (1,004 Views)

Accepted Solution

Re: Crashing with new gpu

★★★ Novice

I have for the 1070 just yesterday. Its probably tyr 1050 ti that hasn't been updated.

View in thread

Message 5 of 13 (963 Views)

All Replies

Re: Crashing with new gpu

Community Manager

Hey @RingMaster258 can you grab us a DxDiag so that we can take a look at your system: https://help.ea.com/en-us/help/pc/how-to-gather-dxdiag-information/

 

The more info available to use the better we can help.


Darko

Darko.png
Message 2 of 13 (985 Views)

Re: Crashing with new gpu

★★★ Novice

The 1050 ti in the list is nothing more than an video encoder, so don't worry about that. The 1070 is my main card.

Message 3 of 13 (977 Views)

Re: Crashing with new gpu

Community Manager

First thing I would suggest @RingMaster258 is updating your GPU drivers. Yours are showing as being almost 2 months old and I'm pretty sure there was an update for the 1070 in recent weeks.

 

I am seeing quite a few errors in your DxDiag. I would recommend ensuring that your system is fully up to date and there's no harm running CCleaner's registry cleaner: https://www.ccleaner.com/ccleaner/registry-cleaner

 

Just so you are aware CCleaner is a third party tool.


Darko

Darko.png
Message 4 of 13 (969 Views)

Re: Crashing with new gpu

★★★ Novice

I have for the 1070 just yesterday. Its probably tyr 1050 ti that hasn't been updated.

Message 5 of 13 (964 Views)
Highlighted

Re: Crashing with new gpu

Community Manager

Hey @RingMaster258 your 1070 drivers are showing as being from the 21/5/19. Can you download and install the latest GPU driver from here: https://www.geforce.com/drivers

 

Darko

Darko.png
Message 6 of 13 (957 Views)

Re: Crashing with new gpu

★★★ Novice

Again I did just yesterday. The 1050 ti s probably the one with the outdated drivers. And again the 1050 to is just a video encoder.

Message 7 of 13 (945 Views)

Re: Crashing with new gpu

★★★ Novice

I saw where it said 5/21/2019 but I literally just yesterday downloaded the latest drivers, and they till are.

Message 8 of 13 (926 Views)

Re: Crashing with new gpu

Community Manager

You may have downloaded the most recent drivers for the 1070 but that is not reflected in your DxDiag @RingMaster258.


You 1070 date is showing in the line: Driver Date/Size: 5/21/2019 8:00:00 PM, 958312 bytes

 

Did you check the registry for issues as I suggested above?

Darko

Darko.png
Message 9 of 13 (904 Views)

Re: Crashing with new gpu

★★★ Novice

I did  check the registry and some of them are Missing shared DLL, unused file extension, active X, invalid or empty file class, and open with application issue. I think the Apex issue has to deal with DDL? I did fix selected issues and ran it again but the issue still showed up in CC cleaer as an issue 

Message 10 of 13 (893 Views)