DonRomano 2 Posted October 28, 2018 Hey there, I have a problem with Houdini 17, after I open it and start to work it crashes. It's doing this each time I try to work. I was working on Houdini 16.5 QT4 and all was working correctly, but now that I want to test vellum and new features, I can't because Houdini isn't working. I have a MSI GL62 6QD, all my drivers are okay, I disabled Nahimic features, and I don't know what I can do to work with H17. I have i5 6300 HQ, 8 Go Ram, Gtx 950M, 1 To HDD, Windows 10 64 Bit. Share this post Link to post Share on other sites
Atom 919 Posted October 28, 2018 (edited) I would guess it is your hardware. That is a fairly low end system for Houdini. According to nVidia specs, Windows 10 is not certified for that video card. https://www.geforce.com/hardware/notebook-gpus/geforce-gtx-950m/specifications There is also this on the SideFX supported graphics card page for mobile graphics cards such as the gtx950M. Quote (OpenCL 1.2 is no longer supported with the latest driver for Fermi architecture cards.) Edited October 28, 2018 by Atom Share this post Link to post Share on other sites
pixteur 0 Posted October 28, 2018 I'm getting constant crashes too in H17. If I hit tab to lay down a node houdini crashes to desktop without any logs. Quite surprised by this! H 16.5 is fine on my rig. i7 6950X 128GB ram. 4x 1080 gpu Win 10 pro Rig mainly runs maya, Max vray and redshift. It's clean and was rebuilt a couple months ago. Used DDU and wiped my nvidea drivers. Running the latest and greatest. thoughts? Share this post Link to post Share on other sites
DonRomano 2 Posted October 28, 2018 1 hour ago, Atom said: I would guess it is your hardware. That is a fairly low end system for Houdini. According to nVidia specs, Windows 10 is not certified for that video card. https://www.geforce.com/hardware/notebook-gpus/geforce-gtx-950m/specifications There is also this on the SideFX supported graphics card page for mobile graphics cards such as the gtx950M. I just disabled Nahimic at start and it seems to work, I run a quick sim and I could work nicely. It looks like it was this thing which was in conflict with the gpu, but seems to be fixed now. 28 minutes ago, pixteur said: I'm getting constant crashes too in H17. If I hit tab to lay down a node houdini crashes to desktop without any logs. Quite surprised by this! H 16.5 is fine on my rig. i7 6950X 128GB ram. 4x 1080 gpu Win 10 pro Rig mainly runs maya, Max vray and redshift. It's clean and was rebuilt a couple months ago. Used DDU and wiped my nvidea drivers. Running the latest and greatest. thoughts? Sometimes GPU is conflicted with audio features (like Nahimic) and it makes the gpu crash. What is your motherboard ? 1 Share this post Link to post Share on other sites
pixteur 0 Posted October 28, 2018 asus rog rampage V edition 10 I have no idea what Nahimic is and or how to disable it. Share this post Link to post Share on other sites
DonRomano 2 Posted October 28, 2018 3 minutes ago, pixteur said: asus rog rampage V edition 10 I have no idea what Nahimic is and or how to disable it. Nahimic is a "audio enhancer" on MSI Laptops, and sometimes it mess with the gpu and makes Houdini crash (it tries to make sound out of the 3d space in Houdini). It may come from this, try to disable your audio enhancer and see if it works. Did you contact SideFX to fix the problem ? Never heard that from Asus stuff. Share this post Link to post Share on other sites
pixteur 0 Posted October 28, 2018 Apparently on asus those drivers are installed as well. I removed them and so far H17 is running stable. Thanks a million! Share this post Link to post Share on other sites
DonRomano 2 Posted October 28, 2018 27 minutes ago, pixteur said: Apparently on asus those drivers are installed as well. I removed them and so far H17 is running stable. Thanks a million! Glad to hear that ! I should report it to SideFX to see if they can fix it ! Share this post Link to post Share on other sites
kumpa 2 Posted November 10, 2018 Houdini 17 (both production and daily build) crashes upon opening preferences dialogue. Oddly enough, opening fairly complex scene doesn't seem to cause it to crash. This is what it says when it starts: k / opt hfs17.0.396 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 cl_get_gt_device(): error, unknown device: 0 And this is what is says when it crashes: 3737: Fatal error: Segmentation fault (sent by pid 171) Crash log saved to /tmp/houdini_temp/crash.untitled.k_3737_log.txt And this are the contents of the log: Traceback from 3737 ThreadId=0x7ff31c34bd00 AP_Interface::coreDumpChaser(UTsignalHandlerArg) <libHoudiniUI.so> AP_Interface::si_CrashHandler::chaser(UTsignalHandlerArg) <libHoudiniUI.so> signalCallback(UTsignalHandlerArg) <libHoudiniUT.so> UT_Signal::UT_ComboSignalHandler::operator()(int, siginfo_t*, void*) const <libHoudiniUT.so> UT_Signal::processSignal(int, siginfo_t*, void*) <libHoudiniUT.so> __funlockfile <libpthread.so.0> PyDict_GetItem (dictobject.c:714) _PyType_Lookup (typeobject.c:2521) _PyObject_GenericGetAttrWithDict (object.c:1389) PyEval_EvalFrameEx (ceval.c:2256) PyEval_EvalFrameEx (ceval.c:4107) gen_iternext (genobject.c:84) PyEval_EvalFrameEx (ceval.c:2497) gen_iternext (genobject.c:84) PyEval_EvalFrameEx (ceval.c:2497) PyEval_EvalCodeEx (ceval.c:3253) function_call (funcobject.c:526) PyObject_Call (abstract.c:2529) instancemethod_call (classobject.c:2602) PyObject_Call (abstract.c:2529) call_method.constprop.47 (typeobject.c:1261) PyEval_EvalFrameEx (ceval.c:1391) PyEval_EvalFrameEx (ceval.c:4107) PyEval_EvalFrameEx (ceval.c:4107) PyEval_EvalCodeEx (ceval.c:3253) PyEval_EvalFrameEx (ceval.c:4117) PyEval_EvalCodeEx (ceval.c:3253) PyEval_EvalFrameEx (ceval.c:4117) PyEval_EvalCodeEx (ceval.c:3253) PyEval_EvalFrameEx (ceval.c:4117) PyEval_EvalCodeEx (ceval.c:3253) PyEval_EvalFrameEx (ceval.c:4117) PyEval_EvalCodeEx (ceval.c:3253) PyEval_EvalFrameEx (ceval.c:4117) gen_iternext (genobject.c:84) PyEval_EvalFrameEx (ceval.c:2497) gen_iternext (genobject.c:84) PyEval_EvalFrameEx (ceval.c:2497) PyEval_EvalCodeEx (ceval.c:3253) function_call (funcobject.c:526) PyObject_Call (abstract.c:2529) PyEval_EvalFrameEx (ceval.c:4334) PyEval_EvalCodeEx (ceval.c:3253) PyEval_EvalFrameEx (ceval.c:4117) PyEval_EvalFrameEx (ceval.c:4107) PyEval_EvalCodeEx (ceval.c:3253) PyEval_EvalCode (ceval.c:667) PY_CompiledCode::evaluateUsingDicts(PY_Result::Type, void*, void*, PY_Result&) const <libHoudiniUT.so> PY_CompiledCode::evaluate(PY_Result::Type, PY_Result&) const <libHoudiniUT.so> PYrunPythonExpression(char const*, PY_Result::Type, PY_EvaluationContext*) <libHoudiniUT.so> PYrunPythonExpressionAndExpectNoErrors(char const*, PY_Result::Type, char const*, PY_EvaluationContext*) <libHoudiniUT.so> PYrunPythonExpressionOfExactType(char const*, PY_Result::Type, PY_Result&, char const*, char const*, PY_EvaluationContext*) <libHoudiniUT.so> BR_HelpManager::runPythonExpr(char const*, PY_Result::Type, PY_Result&) <libHoudiniUI.so> BR_HelpManager::evalPythonExpr(char const*, UT_String&) <libHoudiniUI.so> BR_HelpManager::getHelpCardURL(char const*, UT_String&) <libHoudiniUI.so> FUSE_PrefDialog::handlePageChange(UI_Event*) <libHoudiniAPPS3.so> UI_Queue::processNextEvent() <libHoudiniUI.so> UI_Queue::drain() <libHoudiniUI.so> UI_Queue::eventLoop() <libHoudiniUI.so> main <libHoudiniUI.so> __libc_start_main <libc.so.6> main <houdinifx-bin> Fedora Core 29 NVIDIA Driver Version: 410.73 Anyone experiencing same issue ? Share this post Link to post Share on other sites
bavarianbasti 0 Posted November 22, 2018 kumpa, I am getting a similar error. Did you ever find a solution? Share this post Link to post Share on other sites
Activate 42 Posted November 24, 2018 Since Windows updated to 1809, Houdini 17.0.352 is constantly crashing for me as well. Seems to be UI related. Latest NVidia driver. OpenCL in Houdini no longer recognizes my GPUs anymore either. Houdini Version 17.0.352 [windows-x86_64-cl19.15] Uptime 165 seconds Sat Nov 24 15:42:51 2018 Caught signal 11 Traceback from 7632 ThreadId=0x00004df0 CURRENT THREAD 19952 +0x163bd19c [GA_Attribute::getStorageClass] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGA.dll +0x163c0645 [GA_Attribute::needsTransform] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGA.dll +0x1c20dfd1 [GT_GEOElementArray::getTypeInfo] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGT.dll +0x06cd0695 [GR_GeoRender::fillGeoAttribs] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGR.dll +0x06ccfbb9 [GR_GeoRender::fillAttributesGL3] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGR.dll +0x06ce77a8 [GR_PolySurfaceGL3::buildSurfaceAttributes] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGR.dll +0x06ce7a88 [GR_PolySurfaceGL3::buildVertexAttributes] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGR.dll +0x06ce438c [GR_PolySurface::update] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGR.dll +0x06ca993a [GR_PolyCurveGL3::supportsInstances] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGR.dll+0x06c81874 [GR_Primitive::updatePrim] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGR.dll +0x06c9c025 [GR_PrimPacked::updateInstanceGeometry] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGR.dll+0x06c9b6d7 [GR_PrimPacked::update] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGR.dll +0x06c8fba9 [GR_PrimFragments::update] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGR.dll +0x06c81874 [GR_Primitive::updatePrim] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGR.dll +0x06ab936d [GUI_GeoRender::updatePrimitives] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGUI.dll +0x06ab6d5b [GUI_GeoRender::update] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGUI.dll +0x06a8a403 [GUI_DetailLook::updateForRender] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libGUI.dll +0x06959bd6 [DM_VPortAgent::setupGeometry] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libDM.dll +0x06955dc7 [DM_VPortAgent::renderViewport] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libDM.dll +0x06945b1a [DM_VPortAgent::doRender] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libDM.dll +0x0691d8fd [DM_Viewport::doRender] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libDM.dll +0x055e93f4 [UI_Feel::renderMe] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x055e3f21 [UI_Feel::doRenderKids] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x055e3e00 [UI_Feel::doRender] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x055e93f4 [UI_Feel::renderMe] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x055e3f21 [UI_Feel::doRenderKids] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x055e3e00 [UI_Feel::doRender] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x056eccf2 [UI_Viewport::reRender] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x056f38c7 [UI_Window::renderChildViews] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x056f0737 [UI_Window::doRedrawSubclass] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll+0x0691331d [DM_ViewLayout::doMakeTriple] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libDM.dll +0x056f306e [UI_Window::redrawRequest] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x056923c8 [UI_Queue::doWindowRedraws] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x056d3775 [UI_Timer::handleEvent] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x0566cb78 [UI_Manager::handleEvent] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x05694724 [UI_Queue::processNextEvent] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll+0x056924e9 [UI_Queue::drain] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x05692878 [UI_Queue::eventLoop] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libUI.dll +0x0542c7f0 [AP_Interface::loadWindowGeometry] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libSI.dll +0x0542d25d [myWinMain] C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\libSI.dll+0x40001b9a C:\Program Files\Side Effects Software\Houdini 17.0.352\bin\hindie.exe +0x7df67e94 [BaseThreadInitThunk] C:\WINDOWS\System32\KERNEL32.DLL +0x806f7ad1 [RtlUserThreadStart] C:\WINDOWS\SYSTEM32\ntdll.dll Share this post Link to post Share on other sites
kumpa 2 Posted November 28, 2018 On 22/11/2018 at 7:31 PM, bavarianbasti said: kumpa, I am getting a similar error. Did you ever find a solution? Hey, sorry for late reply. Unfortunately I didn't, since it is my home computer I didn't bother too much. All I do is to apply all the updates to the system and hope for the best. I have no issues with it at work (Fedora 26). I am by no means a linux expert but I somewhat suspect latest nvidia driver to be the culprit ( 410.73 ). Share this post Link to post Share on other sites
Atom 919 Posted November 28, 2018 Try dialing back your over clocking rates. Signal 11 is about a 50% chance it's a hardware problem. Share this post Link to post Share on other sites
kumpa 2 Posted November 28, 2018 Interesting. I did notice some odd artefacts in houdini and slack (!) but games seem to work just fine. Card is gf 1060 and I haven't meddled with it in any way. Thank you for the tip Share this post Link to post Share on other sites
AngelAnima 0 Posted January 4 Hi, I´m having a similiar problem, after working for a few seconds Houdini freezes and doesn´t respond. Tested with production and daily build. How can I get a log to see what the problem is? Using Houdini 17.0416 Aprrentice System OS: Windows 10 Pro Version: 10.0.17763 Processor: AMD FX 8350 MB: M5A99X EVO R2.0 Rev 1.xx RAM: 8 GB Video Card: ATI FirePro V4900 Catalyst Control Center: 2015.1104.1643.30033 Direct3D 9.14.10.01128 OpenGL 6.14.10.13399 Share this post Link to post Share on other sites
Activate 42 Posted January 5 Houdini should tell you where it saves the crash logs. For me, they show up in C:/Users/<username>/AppData/Local/Temp/houdini_temp/. If you are lucky you can also find a saved version of your HIP file in there. Share this post Link to post Share on other sites
Atom 919 Posted January 5 @AngelAnima From your posted specs, your computer hardware does not meet the minimum requirements to run Houdini. https://www.sidefx.com/Support/system-requirements/ Share this post Link to post Share on other sites
Dome1812 0 Posted January 27 On 28.10.2018 at 4:31 PM, DonRomano said: Nahimic is a "audio enhancer" on MSI Laptops, and sometimes it mess with the gpu and makes Houdini crash (it tries to make sound out of the 3d space in Houdini). It may come from this, try to disable your audio enhancer and see if it works. Did you contact SideFX to fix the problem ? Never heard that from Asus stuff. I just created an account here, to confirm this issue with my MSI G63 stealth thin. I had continously crashes after minutes, using Houdini, without any warning. I am using Houdini H17 and keep updating it to the dayly build but nothing worked. After deleting the Nahimic driver, I can use Housini for hours without any crashes so far. Thank you very much for you information DonRomano, it was very frustrating suffering from this crashes for weeks now. Share this post Link to post Share on other sites
