Crash to desktop not fixed

General Discussion
1

Hello people, despite a lot of players having this issue(crash to desktop) while looking for matches i cant find a single answer or comment from devs.
At this point is getting so annoying the ctd every 3 or 4 fights.
My system spec:
Win 10 last built 64 bits pro
I7 4.1 ghz
Gtx 980ti
12gb ddr3 ram
Game installed on ssd
I just reinstalled windows, put everything up to date and just installed killer instinct. And it keep crashing on the fresh and up to date win install.
ANY HELP ON THIS? PLEASE
EDIT: I also remove all oc from my rig. Everything running on stock frequency. Still crashing
Also installed the game on a different ssd. Still crashing.
Im running out of ideas at this point.

Also noticed after crashing, checking msi afterburner log, the previous 30 or 50 seg before the crash my gpu utilization is all over the place. Every sec is changing like 3% and the next 70% and the next sec 8% and the next 55%. Something like that.

EDIT 2
i found some error relate to KI on my event logs viewer on windows 10. this is what a found so far
ON GENERAL TAB
Nombre de la aplicación con errores: KillerInstinct_UWPx64_r.exe, versión: 0.0.0.0, marca de tiempo: 0x56ff10e6
Nombre del módulo con errores: KERNELBASE.dll, versión: 10.0.10586.162, marca de tiempo: 0x56cd45b4
Código de excepción: 0xe06d7363
Desplazamiento de errores: 0x0000000000071f28
Identificador del proceso con errores: 0x1b34
Hora de inicio de la aplicación con errores: 0x01d19ec2ec6e67e2
Ruta de acceso de la aplicación con errores: C:\Program Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\KillerInstinct_UWPx64_r.exe
Ruta de acceso del módulo con errores: C:\Windows\system32\KERNELBASE.dll
Identificador del informe: 113a6afe-71bb-4bb6-99a4-518705780794
Nombre completo del paquete con errores: Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe
Identificador de aplicación relativa del paquete con errores: KillerInstinct.App

ON DETAILS TAB
EVENT DATA

KillerInstinct_UWPx64_r.exe
0.0.0.0
56ff10e6
KERNELBASE.dll
10.0.10586.162
56cd45b4
e06d7363
0000000000071f28
1b34
01d19ec2ec6e67e2
C:\Program
Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\KillerInstinct_UWPx64_r.exe
C:\Windows\system32\KERNELBASE.dll
113a6afe-71bb-4bb6-99a4-518705780794
Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe
KillerInstinct.App

i have a couple of this errors, here is another one. its all cash related

Depósito con errores 133316753518, tipo 5
Nombre de evento: MoAppCrash
Respuesta: No disponible
Identificador de archivo CAB: 0

Firma del problema:
P1: Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe
P2: praid:KillerInstinct.App
P3: 0.0.0.0
P4: 56ff10e6
P5: KERNELBASE.dll
P6: 10.0.10586.162
P7: 56cd45b4
P8: e06d7363
P9: 0000000000071f28
P10:

Archivos adjuntos:
C:\Users\Endle\AppData\Local\Temp\WERAC31.tmp.WERInternalMetadata.xml

Es posible que estos archivos estén disponibles aquí:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Killer_323c39a59b42a91e12bcdb1cda28ce5d0d2b379_a7093ede_1b70b307

Símbolo de análisis:
Nueva búsqueda de una solución: 0
Identificador de informe: 113a6afe-71bb-4bb6-99a4-518705780794
Estado del informe: 0

ON DETAILS TAB (XML VIEW)

  • 1001

    4
    0
    0x80000000000000

    1621

    Application

    SKYNET

  • 133316753518

    5

    MoAppCrash

    No disponible

    0

    Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe

    praid:KillerInstinct.App

    0.0.0.0

    56ff10e6

    KERNELBASE.dll

    10.0.10586.162

    56cd45b4

    e06d7363

    0000000000071f28

    C:\Users\Endle\AppData\Local\Temp\WERAC31.tmp.WERInternalMetadata.xml

    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Killer_323c39a59b42a91e12bcdb1cda28ce5d0d2b379_a7093ede_1b70b307

    0

    113a6afe-71bb-4bb6-99a4-518705780794

    0

    af2e3eda8955ae710a922cdeac19b8bf

EDIT 3
I found the full crash report named report.wer on my pc. gonna copy paste.
i think its the full log, from the game boot till the crash
i would love some devs words on this

Version=1
EventType=MoAppCrash
EventTime=131060430382336126
ReportType=2
Consent=1
UploadTime=131060430382521148
ReportIdentifier=9aae60d6-0ab7-11e6-8467-04300ae80082
IntegratorReportIdentifier=113a6afe-71bb-4bb6-99a4-518705780794
NsAppName=praid:KillerInstinct.App
Response.BucketId=af2e3eda8955ae710a922cdeac19b8bf
Response.BucketTable=5
Response.LegacyBucketId=133316753518
Response.type=4
Sig[0].Name=Nombre completo del paquete
Sig[0].Value=Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe
Sig[1].Name=Nombre de la aplicación
Sig[1].Value=praid:KillerInstinct.App
Sig[2].Name=Versión de la aplicación
Sig[2].Value=0.0.0.0
Sig[3].Name=Marca de tiempo de la aplicación
Sig[3].Value=56ff10e6
Sig[4].Name=Nombre del módulo con errores
Sig[4].Value=KERNELBASE.dll
Sig[5].Name=Versión del módulo con errores
Sig[5].Value=10.0.10586.162
Sig[6].Name=Marca de tiempo del módulo con errores
Sig[6].Value=56cd45b4
Sig[7].Name=Código de excepción
Sig[7].Value=e06d7363
Sig[8].Name=Desplazamiento de excepción
Sig[8].Value=0000000000071f28
DynamicSig[1].Name=Versión del sistema operativo
DynamicSig[1].Value=10.0.10586.2.0.0.256.48
DynamicSig[2].Name=Id. de configuración regional
DynamicSig[2].Value=11274
DynamicSig[22].Name=Información adicional 1
DynamicSig[22].Value=a822
DynamicSig[23].Name=Información adicional 2
DynamicSig[23].Value=a822497e2c0b06ab53d5b00bdd7c527d
DynamicSig[24].Name=Información adicional 3
DynamicSig[24].Value=b26b
DynamicSig[25].Name=Información adicional 4
DynamicSig[25].Value=b26b9744f48c50c013b00e8bce7a1aaf
UI[2]=C:\Program Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\KillerInstinct_UWPx64_r.exe
LoadedModule[0]=C:\Program Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\KillerInstinct_UWPx64_r.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\combase.dll
LoadedModule[5]=C:\Windows\system32\msvcrt.dll
LoadedModule[6]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe\vccorlib140_app.DLL
LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
LoadedModule[8]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe\MSVCP140_APP.dll
LoadedModule[9]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe\VCRUNTIME140_APP.dll
LoadedModule[10]=C:\Windows\system32\bcryptPrimitives.dll
LoadedModule[11]=C:\Windows\system32\WS2_32.dll
LoadedModule[12]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[13]=C:\Windows\system32\sechost.dll
LoadedModule[14]=C:\Windows\SYSTEM32\ucrtbase.dll
LoadedModule[15]=C:\Program Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\XINPUT1_4.dll
LoadedModule[16]=C:\Windows\SYSTEM32\d3d11.dll
LoadedModule[17]=C:\Windows\SYSTEM32\dxgi.dll
LoadedModule[18]=C:\Windows\SYSTEM32\D3DCOMPILER_47.dll
LoadedModule[19]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[20]=C:\Windows\system32\gdi32.dll
LoadedModule[21]=C:\Windows\system32\USER32.dll
LoadedModule[22]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[23]=C:\Program Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\MeldRelease_UWP.dll
LoadedModule[24]=C:\Program Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\bink2winrt_x64.uni10.dll
LoadedModule[25]=C:\Windows\SYSTEM32\XAudio2_9.dll
LoadedModule[26]=C:\Windows\SYSTEM32\DEVOBJ.dll
LoadedModule[27]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[28]=C:\Program Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\D3D11LibRelease_UWP.dll
LoadedModule[29]=C:\Program Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\WPFLibRelease_UWP.dll
LoadedModule[30]=C:\Windows\SYSTEM32\MMDevAPI.DLL
LoadedModule[31]=C:\Windows\SYSTEM32\AVRT.dll
LoadedModule[32]=C:\Windows\SYSTEM32\MFPlat.DLL
LoadedModule[33]=C:\Windows\SYSTEM32\MFReadWrite.dll
LoadedModule[34]=C:\Windows\system32\advapi32.dll
LoadedModule[35]=C:\Windows\SYSTEM32\PROPSYS.dll
LoadedModule[36]=C:\Windows\system32\IMM32.DLL
LoadedModule[37]=C:\Windows\system32\kernel.appcore.dll
LoadedModule[38]=C:\Windows\SYSTEM32\RTWorkQ.DLL
LoadedModule[39]=C:\Windows\System32\twinapi.appcore.dll
LoadedModule[40]=C:\Windows\System32\WinTypes.dll
LoadedModule[41]=C:\Windows\system32\shcore.dll
LoadedModule[42]=C:\Windows\System32\ActXPrxy.dll
LoadedModule[43]=C:\Windows\System32\execmodelclient.dll
LoadedModule[44]=C:\Windows\SYSTEM32\CoreMessaging.dll
LoadedModule[45]=C:\Windows\system32\CoreUIComponents.dll
LoadedModule[46]=C:\Windows\system32\execmodelproxy.dll
LoadedModule[47]=C:\Windows\SYSTEM32\mrmcorer.dll
LoadedModule[48]=C:\Windows\SYSTEM32\windows.ui.dll
LoadedModule[49]=C:\Windows\system32\uxtheme.dll
LoadedModule[50]=C:\Windows\system32\MSCTF.dll
LoadedModule[51]=C:\Windows\SYSTEM32\dwmapi.dll
LoadedModule[52]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[53]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[54]=C:\Windows\system32\Shell32.dll
LoadedModule[55]=C:\Windows\system32\windows.storage.dll
LoadedModule[56]=C:\Windows\system32\shlwapi.dll
LoadedModule[57]=C:\Windows\system32\powrprof.dll
LoadedModule[58]=C:\Windows\system32\profapi.dll
LoadedModule[59]=C:\Windows\system32\nvspcap64.dll
LoadedModule[60]=C:\Windows\system32\ole32.dll
LoadedModule[61]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[62]=C:\Windows\system32\PSAPI.DLL
LoadedModule[63]=C:\Windows\SYSTEM32\WINHTTP.dll
LoadedModule[64]=C:\Windows\system32\nvapi64.dll
LoadedModule[65]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[66]=C:\Windows\System32\Windows.ApplicationModel.dll
LoadedModule[67]=C:\Windows\System32\threadpoolwinrt.dll
LoadedModule[68]=C:\Windows\SYSTEM32\AUDIOSES.DLL
LoadedModule[69]=C:\Windows\System32\Windows.Devices.Enumeration.dll
LoadedModule[70]=C:\Windows\SYSTEM32\BiWinrt.dll
LoadedModule[71]=C:\Windows\SYSTEM32\deviceassociation.dll
LoadedModule[72]=C:\Windows\System32\DevDispItemProvider.dll
LoadedModule[73]=C:\Windows\system32\napinsp.dll
LoadedModule[74]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[75]=C:\Windows\system32\NLAapi.dll
LoadedModule[76]=C:\Windows\System32\mswsock.dll
LoadedModule[77]=C:\Windows\SYSTEM32\DNSAPI.dll
LoadedModule[78]=C:\Windows\system32\NSI.dll
LoadedModule[79]=C:\Windows\System32\winrnr.dll
LoadedModule[80]=C:\Windows\System32\wshbth.dll
LoadedModule[81]=C:\Windows\System32\Windows.Networking.Connectivity.dll
LoadedModule[82]=C:\Program Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\Microsoft.Xbox.Services.dll
LoadedModule[83]=C:\Program Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\cpprest140_uwp_2_6.dll
LoadedModule[84]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe\CONCRT140_APP.dll
LoadedModule[85]=C:\Windows\SYSTEM32\gamingtcui.dll
LoadedModule[86]=C:\Windows\System32\DDORes.dll
LoadedModule[87]=C:\Windows\System32\DefaultDeviceManager.dll
LoadedModule[88]=C:\Windows\System32\Windows.Globalization.dll
LoadedModule[89]=C:\Windows\SYSTEM32\Bcp47Langs.dll
LoadedModule[90]=C:\Windows\SYSTEM32\globinputhost.dll
LoadedModule[91]=C:\Windows\SYSTEM32\nvwgf2umx.dll
LoadedModule[92]=C:\Windows\SYSTEM32\dcomp.dll
LoadedModule[93]=C:\Windows\system32\windowscodecs.dll
LoadedModule[94]=C:\Windows\System32\Windows.Web.dll
LoadedModule[95]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[96]=C:\Windows\System32\Windows.Storage.ApplicationData.dll
LoadedModule[97]=C:\Windows\System32\deviceaccess.dll
LoadedModule[98]=C:\Windows\System32\Windows.Security.Authentication.Web.Core.dll
LoadedModule[99]=C:\Windows\system32\CRYPT32.dll
LoadedModule[100]=C:\Windows\system32\MSASN1.dll
LoadedModule[101]=C:\Windows\System32\usermgrproxy.dll
LoadedModule[102]=C:\Windows\System32\vaultcli.dll
LoadedModule[103]=C:\Windows\system32\rsaenh.dll
LoadedModule[104]=C:\Windows\System32\WinRtTracing.dll
LoadedModule[105]=C:\Windows\System32\wpnapps.dll
LoadedModule[106]=C:\Windows\SYSTEM32\RMCLIENT.dll
LoadedModule[107]=C:\Windows\System32\msxml6.dll
LoadedModule[108]=C:\Windows\SYSTEM32\DPAPI.dll
LoadedModule[109]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[110]=C:\Windows\SYSTEM32\wininet.dll
LoadedModule[111]=C:\Windows\SYSTEM32\tokenbinding.dll
LoadedModule[112]=C:\Windows\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[113]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[114]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[115]=C:\Windows\SYSTEM32\userenv.dll
LoadedModule[116]=C:\Windows\SYSTEM32\profext.dll
LoadedModule[117]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[118]=C:\Windows\System32\rasadhlp.dll
LoadedModule[119]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[120]=C:\Windows\system32\schannel.DLL
LoadedModule[121]=C:\Windows\SYSTEM32\mskeyprotect.dll
LoadedModule[122]=C:\Windows\SYSTEM32\ncrypt.dll
LoadedModule[123]=C:\Windows\SYSTEM32\NTASN1.dll
LoadedModule[124]=C:\Windows\system32\WINTRUST.dll
LoadedModule[125]=C:\Windows\System32\cryptnet.dll
LoadedModule[126]=C:\Windows\system32\ncryptsslp.dll
LoadedModule[127]=C:\Windows\System32\Windows.Gaming.XboxLive.Storage.dll
LoadedModule[128]=C:\Windows\System32\XblGameSaveProxy.dll
LoadedModule[129]=C:\Windows\System32\Windows.ApplicationModel.Store.dll
LoadedModule[130]=C:\Windows\SYSTEM32\webservices.dll
LoadedModule[131]=C:\Program Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\Microsoft.Xbox.GameChat.dll
LoadedModule[132]=C:\Program Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\microsoft.xbox.chataudio.dll
LoadedModule[133]=C:\Windows\System32\Windows.Networking.dll
LoadedModule[134]=C:\Windows\system32\FirewallAPI.dll
LoadedModule[135]=C:\Windows\SYSTEM32\Windows.Networking.HostName.dll
LoadedModule[136]=C:\Windows\SYSTEM32\fwbase.dll
LoadedModule[137]=C:\Windows\System32\Windows.Networking.XboxLive.ProxyStub.dll
LoadedModule[138]=C:\Windows\System32\Windows.Media.Devices.dll
LoadedModule[139]=C:\Windows\System32\XblAuthTokenBrokerExt.dll
LoadedModule[140]=C:\Windows\System32\XblAuthManagerProxy.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Dejó de funcionar
ConsentKey=MoAppCrash
AppName=Microsoft.KillerInstinct-Win10_8wekyb3d8bbwe!KillerInstinct.App
AppPath=C:\Program Files\WindowsApps\Microsoft.KillerInstinct-Win10_3.0.4.0_x64__8wekyb3d8bbwe\KillerInstinct_UWPx64_r.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=583DC432C7B4BF0F507828A011CF5A3A

2

happens to all , u just have to wait for the next update

3

It happens to all, yet we dont have any response on this. And believe it or not, this ctd thing is driving me crazy. This should be the 1st issue to fix.
For me its more important than the refresh rate problem, cuz this is a game breaker stuff and despite all this we still waiting for some responses.

1 Like
4

It well today is the frist time ki crahsed for me i hope they fix that and the teddeo thing so i can play online

5

Funny thing i dont read much about it on this forum.

6

I agree with you. Normally the internet explodes when there’s an issue like this. I’ve found three threads, so far. Yours, another one in this forum, and one on Reddit.

It does seem like this is effecting everyone playing on Win10. It certainly happens to me like you said–every 3-6 matches or so. I saw a post in the other thread in this forum saying IG are aware and they’re working on a fix, but I’m not sure if the poster was actually IG or if they were just trying to take a guess on behalf of IG.

Good news is that patch 3.1 (I’m assuming that’s the XOne number) comes out this week with Mira. Maybe that will fix this (fingers crossed).

7

I hope they read this topic and post something about it. For real… but (sadly) i know how bad ig is communicating with the fans.
I dont own a xbox one but i read the game is working good there.
This is something 100% on ig end.
But what really really bugs me is the lack of people demanding a fix on this. I mean… a ctd issue is top priority on any pc game. I dont know what is happening here.

8

I’m looking on the app store, and only 1.5k people have rated KI on Win10. Also, all I ever read online is opinions of people who are scared to upgrade to Win10 for some reason. Maybe the Win10 player base is much smaller than the average game with a crash to desktop issue at launch.

Or maybe the problem is limited and only a minority of us on Win10 are seeing it. However, that’s super hard for me to believe. I have the most meat-and-potatoes, dog-and-bone PC one can build. Standard hardware (no overclock, no customization, no SLI), absolutely no fancy software, stock user settings and the commercial version of Win10.

Or, and this would be interesting, most players don’t play long enough to see the crash. Most reliably, we’re seeing crashes after 6 matches. Think about Giant Bomb, Gamespot, IGN, etc. who are reviewing it. Maybe none of those guys spent long enough with the game in one sitting to see these crashes. It is weird that none of their Win10 reviews of the game mention it.

At any rate, lots of possibilities and crossed fingers :stuck_out_tongue:

9

This hasn’t happened to me a lot, it did at one point but that was when I was searching for a game before I had a chance to let the top killers load. Once I did that it stopped crashing in ranked, then it crashed once when searching for a lobby, I dunno I guess I’m lucky for not really having many problems

10

Interesting about the “top Killers loading” bit, DrPepper. I’m going to pay attention to that and see if I notice anything on my end.

Out of curiosity, how many online matches do you usually play before exiting the game?

11

A ■■■■ load lol, anywhere between 5-9 hours of games since I have been waiting for this game to release on pc for 3 years.

12

Lucky you. For me is 1 or 2 fights and a crash. Since day one. And i cant find a fix. Sometimes my game crash, i fire up ki again, and the moment i try to search for a game, crash again.
I can play offline for hours without a single crash tho.
But multiplayer is so damn bugged for me. Still waiting for a response from the guys that should be giving support for paying customers

13

i think i may have an idea why all these crashes are happening, when did you install windows 10? because i installed windows 10 right before downloading killer instinct, maybe you have to reinstall windows 10 or something

14

I tried letting the top Killers field load before searching for matches, last night. I noticed two things:

  1. Even in between matches, it does take about 10 seconds for that field to load. Normally I hit “search” ASAP, so I miss it.

  2. KI seemed to find opponents much more quickly than usual. It was common before last night to wait over a minute for a match. Matches last night, after waiting for top Killers to load were reliably found within 10 seconds.

Might be another placebo effect, here (or other effects may be confounding the test results), but so far results are interesting. Maybe the game risks crashing if the search is executed before it has a chance to connect with KI servers.

15

yeah it may be a placebo effect but it sure does seem like it helps, and honestly the explaination you gave of it may be that you need to connect to the servers first does make a lot of sense, and loading the top killers is a good indicator for when you have finally got onto the servers

16

Happens for me as well while searching a match. Has anyone checked their system event log to see if anything shows up when it crashes. I’ll make a point to look next time it happens for myself.

17

Gonna check it on my next session

18

As i posted in the original post, i also thought that my system was unstable or something. So i made a clean and fresh install. Updated everything on drivers side and just installed ki. The game crashed righ away after 3 fights.

19

It kinds of annoys me too, the thing is that I have 2 screens on my setup, so I work on one screen while I’m looking for a match in the other, for some reason it tends to crash more while I’m doing this.

I hope this get fixed soon

20

I’ll check my event log, too. See what I see.