Vortex not starting

[BigBizkit]

Dumps folder is empty. No errors in the background. Can't attach vortex.log here, is there another place I should send it?

Click the three dots in the top right corner and select "Send Feedback".

 

Enter a descriptive title and pertinent information.

 

At the bottom, click on "Attach Special File" and select "Vortex Log".

 

After that, just hit "Submit Feedback" in the bottom right corner.

 

[Sacrifyx]

Might just be going blind but I can't find 3 dots in the upper right corner nor any menu option that points to 'Send Feedback'.

[HadToRegister]

Might just be going blind but I can't find 3 dots in the upper right corner nor any menu option that points to 'Send Feedback'.

 

[jackpie]

If it helps, I just downloaded 0.16.9 from Github and it has the same crash (event ID 1000):

 

Faulting application name: Vortex.exe, version: 0.16.9.0, time stamp: 0x5ba21cdf

Faulting module name: KERNELBASE.dll, version: 10.0.17134.319, time stamp: 0x1e206b26

Exception code: 0xe06d7363

Fault offset: 0x000000000003a388

Faulting process id: 0x4470

Faulting application start time: 0x01d46bf486c2dd00

Faulting application path: C:\Program Files\Black Tree Gaming Ltd\Vortex\Vortex.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report Id: d69bae02-6fcb-453b-8b60-24eaaceb6855

Faulting package full name:

Faulting package-relative application ID:

So the issue was introduced between 0.16.8 and 0.16.9. Hopefully this would narrow it down a bit?

[jackpie]

And Windows error report when 0.16.10 crashed:

 

Version=1
EventType=APPCRASH
EventTime=131849005912076051
ReportType=2
Consent=1
UploadTime=131849005914683161
ReportStatus=268435456
ReportIdentifier=0427d330-a790-4ca2-a05a-f0c76233e011
IntegratorReportIdentifier=7a62b42c-7954-4a90-bd98-05cca67564b1
Wow64Host=34404
NsAppName=Vortex.exe
AppSessionGuid=0000416c-0001-0028-7279-9de8f86bd401
TargetAppId=W:0006974a3aacf1aa3b2cc6da1f4d59e585fd00000904!00009e44cb841df4bade8734e8fe42aede7155398a42!Vortex.exe
TargetAppVer=2018//09//19:09:54:39!408f90b!Vortex.exe
BootId=4294967295
TargetAsId=3426
IsFatal=1
Response.BucketId=d77b93f7071ef822c721dd3f5aa893eb
Response.BucketTable=4
Response.LegacyBucketId=1666856601277469675
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Vortex.exe
Sig[1].Name=Application Version
Sig[1].Value=0.16.10.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5ba21cdf
Sig[3].Name=Fault Module Name
Sig[3].Value=KERNELBASE.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.17134.319
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=1e206b26
Sig[6].Name=Exception Code
Sig[6].Value=e06d7363
Sig[7].Name=Exception Offset
Sig[7].Value=000000000003a388
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.17134.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=aa19
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=aa190c0f3a2f41a373e46a511ee43f45
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=bfcc
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=bfccbc352f6e665286eec533601d3c31
UI[2]=C:\Program Files\Black Tree Gaming Ltd\Vortex\Vortex.exe
LoadedModule[0]=C:\Program Files\Black Tree Gaming Ltd\Vortex\Vortex.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\COMDLG32.dll
LoadedModule[5]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.17134.345_none_fb429a5930656358\COMCTL32.dll
LoadedModule[6]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[7]=C:\WINDOWS\System32\combase.dll
LoadedModule[8]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[9]=C:\WINDOWS\System32\shcore.dll
LoadedModule[10]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[11]=C:\WINDOWS\System32\USER32.dll
LoadedModule[12]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[13]=C:\WINDOWS\System32\win32u.dll
LoadedModule[14]=C:\Program Files\Black Tree Gaming Ltd\Vortex\node.dll
LoadedModule[15]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[16]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[17]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[18]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[19]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[20]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[21]=C:\WINDOWS\System32\PSAPI.DLL
LoadedModule[22]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[23]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[24]=C:\WINDOWS\System32\sechost.dll
LoadedModule[25]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[26]=C:\Program Files\Black Tree Gaming Ltd\Vortex\VCRUNTIME140.dll
LoadedModule[27]=C:\Program Files\Black Tree Gaming Ltd\Vortex\MSVCP140.dll
LoadedModule[28]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[29]=C:\WINDOWS\System32\profapi.dll
LoadedModule[30]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[31]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[34]=C:\WINDOWS\System32\FLTLIB.DLL
LoadedModule[35]=C:\WINDOWS\System32\ole32.dll
LoadedModule[36]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\winmmbase.dll
LoadedModule[38]=C:\WINDOWS\System32\IMM32.dll
LoadedModule[39]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\UIAutomationCore.DLL
LoadedModule[41]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[42]=C:\Program Files\Black Tree Gaming Ltd\Vortex\ffmpeg.dll
LoadedModule[43]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\USP10.dll
LoadedModule[45]=C:\WINDOWS\SYSTEM32\dbghelp.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\ncrypt.dll
LoadedModule[48]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[49]=C:\WINDOWS\SYSTEM32\DWrite.dll
LoadedModule[50]=C:\WINDOWS\SYSTEM32\MSIMG32.dll
LoadedModule[51]=C:\WINDOWS\SYSTEM32\UxTheme.dll
LoadedModule[52]=C:\WINDOWS\SYSTEM32\OLEACC.dll
LoadedModule[53]=C:\WINDOWS\SYSTEM32\NTASN1.dll
LoadedModule[54]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[55]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[56]=C:\WINDOWS\SYSTEM32\CRYPTBASE.DLL
LoadedModule[57]=C:\WINDOWS\system32\mswsock.dll
LoadedModule[58]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule[59]=C:\WINDOWS\System32\NSI.dll
LoadedModule[60]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[61]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
LoadedModule[62]=C:\WINDOWS\SYSTEM32\WINNSI.DLL
LoadedModule[63]=C:\WINDOWS\system32\napinsp.dll
LoadedModule[64]=C:\WINDOWS\system32\pnrpnsp.dll
LoadedModule[65]=C:\WINDOWS\system32\NLAapi.dll
LoadedModule[66]=C:\WINDOWS\System32\winrnr.dll
LoadedModule[67]=C:\WINDOWS\System32\wshbth.dll
LoadedModule[68]=\\?\C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\node_modules\winapi-bindings\build\Release\winapi.node
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=17134
OsInfo[3].Key=ubr
OsInfo[3].Value=345
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=39
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=200056
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.345.17134.0-11.0.90
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16286
OsInfo[19].Key=svolsz
OsInfo[19].Value=1849
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=180410
OsInfo[22].Key=bldtm
OsInfo[22].Value=1804
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs4_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.17134.345.amd64fre.rs4_release.180410-1804
OsInfo[30].Key=buildflightid
OsInfo[30].Value=7B3F085B-AF94-4576-9A9C-9A5E41CD1FC9.1
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=RS:17A7
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Vortex
AppPath=C:\Program Files\Black Tree Gaming Ltd\Vortex\Vortex.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=D4973364906DF8EE6CAEEC1733CA236A
MetadataHash=-1989981019

[jackpie]

Based on what WER showed, that winapi.node was the last module loaded before it crashed (makes sense since it likely provides API to KernelBase.dll), I managed to workaround the issue by following these steps:

 

 

1. Install 0.16.8

2. Copy C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\node_modules\winapi-bindings\build\Release\winapi.node to a different location

3. Upgrade to 0.16.10

4. Replace C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\node_modules\winapi-bindings\build\Release\winapi.node with the saved one from 0.16.8

 

After that I was able to launch 0.16.10. Not sure if there are any other issues but so far it seems working fine.

 

@Tannin42, since you also maintain winapi-bindings, it should be useful to provide my Windows version information to help you debug:

 

Windows 10 Pro, version 1803 (build 17134.345)

[Katarsi]

Based on what WER showed, that winapi.node was the last module loaded before it crashed (makes sense since it likely provides API to KernelBase.dll), I managed to workaround the issue by following these steps:

 

 

1. Install 0.16.8

2. Copy C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\node_modules\winapi-bindings\build\Release\winapi.node to a different location

3. Upgrade to 0.16.10

4. Replace C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\node_modules\winapi-bindings\build\Release\winapi.node with the saved one from 0.16.8

 

After that I was able to launch 0.16.10. Not sure if there are any other issues but so far it seems working fine.

 

@Tannin42, since you also maintain winapi-bindings, it should be useful to provide my Windows version information to help you debug:

 

Windows 10 Pro, version 1803 (build 17134.345)

 

I tried doing this. And Vortex indeed launched. And I was greeted with a bright red screen saying "failed to render". Not recommendable, to say the least.

[Tannin42]

Is the entire screen red or do you have the navigation bar on the left? If so (which I assume) you should be able to solve that by going to settings->Interface and there disable the "ToDo List".

 

I believe the error is caused by the winapi library reporting an error (*) but instead of stopping it goes on to cause a follow-up error that is _not_ handled.

 

Replacing winapi may work - it will produce errors in the background but those are mostly handled silently, except for the ones Katarsi is seeing because 0.16.10 uses functions from winapi.node that the old version doesn't have at all.

 

(*) Now the cause of this error is not clear yet, but it may be minor. It's almost certainly related to a problem accessing the registry. Vortex tries to check the registry to find games as well as determine if/where steam is installed. It is able to deal with stuff being missing so I'm not sure what the error here is. Might be an odd permission setup in the registry or something like that. Any idea if you have done something "unusual" with your registry? I know it's a very open question but since this original error isn't reported I know very little about what's causing it.

[jackpie]

...

(*) Now the cause of this error is not clear yet, but it may be minor. It's almost certainly related to a problem accessing the registry. Vortex tries to check the registry to find games as well as determine if/where steam is installed. It is able to deal with stuff being missing so I'm not sure what the error here is. Might be an odd permission setup in the registry or something like that. Any idea if you have done something "unusual" with your registry? I know it's a very open question but since this original error isn't reported I know very little about what's causing it.

No, I don't recall I messed with registry at all. IIRC, in a normal startup game detection happens after Vortex logs startup message (need to check log when I get back home), but when it failed with 0.16.9/10, there was nothing logged at all, so I am not sure if it got that far when the crash happened.

 

[Edit] I think you are right. I tried 0.16.8 with winapi.node from 0.16.9 and it still worked, so it is almost certain the cause is in one of the 4 new registry methods introduced in winapi-bindings 1.3.0.

[Beowulf6666]

i have the same issue...i downloaded vortex...installed it....after which i tried to run the app and nothing happend

 

i checked with bitdefender to make sure its not being blocked....its not

i checked the process manager...i see it starting up and closing right away

 

so i checked the event viewer...this is what i got:

 

Faulting application name: Vortex.exe, version: 0.16.10.0, time stamp: 0x5ba21cdf

Faulting module name: KERNELBASE.dll, version: 10.0.17134.319, time stamp: 0x1e206b26

Exception code: 0xe06d7363

Fault offset: 0x000000000003a388

Faulting process id: 0x35b0

Faulting application start time: 0x01d46cbd96a3c1a6

Faulting application path: C:\Program Files\Black Tree Gaming Ltd\Vortex\Vortex.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report Id: a770f81e-d5ec-47c5-8376-958ffacfd54d

Faulting package full name:

Faulting package-relative application ID:

i have reinstalled the app twice...still same issue same crash...hope this helps u guys troubleshoot

i was really looking forward to using this