Store Page
FaceRig
All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

FaceRig

Store Page
View Stats:
Global Achievements
FaceRig > Bugs & Troubleshooting > Topic Details
jmarsella09 13 Sep, 2020 @ 6:18am
Crash on first boot
Just downloaded Facerig and it crashes on startup

Vplog: https://pastebin.com/Cc1kjJjq

installscript_log.txt fil : This file is not in my Steam logs folder so I'm at a loss.

dxdiag info: https://pastebin.com/VytCUAQG

I get this message when I start the program

STACK DUMP saved in
C:\Program Files (x86)\Steam\steamapps\common\FaceRig\Bin\FaceRig_stack_2020-09-13_22-17-10.dmp

EXCEPTION: Access violation while 'writting to' address 0x0 at address 0x784c84e3
SegGs=0x2b SegFs=0x53 SegEs=0x2b SegDs=0x2b
Edi=0x0 Esi=0x158c234 Ebx=0x0
Edx=0x16 Ecx=0x52c5 Eax=0x5
Ebp=0x158c230 Eip=0x784c84e3 SegCs=0x23
EFlags=0x10206 Esp=0x158c1a8 SegSs=0x2b
Dr0=0x0 Dr1=0x0 Dr2=0x0
Dr3=0x0 Dr7=0x0 Dr7=0x0


SymInit: Symbol-SearchPath: 'C:\PROGRAM FILES (X86)\STEAM\STEAMAPPS\COMMON\FACERIG\BIN\;.;C:\Program Files (x86)\Steam\steamapps\common\FaceRig;C:\Program Files (x86)\Steam\steamapps\common\FaceRig\Bin;C:\WINDOWS;C:\WINDOWS\system32;', symOptions: 210, UserName: 'JMars'
DbgHelpPath: 'C:\WINDOWS\SYSTEM32\DbgHelp.dll'
DbgHelpVersion: '6.2.0'
OS-Version: 6.2.9200 () 0x300-0x1

---CallStack---
784C84E3 (EngineDll10): (filename not available): public: virtual void __thiscall cRenderDX11::ApplyPostProcessing(void)
784C9261 (EngineDll10): (filename not available): public: virtual void __thiscall cRenderDX11::UpdateAmbientCubeTex(struct ID3D11DeviceContext *,struct tColor const *,struct ID3D11Resource *,int,int)
784C87FE (EngineDll10): (filename not available): public: virtual void __thiscall cRenderDX11::UpdateAmbientCubeTex(struct tColor const *,char const *)
7831DC83 (EngineDll10): (filename not available): public: void __thiscall cLightEngine::SetAmbientCube(struct tColor const *)
0040C6C7 (FaceRig): (filename not available): (function-name not available)
00414320 (FaceRig): (filename not available): (function-name not available)
004769CC (FaceRig): (filename not available): (function-name not available)
003FE59D (FaceRig): (filename not available): (function-name not available)
00589B62 (FaceRig): (filename not available): (function-name not available)
76C1F989 (KERNEL32): (filename not available): BaseThreadInitThunk
776274A4 (ntdll): (filename not available): RtlGetAppContainerNamedObjectPath
77627474 (ntdll): (filename not available): RtlGetAppContainerNamedObjectPath
< >
Showing 1-6 of 6 comments
Adina_Animaze  [developer] 15 Sep, 2020 @ 6:44am 
Hello,
due to GDPR restrictions, it would be better if you delete the VP.log and dxdiag from here and send them to us at info[at]facerig[dot]com
#1
david_animaze  [developer] 16 Sep, 2020 @ 4:36am 
Make sure that your video card drivers are up to date and that you're also running FaceRig on DX9 (bypass the Launcher when you start FaceRig). Let me know how it goes.
#2
jmarsella09 18 Sep, 2020 @ 8:39pm 
Originally posted by Aty:
Hello,
due to GDPR restrictions, it would be better if you delete the VP.log and dxdiag from here and send them to us at info[at]facerig[dot]com

I sent an email at the same time I posted this comment but have yet to get a response on that end. I will resend it to be sure.
#3
jmarsella09 18 Sep, 2020 @ 8:49pm 
Originally posted by david_facerig:
Make sure that your video card drivers are up to date and that you're also running FaceRig on DX9 (bypass the Launcher when you start FaceRig). Let me know how it goes.


My video card drivers appear to be up to date. And putting it in DX9 just results in it being stuck on a black screen.
#4
Sazzaj  [developer] 26 Sep, 2020 @ 6:28am 
Hi,

Chiming in for a more technical response. The problem we see in the app's log is that the rendering engine cannot allocate enough video memory, hence the [SYSTEM ] ERROR: Failed to map temp texure (error: 0x8007000e) (DX11) on the last line, which is a DirectX error.

Historically we found that this 0x8007000e (code for Out of Memory) error is caused by some faulty drivers, especially on AMD video cards, that is why David suggested updating the video card drivers, and unfortunately it's the only solution. Also, judging by the dxdiag you posted, the AMD driver date is 8/6/2015. I'm not sure if there aren't any newer versions, but the drivers or the video card are still at fault.

I would try workaround, go to whatever AMD control video control panel (not sure what software suite you have) and force FaceRig to run on the Intel(R) HD Graphics 530 video card that is also available on your system. See if that helps.
#5
jmarsella09 27 Sep, 2020 @ 12:41am 
Originally posted by Sazzaj:
Hi,

Chiming in for a more technical response. The problem we see in the app's log is that the rendering engine cannot allocate enough video memory, hence the [SYSTEM ] ERROR: Failed to map temp texure (error: 0x8007000e) (DX11) on the last line, which is a DirectX error.

Historically we found that this 0x8007000e (code for Out of Memory) error is caused by some faulty drivers, especially on AMD video cards, that is why David suggested updating the video card drivers, and unfortunately it's the only solution. Also, judging by the dxdiag you posted, the AMD driver date is 8/6/2015. I'm not sure if there aren't any newer versions, but the drivers or the video card are still at fault.

I would try workaround, go to whatever AMD control video control panel (not sure what software suite you have) and force FaceRig to run on the Intel(R) HD Graphics 530 video card that is also available on your system. See if that helps.

Thank you for the response.
I figured it might be a system problem on my end. My drivers are telling me they are up to date so I might be outta luck. My computer is a few years old and it might just not be able to run Facerig.
#6
< >
Showing 1-6 of 6 comments
Per page: 1530 50

FaceRig > Bugs & Troubleshooting > Topic Details
Date Posted: 13 Sep, 2020 @ 6:18am
Posts: 6

Discussions Rules and Guidelines